> What: Gareth from SCALE has really kindly offered Enlightenment.org
> (that's use guys) free floor/booth space @ SCALE ( http://www.socal
> linuxexpo.org/ ) Next February (2008). So it looks like I will be
> there. Also Nathan of EWL fame and work will likely be there.
> Is there anyone else in the area (This is southern califronia) who
> wants to join and help put together/man a booth and at an expo?
> Hands up now?
>
I can make it there if need be.
> Suggestions on things to do are welcome.
>
How about taking the opportunity to discuss "what could be
done" to improve the project, to address its weaknesses, to enhance
its strenghts, etc.? How about coming up with some concrete short
and long-term goals that people can see as real things that can be
worked on? (and I don't mean just e17-todos)
I'll even start it here by listing some of the next-generation
projects in e's cvs.
1. The "core" efl libs:
evas, ecore, eet, embryo, edje, and some language bindings.
2. The "utility" libs:
esmart, efreet, e_dbus, epsilon, evfs, exml, ...?
What else belongs here?
3. The main toolkits:
ewl, etk, and some language bindings.
What are utility libs for these?
4. The "important" apps:
e17, entrance, ...?
What else belongs here?
5. The "utility" apps:
edje_cc, ...
What else should go here?
5. Other apps:
What should go here?
What are short/long-term goals, aims, roadmaps, progress, ...
for these things? What about for how they 'fit together'? What's
important in E and what's just incidental?
Let's take epsilon for example. There was recent discussion
on how to perhaps improve epsilon in this or that way, some ideas
and whatnot... But, will anything come of that? Why should anything
be done to this lib at all?
I'm starting to think that having certain of these special-
purpose libs is a "bad thing". It just seems to lead to projects
falling by the wayside because there's little or no mechanism,
or community built around them, to ensure that their fires keep on
burning.
It might've been better if epsilon had been an 'ecore_thumb'.
Maybe then there would've been more attention paid to it over time.
Ecore may be a mish-mash of things, and some dependencies
there might be a bit twisted... But it's ONE identifiable important
thing that many people look at and work on. Much the same could be
said about e17 as well.. it at least manages to stay focused and
un-fragmented.
jose.
_____________________________________________________________
Chart your path to success with a smart new business plan. Click here!
http://thirdpartyoffers.juno.com/TGL2121/fc/Ioyw6i3nojL2rIySqaVgJajQyq8UopyPUUiwgkMYrxPeEyvcbDFiAI/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
