On Sat, 4 Oct 2003 17:48:18 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> GUI editor is just used to create filter programs, that's all. It can only > create a (simple) subset of the valid programs in this language, this is > why it is useful to also have the possibility to type the program text > directly Advantages of script over Gui are very poor. It has no variables and no procedures. It can do arithmetic and string concatenation, but what use is there for it? > but even if it could generate all programs it still wouldn't mean > that we don't need the filter language because this is what is executed > when the filter is used. Or do you mean to just remove/drop the parsing > part of the filter language (for me the language is not just the parser but > also the interpreter itself)? As I understand it, there are several steps from Gui editor to actual filtering: * Editing * Writing Gui settings to data structure (MFDialogSettings?) * Saving settings to profile * Generating script from data structure * Parsing script * Evaluating script I think that evaluating the data structure directly is much simpler than first translating it to script and then evaluating that script. > As for Python, the only advantage is simplicity, i.e .that we can have GUI > editor and built in interpreter for the filter language but not for Python. > Its syntax is also more suitable for this particular task IMHO... But in-memory data structure with profile serialization is much simpler and it is 90% there already. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
