🚀 go-pugleaf

In article <3ef5816a.0303101556.791b372b@posting.google.com>, Brian
Hannan <bhannan@mac.com> wrote:

> I too want to use CW for Cocoa Java development.  I have a bunch of
> existing code in Java but don't wish to proxy it in Objective-C or
> learn another SmallTalk variant.  Or use ProjectBuilder.  Essentially,
> I want to develop a non-Swing GUI for MacOS X to make it more MacOS X
> sexy.
> 
> So I played around with ProjectBuilder to see what I could get. 
> Basically, I can develop and build in CodeWarrior, but use
> ProjectBuilder to package and debug the Coca side.
> 
> Here's an overview of what I got to work.  All this assumes CW Pro
> 8.3, ProjectBuilder 2.1 December 2002 Dev Tools, MacOS 10.2.3 and JDK
> 1.4 Preview Release 10.
> 
> What I do is develop in CodeWarrior and include the classes in
> /System/Library/Java in my CW project (but prevent those classes from
> being merged into the target JAR I build).
> 
> In ProjectBuilder, I make a Cocoa Java project, remove all Java code
> and import my CW produced JAR into the project.  Then I added an extra
> build phase to to copy the JAR I produced with CW into the Java
> resources, and remove the JAR produced by ProjectBuilder.
> 
> That works for me.  I develop and build in CW.   When I want to bundle
> the MacOS X app I build in Project Builder.  If I point Project
> Builder at my source files dir, I can also debug the Coca app as well
> from Project Builder.  I'm sure there's a way to get the debug side to
> work from CW, just using a Pure Java solution and calling
> NSApplication correctly, but I didn't figure that out yet.
> 
> Actually, you could skip Project Builder.  Essentially it produces a
> small binary from the Objective-C stub in the main.m you'll see in
> your Cocoa Java project.  I can take this produced binary from one
> MacOS X app package and use it with another jar and set of resoruces I
> produce.  So it shouldn't be hard to write a Perl or Shell script to
> do the packaging without ProjectBuilder, and have that script called
> from CodeWarrior.
> 
> Anyways, hope this helps.  If you think this is all too confusing then
> perhaps use ProjectBuilder.  However, once you set this all up, it's
> easy to do for any number of Java Cocoa apps you have, and easy to
> run.  And if you really love the CW dev tools like I do, then being to
> use those alone will save you time over using ProjectBuilder.
> 
> Cheers.

Jar Bundler from the Dec deb tools package is what I use to take the CW
generated jar and pop out a .app package. Check it out.