--- Glenn Carr <[EMAIL PROTECTED]> wrote:

> Hey Brent,
> 
> > 1) the script type is more of a pain than
> currently
> > because you'll have to remember to escape all the
> > javascript correctly in the xml
> 
> Can we use CDATA junks to avoid having to escape
> script?

Yes, I think so - then you just have to remember the
CDATA format :)

> 
> > 2) Re: xml format
> > 
> 
> Actually that was close to what I had in the initial
> version
>
(http://dqsd.cvs.sourceforge.net/*checkout*/dqsd/dqsd/preferences.xml?revision=1.1),
> but after I added some <possible_value /> elements
> like so [1], it seemed a bit unweildy [2].  Plus I
> think it might introduce some problems dealing with
> unintentional carriage returns.  Not sure though, it
> does seem weird to use the element text for
> <possible_value /> but not for <option />.

Ahh, yes I see your point
 
> And, 'description' > 'display_name', agreed, but how
> about 'caption' so that we can use 'description' for
> more verbose text describing what the option
> is/does.  I can see the description being displayed
> in a tooltip or detail pane, but the caption being
> used for, uhm, well the caption.
> 
> I'd also change 'var_name' to 'var'.

Yes, if var_name were changed to var instead of name
we could use name instead of description, caption, or
display_name.
 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to