Hi, I was thinking about splitting my current application into a smaller core and a number of plugins. I would like to be able to represent the plugins as data of a Model but I think there are better ways of doing this than what I have managed so far.
Almost all functionality accessible to logged in users will be plugins. I wanted to avoid using SQL for the data since there will usually be between, say, 3 and 8 plugins for each installation and all basic information about the plugins will be "static" once the installation is done. Having a table with 4-5 fields and 3-8 records has felt clumsy so far. But I still want to be able to link to a plugin using associations. For example I would like to have a "main menu" displaying links to each plugin available to a certain user. I also want real restrictions based on user->plugin association. Things like that. Is there a way to setup a Plugin Model without a table and instead take the data from a configuration file of some similar source? Sort of like a Fixture even though Fixtures actually load their data info the database and then work like normal Models. If using a fixture for the data does not give me a great overhead (extra SQL) it would be a possibility. When I build a new plugin it would be more natural to enter some data for it in a php-file instead of creating SQL data and remembering to update the db in each installation at the same time I upload the new files. Any tips and experiences in the field of alternative Models greatly appreciated. /Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
