"Diethelm Guallar, Gonzalo" wrote:
> Anyway... Some people here have been asking how well does
> a Turbine WM- (Velocity-) based template integrate with
> those wimpy HTML editors. I have never touched one of those,
> and do my HTML programming by hand, so I have no idea how
> they work, but there are some obvious questions that pop up:
HTML editors are for sissies! :)) Seriously, they are good
for quickly laying out the page, or mocking up a statical
preview of the site to show it to the customer.
Once the graphical design is agreed upon, you start coverting
the htmls into WMs and then HTML editor won't help you much.
If you create the page in the editor in a sensible way, you'll
have comments showing where you need to cut the page, or
insert custom stuff. The preview needs to be done via Turbine,
because there is no obvious way to force the editor to show
images and such.
> * How does WM code appear on the HTML editor? I'm guessing
> it will just appear as text preceded with a $ or #, right?
It will look like junk. All the text you insert inside <table>
but outside <td> tags, will end up above or under the table.
> * Say you want to embed an image on a page. Is there a way to
> make the editor show the image (that would mean referencing
> the image in a way the editor can find it) and also make
> the SRC a valid one under Turbine?
The solution for that is putting the site in / directory of
a webserver (Apache virtual server would be ideal), and then
specifying <base href=""> inside head when you start serving
in under Turbine (needed only when your app is not running
in the root context).
> * Same thing for URLs and HREFs.
DynamicURI won't work in the editor :(
> * I have heard scary tales of how these editors will take
> control over your HTML, meaning they will rip it apart
> and put it back together in a form you would never
> recognize. I can see how this could have potential impact
> on the order of execution of WM calls (not that depending
> on this is a very clever idea anyway). Anybody has any
> experience in this regard?
If you use something that has an M$ mark on the box, it's
more than likely :). If you use Macromedia DreamWeaver, and
you turn off html rewriting in the options, you should be fine.
> * Any other good or bad comments on the idea of using an
> HTML editor for developing WM templates? Any one you could
> recommend?
Our approach is use Adobe ImageReady for cutting graphics +
skeletal HTML, massage it a bit more in MM DreamWeaver 3,
and them convert to .wm files in your faourite text editor,
previewing from under Turbine.
I heard that DreamWeaver can be extensively customized
using JacvaScript. It would be nice if someone came up with
a DW mod that was WM aware (not the images/links but structure)
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
