+1 for me too ! I also opened a CQ for the bundle spy (CQ 9096 <https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9096>). We will have to new spies in a few time..
<http://www.opcoach.com/> Olivier Prouvost <mailto:[email protected]?subject=Demande%20de%20renseignements> Formation et Expertise Eclipse <http://www.opcoach.com/> Mobile : +33 (0)6 28 07 65 64 <http://www.eclipse.org/membership/showMember.php?member_id=987> > Le 10 janv. 2015 à 17:53, Lars Vogel <[email protected]> a écrit : > > +1 from me to integrate it into the e4 tools (obviously) > > I think we need a few more +1 from e4 committers to start the migration > process from Github to the e4 spies. > > Am 09.01.2015 15:27 schrieb "Ed Merks" <[email protected] > <mailto:[email protected]>>: > Wim, > > Yes, there are cases where the changes to the preference are assumed to > happen directly via the UI (preference page) rather than by listening to the > preference itself change. That's unfortunate... > > Cheers, > Ed > > > On 09/01/2015 2:51 PM, Wim Jongman wrote: >> Just an FYI as well... >> >> What often is overlooked in preference managers is that there can be >> additional things done besides just changing a preference value. >> >> For example, when changing the preference "Plug-in Development/Include all >> plug-ins from target in Java search" a job is activated that updates the >> java search scope. You can see this for yourself when you open the progress >> view and flip the value. When this preference is set directly through the >> preference store then this job is not activated which obviously is very >> confusing. >> >> In other words, preferences like this cannot be managed correctly by Oomph, >> the Workspace Mechanic and now the Preference spy. >> >> Since the preference pages are all manually coded UI panels, there is no way >> in knowing what things are managed beside the actual preference. >> >> Cheers, >> >> Wim >> >> >> >> On Fri, Jan 9, 2015 at 2:07 PM, Ed Merks <[email protected] >> <mailto:[email protected]>> wrote: >> Simon, >> >> Just an FYI... The Oomph project has an EMF model that wrap Eclipse's >> preferences. This allows all preferences to be inspected (and even >> changed), including secure preferences. When the model is opened in an >> editor, that editor will select any preference that changes. This aspect is >> very crude compared to what's in the blog, but we often use it like a "spy" >> to figure out where preferences changed via the UI are actually stored in >> the preference store. The primary purpose of this preference model is for >> use in other Oomph models... >> >> Cheers, >> Ed >> >> >> On 09/01/2015 1:45 PM, Simon Scholz wrote: >> Dear e4 developers, >> >> I like to contribute the Preference Spy, which I introduced in the >> http://blog.vogella.com/2014/12/28/preferences-spy-for-eclipse-ide-and-rcp/ >> <http://blog.vogella.com/2014/12/28/preferences-spy-for-eclipse-ide-and-rcp/> >> blog entry , to the E4 tools, so that it becomes an official spy, like the >> Model Spy and others. >> >> We at the vogella GmbH already use this Preference Spy a lot, especially for >> the saneclipse project. >> Olivier Prouvost already gave the Preference Spy a try and explained how to >> embed the Preference Spy as official E4 SpyPart. >> >> All necessary information can be obtained from the blog entry >> http://blog.vogella.com/2014/12/28/preferences-spy-for-eclipse-ide-and-rcp/ >> <http://blog.vogella.com/2014/12/28/preferences-spy-for-eclipse-ide-and-rcp/>, >> like an introduction for it, the github repository >> (https://github.com/vogellacompany/PreferencesSpy >> <https://github.com/vogellacompany/PreferencesSpy>) or the p2 updatesite >> (http://dl.bintray.com/vogellacompany/eclipse-preference-spy/ >> <http://dl.bintray.com/vogellacompany/eclipse-preference-spy/>). >> >> What do you think about the plan to integrate the Preference Spy as official >> SpyPart? >> >> Comments or Github issues are welcome and appreciated. Thanks in advance. >> >> best regards, >> >> Simon Scholz >> >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] <mailto:[email protected]> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> <https://dev.eclipse.org/mailman/listinfo/e4-dev> >> >> >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] <mailto:[email protected]> >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> <https://dev.eclipse.org/mailman/listinfo/e4-dev> > > _______________________________________________ > e4-dev mailing list > [email protected] <mailto:[email protected]> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/e4-dev > <https://dev.eclipse.org/mailman/listinfo/e4-dev> > _______________________________________________ > e4-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev
