Mac Programmer help required - Can pay if necessary.

[C Heat]

I'm trying to figure out how a Plug-in resource is 'packaged'.

I've Googled for hours and can't seem to find what I'm looking for. It's probably the 'terminology' I'm using to find what I'm looking for

I've worked out that I can Unstuff the 'package' to show it's contents, but the source file has it's own file name extention. It's not .zip or .sea etc. And it's not a Package because it does not allow 'Show Package Contents' option...

It appears that when this file is 'accessed' by the Plugin it automatically self extracts to allow the app to view the included image Resource and XML file.

If anyone can help me work out how to 'package' a similar file could you please PM me?

I'd really appreciate the assistance.

I'm (reasonably) prepared to pay for your time and expertise.

Thank you.

[C Heat]

Bump

[colinmiller]

Do you have the Apple Developer kit? It has programs for packaging up these things.

Generally applications are just folders with the executable and resource files in it. For applications its .app and for components its .component. But again the developer kit has all the tools and instructions for this stuff.

OH and they even have step by step instructions for writing plugins while having you make an example plugin in the process.

[C Heat]

Thanks Colin.

I am aware of the Apple resources available. I'm just a little stumped however — the file extention is not .app .scrpt .sea .pkg etc. etc.

It's proprietary in looks and name...



I'm sure it's something very simple — once I know what it is and how it's created.

It just looks like a whole 'secret secret' type of crowd. Maybe I need a special password to get 'in'.

[colinmiller]

Are you perhaps referring to the rsrc reserource file in the package that contains all the images and stuff? It used to be Resedit, but I don't think there is an OS X version. I think there is a shareware app that can de-compile them, but I don't remember the name.

[C Heat]

It's funny, it's not actually a package.

It's one file. I can Unstuff it, and then there is one folder containing images and an XML file only.

I'll have a search for de-compile :)

Thanks Colin. I appreciate you efforts.

[docbop]

Originally Posted by C Heat

Thanks Colin.

I am aware of the Apple resources available. I'm just a little stumped however — the file extention is not .app .scrpt .sea .pkg etc. etc.

It's proprietary in looks and name...



I'm sure it's something very simple — once I know what it is and how it's created.

It just looks like a whole 'secret secret' type of crowd. Maybe I need a special password to get 'in'.

Remember OS X is Unix under the hood. In Unix everything is a file and it will attempt to execute any file, it doesn't care about extensions.

[C Heat]

Originally Posted by docbop

Remember OS X is Unix under the hood. In Unix everything is a file and it will attempt to execute any file, it doesn't care about extensions.

Ok wow. That's some good info there. Thanks docbop.

So now I can name the file anything. Cool. I renamed the folder...

But.

NOW, the problem remains that I need to make a Folder 'one file'. So when you click on it it doesn't show all contents, so the contents are invisisble.

I think I may need to compile it somehow.

[colinmiller]

the way it works is inside the package is the MacOS section which holds the actual plugin file. This can't be opened, it's compiled binary code. Then there is the resource folder which holds the RSRC files which hold things like images and data used by the plugin. This file you may be able to decompile with an app like you used to with Resedit in OS 9. Its basically the resource fork equiv in OS X.

[Fredrik]

AFAIK there is no need for res edit in os X, since you can see the contents of a executable pkg by right clicking. The resource file (graphics and sounds etc) can be viewed directly in the pkg but the source code have already been compiled so it will be a binary file. I think a decompiler is not going to decompile back to the original form 100%, somthings will get lost AFAIK.


BTW I´m not a programmer.

[C Heat]

FWIW I think I'll just place a job listing online somewhere in the Mac developer community and get this sorted.

I'm sure it's literally a 1hr job.

Just gotta know the 'what' and 'how's'...

[Fredrik]

Isn´t there a template for plugins in Xcode? I´d guess that you would get a working plugin file when you build it in Xcode. If you build a cocoa app in Xcode you get a executable .app file atleast.

[colinmiller]

Originally Posted by Fredrik

Isn´t there a template for plugins in Xcode? I´d guess that you would get a working plugin file when you build it in Xcode. If you build a cocoa app in Xcode you get a executable .app file atleast.

Yes it does. And it's very easy. I have even made plugins using it. Xcode has all the package management tools built in. But to backwards engineer it, de-compiling would be needed. The actual plugin is a binary file and doesn't need an extension, and the resources are compiled into a resource file.

For a simple AU plugin though you don't need any resources and thus no need for a package since it's jsut using aqua components for the interface. In that case I think the plugin is jsut compiled as pluginname.component. And that also means you won't have any kind of icon for the plugin, just the generic one since the icon would be stored in the package.

