Hey Stef, About the templates: using a template engine will allow users to easily customize templates and it will also make upgrading much easier than if you use static templates.
If you want to make upgrading easy for your users then I would suggest you script your software using object orientated code so they can use it as a library. If users would like to modify your application they can do this by extending your class(es). This is how the frameworks like Zend and PEAR work. Upgrading will of course have to be done manually for best security and compatibilty but if you really have a reason to automate upgrading, say for example with the use of crons or at a trigger call the user will have to certain folders writeable to everyone which is not recommended at all. I can't really help you with choosing a framework since I use different ones myself, for example I use the Zend DB engine as I find the PEAR MDB2 way to heavy and since Zend focuses on PHP 5 no extra code is included to ensure PHP < 5 support. And I use several PEAR classes because either Zend's does not meet my needs or it doesn't support the feature/service I require. Just browse the PEAR packages and the Zend framework packages, compare them and use the one which meets you needs. There is no need to keep yourself to one. On Fri, Mar 28, 2008 at 9:51 AM, Stefan Schwarzer < [EMAIL PROTECTED]> wrote: > Hi there, > > I don't know anything about ZEND. And before starting to plunge into it, > it would be great if someone could give me a hint or two to comment if we're > on the right track with what we want to achieve. > > So, here's the situation: > > We've developed a dynamic Data Portal ( http://geodata.grid.unep.ch ) over > the last years; it gives UN organizations (and in principal: everybody) > access to a broad range of data (> 500 unique variables), with possibilities > to draw maps, graphs and tables and to download the data in various formats. > > Now, we're thinking of developing an "opensource" package, which > interested bodies (especially Environmental Ministries with whom we're > working) could download, install and use to serve/distribute their data. > > But how would then the updating of these portals been done, when a new > release (with new functionality or/and fixed bugs) appears? As they will > surely customize the interface and eventually as well add/change some of the > features & functions, it's difficult for me as a > less-than-semi-professional-developer to understand how this could be > achieved. > > We're working with PHP templates… so layout and functions are somewhat > separated. But I guess this has to go much further, transforming our > existing functions into PEAR or ZEND libraries for example or using > webservices for some of the dynamic stuff… > > If anyone has a moment to give us a hint or two, that would be great! > > Thanks a lot, > > Stef > > (PS: We're using Linux, PHP, Postgres, Minnesota Mapserver and JpGraph.) > -- Isaak Malik Web Developer [EMAIL PROTECTED]
