Hello guys,
This goes a bit off-topic, but is still related.
Tarjei Huse wrote:
<snip />
18:31 <@torben> now to 2. 18:32 <@torben> define ""latest" section of all subpages" please 18:33 < tarjei> in "normal" midgard I'd do mgd_list_topic_articles_all($id, 'date') 18:34 < tarjei> where $id = root_topic 18:34 <@torben> ah 18:34 <@torben> you want f.x. the latest 5 changes of the site? 18:36 < tarjei> yep 18:36 <@torben> hm 18:36 <@torben> ok 18:36 <@torben> this is not that easy out of the boxx 18:36 <@torben> and calls for some helper in midcom_helper_nav actually 18:36 <@torben> what you need to do: 18:37 <@torben> recursivly iterate over the whole site, load all topics and nodes into an array indexed by the revised nap timestamp 18:38 < tarjei> I'd say ouch. Yes 18:38 <@torben> perhaps you could skip the topics, but i'm not sure there, it would depend on what the user wants i think 18:38 <@torben> it is not that bad, if you use midcom's caching 18:38 <@torben> the list would have to be generated only once per db change, and would then come out of the cache 18:40 <@torben> i think it is feasible, regarding the performance of the sitemap, which isn't that bad. 18:41 <@torben> i also think it is a way with a good future, as with the nap metadata interface the chance for a nap data cache is quite high 18:45 <@torben> tarjei: you've got an idea about what you need? 18:47 < tarjei> yes 18:47 < tarjei> thanks a lot.
We've been thinking about a new component that would list the latest changes on the whole site/part of a site. It would be a great feature to this component to offer a dynamic_loadable interface (i.e. /mytopic/latest/5) which could be used on frontpage or sidebar of a site.
The content tree traversing would be similar to the d.l.sitemap, which still lacks some crucial features like ViewerGroups support.
So, I'd vote for making a helper function for traversing a content tree. Then both d.l.sitemap and the "latest updates" components could use it as the basis (to build a gigantic array or something).
Another alternative would be to make NAP be aware of the latest documents (articles/topics) in the given tree (this could be from the site root or any topic in the tree). This might be the most efficient way to do it, since NAP has to traverse the tree all the time anyways.
Torben, any comments?
Tarjei
Cheers!
//Henri
-- Henri Kaukola [EMAIL PROTECTED] Consultant Tel: +358-20-198 6037 Nemein Oy http://www.nemein.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
