Comment 1 Eric Moffatt 2011-10-07 14:30:30 EDT

The general idea in e4 is that we shouldn't have to 'tweak' the model for this type of thing. We have instead designed in other mechanisms to allow the developer to control the UI at a fine-grained level based on their (your) specific needs.

One approach is to create an addon that detects Shells being rendered and implements the necessary SWT hooks to constrain its size. This is not difficult, if you look at the model for a running Eclipse 4 session you will see that it uses a number of Addons to support itself, they're simply Pojo's like your views that get created once the model is loaded. 

This is not just a case of us not wanting to do the work but is really to your advantage; you get the implementation that *you* want, don't have to wait on us...

One of the main reasons that the 3.x code stream is as overly complex as it is stems from the necessity of its having to be the implementation container for *everybody's* 'tweak'.

Let me know what you think and I can attach a skeleton addon impl if you think it's a good idea...

Comment 2 Thomas Schindl 2011-10-07 14:56:49 EDT

After having thought about this a bit it more I think this is in reality a CSS request because SWT properties should be controlled through it!

So if CSS would suppport the mimimumSize-Property one would simply write:

Window#mainWindow {
  minimumSize : Point(500,600)
}

Comment 3 Eric Moffatt 2011-10-07 15:06:16 EDT

Interesting...never thought of it that way. Are properties like 'mimimumSize' already in use for browsers?

Comment 4 Thomas Schindl 2011-10-07 15:29:26 EDT

(In reply to comment #3)
> Interesting...never thought of it that way. Are properties like 'mimimumSize'
> already in use for browsers?

No but my take on all the css stuff is that we should prefix ALL our properties using -swt so the css should better read:

Window#mainWindow {
  -swt-minimum-size : Point(500,600)
}