My philosophy is that if it has some nugget of useful information in it that 
shouldn't be lost, then move it to the "deprecated" section as a quick fix. 
However, if everything in it is out-of-date and misleading and no longer 
applicable, then the body of it should get replaced with a pointer to the 
current instructions, at least until any Google searches no longer point to 
it... Do we have access to page views and such?

How many new developers walk away from WO every year because of old pages like 
this laying around? Yes, this is a rhetorical question, that has been asked 
many times before...

I've been trying to go through and modernize stuff as I have time, especially 
the basics, but the WO/WOLips/Wonder spaces often times have redundant pages 
and I always feel like I'm trying to put out a house fire with a garden hose. 
If only we could really capture the fire hydrant of information that WOWODC is 
every year in the Wiki... sigh.

I _really_ think we should merge the WO, Wonder and WOLips spaces of the Wiki. 
While they are distinct things, how many of us, in the past 4 years, has ever 
used them independently?

It's time to stop pretending that WebObjects is a solution by itself anymore. 
WebObjects is really just WonderFoundation at this point. No new developer 
should ever be starting a plain-jane WO project. Ever. Not even a Hello World 
app.

I'm sure this will be a topic discussed at WOWODC this year. Come make your 
voice heard!

Dave (A)


On May 6, 2011, at 7:23 AM, Pascal Robert wrote:

>> As I try to do the beginner tutorial here: 
>> http://wiki.objectstyle.org/confluence/display/WO/Hello+World+-+Your+First+WebObjects+Application
> 
> Should we keep that page or should we delete it?

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to