Bug 426034 - [Trim] Allow fine-grained control over the visibility of Min/Max buttons in parts
Summary: [Trim] Allow fine-grained control over the visibility of Min/Max buttons in p...
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.3.1   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-17 17:39 EST by Georg Fiechtner CLA
Modified: 2014-07-21 16:12 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Georg Fiechtner CLA 2014-01-17 17:39:09 EST
I want to pick up the suggestion that was made during the discussion of https://bugs.eclipse.org/bugs/show_bug.cgi?id=394231.

My use case is the following: we have many parts that can be maximized/minimized, except one, that acts like a Dashboard which always stays prominently in maximized state. 
Currently, with the help of the MinMaxAddon, we are able to either show Min/Max buttons for all or for none of the parts.
So for that part, being able to hide these buttons would be handy.
Comment 1 Eric Moffatt CLA 2014-06-23 15:38:37 EDT
Georg, don't take this wrong...I'm gonna use you as an example...;-).

The reason that the MinMaxAddon is an *addon* is so that you (i do mean you) can replace it with a different one that meets your needs. Not enough folks are likely get get enough value from this to make it part of the platform but you can certainly clone the existing package (just do 'Import as Source' from the plug-ins view) and modify it as you see fit.

The underlying reason is that this type of tweak seems fine for one request but once you get 15 different requests for behavioral tweaks then the code starts to get *really* messy (this is one of the reasons that 3.x eventually needed a rewrite).
Comment 2 Georg Fiechtner CLA 2014-07-21 16:05:01 EDT
Hi Eric,

thx for your reply. No worries, I don't get this wrong. :)
I've been developing Eclipse 3.x RCP applications for a long period of time now and I kinda got used and comfortable with the 'tight embracement' the 3.x platform provided (including the drawbacks and limitations).
Now, with e4 it felt like being thrown in 'open water', so I was a bit helpless at first, but after a while the newly won freedom felt nice and now I do not want to miss it anymore!
So, long story short: developers (including myself) that start with e4 are not used to this kind of freedom and need some time to understand (many things to learn and figure out), but once this time has passed...there is no going back to 3.x anymore. :)

Anyway, thank you for pointing out one of the best ways to go for this requirement, as I was not sure on how to proceed. As maybe others will stumble upon this entry as well: not too long ago, I read a blog entry about achieving something similar using CSS. Is this possible? (Unfortunately I cannot find the blog entry anymore...)
Comment 3 Georg Fiechtner CLA 2014-07-21 16:12:37 EDT
ok, forget my last question...just for people who want to know: here is more about CSS styling -> http://wiki.eclipse.org/E4/CSS/SWT_Mapping
Without trying now, the CSS property 'swt-maximize-visible' applied to the view should do the trick...