Hi, I started to compare the two implementations…
The debug.ui implementation uses events (I discovered it !) to be notified from IEclipseContext … I could use it in my implementation to refresh the content correctly. Another feature is the display of the location where objects are used… I must see how it has been done... My implementation get directly the map of context using introspection and displays it… It is a direct display with less updates than the debug.ui implementation. I will update it… In my implementation the search is more advanced and highlight the tree nodes or tables lines where the string is found. I will continue to investigate and update my version as soon as possible ! Regards Olivier Prouvost Formation, Expertise Eclipse, Java, Open Source Mobile : +33 (0)6 28 07 65 64 Le 20 nov. 2013 à 16:08, Paul Webster <[email protected]> a écrit : > On Wed, Nov 20, 2013 at 9:54 AM, Markus Alexander Kuppe > <[email protected]> wrote: > I do not care much for backward compatibility... OTOH though I find it > important that at least one incarnation of the context explorer does not > drag in any dependency towards 3.x. > > Right, I would suggest an Eclipse4 plugin and a 3.x plugin that consumes the > Eclipse4 plugin (re-uses the work). > > The backward compatibility here is important. > > PW > > -- > Paul Webster > Hi floor. Make me a sammich! - GIR > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
