|
|
|
| Re: How to disable the Preference Recorder [message #1697981 is a reply to message #1697959] |
Wed, 10 June 2015 05:17   |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Silvio,
Comments below.
On 09/06/2015 11:09 PM, Silvio Bierman wrote:
> No, I don't. I do have preferences that may span workspaces but these
> preferences also span applications I use, machines I work on and so on.
I doubt that, but again, there's no point in preaching to those who
don't want to hear.
> Putting something as invasive and heavyweight as this in Eclipse for
> such a futile task (setting some preferences in workspaces I have
> about 2-3 at the same time and each of those for multiple years)
You certainly use heavyweight wording...
> I consider an extreme form of over-engineering.
We're all entitled to opinions.
> What was wrong with exporting and then importing the same preferences
> across workspaces?
Do you actually do that? I can enumerate a long list of what's wrong
with that. E.g., all my git clones remembered but Egit replace the ones
I have in my workspace. Kind of a disaster for me. But it sounds like
your limited use cases for it work fine for you.
> A much more powerful method that also works when I get a new laptop.
Perhaps, but many preferences refer to hard-coded locations that are
different on different machines.
>
> But it is good to know I can opt out of this in RC4.
We aim to please, but there's no pleasing everyone.
>
> Thank you.
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
| Re: How to disable the Preference Recorder [message #1698013 is a reply to message #1698003] |
Wed, 10 June 2015 11:29 |
|
Am 10.06.2015 um 11:49 schrieb Silvio Bierman:
> I can accept that there are use-cases where something like the Preference Recorder might be useful and even an
> improvement over existing methods. I have little use for many workspaces at the same time (unless for the reason of
> testing Eclipse versions that need to convert a workspace into something that will not work with earlier versions) but
> that is because my company provides only a couple of standard products we work on for years in a row. I know others
> continously create new projects and possibly workspaces so there is no one-size-fits-all solution.
>
> But why not implement such a thing as a plug-in? That way everyone who needs it can opt-in on the functionality or
> ignore it if they don't want it.
Of course it's a plug-in and users can opt-in unless they use a product that contains this plug-in by default. The
products you can download from Eclipse's download pages are governed by the Eclipse Packaging project (EPP) and they've
decided to include our (the Oomph project's) plug-in in all their products.
> Anyway, seems like in RC4
Neither EPP nor Oomph have provided RC4 builds, yet. Our's will come today, EPP's on Friday.
> the problem went away on its own.
No, Ed has fixed https://bugs.eclipse.org/bugs/show_bug.cgi?id=469652 as he pointed out in an earlier reply.
> Perhaps because it is a plug-in now?
Eclipse tools are always plug-ins.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03661 seconds
] 
Search
Help
Register
Login
Home
