Gerald Richter wrote:
> Question (so I can make the next version better): Embperl makes a lot
> efforts to work with the code these Highlevel HTML editor produces. For
> example our customers use MS Frontpage to edit pages which contains Perl
> blocks, and Embperl is still able to interpret them afterwards (e.g. it
> converts things like < back to <).
Editors with support for ASP tags don't change the code at all. That is
the
point. So no action is required afterwards and designer won't see the
code, but only a replacement icon.
> What problems you exactly have when using [ .. ] blocks? Is it that the perl
> code is visible to the designers or is it that your editor breaks the perl
> code? If it breaks the perl code, what does it do to the code?
I've tested Dreamweaver, GoLive and Homesite. They do all ASP, some do
ColdfusionML, SSI or PHP. The best one was Dreamweaver, the worst
GoLive (only ASP). I couln't test Frontpage.
> Also consider code like <TR BGCOLOR=[+ $col +]> or even <TR [$ if $col
> $]BGCOLOR="#ffffff"[$endif$]>, how should this look with the new syntax?
<% is like [- and
<%= is like [+
Example:
<TR BGCOLOR="<%= $col %>"> (The editors I tested had no problem with
double
closing tags as long as they use '%>'
The other example was given in a previous posting, I'm not an expert in
ASP syntax.
> More comments on this topic would be very helpfull! Anything you say now has
> the chance to go into the next version...
I guess there is no need to make the syntax configurable to any sequence
of characters as brackets but just the popular ones with priority to ASP
because of my tests.
> Gerald
--
Frerk Meyer mailto:[EMAIL PROTECTED]
Channel.One http://www.channel-one.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
