From: George B. <gbr...@lu...> - 2004-08-06 00:00:00
|
For some reason, I didn't get Eloi's response to my original message (his response is copied below). Anyway, the more I think of it, the more I think what would be useful is a core section class that's designed to work like the item class. The item class has to be told what table to use in the database (so the module using it does the table creation on boost) and the item class goes looking for the calling class and its variables and checks how they line up with the columns in the table. There are probably other neatsy-keen techniques involved, but that allows one to use the item class to store just about anything as an item. A section class could do the same, and if the programmer were happy with the basic capability (to edit and view sections consisting only of text or image or both, and a subtitle), she could use it pretty much un--altered. Anyway, there is no core section class. I could write one, I suppose, based on PHPWS_Section. But maybe that's not the best way to proceed. I've been thinking of a newspaper module that offers a choice of several layouts, each with one or more sections, and lets users edit each section to add title, text or image or both as in article or Pagemaster. To create an edition, you choose a layout and then fill in the corresponding sections. It shouldn't be too hard to do, but I was trying to shortcut things by commandeering Pagemaster's section code. Which I can do, of course, by simply copying it and changing some parameters. Does that make it clearer, Eloi? George > It"d work, but you"d have to consider things like how to keep it from > creating a new page instead of a new newsletter and so forth. > > I"m not certain you"re attacking the basic question from the right > angle, though. > What are you looking for in this Student Newsletter Module? |