Item8674: MultiTopicSavePlugin what I would ideally have is a means to add a few parameters to SEARCH to make the SEARCH writable

Rather than introduce completely different syntax, ideally this plugin would have the means to just add a few parameters to SEARCH.

This would make the SEARCH writable.

Also, the SAVEINPUT types should default to the form defaults for the field, rather than needing them in the page.

-- MartinCleaver - 05 Mar 2010

You have two thing in this

• You say it should be part of SEARCH. Well. Search is pretty heavily loaded. Maybe one day we get a core feature but as part of SEARCH? I don't think so.
• Yoy say that the default type should be the type from the form. Yes. Maybe. I have considered this BUT that requires that
  • The plugin keep on asking the form definition for the type. The type is not part of a topic today. So the plugin would have to look up the actual type again and again. Maybe I could somehow cache it so it only happens once. I will think about it.
  • The plugin would need a little extension to also include date fields. I plan to do that also

It is however important that the plugin can present a different type than used in the form. For example when you want to use the plugin to add additional values to a multivalue field. In this case it is often desired to use a plain text field.

Keep on giving me good ideas. I will keep this one open and come back to it.

-- KennethLavrsen - 05 Mar 2010

Yes, I'd certainly want to be able to override the type in the form. But, consider that I might design it in the Form and would have to repeat the definition in the (my case) grid. Then I change my mind in the Form and I have to repeat the change in the grid.

Unless I want to make them different I'd want the grid to follow whatever is in form.

-- MartinCleaver - 05 Mar 2010

WRT: Search - even if it wasn't part of SEARCH it could take exactly the same parameters, but then be called SEARCHEDITABLE or something.

And I appreciate SEARCH implementation is complicated but I suspect the implementations will be more complicated if not reconciled.

M.

-- MartinCleaver - 05 Mar 2010

This is a bug report that suggests an enhancement to core and not a bug report or enhancement to my plugin.

This is a HUGE proposal that has to go through a feature proposal - which I would be one of the first to raise concern against. I think this would not be a thing to add to SEARCH.

The other part of the proposal is covered by another item and feature proposal concerning API to Form.pm.

Until a feature proposal is made AND committed AND accepted this bug item cannot be actioned. SO I No action it now.

-- KennethLavrsen - 08 Mar 2010

Commenting is disabled while not logged in