On Wed, 14 Nov 2007 20:44:59 GMT,
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote :

> 
>       Simon wrote:
> 
> > > I hope that everyone can be just as excited. I know I am.
> > > I smell a new age of... Enlightenment.  :) :) 
> > 
> > I'm really excited about this too! Especially about the new
> > communication plan! I actually even think we should do more on
> > the communication point. It would be great to establish a roadmap
> > for example, with a list of items to get done in priority, for the
> > different release-candidates, with eventually some mock-ups. It
> > would also be good to have a place where designers or users could
> > share easily some UI ideas. And not only for Enlightenment itself,
> > but for all the libs/apps around E.
> > A good thing to do too would be to *really* define the scope of
> > the project. Are we just doing a WM, or are we aiming at something
> > bigger?
> > If this is something bigger, what should be the caracteristics of
> > an E-app? Should it just use EFL? Should it be sexy? These questions
> > would have to be answered if we want to get somewhere imo.
> 
>       Ok, so what is it that you want raster to tell you here?
> He's already made it clear that his main interest is in the wm and
> the core efl libs, and that's likely all he really has time for -
> besides everything else.
I'm not interested *only* by raster's opinion as you seem to think!
I know these questions have to be answered by *all* the developers: we
would have to agree on a common project and we would all have to share
the same goals. Currently, there is no limitations, no well-defined
bounds and the E project sometimes (often?) goes in several directions
that are sometimes opposed, which may result in a big waste of our
dev-time.

>       But again, since he's the "project" leader, things like this
> keep being thrown at him. Do you really want him to be responsible
> for the direction of etk too? Or maybe just bless it as the 'official'
> raster-sanctioned gui toolkit?
Being a leader doesn't mean you have to take *all* the decisions! It's
not because Raster may only want to work on the WM that our project
should only be about getting a working WM. He will not "forbid" the
development of a full desktop-environment that would use E17 as a WM. If
all the devs agree on a common desktop-environment project that would be
coherent with e17, I see no reason why raster would refuse it.
But Raster will/should always make the final decisions about the dev of
E17 as it is his baby, as I will always make the decisions about the
directions taken by Etk. You can't take away the power of decision from
the creator of a project just for the name of "community-development".

>       What happens when something like etk or ewl, or some other
> large 'thing' whose scope in many ways overlaps or even overwhelms
> the scope of something like the wm, is also part of the "E" project?
> If raster says "...we need to...", or "... I'd like to see...", or
> something similar, then is he speaking for all "e", all projects,
> or just for e-the-wm, or what? Or if he doesn't say anything about
> 'myProject' then is it irrelevant to "E"?
As I said, imo devs should agree on a common project. Now, if a new
sub-project doesn't respect the project's definition or if it is
redundant with an existing project, it should not be a part of our
common project. That would be the rule to apply with new sub-projects.
For existing projects, the problem is more complex, as you can't decide
and say to a developer that his own project no longer belongs to our
project. But I think that sooner or later, we will have to make
choices. There is no good reason to have three different toolkits in
the same project, as there is no good reason for several video players
or several image-viewers. An application should follow the guidelines
set by the project-definition, and there should not be two
applications/libraries with the same purpose belonging to the same
project.

> 
>       You're the "project" leader of etk Simon. What do you want
> to do? How about a framework like javaFX, or Mozilla's xul, or MS's
> xaml? Would that be something you'd like to see? What are your
> thoughts on the future of graphical UIs? Do you have a 'roadmap'
> for etk+whatever?
I think the first step to accomplish would be to get all the current
widgets usable. For now, some widgets are really far from being
finished. The next big step would be to integrate a tool like "evolve"
to be able to build really-customizable UI from a descriptive file.
This tool should be directly part of Etk, and it should have a really
good and easy-to-use editor. With that, we could start to build really
nice apps quite easily, that would be as themable as native Edje apps.
It would have to be far more detailled, but that is globally the roadmap
I have in mind.

> 
>    jose.
> 
> _____________________________________________________________
> It pays to Discover.
> 0% Intro APR. 5% cashback bonus. Apply now!
> http://thirdpartyoffers.juno.com/TGL2121/fc/JKFkuJi7D6pVbTzJh1jOy7MhejicTzlUY9Bsj7P81ToRL02ZpPJAgw/
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a
> browser. Download your FREE copy of Splunk now >>
> http://get.splunk.com/ _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to