Re: [e4-dev] Prioritized bug list for shipping, process for updating it

[Eric Moffatt <emoffatt@xxxxxxxxxx>]

Lars, I agree wholeheartedly. 

One of the reasons for having a live
editor is to help ensure that *legal* changes to the model get reflected
in the UI. This is really just a matter of timing I think. By the time
this missing functionality was reported we were all completely swamped
with the SDK work...

Here's a quick comment about each defect
(I'll update the defects after):

https://bugs.eclipse.org/bugs/show_bug.cgi?id=318383
  I think that this would work if the 'move' were broken down into
a 'remove' followed by an 'add(index)'...we can look into an optimized
'move' later

https://bugs.eclipse.org/bugs/show_bug.cgi?id=318394
  This is a good one...we have a variety of issues in the model's
definition of TrimBars, notably that the model allows more than one bar
on a side (and allows a bar to switch sides...;-). I sort of like the idea
of being able to define multiple 'top' bars since it gives an alternative
to the current layout that may be better for some apps). While the ability
to change the side of an existing TrimBar is rarer it's still the right
thing to do... In order to fix this we'd first have to provide the support
for multiple TrimBars on a side; otherwise we end up with a very complex
system (i.e. you can't change the side to 'RIGHT' if there's already one
there...).

https://bugs.eclipse.org/bugs/show_bug.cgi?id=318435
  This is really strange since it was one of the first responses we
added and certainly worked at some point...What type of Menu(Item) was
it? I ask because at least some of the UILabel info for a 'HandledItem'
comes from the MCommand backing it...

It is indeed a cornerstone of Modeled
UI engines that they respond to *all* (legal) UI changes whether in attribute
values or structure. The live editor should make the discovery of issues
much easier as well as providing a mechanism to determine if the issue
is fixed. Note that there may also be cases where the current model design
may not be tight enough, allowing 'illegal' shapes. If any of these are
found we should re-examine the model's definition to see if there are changes
needed.

Onwards,
Eric

From:	Lars Vogel <lars.vogel@xxxxxxxxxxxxxx>
To:	E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
Date:	07/12/2010 04:00 PM
Subject:	Re: [e4-dev] Prioritized bug list for shipping, process for updating         it...
Sent by:	e4-dev-bounces@xxxxxxxxxxx

---

I personally find it also "against the e4 story"
 that that the e4 application (renderer) does not always react to
model changes. For example:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=318383
https://bugs.eclipse.org/bugs/show_bug.cgi?id=318394
https://bugs.eclipse.org/bugs/show_bug.cgi?id=318435



2010/7/9 Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>
Hi Susan,

It's a P4/P5 issue but one that really makes the nice L&F of 4.0 SDK
less attractive. I'm talking about the Gif-Icons (the most prominent
ones in the toolbar for Launch, ... => see attached images) who have
some white pixels surrounding them. I know for many of us this is not a
problem but it really hurts my eyes to see this white pixels but without
having at least access to the original files (I at least hope that there
are not only those GIF-Files available).

Another problem I see is that we somehow need to disable the PDE wizards
who create not launchable 3.x RCP-Applications in the 4.0 SDK (Bug
317912). For me this is a P3/P4 issue because many people we'll give
those wizards a try and we make them fail without a warning.

The workbench recovery you mention on the wiki is talked about in Bug
313883 which is something I could probably work on as well and deserves
a P3 because it makes it easy to reset the state so that the UI comes up
in case the delta is completely broken (P3).

And finally I'd like to work on bug 318821 which has nothing todo with
SelfHosting but user experience and troubleshooting when missing DS in
the launch config which is a (P4).


Tom

Am 09.07.10 01:05, schrieb Boris Bokowski:
>> If there is something that you think should be
on this list that is
>> not listed, or if there is a bug that you feel should get promoted,
>> please do the following:
>
> For those in Ottawa, you can also just talk to me or IM me bug numbers.
>
> Boris
>
>
>
> _______________________________________________
> 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                  
                     geschaeftsfuehrer/CEO
------------------------------------------------------------------------
eduard-bodem-gasse 5/1    A-6020 innsbruck      phone
   ++43 512 935834

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




-- 
Lars
http://www.vogella.de
- Tutorials about Java, Eclipse and Web programming
http://www.twitter.com/vogella
- Lars on Twitter_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev