> The big question is how web2py will evolve with regard to plugin/ > appliance architecture, because that would determine how to go about > adding geo stuff in a systematic manner. I'm not sure I'd like > it as a t2-style addon, but then again adding it to the core would > mean way too many dependencies and try/catching. That's an interesting point. Very cruicial actually. I must admit not having read the manual, yet. But I hope that there is a way to add functionality on top of the base system without a) modifying the core b) needing to add the files to each application again.
Maybe Massimo can highlight here. For instance: I would start with a OpenLayers map widget that could be inserted in any site (page, wiki) and administered through the wiki. As far as I know, turbogears do solve this by distributing every appliance as a package. This introduced a culture of small applications with many dependecies (something Massimo apparetly wanted to avoid). Sofar, I do not have an idea. I think there should be a generic plugin functionality to add new features to core without modifying it and regardless of the inidvidual appliance. Kind regards, Timmie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
