Am Mittwoch, den 22.11.2006, 14:27 +0100 schrieb Mattias Gaertner: > > > No solution to your problem, but: > > > > > > I'd really love to have something like that for fpc/lazarus. > > > Reading xml and generating form components according to default or > > > configured mapping would be very helpful in creating input or > > > editing forms. > > Can you explain this and/or give an example?
With pleasure: Imagine some dataset files in any format, represented as XML. The contents of this files are similar because they contain an explanation what is in there, a name, id, owner and/or creators name and so on. They differ because the rest of the file consists of some data sets in form of matrix data (2 and 3 dimensions), tabular data similar to relational tables, scalar values, etc. The count and presence of possible elements is mixed, but the main types are always of some well known sort. In this special case the files are collections of measuring data and related texts, maybe scripts or image data. Now think of XSLTing this files into XForms [1] and having the browser show an input form depending on the content of the file. This could be done by a runtime loader and form generator in fpc/laz programs, too. For easy usage there must be a configuration or description, which datatype is reperesented by what form element. For example a filename would be a string (input component) but is a special case with a button and browsing dialog. An integer could be restrained to a range or set of possible values. The general idea behind this is already realized through xforms, but I want to write only one programm presenting editing forms for any data collection file. This way the need for one specialized input form for each data file class would vanish. More helpful with increasing count of different file types... Concluding I must admit, an xforms processor for fpc would be it. Only some special mime type "application/internal-proc" or similar would be needed for connecting to a library of handling functions. And the other difference is it can be client-only, no server involved. But from reading the xforms standard I think the whole thing would need a huge effort in writing. And I don't see any other uses of such a thing besides the one described ... Dreaming on, Marc [1] http://www.w3.org/TR/xforms/ _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
