From: Sergey A. <se...@ac...> - 2003-08-27 14:22:06
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> Hello all,<br> <br> Actually I do not see any points to remome prefix except one: jump put of <br> PN. Why? There are a lot of modules and blocks, that was written for PN,<br> using pnAPI, and a lot of ppl continued write software for PN. Why you want<br> to drop compatibility? I'm sure, PN team not going to drop prefix. Compatibility<br> layer? Good idea. But why? For useing enoAPI, envoHTML and so on?<br> Ok, let's create compatibility layers for all open source CMS you can find.<br> Do you really need it? Probably you, guys have to do a lot of work to cleanup code<br> before change compatibility level of Envo. What do you mean "central api"?<br> Guys, there are "central API" - this is pnAPI. It was developed a long time, a lot of<br> ppls are using it, and you decided to destroy that? Why? To make Envo dominant?<br> You have to think more to start this work. Main goal of using pnAPI - compatibility<br> and it's not nessesarly to create additional layer . If you want to, just create ENVO <br> compatibility layer, and write all you, guys want, but leave space for those, who<br> want to use Envo core with pnModules and pnBlocks. <br> <br> Don't forget to remove _pn_ prefixes from table and column names - that will be<br> "point of no return" for Envo.<br> <br> Thank you very much. <br> <br> Serg aka Goblin.<br> <br> Eric Barr wrote:<br> <blockquote type="cite" cite="mid20038272142.786407@xenomachine"> <pre wrap="">I am actually in the planning stages of such a system now. The goal is to be able to have compatibility layers for any cms system that uses a standard central api. There are several different ways to approach this that I'm looking into and it will all boil down to the method that is most efficient. Keep the suggestions coming in, creative ideas like this are what we need around here! Eric Barr Project Manager :: E n v o l u t i o n On Tue, 26 Aug 2003 18:40:30 -0400 (EDT), Mark Chaney wrote: </pre> <blockquote type="cite"> <pre wrap="">I like the idea too, couldnt there also be an compatibility layer or api that would be able to tell old pn or env mods where to look for the current api's, etc. Just an idea, but i know in the past we were looking at somethig like that. -MACscr </pre> <blockquote type="cite"> <pre wrap="">On Tue, 2003-08-26 at 14:03, Eric Barr wrote: </pre> <blockquote type="cite"> <pre wrap="">I would like to suggest the removal of all prefix's such as "pn" and "env" from the filenames in the codebase. Prefix's in my opinion should be reserved for package naming. Does anyone else have an opinion on this? If so sound off! Eric Barr Project Manager :: E n v o l u t i o n </pre> </blockquote> <pre wrap="">I agree. But I also think we should go ahead and standardize on the no- prefix thing for all code as well. Cause if the core code is "prefix-less" most modules would require a rewrite anyway because they will no doubt make calls to the old prefix code left over from postnuke...for example pnAPI.php Zoom ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:<a class="moz-txt-link-freetext" href="http://www.vmware.com/wl/offer/358/0">http://www.vmware.com/wl/offer/358/0</a> _______________________________________________ Envolution-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Env...@li...">Env...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/envolution-devel">https://lists.sourceforge.net/lists/listinfo/envolution-devel</a> </pre> </blockquote> <pre wrap=""> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. <a class="moz-txt-link-freetext" href="http://thinkgeek.com/sf">http://thinkgeek.com/sf</a> _______________________________________________ Envolution-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Env...@li...">Env...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/envolution-devel">https://lists.sourceforge.net/lists/listinfo/envolution-devel</a> </pre> </blockquote> <pre wrap=""><!----> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. <a class="moz-txt-link-freetext" href="http://thinkgeek.com/sf">http://thinkgeek.com/sf</a> _______________________________________________ Envolution-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Env...@li...">Env...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/envolution-devel">https://lists.sourceforge.net/lists/listinfo/envolution-devel</a> </pre> </blockquote> <br> <pre class="moz-signature" cols="72">-- Thank you, -- Sergey Alexandrov ACT Inc. Tel: (770) 935-0300 FAX: (770) 935-0303 email: <a class="moz-txt-link-abbreviated" href="mailto:se...@ac...">se...@ac...</a> </pre> </body> </html> |