Re: Apple's Support of WebObjects
Re: Apple's Support of WebObjects
- Subject: Re: Apple's Support of WebObjects
- From: Kieran Kelleher <email@hidden>
- Date: Sat, 5 May 2007 18:47:12 -0400
On May 5, 2007, at 5:27 PM, Jean Pierre Malrieu wrote:
This IDE kinds of remind me everyday that I don't really master it.
And I don't like the way it tends to fill up the screen, or the way
it pretends to show everything simultaneously by adding views all
around.
May be the default WOLips perspective should only have 2 or 3
views (package explorer–or how is it called?–, editor, console/
problems)?
Well, it is pretty easy to customize the perspective. In a* few
seconds* you can reposition views by dragging tabs around the
perspective and of course you can close as many views as you like. I
actually like the tab stuff much better than XCode navigation. I
really love the fact that you can double-click a tab to fill the
whole perspective and double-click again to go back to regular layout.
I find that a big screen (23") helps a lot. In fact, with XCode I was
always using expose to see where various windows were at. I think the
Eclipse layout is well designed to optimize a developer's
productivity. If you have two screens, you can just open another
window and fill that too, although I usually leave the smaller screen
for the browser interaction.
When I open NetBeans for example, I always think "what a
nicer UI". Maybe because it is more colorful? With bigger icons? But
this is more an overall feeling, and I think WOLips developers can do
a lot about it.
Sorry I meant "I think WOLips developers CANNOT do a lot about it".
The biggest problem with WOLips is the "dual" compiler. One should
not have to fiddle with ant tasks to do WebObjects development, i
think.
I did not want to scare users who want to switch to Eclipse/WOLips.
"Do the thing you fear and the death of fear is certain" - old Irish
proverb ;-)
In fact, just doing WO development, fiddling with ant task never
happens, as you always use the incremental compiler.
To deploy, you must use ant. Both compiler have similar result, and
generally, you don't see any difference between then.
In general though this gives more flexibility especially for
different kinds of builds, options to embed frameworks, etc. ....
plus you can automate build and deployment of one or more apps and
frameworks by calling project ant files from bash scripts or
whatever. Once you spend a little while studying the build.xml file,
it's not that scary after all.
But some issues can arise because both compilers do not have the
same policy with respect to flattening of resources.
And recently, some glitches showed up with localized resources in
rapid turnaround mode in frameworks.
But these are really minor issues.
True .... compared to the value that can be added by WOLips team
adding/improving component editing and component refactoring, these
things are probably low-priority
JPM _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
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