Changes for page WO Builder Ideas

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,6 +1,6 @@
1		-This page discusses ideas for a WOBuilder replacement / successor / clone and ideas how to achieve it.
	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.
2	2
3		-== General Idea for additional tool: Split WYSIWYG/web designer and WO develoer needs ==
	3	+== General Idea for additional tool: Split WYSIWYG/web designer and developer needs ==
4	4
5	5	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.
6	6
...	...	@@ -24,7 +24,7 @@
24	24
25	25	----
26	26
27		-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.
	27	+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.
28	28	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.
29	29
30	30	In the BVM too I'd like to be able to select a flow, or more than one, of page portions[[†]] that would be presented in some meaningful sequence to the client browser[[‡]].
...	...	@@ -40,19 +40,21 @@
40	40
41	41	We should also make a list of how it can be done. I think the options are:
42	42
43		-=== -- a plugin for DreamWeaver (akin to the Lasso plugin)-- ===
	43	+===== A plugin for DreamWeaver, GoLive... (akin to the Lasso plugin) =====
44	44
45	45	See general idea about an additional tool to the WOBuilder replacement above.
46	46
47		-h3 - a Eclipse plugin
	47	+===== Eclipse plugin =====
48	48
49	49	Has anyone used eZingBuilder ? it's a wysiwyg html editor eclipse plugin for tapestry.
50	50	http:~/~/ezingbuilder.sourceforge.net/cms/
51	51
	52	+----
	53	+
52	52	http:~/~/www.aptana.com/ and
53	53	http:~/~/www.aptana.com/docs/index.php/Plugging_Aptana_into_an_existing_Eclipse_configuration
54	54
55		-=== -- a standalone Java app-- ===
	57	+===== A standalone Java app =====
56	56
57	57	Good for integration with IntelliJ etc.
58	58
...	...	@@ -61,16 +61,16 @@
61	61	SOPE template editor is available for Mac OS X, could serve as input for a similar solution in Java:
62	62	http:~/~/www.mulle-kybernetik.com/software/WOEditor/downloads/
63	63
64		-=== -- a way to call WOBuilder from Eclipse-- ===
	66	+===== A way to call WOBuilder from Eclipse =====
65	65
66	66	I don't know if that will be functional after the Java Bridge is gone, probably a short term strategy only.
67	67
68		-=== Additional options ? ===
	70	+===== Additional options ? =====
69	69
70	70	//Above options as listed in http:~/~/lists.apple.com/archives/webobjects-dev/2006/Sep~/~/msg00079.html_
71	71	//Please add options or additional content to this preliminary list, thanks
72	72
73		-== Fundraising ==
	75	+== Fundraising for WOBuilder replacements ==
74	74
75	75	Idea to fund a first prototype with donations, eg. using PayPal or similar.
76	76