Re: SF Tasks

I dont know all the details, but an api is already developed or being
developed to switch out the env with the pn api when needed. I was pretty
inpressed when i first heard about it.

-MACscr

----- Original Message -----
From: "josh" <[email protected]>
To: <[email protected]>
Sent: Tuesday, September 10, 2002 3:57 AM
Subject: Re: [envdev] SF Tasks


> Not that I have any say, but I would encourage the use of deprecation
> instead of removal.  So instead of removing pn methods, simply add
> corresponding env methods and phase out the pn methods in the next major
> release, or whenever.  Actually, if it were my call, I wouldn't phase
> out the pn methods until envolution had developed a strong support
> network of third-party module developers using its own API.  That way
> backward compatibility would be maintained and users could continue to
> use old postnuke modules until a newer envolution module was released.
> Third party modules are key, and the system that gives me the most
> choices is the best choice.
>
> jOsh
>
> On Tue, 2002-09-10 at 00:37, Antonio Delgado Frias wrote:
> > Hello all,
> >
> > I dont know if this is the place to discuss SourceForge's tasks or the
> > project's forum at SF, so please tell me to not post again in the
future.
> >
> > I've been asigned a task named: "Corrective Branding: Removal of all PN
> > branding, schemas and methods. Conversion to Env styles, and the
> > compatibilities related to this task." and surely I'm wrong, but if I
> > understand the goal of this task, should we rename all current functions
and
> > class methods like pnSomething to EnvSomething? In my sight this could
bring
> > enormous compatibility drawbacks with 3rd party modules and we'll have
to
> > recode every module/block.
> >
> > Am I saying nonsense? Or did I misunderstood the task?
> >
> > Best Regards,
> >
> > Antonio Delgado
> > (aka addf)
> >
>
> --------------------------------------------------------------------------
------------
> > This message and any files transmitted with it are confidential and
intended solely
> > for the use of the individual or entity to whom they are addressed. No
confidentiality
> > or privilege is waived or lost by any wrong transmission.
> > If you have received this message in error, please immediately destroy
it and kindly
> > notify the sender by reply email.
> > You must not, directly or indirectly, use, disclose, distribute, print,
or copy any
> > part of this message if you are not the intended recipient. Opinions,
conclusions and
> > other information in this message that do not relate to the official
business of
> > Ydilo Advanced Voice Solutions, S.A. shall be understood as neither
given nor endorsed by it.
>
> --------------------------------------------------------------------------
------------
> >
> > _______________________________________________
> > Envdev mailing list
> > [email protected]
> > http://www.madhatt.info/mailman/listinfo/envdev_madhatt.info
>
>
>
> _______________________________________________
> Envdev mailing list
> [email protected]
> http://www.madhatt.info/mailman/listinfo/envdev_madhatt.info