So we ok reversing fields? And adding optional in label?
Me changing this in abstract main class will affect all product using it. And it hard to do a good job there because all internal details of this page is API.
There are few options
- I don't do anything in CDT and just change our product
- I change current AbstarctMain tab with some ugly hacks to not break API
- I create another AbstractMain2 and deprecated existing one but leave old one as is
Regarding projectless, ignore my statement that it does not work in cdt, I just testing something something else. Default launch config allows it, but it also disables ALL validation
of project and path which I think is really not good. Because if there is mistake there you will get an ugly error in "final launch sequence", If you do a new tab, I can add
more granular validation rules, i.e.
- check that project is empty OR exists and open
- check that binary exists (in workspace or outside)
In general I think we need more due diligence when committees changing UI, It is hard to understand what ui looks like by doing reviews. If somebody would change common UI
I would suggest to post mockups/screenshots on this list so people can reviews prior to getting into stage where is too late to change (like right now)