Re: A "Why WebObjects" Site / Initial Thoughts Please
Re: A "Why WebObjects" Site / Initial Thoughts Please
- Subject: Re: A "Why WebObjects" Site / Initial Thoughts Please
- From: Daniel Mejia <email@hidden>
- Date: Wed, 7 Jul 2004 16:05:27 -0500
Hi all,
I would like to know how can I contribute and/or who is going to be the
main contact or coordinator to this project.
This could be the "marketing" site that any person who is thinking to
switch to WO can use to compare the technology and also could be a
great piece to have a better communication with the WO community
besides programming problems or bugs
I have some WO documents in spanish and I have some powerpoint
documents that I would like to contribute to this project.
Saludos,
Daniel.
On Jul 7, 2004, at 11:17 AM, email@hidden
wrote:
>
> From: Dario Bagatto <email@hidden>
> Date: July 7, 2004 7:16:27 AM CDT
> To: WebObjects (Apple) <email@hidden>
> Subject: Re: A "Why WebObjects" Site / Initial Thoughts Please
>
>
> Hi all,
>
> Although I see a lack of direction regarding WebObjects I don't fear
> that it will go away that quick and I certainly do not want to switch
> any of my WebObjects projects to anything else for now (although I
> always have an open eye for new things).
>
> Ryan I really like your idea and I think such a site would be of big
> help. OK there are web sites around dedicated to WebObjects
> development or WebObjects projects but most of them are focussing on
> an audience that already knows WebObjects and know of the distinct
> parts of it like EOF, JavaClient, etc.
>
> What is missing IMHO is a site that handles WebObjects related stuff
> for an audience that only knows very little about WebObjects an
> audience which probably is using non WebObjects vocabulary in their
> searches (often terms coming from the J2EE or .NET world). There are
> also two kind of newbies those that are new to development in general
> and are now starting development with WebObjects and there are the
> experienced [Java] developers just new to the WebObjects technology.
> Such a site may try to serve both of them but this also means to use a
> simpler vocabulary for absolute development newbies and adequate
> educated vocabulary for the experienced developers which compare
> WebObjects to something they know or currently use. They could also
> find info on how to smoothly integrate WebObjects within their
> currently used development environment.
>
> One thing is advocating WebObjects, so that it is better known and
> that it may become easier to bring it up as a potential technology for
> clients and/or company management. Having adequate material and/or
> resources surely helps to sell WebObjects to these guys.
>
> But I think there is also another underestimated problem (and I speak
> a little from experience) that can be addressed by such a site. Let's
> suppose I as an executive group leader was able to convince my
> management to finally select a technology like WebObjects for a new
> project (this already as we all know may be a hard task).
>
> To make the project a success I need as always the support of my
> developers. Now usually if you start with a new technology your
> development team has to learn this technology first. If this team does
> not find answers and resources fast and easy they may get frustrated
> and you start to hear things like "... it does not work at all and I
> don't know why...", "... no I could not find anything about this on
> the web..." or "... with another technology like EJB it would be much
> easier..." etc. etc. It may very fast come to a point where all
> spurious errors appearing during development suddenly are solely
> because of the newly adopted technology and suggestions come up to
> move back to another technology the developer team knows better. Once
> this happens the project will most probably fail and this also means
> WebObjects as new technology will be hard to bring up ever again! [You
> may argue that this is just a management problem and one can force the
> developers to work with it and period but first IMHO I don't think
> this helps to introduce a new technology and second it kills
> innovation. ]
>
> Having a dedicated site aimed at a clear defined audience helps that
> experienced developers new to WebObjects get answers, how-tos,
> examples and contact to other WebObjects developers.
>
> There is a big potential but I am also realistic, such a site means a
> BIG effort and is nothing that is build within a short period of time
> and needs a bunch of helping hands especially to maintain it, as it is
> quite important to be current and to provide regular updates. I also
> think that it is important to have a clear concept with a focussed
> goal of this initiative first before starting at all.
>
> Last but not least I would certainly try to give a helping hand and to
> contribute to such a site if I can be of any help,
>
> best regards
> Dario
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.