On 11/22/05, Allen Gilliland <[EMAIL PROTECTED]> wrote: > So, I think what you have on your site looks pretty cool, but I'm not > sure I see why it should be part of our core application?
I don't think it should. But I want to maintain it without hacking at the Roller core, so I could publish it as a separate package/jar that users could deploy on top of Roller. > I think that we can definitely do some things to make some of your > modifications a bit easier to plugin to Roller, but I don't think you > are ever going to have a way to store additional data like your latitude > and longitude data without hacking at the application a bit. While building it, I thought it's possible. The geo info is in a separate table that joins against rag_entry. The class is a subclass of PlanetEntryData in a separate package. To generalize, I think plugin authors can use Hibernate subclasses to do it. > To be totally honest, I think I would like to see a little *more* > separation between our Planet Roller aggregation tools and the core > Roller blogging tools. I am just thinking out loud right now, but I > like the idea that a Roller admin could download both of those > components separately and piece them together if they wanted to. > > In any case, I prefer to have a more trimmed down application that is > more focused, rather than adding more and more stuff. By that line of reasoning: many of the Roller features can be separate plugins (or Spring-managed beans if we adopt that framework). The separation between aggregation and blogging can be the basis of a blogging tools suite, and Roller as it stands right now their integration.
