I am looking to get involved with e. Experience cutting comms code, gui
design and stochastic optimisation techniques :-) I can pretty much have
a look at anything so let me know as to what people would like me to get
kenjinX( Declan ).
From: Carsten Haitzler (The Rasterman) <raster@ra...> - 2004-05-28 01:54:46
On Wed, 12 May 2004 23:14:08 +0100 Declan Conlon <dec@...> babbled:
> I am looking to get involved with e. Experience cutting comms code, gui
> design and stochastic optimisation techniques :-) I can pretty much have
> a look at anything so let me know as to what people would like me to get
> involved with.
aaah well then. first. if you want to help - welcome. first i'd suggest dropping
and "hanging out" on irc for a bit. on irc.freenode.net you will find people in
#e and the developers mainly chatter in #edevelop. this is immensely useful as
you can get instant feedback.
often things will go:
<developer1> Hmm that didn't run. segv. here's the gdb backtrace:
<developer1> ... some gdb dump ...
<developer2> Ooooh bugger. can u print variable_x ?
<developer1> variable_x = 0x0
<developer2> Aaaaah got it.
<developer2> just a sec...
<developer2> ok committed to cvs - update and try again
<developer1> ok - just a sec
<developer1> ok - it works! excellent
<developer1> excellent! added feature X to Y. in CVS now.
<developer5> just updated - thats great! how about doing X as well?
<developer1> aah good plan... will get to it.
it is really useful to have interactive debugging sessions there - and
discussions on ideas etc. too.
anyway - this mailing list is fine too- but responses can be painfully
slow/lagged at times. as for "what to do" what do you enjoy doing?
i have a few things on my hit list (in no particular order).
1. edb trimming. edb is just too big. we inherited all of the sleepycat db2.7.x
code and we probably only use 20% of it. lets trim the fat.
2. ecore_con SSL handling could do with having SSL server support added for
ecore_con servers. it would be nice to add transparent zlib compression there
too (probably prior to encryption if you use SSL as well. since SSL is a bitmask
option you could have zlib compression too and it can be just quietly handled
for you by ecore_con and apps just select it as part of the connection type).
3. embryo. embryo inherits code from the SMALL language. the engine itself is
almost a rewrite and a lot cleaner, but the compiler is nasty. the code needs
cleaning. it needs windows-ism's removed. it needs to be made PROPERLY portable.
it needs to be tested and fixed for 64bit cpu's. it needs love and attention.
embryo is a virtual machine + compiler (like java or C#) and its tiny.
4. edje + embryo. edje uses embryo to run "macromedia flash"-like "actionscript"
code snippets within and edje theme object. this makes edje an amazingly
powerful theme system - but the scritps need more access to function calls.
there's a rough list of everything i'd like to see exported to the scripts as
accessible api calls - so far a small number of these calls have been exported.
5. edje. edje's program code has become a little messy and could do with a
clean. it could do with profiling and optimising.
6. lots more
this is just a quick list... there is much more than can be done... what tickles
your fancy? :)
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) raster@...
熊耳 - 車君 (数田) raster@...
Tokyo, Japan (東京 日本)