Everyone has their own favorite IDE, but I really prefer XCode over
Eclipse. I sure hope I don't have to go down the Eclipse path to
stick with WebObjects. If so, I will likely jump ship to Ruby on Rails.
I am assuming that Apple will continue with EOF support directly
within XCode since it seems like they have already invested in that
path and it is almost a fully functional replacement of EOmodeler in
the current version of XCode. I could be wrong, though, since I
don't know what Apple is really thinking.
As others have already mentioned, the other big piece to replace is
WOBuilder. Since WOBuilder is being deprecated, my dream replacement
would be something similar to Dashcode (see http://
developer.apple.com/leopard/overview/dashcode.html) or a cross
between Dashcode and iWeb with support for Cocoa style bindings. In
the very least it would be nice to have a Dashcode like application
supporting client side scripting and additionally to take those
concepts and apply them to server side, also.
Among the features that I like:
- support for themes
- prebuilt JavaScript controls
- easy layout with Interface Builder like features (e.g. generation
of CSS based on inspector layout and metric settings )
- generation of the necessary source code files (e.g. JavaScript,
HTML, CSS)
- support for modern standards
- hooks for developers to customize code
As much as I like WOBuilder as a tool for programming functional web
applications it would also be nice to have the iWeb/Dashcode features
which would make it easier for us to build truly beautiful web based
applications. I think Dashcode gets it right, and I would like to
see WOBuilder's replacement deliver that same experience. I guess as
a dream, I would like to see Apple deliver something like an "iWeb
Pro" application that combines concepts from Dashcode and iWeb and
mates them to a freshly optimized, standards compliant WebObjects
framework.
-tom
On Jan 22, 2007, at 11:50 AM, [EMAIL PROTECTED]
wrote:
Message: 1
Date: Mon, 22 Jan 2007 02:31:50 +0100
From: Georg Tuparev <[EMAIL PROTECTED]>
Subject: Re: WOBuilder in the future of WO?
To: WebObjects Dev Apple <webobjects-dev@lists.apple.com>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
sorry, pressed the send button too soon...
-------------
I too have mixed feelings about WOBuilder. With all its bugs, it is
still faster to bind a WOString to
Session.observatory.controlRoom.telescope.positioningInstruments.curre
nt
PointingModel.declination using WOBuilder then type it.... And it is
less error prone...
I do not like making announcements like a Microsoft sales rep and
never keep them, but I will make an exception. When the Leopard seed
came first out, I (as usual) started investigating all new goodies by
trying to develop a moderately difficult application. This time my
seed came almost the same time as Cliff's late summer announcements,
so I naturally decided to write a WOBuilder replacement :-)
How far am I? Well, I can already do the operation I described above
using my app. Not much more, but for something I spent not more then
30 min a day not that shabby too. So, do not expect it to be ready
too soon, but soon enough for "Apple's transition plan"...
Actually, to call my attempts WOBulder replacement is not very
correct. My focus is on correctly laying out DIVs, CSS, and Wonder's
AJAX framework. And yes, it also makes WO bindings and understands
from Xcode integration (I see Chuck's and Anjo's faces :-) One neat
idea I am really proud of is the "Project's Component Catalogue"...
Another is that actually I have a forth view - called provisionally
"The Real Thing" that simulates what will happen if one actually
executes the WOApplication by putting fake values for the WO
elements... OK, more on this later.
cheers
gt
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
