Skip to Content

Changes for page WO Builder Ideas

Last modified by Marc Oesch on 2006/10/25 12:13
From version 33.1
edited by Marc Oesch
on 2006/09/07 09:59
Change comment: There is no comment for this version
To version 37.1
edited by Marc Oesch
on 2006/09/08 11:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  == General Idea for additional tool: Split WYSIWYG/web designer and developer needs ==
6 6  
7 -However, we could focus on a much lower target in **addition to the WOBuilder replacement** : plugins for both DreamWeaver and Golive (or .wo -> HTML -> .wo conversion tools) that allow web designers to edit a WO component without destroying the WO tags. I believe the WO developer tasks and the WYSIWYG appearance tasks are completely separate activities, often done by different people, and with entirely different requirements.
7 +We could focus on a much lower target **in addition to the WOBuilder replacement** : plugins for both DreamWeaver and Golive (or .wo -> HTML -> .wo conversion tools) that allow web designers to edit a WO component without destroying the WO tags. I believe the WO developer tasks and the WYSIWYG appearance tasks are completely separate activities, often done by different people, and with entirely different requirements.
8 8  
9 9  == General Feature Wishlists ==
10 10  
... ... @@ -13,6 +13,22 @@
13 13  
14 14  ----
15 15  
16 +I'd like to have the ability to triple-click on a <webobject
17 +name="blah"> tag in Eclipse's HTML source view and have it select
18 +that tag and the corresponding </webobject> end tag. I find this
19 +immensely useful for all HTML editing. In fact, not just limited to
20 +webobject tags, but also regular HTML tags such as <table> </table>,
21 +etc.
22 +
23 +Another thing I think could be useful would be the object browser
24 +being available in some sort of hybrid HTML/graphical source view.
25 +What I mean by this is instead of having a wysiwyg mode, the layout
26 +mode could use tag objects that you could drag and drop from the
27 +object browser to in order to set bindings. Of course, we'd need a
28 +tag inspector as well. I hope that makes sense. It does in my mind.
29 +
30 +----
31 +
16 16  I never really understood the hype surrounding WOBuilder's Preview view and have only used it a few times with disappointing results.
17 17  The WOBuilder replacement should, however, have a Source and Layout view and allow the same (or better) ease of switching back and forth between the two views with selections of components from either view carrying into the other view. In a complicated HTML hierarchy, I've found this capability among the most helpful of services that WOBuilder offers.
18 18  
... ... @@ -44,8 +44,12 @@
44 44  
45 45  ===== A plugin for DreamWeaver, GoLive... (akin to the Lasso plugin) =====
46 46  
47 -See general idea about an additional tool to the WOBuilder replacement above.
63 +I was thinking that a Dreamweaver plugin would make WebObjects more corporate friendly. Maybe there is a second tier company that would like to step up to the plate... Softpress' Freeway or such? Seems like it could be in their best interest too.
48 48  
65 +----
66 +
67 +See general idea about a separate WYSIWYG tool (in addition to the WOBuilder replacement for developers).
68 +
49 49  ===== Eclipse plugin =====
50 50  
51 51  Has anyone used eZingBuilder ? it's a wysiwyg html editor eclipse plugin for tapestry.
... ... @@ -69,6 +69,11 @@
69 69  
70 70  I don't know if that will be functional after the Java Bridge is gone, probably a short term strategy only.
71 71  
92 +----
93 +
94 +Current issues when running WOBuilder with WOLips:
95 +http:~/~/www.objectstyle.org/confluence/display/WOL/Using+WOBuilder+with+WOLips
96 +
72 72  ===== Additional options ? =====
73 73  
74 74  Above options as listed in http:~/~/lists.apple.com/archives/webobjects-dev/2006/Sep~/~/msg00079.html_