Re: Module re-write question
"MADHATter7" <[email protected]>
| Newsgroups | gmane.comp.web.envolution.devel |
|---|---|
| Message-ID | <002501c241aa$79a1fc60$431e4ed8@t6a4q5> |
ak: Answers are below: ----- Original Message ----- From: "ak" <[email protected]> To: <[email protected]> Sent: Saturday, August 10, 2002 8:53 AM Subject: [envdev] Module re-write question > Hi gang, > > I got some time on my hands today, so I will start on "sections" module > rewrite. Several questions before I begin: > > 1. Are we going for 100% API compliance? If yes, what are the changes > (additions) are planed for 1.00 release? Yes, eventually all modules will be API compliant... however not in the 1.00 release. We are going to cleanup, revise and enhance the API to meet Envolution's needs. However, if you wish to code to the API now, that would be outstanding. (Just bear in mind the pnHTML is deprecated) Ideally, rewritten modules would use Encompass methods... but for 1.00 this is not a requirement. > 2. What is our code base? PN0.714 or PN0.20? Does not make any > difference to me, but IMHO, we all should be on the same page here. We will officially fork at 0.714 --however, we are going to be reviewing and making some changes based off the 0.72 release... > 3. Is there going to be a CVS setup or someone will take on integrator's > and coordinator's duties for the time being? We have our own project at SourceForge, Envolution is the name. I personally can not get my CVS Client and/or SSH configured properly yet. I should have this (properly) setup tomorrow. I suppose MagicX and myself are coordinating for the time being, but this may change here in the not too distant future. > 4. As I understand, there will be an upgrade path for PN users. A > suggestion, if I may. Let's pick one "stock" release (PN0.714 for > instance) and tailor all upgrade scripts to that one. It is going to be > a mess, IMHO, to try to support (upgrade wise) all legacy releases. But, > as I said, just MHO. Agreed here, we will do an upgrade scipt from PN 0.714 to Envolution 1.00... this is the best route to take, IMO. Anything less would be a serious mess :( > Well, I guess that is all I need to know before I start cleanup and > minor feature additions for "sections" module. > > Good luck to all, > > ak Thanks, mh7 > _______________________________________________ > Envdev mailing list > [email protected] > http://www.madhatt.info/mailman/listinfo/envdev_madhatt.info >