Jean-Philippe PIALASSE
2018-02-04 18:48:37 UTC
Hi all,
As John is making a good advance and we have seen also the possibility
by Stefano's great work and Tony's, we might need to think about how we
could make the new manager more modular.
1/ Curtently every new contrib has its own page in the manager. So if
you want to add a property to handle an ibay (let's say Allow Override
fro .htaccess files) then you create a new page listing all ibays and
alow to modify this.
A more user friendly way would be to add this on the existing page of
the ibay.
This would need to either plan a hook on the display and processing
functions, either to use a sort of configuration file to list the field
to display /process and how to check them and what function to use to
process them.
2/ Currently everey new panel needs a complete page of code. It could be
great to be able to instead parse a configuration file with a list of
fields, type of field, link in the db and events that need to be
processed. That way people without any perl knowledge will be able to
easily create a new page or to add field on existing pages.
We could then either have an init fucntion to read all the config files,
or simply use our template system to generate a config file per page. A
contrib will simply add a fragment where needed to alter a page.
Any idea? Suggestion ? Other known alternatives ? Known limitation ?
As John is making a good advance and we have seen also the possibility
by Stefano's great work and Tony's, we might need to think about how we
could make the new manager more modular.
1/ Curtently every new contrib has its own page in the manager. So if
you want to add a property to handle an ibay (let's say Allow Override
fro .htaccess files) then you create a new page listing all ibays and
alow to modify this.
A more user friendly way would be to add this on the existing page of
the ibay.
This would need to either plan a hook on the display and processing
functions, either to use a sort of configuration file to list the field
to display /process and how to check them and what function to use to
process them.
2/ Currently everey new panel needs a complete page of code. It could be
great to be able to instead parse a configuration file with a list of
fields, type of field, link in the db and events that need to be
processed. That way people without any perl knowledge will be able to
easily create a new page or to add field on existing pages.
We could then either have an init fucntion to read all the config files,
or simply use our template system to generate a config file per page. A
contrib will simply add a fragment where needed to alter a page.
Any idea? Suggestion ? Other known alternatives ? Known limitation ?
--
*Jean-Philippe Pialasse *
*Jean-Philippe Pialasse *