Ryan,
I see your logic here. We are going to be doing re-writes of several
modules for the 0.9.3 release so they use the Item/Manager classes.
During this re-write would be the best time to try and implement something
like this. It would require working out several issues before any
implementation could happen. Here's a few I can think of off the top of
my head:
FatCat would need a module to specify which categories it should create,
easy part. You would then need a method for selecting items from the
category without creating confusion to the user, a little harder. Then,
once the item has been selected, you must make the page, event, or link
aware of the categorized item it uses, again not too bad just tricky.
Then, you would need to take into account a categorized item that gets
deleted. This could be the worse of it. You would have to traverse the
items using the deleted categorized item and either remove it or set it to
hidden or something.
> Since my group has a great deal of interest in the Pagemaster module due
> to its importance in our use of the system, I have put considerable
> thought into it.
>
> One of the thoughts that I had was in regard to the Categorizer. Firstly,
> I am considering expanding Pagemaster's ability to add images to a page.
> Obviously if people are allowed to upload their own images each time they
> want to add one to a page, it could lead to severe file duplication on the
> server. My thought is to use the document manager to upload the images
> and handle them. Here's where my thought regarding the Categorizer comes
> into play.
>
> Say that the categorizer comes with some specific categories (i.e.
> Pagemaster->Images, Pagemaster->Links, etc), to which administrators,
> wishing to create a portfolio of images for use in the Pagemaster module,
> could add their images. Then in the pagemaster module, when a page
> creator is trying to add an image to their page, they get a portfolio of
> images made up of all the images in Pagemaster->Images.
>
> This would work for other modules as well: Menuman->Links,
> Calendar->Images, etc.
>
> It seems to me, and please correct me if I'm wrong, that so far the
> categorizer module has been used to group items together within a module
> for relevance. All sports related pages/announcements are distinct from
> all science related pages/announcements/etc. The reason I think this
> would be most beneficial is that it would take that distinction and allow
> it to be of use in the functionality of other modules (which is something
> that I don't see it being used for yet). Plus I don't see it as being too
> much of a change in code as much as a change in the way other modules use
> the categorizer.
>
>
> These are just my meandorings, but I was curious what the developer comm.
> thought about it. Let me know if I jumped around too much and need to
> explain anything better... I tend to ramble :)
>
>
> Thanks,
>
>
> Ryan Roland
>
> Application Developer
> Information Technology Department
> Division of Recreational Sports
> Indiana University
>
> rmr...@in...
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
--
Adam Morton
Developer - Electronic Student Services
http://phpwebsite.appstate.edu
Founder - Appalachian Linux Users Group
http://alug.appstate.edu
|
