Hi 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
For manual editing, yes, but I guess the idea is that the UI should be the primary editor. It should be pretty easy to make it escape data correctly. > 2) Re: xml format > > I think I'd prefer > > <option description="Local events file" type="string" > name="localeventsfileurl">localevents.xml</option> I haven't thought about the format at all, but one drawback I can see with this is that the format becomes pretty unnatural if <option> has further children, such as the <possible_values> proposed by Glenn. It would turn into something like: <option ...> localevents.xml <possible_values> ... </possible_values> </option> which is probably legal, but looks weird. Then again, I'm not crazy about the underscores, so we should probably bash the format spec around until everybody's happy :-) - Kim ------------------------------------------------------------------------- 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
