AW: Dreamweaver translator extension for WebObjects
AW: Dreamweaver translator extension for WebObjects
- Subject: AW: Dreamweaver translator extension for WebObjects
- From: "Thomas Engeroff" <email@hidden>
- Date: Thu, 29 Jul 2004 10:23:40 +0200
Hi Scott,
I tried about the same a couple weeks ago with Adobe GoLive CS. There was an
extension out there for GoLive some years ago. Anyways, I tried to do about
the same you try to do for Dreamweaver. The Problem was, that GoLive was
crashing down all the time, and that I had to restart the Program all the
time. That was very annoying and made me stop this attempt.
Anyways, I would be interested to see how good extension development is in
Dreamweaver. I'll take a look at it next week.
Would be great if you could give me a starting point. Maybe you can send me
your WO-extension so I can easily get into it.
If it's a little better than with GoLive I would be very interested in
helping you develop that Dreamweaver extension.
Greetings,
Thomas
-----Urspr|ngliche Nachricht-----
Von: email@hidden
[mailto:email@hidden] Im Auftrag von Scott Ahten
Gesendet: Mittwoch, 28. Juli 2004 21:54
An: WebObjects (Group)
Betreff: Dreamweaver translator extension for WebObjects
Before posting my question, I'd like to introduce myself. I'm a JSP and
Servlet developer who is interested in using Webobjects on some of my
larger, complex projects. I'm looking forward to learning more about
WebObjects!
Now on to my question...
Does anyone use Dreamweaver MX 2004 with WebObjects?
I've found Webobjects builder, well, quite limited when it comes to
developing complex HTML pages and displaying CSS styled content.
I've been digging thorough the Dreamweaver extension APIs in an effort
to add visual rendering support for WebObjects components in layout
mode. The APi includes using Javascript "Translators" which replaces
original markup with stand-in content displayed only in the visual
pane.
I've created an extremely simple proof-of-concept translator which
provides textual representations of non-mixed content objects (empty
elements such as images, etc., show up as [webobject]) and provides
generic stand-ins for input elements and buttons if the WebObject's tag
name matches a particular signature. There are still a few bugs with
copy and paste operations, but it looks like it's a concept that can be
refined to provide non-binding / visual support for WebObjects by
parsing a components .wod file.
Is anyone working on something similar? Would anyone be interested in
becoming involved in this project?
A curious mind would like to know...
Thanks,
- Scott
- - - - -
:: email@hidden
:: http://www.pixelfreak.net
- - - - -
- - - - -
:: email@hidden
:: http://www.pixelfreak.net
- - - - -
- - - - -
:: email@hidden
:: http://www.pixelfreak.net
- - - - -
- - - - -
:: email@hidden
:: http://www.pixelfreak.net
- - - - -
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.