Wiki source code of WO Builder Ideas

Version 41.1 by Marc Oesch on 2006/09/08 11:15

version	line-number	content
22.1	1	This page discusses ideas for a WOBuilder replacement / successor / clone and ideas how to achieve it. Below are excerpts pasted from various ideas from the WO mailing lists. Please add and update your ideas here to keep the page up to date.
14.1	2
22.1	3	A separate page for active projects is available here [[WO Builder Tasks]] .
	4
18.1	5	== General Idea for additional tool: Split WYSIWYG/web designer and developer needs ==
14.1	6
40.1	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.
14.1	8
	9	== General Feature Wishlists ==
	10
	11	We do NOT need a WYSIWYG WOBuilder replacement. We need an editor that, like WOBuilder, displays the organisation of the component, not the way it will be rendered in a browser. It's fine by me if someone wants to go down the path of developing a separate tool that previews what a component looks like in a browser, CSS and all, but in my opinion that is a waste of time because the rendered result would be so heavily dependent on the data and functionality of the WO application. The only real way to preview a component is to run the WO app and look at it in a browser.
	12	Although a WO development plugin for a commercial Web editor would be nice, I too don't want to buy and learn DreamWeaver. I use Golive.
	13
40.1	14	----
14.1	15
40.1	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.
34.1	22
40.1	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. :-)
34.1	29
40.1	30	----
34.1	31
14.1	32	I never really understood the hype surrounding WOBuilder's Preview view and have only used it a few times with disappointing results.
	33	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.
	34
40.1	35	----
14.1	36
	37	I heavily rely on the visual display of the relationships of the components on the page: this is inside that, which is before that, and so on. As long as this is clearly, graphically displayed, I can do without the HTML rendering. One proviso: we still use tables a lot because of the CSS problems with MSIE, so some visual rendering of tables would be useful.
	38
	39	//The value of the object browser is not just that you can browse actions and keys of your classes, and set bindings, but that you can add keys and actions safely into existing code. This part of it just cannot be emphasised enough; it is a big productivity gain compared to normal editing, refactoring IDE or not.//
	40
	41	Absolutely. WOBuilder might have some serious flaws, but it has many of these almost invisible features that turn out to be key in the rapid, safe, high-level development of WO applications without getting bogged down in the code.
	42
40.1	43	----
14.1	44
18.1	45	For the BVM - that's the Baby's View Modeler that would substitute WOBuilder - I'd like I could start working from a high resolution graphic or SVG design made by a professional designer.
14.1	46	I would then go along marking areas on the picture and saying 'this is going to be a WOForm; these, WOButtons', so that the corresponding web server resources would be automatically created (and properly linked) at different resolutions for different CSS "media" tags, browsing device capabilities, user preferences, etc.
	47
24.1	48	In the BVM too I'd like to be able to select a flow, or more than one, of page portions[[1]] that would be presented in some meaningful sequence to the client browser[[2]].
14.1	49
40.1	50	[[1]] something like the flowing you can do in Acrobat,
	51	[[2]] something like a wap stack.
14.1	52
	53	I know I'm showing my bias thinking again on small real state devices, but if it is awkward to develop for three different desktop browsers, developing for a myriad of small devices is plain crazy. All this should be automated from the beginning to the extreme... and the extreme could be some clever D2W presentational rules that would even take into account if the presentation flow is going to be managed from the server or from the client (some small devices are really stupid). On second thought, something similar could prove useful too for designing whatever substitutes ajax in the future
	54
40.1	55	----
14.1	56
40.1	57	== Implementation Ideas ==
14.1	58
40.1	59	We should also make a list of how it can be done. I think the options are:
14.1	60
20.1	61	===== A plugin for DreamWeaver, GoLive... (akin to the Lasso plugin) =====
14.1	62
34.1	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.
14.1	64
40.1	65	----
34.1	66
	67	See general idea about a separate WYSIWYG tool (in addition to the WOBuilder replacement for developers).
	68
20.1	69	===== Eclipse plugin =====
14.1	70
	71	Has anyone used eZingBuilder ? it's a wysiwyg html editor eclipse plugin for tapestry.
40.1	72	http:~/~/ezingbuilder.sourceforge.net/cms/
14.1	73
40.1	74	----
18.1	75
40.1	76	http:~/~/www.aptana.com/ and
	77	http:~/~/www.aptana.com/docs/index.php/Plugging_Aptana_into_an_existing_Eclipse_configuration
14.1	78
20.1	79	===== A standalone Java app =====
14.1	80
	81	Good for integration with IntelliJ etc.
	82
40.1	83	----
14.1	84
	85	SOPE template editor is available for Mac OS X, could serve as input for a similar solution in Java:
40.1	86	http:~/~/www.mulle-kybernetik.com/software/WOEditor/downloads/
14.1	87
20.1	88	===== A way to call WOBuilder from Eclipse =====
14.1	89
	90	I don't know if that will be functional after the Java Bridge is gone, probably a short term strategy only.
	91
40.1	92	----
34.1	93
	94	Current issues when running WOBuilder with WOLips:
40.1	95	http:~/~/www.objectstyle.org/confluence/display/WOL/Using+WOBuilder+with+WOLips
34.1	96
18.1	97	===== Additional options ? =====
14.1	98
40.1	99	Above options as listed in http:~/~/lists.apple.com/archives/webobjects-dev/2006/Sep~/~/msg00079.html_
22.1	100	//Please add options or additional content to this preliminary list, thanks//
14.1	101
18.1	102	== Fundraising for WOBuilder replacements ==
14.1	103
36.1	104	Idea to fund a first prototype with community donations, eg. using PayPal or similar.
14.1	105
40.1	106	We will probably need:
24.1	107
28.1	108	* Timeline and Feature Cut (see the different options above)
24.1	109	* Potential interested candidates and volunteers
36.1	110	...
24.1	111
14.1	112	== Name for WOBuilder successor ==
	113
	114	Proposed names WOve, Eclipstick, ...
	115
	116	(There are additional names proposed for a suite of community tools with installer etc. like WOO, WOOS, Wonderland, Wonderlust, Wonderlips or /Web )

Wiki source code of WO Builder Ideas

Applications

Navigation

My Recent Modifications

Need help?