Menu
▾
▴
envolution-devel
|
From: Arden W. <ar...@li...> - 2003-05-30 12:58:14
|
Okay these next few days I learn better CVS skills. Right now I am using Cervista front end for Konqueror file manager. I can also use command line. I was able to get all the source from the current cvs but that was two weeks ago. I think much has changed and I want to update my local copy. This is what shows in the GUI please look at cvs2.png file at http://www.linuxguru.ca/download/Screenshots/cvs2.png This is from the root prompt: [root@interceptor root]# cvs -d:pserver:el...@cv...:/cvsroot/envolution login Logging in to :pserver:el...@cv...:2401/cvsroot/envolution CVS password: [root@interceptor root]# cvs -d:pserver:el...@cv...:/cvsroot/envolution logout Logging out of :pserver:el...@cv...:2401/cvsroot/envolution [root@interceptor root]# I obviously connect. If anyone can get me going sooner much appreciated. I would like to use the GUI where possible. |
|
From: <Chr...@t-...> - 2003-05-30 18:46:18
|
Arden Wiebe wrote: >Okay these next few days I learn better CVS skills. Right now I am >using Cervista front end for Konqueror file manager. I can also use >command line. > > Me too, and it works pretty nice, Cervisia and command line. Your login messages are ok. You tried to commit some files (NS-Mulltisites) which hasn't been added to CVS before, This is necassary for the version management. So please use the "Add to Repository" function from the File-menu or from the context. Here is a very nice link to CVS documentation http://cvsbook.red-bean.com/, it's a very fine docu from some of the CVS gurus (from gurus to guru ;-) ) -- mailto:chr...@t-... personal: http://www.christoph-schwaeppe.de CMS: http://www.envolution.de ICQ: 174676647 jabber gat...@am... |
|
From: Arden W. <ar...@li...> - 2003-05-31 16:42:19
|
I have no write access to the tree :( On Fri, 2003-05-30 at 18:45, Christoph Schwaeppe wrote: > Arden Wiebe wrote: > > >Okay these next few days I learn better CVS skills. Right now I am > >using Cervista front end for Konqueror file manager. I can also use > >command line. > > > > > Me too, and it works pretty nice, Cervisia and command line. > > Your login messages are ok. You tried to commit some files > (NS-Mulltisites) which hasn't been added to CVS before, This is > necassary for the version management. So please use the "Add to > Repository" function from the File-menu or from the context. > > Here is a very nice link to CVS documentation > http://cvsbook.red-bean.com/, it's a very fine docu from some of the CVS > gurus (from gurus to guru ;-) ) > > -- > mailto:chr...@t-... > personal: http://www.christoph-schwaeppe.de > CMS: http://www.envolution.de > ICQ: 174676647 > jabber gat...@am... > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Envolution-devel mailing list > Env...@li... > https://lists.sourceforge.net/lists/listinfo/envolution-devel -- Add some eLGie to your eNvironment. http://www.Swingerz.ca http://www.LinuxGuru.ca http://www.WorkWanted.ca |
|
From: Burke A. <bu...@di...> - 2003-06-02 17:41:11
|
There seem to be two places to get this right now. I don't see any
reason why we should maintain these defines in two different places,
especially a static file such as pnAPI.php. I suggest we move away from
having these defined in the php file & only have the info available via
the database.
Currently, references to _PN_VERSION_NUM exist in:
Stats module/index.php (line 462)
Credits module/pnuser.php (lines: 76, 90, 104)
The other two (_PN_VERSION_ID,_PN_VERSION_SUB) don't appear to ever get
used.
pnAPI defines:
define('_PN_VERSION_NUM', "1.2");
define('_PN_VERSION_ID', "Envolution");
define('_PN_VERSION_SUB', "Michelangelo");
and database fields:
/PNConfig Version_Num s:5:"1.2.0";
/PNConfig Version_ID s:10:"Envolution";
/PNConfig Version_Sub s:12:"Michelangelo";
The fields from the database are retrieved via:
pnConfigGetVar('Version_Num')
pnConfigGetVar('Version_ID')
pnConfigGetVar('Version_Sub')
|
|
From: TiMax <ma...@em...> - 2003-06-04 06:31:39
|
Zoom write me about this post in Portalzine, i think now is time= to explain very good to all people differences from Postnuke, so now me and Zoom work to write this document,= maybe later we send proof of this document here so you can add your suggestion before we publish= it. Feel free to go in Portalzine site and explain a little to Magicx= to check before write .... I just check that from September 2002 we start from Postnuke= 714-722 and have add lot of functions to eNvolution, Postnuke add only some little fix's ....... TiMax p.s. I m in test with some hacks and i think now envolution.com= is much fast ----------------------------------------- Hi Max, I found this post over at portalzine.de http://www.portalzine.de/XForum-tid2184.html Of specific interest is the post made by A;exander Graef so= you'll need to scroll down a bit to see his post. I'll quote it hear in case he decides to edit his posting: ---Begin Quote--- MagicX Administrator posted on 3/6/2003 at 11:54 Well I agree that envolution doesnt really provide much more functionality as postnuke. Postnuke allows the use of the native= theme system, autotheme, Xanthia or even use encompass (which is the= basis Xanthia is running on). The current user/developer community for postnuke is much bigger= then the one for envolution. And I dont see many developers jumping on= the envolution train, but in the end its a question of flavor.= Envolution decided to go their own way, which is an open source process that= is quiet popular in the open source scene (well might happen more= often with postnuke [image] ) I have been running postnuke for a long time and it always was= the basis of portalzine. I never had any performance issues. Like said= above, it all depends on your server resources. The more queries you= execute, the more power your server needs to provide. Xoops is another alternative, that provides a good stable and= fast system that can be easily erxtended and maintained. Because of= the OOP character of the system, resources are reused and execution is= optimized quiet nicely. They use a template system aswell. Well Phpnuke wouldnt be my system of choice , there are to many= things happening besides the development , which seem to center around= one person. He progressed nicely concerning features, but seeing= postnuke running completely on the new api soon, phpnuke will loose= ground. Api structure compliant modules are executed much faster and allow= the resuse of functionality across the system. Again postnuke will= allow both module types to run and allows to level your performance= better then phpnuke. Besides , the latest phpnuke release includes a= native forum, which i think slows down the core development even more.= Modules should be handled seperately from the system and should grow individually (not thinking of security issues). Hope that helps a bit. MagicX ---End Quote--- I will explain in detail how, in this post, MagicX made false= statements and perpetuates the "us versus them" mentality that some people= like to keep prominant in the "nuke" community. First paragraph: MagicX states that Envolution doesn't provide much more= functionality than PostNuke. The fact is there are glaring differences in= PostNuke and Envolution. While it is true Envolution forked from the .714= PostNuke codebase it has and still is continuing to evolve into it's own= unique code base. Just to point out the obvious MagicX did say= "Envolution doesn't provide much more functionality than PostNuke" quote,= unquote. What this means is that Envolution does provide MORE= functionality than PostNuke, juts not as much as he would prefer I guess! But I= believe his intention is to lead people to believe that Envolution is behind PostNuke in features, stability, and usfullness. Unfortunately= his FUD spreading is still based on old wounds he has from being caught= red handed stealing code and claiming it as his own original code= from true opensource and free software developers. Shame on Alexander for= at least not being a man about it and accept that the world exists outside= of portalzine and PostNuke. Second Paragraph: MagicX states that the Envolution developer community is much= smaller than PostNuke's developer community. Where has MagicX been? In= fact Envolution's developer community is larger than the current= PostNuke developer community. Our developers just don't project it's= presence like the old PostNuke developer team used to do. In fact= Envolution's official develoeper base is larger than PostNuke and Xoop's. Last= time I checked we had over 30 developers just from the English and= Italian Envolution commuinities. Add in the Asian sites, German sites,= and the new Spanish sites and I believe you'll find those numbers add up= ebven higher yet. I am also quite sure I've forgotten to mention some= other Envolution developer communities, and I apologize if I have. He also sates that, "And I dont see many developers jumping on= the envolution train, but in the end its a question of flavor..."= This is humerous. In fact since April 22, 2003 the English speaking= developer representation has increased by 6 new developers. In fact just= today we have added one more volunteer who wishes to increase the= documentation quality and library! Now ask MagicX how many developers have "jumped FROM the PostNuke= train" in the last year! I would imagine the numbers would add up to= over 100. Including MagicX himself. I know he claims to have left for time= and personal reasons..but fact is he left because he and Neo were= trying to force their wishes on the PostNuke community without regard to= what the community wanted or needs. Paragraph Three: MagicX explains that he is biased toward PostNuke. No kidding?= Maybe that explains why he continually likes to put down the Envolution= CMS and community. Now what MagicX didn't tell you is that Envolution and it's= community has had a large impact on all nuke type CMS's. In fact Envolution= was, and still is, the only community to turn over it's development= and management to the community. We consistantly solicite our= community to get involved and we frequently ask for developers to join in and= take part. Instead of sitting back like pompous fools and wait for= developers to come to us, we seek them out. Why? Because we believe in true= open development for and by the community. Email any developer at Envolution and guess what happens? You= get emailed back! Now try to email one of the developers at= PostNuke, specifically the Project Leader and see what happens! I don't mind criticism about Envolution. It is not perfect. But= it is innovative, has features PostNuke does not have, stable, and has= even affected PostNuke to explore and adopt Xantha as a theme system= for thier next release. Xantha is a fork of Encompass which has been= used in Envolution and developed by Envoilution founders. MagicX hasn't a clue what's really going on in the CMS community= he claims to be part of and serve. In fact I wouldnt be surprised if= he has other motivations besides "helping" out the communty by offering= up this kind of inaccurate and misinformed information. Zoom |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X