Jørn Wildt

Hi!

As explained here http://www.elfi…pic&topic=2468, I developed some features concerning relations between publications.

While doing this, I missed some features, where I had to find some workarounds for:

a: Configuration for input-fields: I would like some possibility to tell the fields some options (as it is done in Formexpress). I needed this for my own input-plugins (which generate selection-lists of one or more publications of a certain type). I would have liked if I could have told the field the type (and a filter statement) of the selectable publications via an options dialog. My workaround was to put the parameter after an underscore (like this: rel_4) into the fieldname and parse it (but I could not implement the filter-feature this way)

b: Possibility of operations in a workflow before the form is displayed: This could enhance the functionality of pagesetter even more towards feproc (I think this would even make it obsolete). I could preload some data from other sources (I will need this for LDAP). Ok, this could be done with the help of input-plugins (but then I would need feature a even more), but it would be a nice addition doing this via workflows, for I could integrate this preload feature more sophisticated (LDAP-example in a workflow: If no state is given, preload the data from LDAP, in approved state save the data even in LDAP). This could be done via an additional "pre" argument in the operations tag!?

c: Integrating the features mentioned here directly into pagesetter: This means just to enhance the code of "getPubList" towards an additional "related=" argument, which is handled similary to the "filter" argument. To do this smoothly, it depends on feature a. I would like to do it and contribute a patch, but to do this I need feature a, because I am not too much into this guppy thingy...

d-z: much more stuff: This would be too weird :-), but I have much more ideas concerning forms...


I had the idea for this features when I began developing an own module (after heavily hacking formexpress and feproc), which should integrate the features of FormExpress, feproc and Pagesetter (and even the relations feature and some more stuff) into one module. Forms and workflows should be defined as xml, because I was very unsatisfied with the way feproc does things.
Then I took a deeper look into pagesetter 6.2.0 and saw that many features I was trying to implement into my own module where already there, and I decided not to work on my module anymore but rather contribute some code to help implementing some still missing features into pagesetter (if they are wanted)...
My goal is to make FormExpress and feproc obsolete for the most tasks, because it costs too much nerves fiddling with 3 modules (each with its own logik and outfit) just to do some easy tasks while it can be done completly with one module...



edited by: casi, Sep 25, 2005 - 01:36 PM