[Fredrik]

Originally Posted by colinmiller

Yes it does. And it's very easy. I have even made plugins using it. Xcode has all the package management tools built in. But to backwards engineer it, de-compiling would be needed. The actual plugin is a binary file and doesn't need an extension, and the resources are compiled into a resource file.

For a simple AU plugin though you don't need any resources and thus no need for a package since it's jsut using aqua components for the interface. In that case I think the plugin is jsut compiled as pluginname.component. And that also means you won't have any kind of icon for the plugin, just the generic one since the icon would be stored in the package.

Ok, I guess I was confused by C Heat´s question. I thought he wanted to know how to get everything packaged into one file.

[ElMosca]

Originally Posted by C Heat

FWIW I think I'll just place a job listing online somewhere in the Mac developer community and get this sorted.

I'm sure it's literally a 1hr job.

This is the equivalent of people calling your studio wanting to "book 10 minutes because their song is six minutes long"....there are entire threads in gearslutz.com decrying this kind of behavior.

I wish you good luck finding help, but I must advise you that what you're proposing is probably not very appealing to the Mac developer community (i.e. a one-hour engagement).

Try to hook up with a local expert (not necessarily a programmer) who can show you insides the Mac OS X. Read a bunch of books on Mac OS X internals and Unix command line tools. You'll be glad you did.

Best,
++aldo

[C Heat]

Originally Posted by ElMosca

This is the equivalent of people calling your studio wanting to "book 10 minutes because their song is six minutes long"....there are entire threads in gearslutz.com decrying this kind of behavior.

I wish you good luck finding help, but I must advise you that what you're proposing is probably not very appealing to the Mac developer community (i.e. a one-hour engagement).

Try to hook up with a local expert (not necessarily a programmer) who can show you insides the Mac OS X. Read a bunch of books on Mac OS X internals and Unix command line tools. You'll be glad you did.

Best,
++aldo

I'd be happy to pay for 4 hours if it was a one hour job.

If it was a five minute job, I'd be happy to pay 4 hours.

Whatever.

I am researching as much as I can and will endeavor to do so.

Thanks.

[C Heat]

Originally Posted by colinmiller

For a simple AU plugin though you don't need any resources and thus no need for a package since it's jsut using aqua components for the interface. In that case I think the plugin is jsut compiled as pluginname.component. And that also means you won't have any kind of icon for the plugin, just the generic one since the icon would be stored in the package.

Very close Colin

1. It's not a package.

2. It has no icon.

So in order to create a 'pluginname.component' I'll need Xcode?

Thanks again

[Fredrik]

Originally Posted by C Heat

Very close Colin

1. It's not a package.

2. It has no icon.

So in order to create a 'pluginname.component' I'll need Xcode?

Thanks again

Xcode is included on the os X install disc.

[C Heat]

Originally Posted by Fredrik

Xcode is included on the os X install disc.

Thanks Fredrik.

[colinmiller]

Originally Posted by C Heat

Very close Colin

1. It's not a package.

2. It has no icon.

So in order to create a 'pluginname.component' I'll need Xcode?

Thanks again

It depends. If you add your own graphics or want to have a custom icon for the plugin, then you must make it a package. If you are just using the aqua resources which are in the system already, then you don't need a package. The plugins made through the xcode tutorial don't us any resources so they aren't packages. But if you look at most comercial ones, they are packages because whoever made them wanted custom graphics and icons.

I don't think you *need* xcode per say, but it has all the tools built in to make it a lot easier. I'm sure technically you could do it with textedit and gcc, but I am far from savy enough to figure that out. Xcode has all the little apps that help package things up, create icons, and has startin examples that you can use as a starting point or template to create your own.

Someone mentioned its on the install CD, but I recomend signing up on Apples site as a developer because you're gonna end up having to re-download the latest version of xcode anyways so its just an extra step to install off the CD. There's no fee or anything to sign up as a developer, and it gives you access to tons of resource libraries/help files, and forums with other developers. So you can ask questions on the developer forums and get really good answers instead of asking us boobs on gearslutz (joking!).

Or maybe PM steve massey since I think hes now writing his plugins for AU. And hes a real programmer, unlike me.

[C Heat]

Thanks Colin.

You rock. Really.

I appreciate your time and efforts

I'll sign up at Apple and get cracking

[C Heat]

Bump.

Any X Code developers out there?

I think I need to make a 'Document Bundle', but man, too many 000's for my brain to take.

I can design, I need someone to deploy.

Thanks.