This is something I have been planning on implementing when using in-
line WO tags. When the WO tags were simply <webobject
name="wodBinding"></webobject> there was no way to differentiate what
type of tag it was without parsing the WOD file as well, which is not
part of the standard Third-Party Tags functionality of Dreamweaver.
Now with the inline tag style, Dreamweaver's Third-Part Tags can now
easily tell what type of tag it is (form, input, radio button, etc)
and parse it accordingly - even assigning a different icon for it.
All it takes is setting up a xml file for the WO tags and putting in
one entry for each tag type. (and make the icon graphics...)
To me, the trick with Dreamweaver is getting the project structure to
match what Dreamweaver expects for images, css and such when the HTML
file is inside a component.
Dave
On Oct 31, 2007, at 8:24 PM, Thomas wrote:
Neil,
I have in the past used Golive for this. It is very easy to define
WO tags for Golive, plus the bindings they need. It also (unlike
DreamWeaver) shows the WO tags as blocks that can be expanded and
collapsed, and a separate binding inspector. (Mike, note that this
is close to what I want!) With DreamWeaver, you only get an image
to mark the start and finish of the block-- if you make the image
yourself and define it in the appropriate XML file.
However, Adobe have now sidlined Golive: after paying over a
thousand dollars for CS3, they want many hundreds more to upgrade
Golive. So I have resigned myself to migrating to DreamWeaver,
which for some reason I never get around to using...
Please see below for my (unofficial, perhaps wrong) answers about
inline tags.
Regards
Thomas
On 01/11/2007, at 10:59 AM, Neil MacLennan wrote:
There is a common theme here, and it is still the one thing I am
missing most from the WOLips Component Editor: the ability to see
at a
glance the layout of the component and all its elements, to click on
an element to view all its bindings (defined or not) and edit these
bindings in a separate area. Flex Builder does this beautifully. WO
Builder does it well enough. Mike's latest outline view changes are
awesome, much better in some ways than WO Builder, but it still
doesn't give me the "what does it really look like" view.
I've been taking a look at DreamWeaver's extensibility recently
with a view to helping me with my "visual" WO development. I've
recently moved to Eclipse/WOLips from XCode and am quite happy --
even with "hand-coding" my tags and wod definitions. Although I
must say that if I hadn't had an upbringing on WOBuilder then it
would have been *much* harder to get into the groove of hand
building my HTML front end. I find myself mentally visualising
what the page would have looked like in WOBuilder to help me make
sure my hierarchies of webobject tags are OK! I wouldn't like to
to come to this, new, for the first time!
Anyway, my Eclipse WOA development tree lives inside a DreamWeaver
site so that I can use DreamWeaver's templating ability to provide
and update my page furniture as well as WYSIWYG for the non-WO
bits (including tables woooo!). The trouble is, of course that DW
ignores the WO tags and it doesn't help me visualise my page
structure any better. I figure that whilst I might not get the
drag'n'drop-ability (?) of WOBuilder if I can get DW to at least
show my WO tags and their hierarchy then that's a great step
forward and might help others who work with page designers rather
than programmers.
To cut a long story short (although I feel it's too late if you've
got this far) DW is really quite extensible and it relatively
straight-forward to add to its tag library (thereby enabling code
completion, elementary validation etc within DW) and also to
create placeholder graphics to show where WO tags are on the page
in a similar way how WOBuilder did it. Further, although it might
be beyond my capability if it needs C programming, one could
create Tag editors within DW which might offer the library of WO
elements to pick from and this would especially suit the inline
style of .wo files rather than the .html/.wod duo.
Here's my question then before I get too deep into this and find
out it wasn't worthwhile:
Because I'm a recent convert to Eclipse/WOLips I'm a bit new to
the inline binding style (which would suit the plan with DW above)
and don't use it myself yet, I'd like to understand a few things.
1) Can the inline binding style *completely* do away with the wod
file?
Yes.
2) Is this what Apple meant in their update notice for 5.4 when
they said, "Combined Component Template Parser that reduces .wo
components to single .html file"
Yes.
3) Are inline bindings for 5.4 only, can I use them in 5.3
(Eclipse only I think, not Xcode), or are they Wonder only?
You can use them for 5.4 (only inline or only .wod) with the
"[thing.thing]" binding style, or using Wonder, correctly
configured, using the "$thing.thing" style. In Wonder you can mix
inline with .wod.
4) Anything else I should know that might help me here (or indeed
if someone has done this before, although a google for "webobjects
dreamweaver tag library" turned up little.)
Being a grumpy person, 8^), I gave up on Dreamweaver when I
realised that making a suitable tag library was beyond my
competence (or my patience).
Neil
--
.neilmac
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%
40woomeranet.com.au
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%
40avendasora.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
