On Tue, 2006-02-28 at 16:44, Sean Gilligan wrote: > Allen Gilliland wrote: > > one entry per page is just a permalink and roller alreayd supports > > that. by default a permalink will contain links to the previous/next > > permalinks chronologically. > > Right. The permalink page has links to previous/next. I'd like the > home page and the category pages to be (or look like) the permalink > pages of the most recent entry (in that category.) I'm not sure what > the best way to do that is...
I'm not sure I understand what you here. Do you just mean you want them to be pagable? Do you want the blog homepage to only have a single entry on it and then be pagable like the permalink urls? > > I don't fully understand how the Weblog template, Velocity context, and > macros are used to handle all the different request URLs they can be > fed. I've looked through the User Manual, Wiki, and used Google, but > haven't found a detailed introductory explanation. I've looked through > the Macro code and the Java code, but haven't (yet) spent enough time to > fully understand how everything works. Unfortunately, I think that process is a bit wacky myself. I couldn't give you a definitive answer, but I believe the objects available in the Velocity context is meant to include what Roller thinks is the proper set of data needed to render the given page. The loading of the velocity context is pretty much the same for all servlets, I belive only having small changes here and there. The bum part is that I don't think there is any concrete way to know exactly what objects you have access to for any url, other than trial and error or tracing through the code. Speaking somewhat abstractly I think my issue with the current process is that Roller tries to do too much for the user, rather than just giving the user access to all the relevant data for their weblog and letting them format it however they like via their templates. I am also not really a fan of the idea of prefetching data for the velocity context, since we don't really know what data is meant to be used anyways. In the long run I would prefer to see an nice object hierarchy/api placed into the velocity context which provides the user an easy way of accessing any data specific to their weblog. IMO many of the macros also try and do "too much" and in some ways end up making things more confusing. I think my biggest pet peeve would be that we do a little too much of this ... #showSomeUrl() and then out pops an html anchor element. while that works i like the idea of having the user do the html part themselves, like this ... <a href="$roller.someobj.properUrl" class="foo">$roller.someobj.properUrlText</a> and we wrap all the proper logic for constructing the url into the code somewhere. > > i don't think there is an easy way to have > > a permalink point to the previous/next permalink in a given category. > > What's the hard way? hacking away at the code :( -- Allen > > -- Sean >
