Re: [eclipse-incubator-e4-dev] Modelled UI change notification - live mo

[Kevin McGuire <Kevin_McGuire@xxxxxxxxxx>]

Hi Tom,

Excellent, I'll have a look to see how you did it.

Looks like we're all in agreement that this is an important feature for
our current code base and should happen soon.

Regards,
Kevin

Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>
Sent by: eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx

09/24/2008 05:23 PM

Please respond to
E4 developer list <eclipse-incubator-e4-dev@xxxxxxxxxxx>

To	E4 developer list <eclipse-incubator-e4-dev@xxxxxxxxxxx>
cc
Subject	Re: [eclipse-incubator-e4-dev] Modelled UI change notification -        live        model

The bug [1] now has small example which shows that
this works (though I
currently only contentrated on easy changes (like updating of labels,
sizes) ) and left out structural changes.

Tom

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=248439

Kevin McGuire schrieb:
> 
> When showing the photo app demo in the two talks I did, one question
> that came up was (an obvious one), "Why do you need to keep restarting
> the RCP app after every model change?".  
> 
> I don't think we've discussed this aspect, but I assume that we
> eventually want to get to the point where model changes can be realized
> against the live app. This matches the web DOM approach where the
way I
> change what is on screen is via DOM element creation/deletion.  My
> understanding is that EMF can provide the change notification, its
a
> matter of us listening and doing the appropriate element deletion
and
> running the factories on the new nodes.  
> 
> Btw, a super cool demo would be to modify the structure of the live
app
> via _javascript_, which you hacked live.
> 
> Some questions:
> 
> 1) Do we agree this is the behaviour we want?
> 
> 2) When do we we think we'd provide it?
> 
> 3) I think I can imagine with the current code base how we handle
> on-the-fly creation and deletion, but what about modification?  Right
> now the factories 'make', they don't 'modify existing'.
> 
> 4) Do we need batching?  Does every model change result immediately
in
> on-screen changes?  I'm not sure how the web handles this; it
doesn't
> seem to require explicit batching but the changes appear to come out
as
> one change (might just be it all happens so fast it looks like one
change).
> 
> Because of the implications for (3), I think we'd like to do this
work
> sooner rather than later.  It would also help to tell the story
of why
> the modelled UI is more interesting than just "I don't need this
all in
> plugin.xml anymore".
> 
> Regards,
> Kevin
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> eclipse-incubator-e4-dev mailing list
> eclipse-incubator-e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev


-- 
B e s t S o l u t i o n . a t            
           EDV Systemhaus GmbH
------------------------------------------------------------------------
tom schindl                  
            leiter softwareentwicklung/CSO
------------------------------------------------------------------------
eduard-bodem-gasse 8/3    A-6020 innsbruck      phone
   ++43 512 935834
_______________________________________________
eclipse-incubator-e4-dev mailing list
eclipse-incubator-e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev