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 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.
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.
-- Allen
Miguel A Paraz wrote:
On 11/22/05, Allen Gilliland <[EMAIL PROTECTED]> wrote:
I am thining along the same lines as Anil on this one. It's hard to tell
exactly what Miguel wants to do without seeing a more complete description, but
if the approach is as grandiose as it sounds then I would be hesitant. I am
certainly in favor of making things pluggable, but I would not agree to expand
the app to do things it really doesn't need to do.
My needs are not grandiose. :) My changes can be done without hacking
Roller, so I'd like the infrastructure for that.
For my current work, temporarily running at:
http://recovery2.blogdns.org:8080/roller/ , I
1. Stuffed in a new ROME module (their name for "plugin" it seems )
for parsing GeoInfo, but I had to hack PlanetManagerImpl to add module
checking
2. Added a joined-subclass for PlanetEntryData to hold the
latitude/longitude. This did not break the existing tables but added a
new one.
3. Added an Action to draw the Google map, filtering out only
aggregator entries that were instanceof my new joined-subclass.
These 3 were in my own package hierarchy under src/ so I'd like the
ability to publish this in the jar.
The other changes:
4. A new JSP in web/planet as the view for the Map Action
5. Since I just stuffed #1-3 in the same source tree, I had to hack
build.xml which relies on a bunch of includes/excludes based on
package name. Nice if we could have separate trees for the parts with
different dependenices.
6. (not done) Publish a new aggregator feed with the GeoInfo. I don't
know if a Velocimacro can do instanceof to publish selectively- think
no.
My plans are at:
http://migs.paraz.com/w/archives/2005/11/10/roller-based-geo-aggregator/
For the code, I could tar it up or diff it for your inspection.
I believe a dependency-injection approach would be good for
modularity- Roller or the proposed ASF blogtools could be
Spring-hosted like say, ActiveMQ.
Even if my needs at the moment are on the aggregator part, I think
blog server authors would like Roller as a toolset which they could
break apart to get the parts they need.
