Re: [e4-dev] 4.3 Plans / API etc

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

Hi Eric,

Over the top priority - not API but I would trade *any* API to this one:
* Get rid of timerExec

My top priorities are:
* nesting of parts
* better lifecycle for model elements (bug 392903) - if we can get a
  general agreement I'll work on this for M6

Generic-Rendering:
As you know I've implemented a new rendering engine from scratch for my
e(fx)clipse project. The problem with the generic stuff is that SWT is
so much different than other Toolkits that I don't think having a
generic renderer makes sense.

e(fx)clipse is coming to Eclipse.org in the next month(s) which makes no
compromise and exploits the toolkit features available completely. Take
a look on my code and you'll see what I mean.

I think the platform-teams time is spent better in other areas but
that's my personal opinion, I'm not afraid of having the platform being
a competitor when it comes to rendering engines ;-)

Tom

Am 05.02.13 20:54, schrieb Eric Moffatt:
> 
> Finally ! With 4.2SR2 on its way out the door I /finally/  get to turn
> my focus back to 4.3 and the future.
> 
> First off is a big thank you to everybody involved for either helping
> out or at least being patient about not being as free to change e4 as I
> know you'd like.
> 
> This will be a discussion topic for this week's e4 meeting and everybody
> is welcome.
> 
> *Where are we ?*
> 
> I ask the question because most of the last year and a half is just a
> blur to me. I know we've talked about many things but I've certainly
> lost track of most of them. Please speak up if there are things that
> we've been holding off on in order to have a stable foundation for the
> service release(s).
> 
> My highest priority concern is to nail down the API (since I have to
> present it at EclipseCon...;-). We can still make changes in the API and
> model while getting the information together but only if we start pretty
> soon. This will allow us to make some of the changes we've already
> discussed like Parts within Parts...I'd like to get a working group
> together to hammer out the details (maybe we could schedule some
> meetings at least at the beginning ?).
> 
> I'm in the process of gathering up what we have so the first question is
> how would we like to do that, In a bugzilla (with related ones for each
> area CSS, Model, DI, services) ? In  a GoogleDoc ? Some other way ?
> 
> *Where do we want to go ?*
> 
> As the effort on the compatibility layer starts to subside (we're not
> finished but we are down to true corner cases now IMO) we should be
> examining how we move the whole platform forwards over time. The two
> main themes I'm aware of are:
> 
> - Moving the platform towards a platform agnostic approach (i.e. not so
> closely tied to SWT) by examining where we can add new agnostic
> superclasses into our current code...
> 
> - Blurring the current separation of e4 and the IDE by
>    - allowing current IDE features to be used in e4 without having to
> bring in the whole IDE
>    - allowing the IDE to host e4 implementations by loosening up some of
> the constraints in our current extension points / API
> 
> Are there others ?
> 
> Ah, time to have some fun :-) I really want to have some 'real' New &
> Noteworthy entries for M6 forwards, I'm sick of having to answer the
> question "What can Eclipse 4 do that 3.x couldn't?" with the word
> "Nothing"...split editors anyone ?
> 
> Thanks again,
> Eric
> 
> 
> 
> 
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
> 


-- 
B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
------------------------------------------------------------------------
tom schindl                 geschäftsführer/CEO
------------------------------------------------------------------------
eduard-bodem-gasse 5-7/1   A-6020 innsbruck     fax      ++43 512 935833
http://www.BestSolution.at                      phone    ++43 512 935834