[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [E-devel] Evas & Evoak future changes
On Fri, 8 Sep 2006 08:15:38 -0500 email@example.com babbled:
> On Fri, Sep 08, 2006 at 09:40:08AM +0000, firstname.lastname@example.org wrote:
> > Now, unfortunately, this discussion came up at a time when
> > people are busy with e17... in particular, the 'owner' of evas is
> > especially so.
> > So basically, either people proceed without him (with a
> > 'branch' or whatever), or they can wait around, or they can let
> > things go..... Or they can discuss ideas, get feedback, etc.
> > I think this last was what Jorge was attempting to get
> > started.. good timing or not.. and I guess he hoped that at least
> > raster would have joined in (even if he did say that he was too
> > busy to do so).
> > I'd suggest maybe keep ideas in mind, let them develop,
> > see what one might need, etc.. until things quiet down a bit on
> > the release front.
> > jose.
> This was more the point I was trying to get across. I didn't mean to
> sound like I was discouraging you three from working on evas. I'm all
> for branching evas and having ya'll work your magic :)
> (lack of time results in short emails that often don't properly convey
> the tone of voice i intended. for that, again, i apologize)
> take care,
and here i come at the end of the tread... FINALLY! :)
(i am hoping i can now mark off this entire thread in hit).
the work jorge is doing is very interesting. it is basically the ability to
virtualize right below the api level and punt off to somewhere else (in this
case a server). this is most interesting but unfortunately touches just about
every bit of api and has some really tricky parts to it.
i think having this work in another branch is fine - i have no problems with
that, but it will cause problems in merging later.
what i think is a good idea is that this happens in a branch and jorge merges
in changes from evas's head branch regularly so the merge back is as painless
i think this work should happen - it has some exciting possibilities. it just
needs to happen in a way that won't affect stability and correctness of the
head evas branch :)
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) email@example.com
Tokyo, Japan (東京 日本)