RE: inherited neglected site, what to do first?
RE: inherited neglected site, what to do first?
- Subject: RE: inherited neglected site, what to do first?
- From: "Bruce Fancher" <email@hidden>
- Date: Sat, 21 Jul 2007 16:53:30 -0400
Markus, this Steve Quirk guy is a dangerous lunatic, so don't listen to him.
It's perfectly OK to use WOBuilder.
Bruce
-----Original Message-----
From: webobjects-dev-bounces+bruce=email@hidden
[mailto:webobjects-dev-bounces+bruce=email@hidden] On
Behalf Of Steve Quirk
Sent: Saturday, July 21, 2007 1:25 PM
To: Markus
Cc: email@hidden
Subject: Re: inherited neglected site, what to do first?
On Fri, 20 Jul 2007, Markus wrote:
> Hello,
>
> I inherited a WebObjects based site. I could use some hints and
> guidance. It looks like this community is alive and thriving. So
> that's a positive sign. :)
>
> I've been making modifications to the ".wo"
> collections inside a WOApp. (i.e. the html file and the .wod file).
> Sometimes my mods break the functionality (such as when a Javascript
> menu is generated from somewhere dynamically), but other times I can
> make modes in the PageName.wo directory with negative consequence.
>
> Can anyone suggest what docs I should read, initially, to get a handle
> on this web application?
>
> I'd like to re-claim administrative and programmatic control, as it is
> simply been hacked on here and there. BTW, Is there a "main crank" to
> turn somewhere in WebObjects (i.e. to produce a new build with new
> binaries)?
>
> If I slurp it all into a XCode (or Eclipse) project, any tips on what
> to configure where? (and how?)
Without knowing how large the app is (how many components, how many
databases/tables, does it depend on external packages without java api's,
...) it's nearly impossible to give too much direction, but...
(1) port it to java. WebObjects 5.x ships with some conversion tools that
are adequate.
You're going to run into the biggest hassles cleaning up the EOModel
(type's
will change) and there will be a bunch of source code turds to clean up.
Get it to compile and mostly work.
(2) restructure it to a decent java program
put your source code into some decent java package structure
remove the empty subproj directories
(3) remove the .woo files of any component that doesn't need it (any
without a display group). seriously.
remove all .api files. seriously.
Once you have that done, and it mostly works as it did in its ObjC
incarnation, you can move forward with enhancements. This will take you
anywhere from 1 to 4 weeks (longer with some hair pulling sessions while you
learn wo).
For IDE, tools, libraries, etc., there are a few cults that exist, join or
not as you like. I'll stay out of that argument (but whatever you do,
*don't* use WOBuilder). For the work described above, a text editor and ant
will be all you need.
Steve
>
> I'm guessing ObjC is not ported to C2D yet, which means I need to use
> a Motorola-based workstation. Are most ObjC WOApps being ported to
> Java, or not necessarily?
>
> Thank you,
> M
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden