XOOPS
add reusable category module/api
Hello, Instead of recreating categories or tags code in xoops why not create reusable code and database maybe in the sql have module name for what the categories system is for. would also speed up development for other plugins.
I can also create concept if you like in xoops api
Thanks for the suggestion! Go ahead and create the concept, so we understand better what you have in mind, and can discuss it in more detail. Thank you!
Richard has brought a new item to 2.6 that is still under development that hasn't been announced yet called the service manager. This would be a great module to make use of the service manager which is built to expose things like this to other modules.
Since it is under active development by Richard he might be the best source but after this week I will be out of school for the summer and will be spending a large portion of my next 4 months working on moving core related code and extensions to the Service Manager model so I can help support this if you want to code it from scratch. If you are unable to code I could perhaps look into it but I will be working on the 2.6 core or core included code first so I can not promise I will get to it this summer.
I am not sure of Richards Vision but mine is that we should be making building blocks for modules into the service manager and going from there. This is one of those building blocks and would be a great addition.
So feel free to email me directly if you want. I will be done with exams by Thursday this week and plan to get back to my Xoops coding on Monday.
Rodney
Date: Sat, 19 Apr 2014 14:08:29 -0700 From: [email protected] To: [email protected] Subject: Re: [XoopsCore] add reusable category module/api (#124)
Thanks for the suggestion!
Go ahead and create the concept, so we understand better what you have in mind, and can discuss it in more detail.
Thank you!
— Reply to this email directly or view it on GitHub.
Yes! We need a category or taxonomy module. I would love to see your concept.
Rodney is correct, I would want it to work through the service manager. I would expect the module you are suggesting to allow the creation and maintenance of the category hierarchy. Additionally, it would define an API that would provide a way to associate content with a position in a hierarchy, list content associated with a position in a hierarchy, render a "breadcrumb" representation of that position and/or a list of categories and links needed to create such a representation.
I would also like everything in that "Additionally" section as part of an interface that defines a taxonomy service. That way, while there is a way to create your own taxonomy using this module, by installing a different taxonomy provider module you could get a standard predefined taxonomy as exists for many disciplines. This would give us the flexibility to handle that need without having to rewrite any modules.
If this hasn't sent you running, I'll send you the docs on the service manager ;) This is the kind of situation it is designed for; separating the attachment of services to the modules which use them from the implementation details of the service.
yea this was my idea as I always seem to rewrite the same thing over and over as I also thinking even form builder too as these are 2 elements that all modules would need where on the backend where in the api we would register forms where in the module itself you can build forms, categories and tags as I done this before with my own custom cms that uses smarty so sure it would not take much to bring something similar over to xoops we could even write some compact classes if we end up changing how the core works to make sure it still works as it did before but maybe we developer debug level for developers are encouraged to change to the new function and telling them what they should use instead.