On Monday 04 June 2001 10:32, Ian Bicking wrote:
> Tavis Rudd <[EMAIL PROTECTED]> wrote:
> > To be honest this was never high on my list as I never
> > use WYSIWYG tools that muck with your sourcecode.  I'm
> > like you and use Emacs for everything.
> > However, many use nothing but WYSIWYG tools and it's
> > a worthy goal to give them something usable.

> Another reason this is a good goal: no one seems to do
> it.  I've seen *very* few template systems that are
> friendly to WYSIWYG editors.  I don't know quite why,
> except perhaps that, like you, most people designing the
> template language use text editors.
Quite true!

> Also, people shouldn't just be able to use WYSIWYG tools,
> but people who use these should be able to interact well
> with people who don't. So, while you *can* use explicit
> terminators instead of newlines, once someone uses
> newlines the template becomes inaccessible to WYSIWYG
> users.

Not quite true. The TemplateDefinition can't be edited safely
in a WYSIWYG editor once it has lazy endings, but the user 
CAN use the template and fill it in with their data.

> [snipsnip]
>
> > > * Relatively safe to delegate responsibility (kind of
> > > like Zope). For the most part I trust my users not to
> > > do anything too bad, but they will make mistakes. 
> > > They should be able to figure out what they've done
> > > wrong, and they shouldn't have any access to Python
> > > code.  I consider putting their HTML into a different
> > > directory from code to be sufficient security for the
> > > most part.
> >
> > That was one of my original goals, but I shifted away
> > from it upon realizing how complex things can become. 
> > The hooks for code security validation are in place so
> > it is possible to build it up if anyone is interested
> > in 'safe-delegation' that guards against malicious
> > stuff.
>
> In a declarative syntax, of course, security is assured
> by definition.  I.e., a declarative page doesn't *do*
> anything, it simply is.  Of course, it is hard to mix
> user code and enforce that the page is functional in this
> form.  I consider it more of an issue of perspective.

That's why I like your data extraction idea.  It allows 
safe delegation very easily!  Safe-delegation becomes 
hard once you have logic blocks, etc. in the template
definition, but there's no reason we can't have it for 
the template users.


_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to