path: root/README (follow)
AgeCommit message (Collapse)Author
2013-02-26adjust readme.Carsten Haitzler (Rasterman)
2012-12-21update e17 readmeMike Blumenkrantz
SVN revision: 81623
2012-09-03add a readme item.Carsten Haitzler
SVN revision: 75943
2008-04-03typoPeter Wehrfritz
SVN revision: 34178
2008-04-03deps lists/ debugging too...Carsten Haitzler
SVN revision: 34177
2007-04-19update readmerephorm
SVN revision: 29606
2006-06-25Include EFL prerequisites / build order in READMErephorm
SVN revision: 23575
2005-08-24rename pointer images, different edje group names (better namespace i guess),Carsten Haitzler
rationalise pointer usage down to 1 for init, 1 for everything else. SVN revision: 16304
2004-12-01readme additiosn for the not so careful out there...Carsten Haitzler
wiljanes bg set ipc... SVN revision: 12323
2004-11-25 _ _ _ _ _____ ___Carsten Haitzler
| | | | ___| | | | ___| __ ___ ___ _______ ___ / _ \__ _____ _ __ | |_| |/ _ \ | | | |_ | '__/ _ \/ _ \_ / _ \/ __| | | | \ \ / / _ \ '__| | _ | __/ | | | _|| | | __/ __// / __/\__ \ | |_| |\ V / __/ | |_| |_|\___|_|_| |_| |_| \___|\___/___\___||___/ \___/ \_/ \___|_| I put E17's wm code into cvs. Hell is freezing over. Duke Nukem Forever will be out next week. Snowballls take up residence in Hell. The Fat Lady sings. The End is nigh... :) SVN revision: 12247
2004-11-25bye bye!Carsten Haitzler
SVN revision: 12246
2004-10-05More raster-speakxenith
SVN revision: 11751
2004-10-05let them know in the README....Carsten Haitzler
SVN revision: 11749
2003-01-15More SPLIT merging.rbdpngn
SVN revision: 6588
2001-09-24been working offline.. wheeeheee! :)Carsten Haitzler
SVN revision: 5374
2001-08-25Ok this has got some initial support with ferite, currently you can onlyboris
assign ferite scripts to menus see data/scripts/ and look at the exit menu item as an example. you will need ferite - i suggest that you use cvs ferite as this is what I am developing this against. This, my friends, is the first step of many :) SVN revision: 5280
2001-02-19oops- typo in readmeCarsten Haitzler
SVN revision: 4253
2001-02-12been working on E............ needs efsd now, desktops are now views, newCarsten Haitzler
background, lists directory, cleaned up some bugs here and there, errrr...... cleaned up menu code and some fixups, added fs abstraction init and working on it.... SVN revision: 4192
2000-12-11Sorry guys.. I had to revert a bunch of changes.. that's life.. but READ theCarsten Haitzler
following (it's in the README now) ------------------------------------------------------------------------------- Enlightenment 0.17.0 CVS Code.... ------------------------------------------------------------------------------- The Rasterman -, ******************************************************************************* **************** READ THIS! It is of the UTMOST IMPORTANCE! ******************* ******************************************************************************* This is the source code for Enlightenment 0.17 - If you got this you got it from Enlightenment's CVS repository - or from someone who took it out of the CVS repository. The CVS repository is full of code *IN DEVELOPMENT* - that often means it's in the middle of being worked on and may install strange things in strange places, make a mess, and may not even be compatible with a final release. If you at all use this code, you are HEAVILY URGED, when it is finally released, to remove all traces of anything this CVS code base has installed on your system (it is COMPLETELY up to you to keep track of that - do NOT expect any help), and then install the full release on a cleaned system. Don't come asking "can I just keep using CVS" oonce things are released - thqat is the reason I pu this paragraph here - so you don't ask. The asnwer is the same as above - if there is a proper final release use that. CVS is really only for those havily hacking on the code. Now we have that warning over and done with. How to build and install from CVS? $ ./ && make $ su Password: <- as root -> # make install You should be able to use the binary of enlightenment as a window manager. you might be advised for cleanliness to do $ ./ --prefix=/usr/local/e-17 so it installs relative to the /usr/local/e-17 directory and keeps all the e-17 development code and data in that tree so it is easily removed when the time codes. NOTES: Read these carefully! Enlightenment does not check for previously running Window Managers right now - so you need to make sure no other WM is running - E will not do that for you. Enlightenment has no menus or keybindings or any way of launching applications right now - you'll have to figure out an alternative way of doing it. Enlightenment only handles a small subset of ICCCM and thus will have bugs - some applications will not behave correctly and may apear in odd spots or not resize or place themselves properly etc. Expect this - it's code being worked on. Just be happy it does as much as it already does. Enlightenment RELIES on lots of libraires that have been written. Ecore, Ebits, Evas, Edb, Imlib2 just to mention a few. Especially Ebits, Ecore and Evas change in CVS often - you will need the absolute latest of these if you wish Enlightenment 0.17 code to run properly or compile. If you update Enlightenment from CVS update these too to get any changes they have in their trees. If you plan on working on the code... STOP! don't rush in and work on it - even if you have CVS commit access - EXPECT me (Raster) to revert any changes you make if you do this - regardless of the changes and how much work you put into them. First read the code well and LEARN it. If you have questions about some of the more obscure hidden program flow - ASK - but don't go tampering with it - Enlightenment 0.17's code is much more complex and intricate than E 0.16 - but at the same time it's much cleaner and more object oriented. Learn it well first. Some parts of E 0.17 are "hacked" with hard-coded stuff, just so, for now, it works. They will be virtualized and imporved over time. If you have plans - tell me about them first - discuss them before you go impliment them. I know I already have a lot of the components of E 0.17's code planned in my head - but I won't get to them for a while - and if people go impliment or hack bad stuff in, it means I have to spend lots of time fixing something that is bad in the first place, or we end up doing duplicate work. There *IS* a plan - believe it or not - but to be honest - it's more complex and large than I can just write down in a README, so talk about your ideas first. I'm going to be ruthless in keeping the code neat, clean and free of nasty hacks (except ones I put in as temporary stop-gap measures to make the thing work - since I know where those are and what I need to do to do it right). If you can't find me or I don't reply to your e-mail - don't get impatient - just wait. I currently have no network access at home, so I'm doing a chunk of code offline. I'll get to your mail and queries as time allows. If you have problems with the code or bugs to report, kindly forward them to /dev/null (the code is in now way or form ready for bug reports - I don't want crap filling my mailbox). I hope that clears things up for now. SVN revision: 3976
2000-12-08e 0.17 ...... :)Carsten Haitzler
SVN revision: 3961