summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorCarsten Haitzler <raster@rasterman.com>2000-12-11 20:08:38 +0000
committerCarsten Haitzler <raster@rasterman.com>2000-12-11 20:08:38 +0000
commit22aa9d2a5d66cb8d80098056f7075babf5e218d4 (patch)
treea417dedbde7909d939262d9ec0e08b474669b3c7 /README
parent603ae6abfd1ca332367320482aefb3e8ca8590f8 (diff)
Sorry guys.. I had to revert a bunch of changes.. that's life.. but READ the
following (it's in the README now) ------------------------------------------------------------------------------- Enlightenment 0.17.0 CVS Code.... ------------------------------------------------------------------------------- The Rasterman - raster@valinux.com, raster@rasterman.com ******************************************************************************* **************** 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? $ ./autogen.sh && 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 $ ./autogen.sh --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
Diffstat (limited to 'README')
-rw-r--r--README95
1 files changed, 94 insertions, 1 deletions
diff --git a/README b/README
index 32dbee666..0f64e13f0 100644
--- a/README
+++ b/README
@@ -1,3 +1,96 @@
1------------------------------------------------------------------------------- 1-------------------------------------------------------------------------------
2 Enlightenment 0.17.0 PRE-RELEASE.... 2 Enlightenment 0.17.0 CVS Code....
3------------------------------------------------------------------------------- 3-------------------------------------------------------------------------------
4 The Rasterman - raster@valinux.com, raster@rasterman.com
5
6*******************************************************************************
7**************** READ THIS! It is of the UTMOST IMPORTANCE! *******************
8*******************************************************************************
9
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
12the CVS repository.
13
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
16places, make a mess, and may not even be compatible with a final release. If
17you at all use this code, you are HEAVILY URGED, when it is finally released,
18to 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
20help), and then install the full release on a cleaned system. Don't come
21asking "can I just keep using CVS" oonce things are released - thqat is the
22reason I pu this paragraph here - so you don't ask. The asnwer is the same
23as above - if there is a proper final release use that. CVS is really only
24for those havily hacking on the code.
25
26Now we have that warning over and done with. How to build and install from
27CVS?
28
29$ ./autogen.sh && make
30$ su
31Password:
32<- as root ->
33# make install
34
35You should be able to use the binary of enlightenment as a window manager.
36
37you might be advised for cleanliness to do
38$ ./autogen.sh --prefix=/usr/local/e-17
39
40so it installs relative to the /usr/local/e-17 directory and keeps all the
41e-17 development code and data in that tree so it is easily removed when the
42time codes.
43
44
45
46NOTES: Read these carefully!
47
48Enlightenment does not check for previously running Window Managers right
49now - so you need to make sure no other WM is running - E will not do that
50for you.
51
52Enlightenment has no menus or keybindings or any way of launching
53applications right now - you'll have to figure out an alternative way of
54doing it.
55
56Enlightenment only handles a small subset of ICCCM and thus will have bugs -
57some applications will not behave correctly and may apear in odd spots or
58not resize or place themselves properly etc. Expect this - it's code being
59worked on. Just be happy it does as much as it already does.
60
61Enlightenment RELIES on lots of libraires that have been written. Ecore,
62Ebits, Evas, Edb, Imlib2 just to mention a few. Especially Ebits, Ecore and
63Evas change in CVS often - you will need the absolute latest of these if you
64wish Enlightenment 0.17 code to run properly or compile. If you update
65Enlightenment from CVS update these too to get any changes they have in
66their trees.
67
68If you plan on working on the code... STOP! don't rush in and work on it -
69even if you have CVS commit access - EXPECT me (Raster) to revert any changes
70you make if you do this - regardless of the changes and how much work you
71put into them. First read the code well and LEARN it. If you have questions
72about some of the more obscure hidden program flow - ASK - but don't go
73tampering with it - Enlightenment 0.17's code is much more complex and
74intricate than E 0.16 - but at the same time it's much cleaner and more
75object oriented. Learn it well first. Some parts of E 0.17 are "hacked" with
76hard-coded stuff, just so, for now, it works. They will be virtualized and
77imporved over time. If you have plans - tell me about them first - discuss
78them before you go impliment them. I know I already have a lot of the
79components of E 0.17's code planned in my head - but I won't get to them for
80a while - and if people go impliment or hack bad stuff in, it means I have to
81spend lots of time fixing something that is bad in the first place, or we
82end up doing duplicate work. There *IS* a plan - believe it or not - but to
83be honest - it's more complex and large than I can just write down in a
84README, so talk about your ideas first. I'm going to be ruthless in keeping
85the code neat, clean and free of nasty hacks (except ones I put in as
86temporary stop-gap measures to make the thing work - since I know where
87those are and what I need to do to do it right). If you can't find me or I
88don't reply to your e-mail - don't get impatient - just wait. I currently
89have no network access at home, so I'm doing a chunk of code offline. I'll
90get to your mail and queries as time allows.
91
92If you have problems with the code or bugs to report, kindly forward them to
93/dev/null (the code is in now way or form ready for bug reports - I don't
94want crap filling my mailbox).
95
96I hope that clears things up for now.