WebObjects Dev tools (Re: some GSWeb wiki pages updated / added)
Lars wrote: > Since Apple is going to deprecate the Java bridge and all the WO > tools in foreseeable future (next WWDC, Leopard?) it is maybe a good > idea to integrate with these. Although WOLips is Eclipse based (and > Java this way) there is at least an existing infrastructure to build > on (or to port to ObjC maybe?) which would need some minimal > extension (mainly some sort of ObjC editor (could be based on http:// > www.eclipse.org/cdt/ possibly?) and some ObjC builder support). I do not care about the Java bridge. The only tools I am using here are EOModeler and WOBuilder. For EOM, there seems to be already something on the way. WOB is a much harder task since it requires integration with somthing that can render HTML like WebKit. For me, these two tools are a big improvement in productivity. That is why we should have GNUstep versions of them in the long term. Editing WOComponents in a text editor is slower and tends to have more syntax errors than "generated" ones. Actually, it may be possible to create a single graphical Editor that can edit Renaissance XML and WOComponents. Any ideas? -- _ _ _(_)(_)_ David Wetzel, Turbocat's Development, (_) __ (_) Buchhorster Strasse 23, D-16567 Muehlenbeck/Berlin, FRG, _/ \_ Fax +49 33056 82835 Phone +49 33056 82834 (__) http://www.turbocat.de/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: WebObjects Dev tools (Re: some GSWeb wiki pages updated / added)
Am 03.01.2007 um 10:19 schrieb David Wetzel: Lars wrote: Since Apple is going to deprecate the Java bridge and all the WO tools in foreseeable future (next WWDC, Leopard?) it is maybe a good idea to integrate with these. Although WOLips is Eclipse based (and Java this way) there is at least an existing infrastructure to build on (or to port to ObjC maybe?) which would need some minimal extension (mainly some sort of ObjC editor (could be based on http:// www.eclipse.org/cdt/ possibly?) and some ObjC builder support). I do not care about the Java bridge. But EOModeler cares. EOModeler uses the Bridged JDBC Adaptor to connect to the Database. So if the Java bridge is gone EOModeler runs no longer. The only tools I am using here are EOModeler and WOBuilder. For EOM, there seems to be already something on the way. In WOLips you've got Entity Modeler which is basically EOModeler without the graphical view. WOB is a much harder task since it requires integration with somthing that can render HTML like WebKit. I for my part don't consider this critical since I can live without it. I use the HTML Editor as part of the WOD component editor which WOLips provides on a daily base. It supports syntax highlighting, syntax checking and code formatting which is more important for me than to have a rendering preview. If you're creating highly dynamic pages the preview WOBuilder provides isn't very useful anyway. But of course everybody has his own preferences. For me, these two tools are a big improvement in productivity. That is why we should have GNUstep versions of them in the long term. Editing WOComponents in a text editor is slower and tends to have more syntax errors than "generated" ones. Actually, it may be possible to create a single graphical Editor that can edit Renaissance XML and WOComponents. Any ideas? -- _ _ _(_)(_)_ David Wetzel, Turbocat's Development, (_) __ (_) Buchhorster Strasse 23, D-16567 Muehlenbeck/Berlin, FRG, _/ \_ Fax +49 33056 82835 Phone +49 33056 82834 (__) http://www.turbocat.de/ regards, Lars ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: WebObjects Dev tools (Re: some GSWeb wiki pages updated / added)
Lars Sonchocky-Helldorf wrote: > But EOModeler cares. EOModeler uses the Bridged JDBC Adaptor to > connect to the Database. So if the Java bridge is gone EOModeler runs > no longer. I just edit the model in EOModeler. If I really need some killer features I power on my old NeXTstation turbo :D > In WOLips you've got Entity Modeler which is basically EOModeler > without the graphical view. So the GS clone is already better? > I for my part don't consider this critical since I can live without > it. I use the HTML Editor as part of the WOD component editor which > WOLips provides on a daily base. It supports syntax highlighting, > syntax checking and code formatting which is more important for me > than to have a rendering preview. If you're creating highly dynamic > pages the preview WOBuilder provides isn't very useful anyway. But of > course everybody has his own preferences. Sure. Syntax highlightning and formatting is very important. How about bindings? Is it able to parse header files? Will you have the methods/instance variables in a list to connect them to the component/dynamic element? Dave -- _ _ _(_)(_)_ David Wetzel, Turbocat's Development, (_) __ (_) Buchhorster Strasse 23, D-16567 Muehlenbeck/Berlin, FRG, _/ \_ Fax +49 33056 82835 Phone +49 33056 82834 (__) http://www.turbocat.de/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: WebObjects Dev tools (Re: some GSWeb wiki pages updated / added)
On 2007-01-03 13:02:50 -0800 David Wetzel <[EMAIL PROTECTED]> wrote: Lars Sonchocky-Helldorf wrote: But EOModeler cares. EOModeler uses the Bridged JDBC Adaptor to connect to the Database. So if the Java bridge is gone EOModeler runs no longer. I just edit the model in EOModeler. If I really need some killer features I power on my old NeXTstation turbo :D In WOLips you've got Entity Modeler which is basically EOModeler without the graphical view. So the GS clone is already better? No I wouldn't consider it better, it should be usable though, but theres a few loose ends, and stuff which could be done better, window placement is all hard coded, missing nextResponders, uses a pop-up button in a way not yet supported by -gui, it contains little beyond what EOModeler has, and is still missing a few things that EOModeler does like the browser editor, and only supports the outline view icon path, as opposed to the one which went above the browser similar to the icon path used in Workspace Manager. also a few missing inspectors (mainly ones where the functionality is duplicated in the table view editor) I believe he was speaking about an eclipse plugin for WO though. anyhow, i've commited some introductory documentation for GDL2 the formatting is pretty bad (as i'm new to texinfo), its still in the initial stages of construction, and i'm definately not a writer... but any criticism is appreciated... I for my part don't consider this critical since I can live without it. I use the HTML Editor as part of the WOD component editor which WOLips provides on a daily base. It supports syntax highlighting, syntax checking and code formatting which is more important for me than to have a rendering preview. If you're creating highly dynamic pages the preview WOBuilder provides isn't very useful anyway. But of course everybody has his own preferences. Sure. Syntax highlightning and formatting is very important. How about bindings? Is it able to parse header files? Will you have the methods/instance variables in a list to connect them to the component/dynamic element? Dave ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev