Am 12.08.2006 um 22:45 schrieb Deepak Nulu:
I am not a fan of manually editing the wod files. I was impressed when I first saw drag-and-drop bindings in WOBuilder (even though I am used to it since Nextstep days with InterfaceBuilder; I just did not expect it for a web-based UI builder :-). So I stick with WOBuilder and EOModeller (you just need to have XCode up and running in the background) and do everything else in WOLipse/Eclipse.
Well good luck...
I do like the auto-completion in the .wod editor in WOLips, but I don't like the fact that the HTML file and the WOD file editing are separate (it is the same in WOBuilder as well if you are not using drag-n-drop). Having to "declare" a component in the HTML file and then switch over to the WOD view to "define" its bindings is not efficient; there is too much loss of context.
This is what I meant in my previous mail... but just because the WO UI is such-and-such, the Eclipse UI needn't be the same. For example, one could display the bindings in the Properties editor, with some easy shortcut to go there. (Just an idea, I have no way of knowing if this is workable or even a good one).
I wish the WOLips editor created a virtual view where the HTML file and the WOD file are combined so that the "definition" of the bindings is in the same place as the "declaration" of the component. The virtual view can then generate the HTML and WOD files behind the scenes. The virtual view could use its own notation which should be shorter than having to type "<WEBOBJECTS name=""></WEBOBJECTS>" boilerplate HTML code (this boilerplate is a pain even though Eclipse has templates that can make this
You may be hitting onto something here. I find the actual WYSIWIG display in WOBuilder totally useless. What I *do* like, though, it the graphical hierarchy it displays in regard of your components. So the a visible nesting would be enough for me. It may be that the outline view provides the same thing, but I have hard time to wrap my head around it.
Some things, though, are a problem with the underlying WST toolkit. As I understand, they didn't want to accept a huge patch from Mike that would affect basically every internal tag in the WST to allow arbitrary contained tags. He might want to provide details so you can file bugs in the Eclipse Bug reporter:
https://bugs.eclipse.org/bugs/ Cheers, Anjo _______________________________________________ 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
