ernst bunders <[EMAIL PROTECTED]> wrote:of corse, sorry..
well, that's the problem. I'm not using the mm:useinput.
Er, actually it is <mm:fieldinfo type="useinput"
I was not aware of this. Maybe it should be made more clear in the documentation?
In preveous taglib version this was not a problem, but now it is. The problem uccured in the kbase (that i am now in the proces of putting online). It dous most things in java and only some in 'taglib'. Anyhow i fixed it by adding an underscore to a parameter name if the request object returns null unexpectedly.
Sigh...
I have allways seen the fieldlist and fieldinfo as a conveniant way for quickly making a form for an object. Of course if you use only taglib for your logic you will allways use the 'useinput' tag to process the input. This is not allways feasable though.
E.g. when not? We could perhaps fix that. input/useinput is implemented as a combo, not to be used stand-alone.
Anyway im'n not allways using the taglib all the wasy becouse i don't like kind the code it yealds when you have a lot of logic. I guess by now it pretty much possible to do everything with the taglib, but you get a lot of code that is not very readble and maintainable. besides sometimes i find it a bit dounting to figure out how things can be made to work using taglib alone. For websites it is really ok, for webapps i like to seperate the logic from the templates. It is allso a matter of taste.
i quote the documentation, fieldinfo type=input:It seems logical to me that the name of the formfield equals the fieldname, and i would allso consider this as a backwards compatability issue.
It is a backwards compatability issue, but I'd say that only for misuse of 'input' in the first place.
It is not logical that the formfield equals the fieldname, because what
should it do when uploading multipible objects, what if other objects with
this name occur? I think that 'automaticly' generated id's should be
recognizable as such, and because of that I perhaps added the leading _.
*"input* A form entry for the field. If the surrounding FieldList has an id, the names of the form entries will be prefixed with it."
It seems to me that this optional prefixing is an excellent solution. It seems to me the underscore is meaningfull only if a prefix is being added.
maybe you're right. I guess if anybody dous so, and is reading in, they should respond. If it's just me, there's no reason to change back.
I'm shure i have used the tag like this before. So, i quess that you should change it back, but decide for yourselfe.
I'm not sure yet if I should change this. Perhaps there are lots of people
who hacked like you.
I don't use the bugtracker becouse i don't know the conventions. I actually thougt that it is used by committers. If not so, i will use it in the future. are there any regulations that i should be aware of?
Anybody can use it to submit bugs. I must admit though that it is not sufficiently interactive and it would probably not have facilitated this discussion.
Michiel
