summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorCarsten Haitzler <raster@rasterman.com>2001-09-24 21:21:25 +0000
committerCarsten Haitzler <raster@rasterman.com>2001-09-24 21:21:25 +0000
commited401627751682e36a960f6401ae23ad2846ad0b (patch)
tree73d83cc01a22f56f554b71aa5ec686cf11f45d13 /README
parentf98201f9af0490c5a58568f6f27af7f35130255b (diff)
been working offline.. wheeeheee! :)
SVN revision: 5374
Diffstat (limited to 'README')
-rw-r--r--README99
1 files changed, 45 insertions, 54 deletions
diff --git a/README b/README
index efd27de55..218dbe159 100644
--- a/README
+++ b/README
@@ -1,15 +1,15 @@
1------------------------------------------------------------------------------- 1+-----------------------------------------------------------------------------+
2 Enlightenment 0.17.pre CVS Code.... 2| Enlightenment 0.17.pre CVS Code.... |
3------------------------------------------------------------------------------- 3+-----------------------------------------------------------------------------+
4 The Rasterman - raster@valinux.com, raster@rasterman.com 4 The Rasterman - raster@rasterman.com
5 5
6******************************************************************************* 6*******************************************************************************
7**************** READ THIS! It is of the UTMOST IMPORTANCE! ******************* 7**************** READ THIS! It is of the UTMOST IMPORTANCE! *******************
8******************************************************************************* 8*******************************************************************************
9 9
10This is the source code for Enlightenment 0.17 - If you got this you got it 10This is the source code for Enlightenment 0.17 - If you got this you got it
11from Enlightenment's CVS repository - or from someone who took it out of 11from Enlightenment's CVS repository - or from someone who took it out of the
12the CVS repository. 12CVS repository.
13 13
14The CVS repository is full of code *IN DEVELOPMENT* - that often means it's 14The CVS repository is full of code *IN DEVELOPMENT* - that often means it's
15in the middle of being worked on and may install strange things in strange 15in the middle of being worked on and may install strange things in strange
@@ -19,9 +19,9 @@ to remove all traces of anything this CVS code base has installed on your
19system (it is COMPLETELY up to you to keep track of that - do NOT expect any 19system (it is COMPLETELY up to you to keep track of that - do NOT expect any
20help), and then install the full release on a cleaned system. Don't come 20help), and then install the full release on a cleaned system. Don't come
21asking "can I just keep using CVS" once things are released - that is the 21asking "can I just keep using CVS" once things are released - that is the
22reason I put this paragraph here - so you don't ask. The asnwer is the same 22reason I put this paragraph here - so you don't ask. The answer is the same
23as above - if there is a proper final release use that. CVS is really only 23as above - if there is a proper final release use that. CVS is really only
24for those havily hacking on the code, or whose curiosity is too much to resist 24for those heavily hacking on the code, or whose curiosity is too much to resist
25not giving it a look and try. 25not giving it a look and try.
26 26
27Now we have that warning over and done with. How to build and install from 27Now we have that warning over and done with. How to build and install from
@@ -42,19 +42,10 @@ so it installs relative to the /usr/local/e-17 directory and keeps all the
42e-17 development code and data in that tree so it is easily removed when the 42e-17 development code and data in that tree so it is easily removed when the
43time comes. 43time comes.
44 44
45 45-------------------------------------------------------------------------------
46 46
47NOTES: Read these carefully! 47NOTES: Read these carefully!
48 48
49Enlightenment does not check for previously running Window Managers right
50now - so you need to make sure no other WM is running - E will not do that
51for you.
52
53Enlightenment has no keybindings right now, but does have a primitve menu for
54launching some applications. It is configurable - it's in a database file
55and tere is a script that builds this menu - you could build a new one after
56editing the script or do whatever your like.
57
58Enlightenment only handles a small subset of ICCCM and thus will have bugs - 49Enlightenment only handles a small subset of ICCCM and thus will have bugs -
59some applications will not behave correctly and may appear in odd spots or 50some applications will not behave correctly and may appear in odd spots or
60not resize or place themselves properly etc. Expect this - it's code being 51not resize or place themselves properly etc. Expect this - it's code being
@@ -62,42 +53,42 @@ worked on. Just be happy it does as much as it already does.
62 53
63Enlightenment RELIES on lots of libraires that have been written. Ecore, 54Enlightenment RELIES on lots of libraires that have been written. Ecore,
64Ebits, Evas, Edb, Imlib2, Efsd just to mention a few. Especially Ebits, 55Ebits, Evas, Edb, Imlib2, Efsd just to mention a few. Especially Ebits,
65Ecore, Efsd ferite, and Evas change in CVS often - you will need the absolute 56Ecore, Efsd, Ferite, and Evas change in CVS often - you will need the absolute
66latest of these if you wish Enlightenment 0.17 code to run properly or compile. 57latest of these if you wish Enlightenment 0.17 code to run properly or compile.
67If you update Enlightenment from CVS update these too to get any changes they 58If you update Enlightenment from CVS update these too to get any changes they
68have in their trees. 59have in their trees.
69 60
70If you plan on working on the code... STOP! don't rush in and work on it - 61If you want to compile & install E 0.17 you probably install the packages
71even if you have CVS commit access - EXPECT me (Raster) to revert any changes 62Enlightenment needs in this order:
72you make if you do this - regardless of the changes and how much work you 63
73put into them. First read the code well and LEARN it. If you have questions 64 (*) imlib2
74about some of the more obscure hidden program flow - ASK - but don't go 65 (*) edb
75tampering with it - Enlightenment 0.17's code is much more complex and 66 (*) imlib2_loaders
76intricate than E 0.16 - but at the same time it's much cleaner and more 67 (*) evas
77object oriented. Learn it well first. Some parts of E 0.17 are "hacked" with 68 (*) ebits
78hard-coded stuff, just so, for now, it works. They will be virtualized and 69 (*) ecore
79imporved over time. If you have plans - tell me about them first - discuss 70 (*) efsd
80them before you go impliment them - once you've discussed them and we all 71 (*) ferite (optional for now, but recommended)
81aree on how it should be done, you can go ahead and do it. I know I already 72 (*) e17
82have a lot of the components of E 0.17's code planned in my head - but I 73
83won't get to them for a while - and if people go impliment or hack bad stuff 74since you got Enlightenment from CVS (if you didn't you should have) you must
84in, it means I have to spend lots of time fixing something that is bad in the 75get all of the above from CVS - because the libraries Enlightenment depends on
85first place, or we end up doing duplicate work. There *IS* a plan - believe 76keep being updated as bugs are found and new features needed - and often they
86it or not - but to be honest - it's more complex and large than I can just 77are not released for a while until things settle down, so make sure you get
87write down in a README, so talk about your ideas first. I'm going to be 78the latest of these from CVS.
88ruthless in keeping the code neat, clean and free of nasty hacks (except ones 79
89I put in as temporary stop-gap measures to make the thing work - since I know 80before you start installing the some of the above, some of the packages you
90where those are and what I need to do to do it right). If you can't find me 81will need - if you don't already have them, are:
91or I don't reply to your e-mail - don't get impatient - just wait. I currently 82
92have no network access at home, so I'm doing a chunk of code offline. I'll 83 (*) freetype (1.1, 1.2 or 1.3 ... NOT 2.0)
93get to your mail and queries as time allows. 84 (*) libxml2
94 85 (*) libpcre
95If you have problems with the code or bugs to report, kindly forward them to 86 (*) fam
96/dev/null (the code is in now way or form ready for bug reports - I don't 87
97want crap filling my mailbox), unless its a patch hat fixes a silly bug 88and possibly ...
98somewhere. Only experienced people should in any way consider sending a bug 89
99report as I need useful reports, not junk cluttering my mailbox. 90 (*) libjpeg
100 91 (*) libpng
101I hope that clears things up for now. 92 (*) zlib
102 93 (*) libtiff
103In the meantime - have fun. 94 (*) libungif