Today Wayne Beaton (Certified Eclipse Evangalist) responded to a question I asked on his blog.
Take a look over here for his response.
It’s about ways to properly architect an Eclipse RCP application.
Or: How to get your users
Simple: Hack to span an Eclipse RCP screen accross more than one monitor. Don’t ask me why, it wasn’t my idea. I’ve just seen this in code somewhere.
Here’s how it works:
Mess up the Window.getInitialSize() so it takes all your screen real estate into acount, you’ve got two displays 1200 pixels wide? Ok, then we make the initial size’s width 2400. Don’t forget to
mutilate alter the Window.constrainShellSize() method accordingly, else Eclipse will act up a bit. (How naughty.)
Now comes the best part. make sure you filter any occurences of SWT.RESIZE when Window.setShellStyle(int newShellStyle) gets called. Yes I said filter. Imagine some gullable developer passing by who thinks restricting window resizing is an excelent end-user screw.
Did I mention that all this was achieved by some aspectj crosscutting??
In the end, it works, sort of. Maximizing is disabled and resizing is disabled. So you end up with a huge piece of
crap window plastered all over your screen real estate. You see, users are just dumb people. Letting them decide how to set their window sizes can only result in trouble. Well, atleast that seems to be the idea.
I hope you all got the point that I think the above is an “excellent” idea. (No, ofcourse I don’t think the above is a good idea.)
Nothing new to those using Linux or Windows. But for the Mac OSX developers there is some great news. Finally there seems to be a solution on its way. Thanks to some changes in OSX it is impossible right now to run AWT code within a SWT based application from within the Eclipse JDT. Something going awfuly wrong with deadlocks and all between the AWT and SWT event handling threads. It has been one of the strongest arguments against using an Apple system for Java development.
Credits to Wayne Beaton’s blog entry for mentioning this excellent news. I wouldn’t have known otherwise. It seems that it is useful to put in radar reports when you come across something ugly in OSX. The Apple devs won’t prioritize an issue when few reports come in on it. So if sh#t hits the fan when devving an Apple app. Report!!
Now if someone could convince Mr. Beaton to actually get a Mac, that would be great. Perhaps some of his Eclipse enthousiasm will rubb onto his Apple system usage. Eclipse is great, but Eclipse on a Mac, is even better. 😛 (Because even an Eclipse/SWT UI remains butt ugly on Windows.)
After a couple of months working on a project going from bad to worst it’s a relieve to finally be on a new assigment. The project I’m in is about building a logistic planning application. It involves planning manpower, material and tracks. Oh did I mention that making the plan for one year takes 200 people nine (!!) months to complete. Talk about a complex process. 🙂
Anyway, I’ll be doing all kinds og GUI related work based on Eclipse 3.0.1 RCP (Rich Client Platform). Never done that before… 😛 This will look good on my resume.