Rob, I like the idea of two different object types. Having one object to represent the publication and another object to represent its pages would make for a cleaner solution.
Thanks for replying, Curtney On Friday 13 August 2004 01:03 am, Rob Vermeulen wrote: > Hi Curtney, > > Your plan sounds like a good solution to accomplish what you want. > Personally i would consider to use 2 different object types. One article > object type, and an (Article) item object type. > I this way you can easily find out which articles you have without > confusing them with the items. > It also makes it more strict that you can relate articles with e.g. your > portal or with a magazine, and that you cannot publish only article items. > > But both solutions would do the job. > > success, Rob Vermeulen > > Curtney Jacobs wrote: > > Greetings! > > > > I am trying to implement a paging (Page 1, Page 2, ...) scheme for > > articles/publications that span more than one page. This kind of paging > > scheme can be seen on javaworld, java.net, etc. or any site that publish > > articles. I would like to know how this can be done using mmbase tags. > > > > My initial plan was to have each page be an object and relate these > > objects > > together. For example, a news object can be related to other news > > objects via > > posrel. When displaying a news item A, I can test for the presents of > > related > > news items (pages) to news Item A. Subsequently, displaying the > > appropriate > > links. > > > > Is the above a plausible solution or is there a more simpler way to this? > > > > > > _Curtney
