Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [e4-dev] Remaining e4 work for Luna

Hi Eric,

I think the 'Life cycle management: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398837' item would be also good to consider. Since we already have a patch for it so maybe we don't need to spend too much time on it. Having it in place we will be able to start thinking about better organization of some areas of the Workbench

thanks,
Daniel


From: Eric Moffatt <emoffatt@xxxxxxxxxx>
To: E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>,
Date: 01/27/2014 05:29 PM
Subject: [e4-dev]  Remaining e4 work for Luna
Sent by: e4-dev-bounces@xxxxxxxxxxx





We're down to the last real development milestone for Luna and there are a number of partly or unfinished initiatives still on the plate:

Life cycle management
:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=398837
    - Tom has a patch but we need to go over it and make sure it covers the various scenarios.


New 'e4' based extension point extensions
:
    -  We've done the 'e4' view work but it hasn't been tested much and we're nowhere on either the Commands / Handlers side of things. Not sure how / if Wim's new 'mixed mode' work affects this...


MWizard / MDialog
:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=421462
    - This still needs to produce some examples of effective code patterns


- New 'find' API:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=424367
  - We have to decide whether we want an interface or an annotation for the 'match' method (or both?).


Anything else ?


In order to get a quick start on this for M6 I'd like to call a 'special' meeting sometime later in the week. This is primarily to discuss 'e4' work that is mostly independent of the IDE so it's more relevant to the 'e4' developers than those working on the Platform UI (i.e. our European community...;-).  In order to get as many of the interested parties as possible to join could you talk amongst yourselves and see of we can come up with a good time ?


Since it took the threat of removing the MWizard stuff to get any action I'm repeating the threat; if we can't come up with some plans *early* in M6 (especially given that most of the people involved likely have EclipseCon commitments as well) then these enhancements will have to be deferred...


Wim, I'm particularly interested in your mixed mode work even though it's not on the list and we can also discuss this as well...


Onwards,
Eric



Inactive hide details for Wim Jongman ---01/25/2014 09:37:42 PM---> the model is created by the compat layer and therefore it dWim Jongman ---01/25/2014 09:37:42 PM---> the model is created by the compat layer and therefore it did not work for > all possible extensio

From:

Wim Jongman <wim.jongman@xxxxxxxxx>

To:

E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>,

Date:

01/25/2014 09:37 PM

Subject:

Re: [e4-dev] True mixed mode

Sent by:

e4-dev-bounces@xxxxxxxxxxx





the model is created by the compat layer and therefore it did not work for all possible extensions. At what point in time do you add your contributions? Did you have any problems so far to contribute any elements?

I planned to run it as a prestart OSGi service but Lars contributed an IStartup extension which it is using now. I think it finally needs to go to the bootstrapping code somewhere. 

Did you have any problems so far to contribute any elements?
I have only worked with parts and partstacks so far. I just do getChildren().add(MUIElement). This will probably not work for all possible elements but that is a trivial addition.

I have just finished the code to support all possible scenarios.

It can: 
extract parts of Application.e4xmi into the running E3 application model (my extension point)
extract parts of fragment.e4xmi into the running E3 application model (my extension point)
load the complete fragment.e4xmi into the running E3 application model (existing extension point)
run processors to alter the running E3 application model (existing extension point)

The last two steps were actually even more easy then the first two. I just run the ModelAssembler again. 

Current;y, the ModelAssembler is running on a wrong time in the application bootstrap. The first time around the model is not yet filled with all E3 model elements. It needs to be called later and then my call can be removed.

To see it in action, create a new workspace, import the five projects, run the E3 application with all workspace bundles.
To run the E4 app for comparison: just run its product (you might need to add required plugins in run config) 
 
Cheers,

Wim
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/e4-dev

_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev



Back to the top