| Re: [eclipse.org-architecture-council] [ide-dev] Fixing the Target platform editor |
|
I have nothing meaningful to technically contribute to this discussion because I have never looked at the code for the Target Editor, but I want to throw my support behind all the changes that have been suggestion.
We have a rule on the target for Eclipse ICE: No one touches it but me. That's such a stupid rule to have! But, we have to have it because without it the project would do nothing but break, constantly. I work with the target by keeping a "scratch copy" that I cannibalize to modify the final target. I've noticed how well Oomph handles target resolutions and thought many times that it would be awesome to see the regular editor be that robust.
So, FWIW, +1 to all of this!
Jay
Jay Jay Billings
Oak Ridge National Laboratory Twitter Handle: @jayjaybillings From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx <eclipse.org-architecture-council-bounces@xxxxxxxxxxx> on behalf of Mickael Istria <mistria@xxxxxxxxxx>
Sent: Tuesday, November 22, 2016 10:51 AM To: eclipse.org-architecture-council@xxxxxxxxxxx Subject: Re: [eclipse.org-architecture-council] [ide-dev] Fixing the Target platform editor On 11/22/2016 04:47 PM, Ed Merks wrote:
The .target editor is basically unusable. It screws up IDE's current resolved target just to open the editor. I never use it and I cringe when I'm at a customer site and they double-click the generated .target file that they need only for their Tycho build.Did you consider contributing enhancement to the default implementation of ITargetDefinition or to the .target editor? I think our community would be better off if there were less things in the platform (PDE and JDT don't belong there).+1. |