| combining "SWT stuff" with "view/perspective stuff" [message #489381] |
Fri, 02 October 2009 13:13  |
Eclipse User |
|
|
|
I'm working on an RCP app where the majority of the page can work just fine as a set of perspectives and their views. However, the app designers have specified the layout such that the top of the window (where a coolbar would normally go) is really a set of stylized tabs and section headers buttons and search box and such (what I might say looks fairly "web-like".)
This top area of the screen isn't something that should ever wrap, and it does not contain just a set of homogenous toolbar items.
I was trying to figure out how to do this with a coolbar, and couldn't come up with anything that works, because of the different item types and coolbars tendency to wrap. I was then trying to figure out if I could just have a view that all perspectives would share, but it can't be resizable while the rest of the views can, so I can't declare a fixed perspective layout. Then I wondered if it was possible to just try to bypass some of the Application window setup logic (the stuff that's creating the coolbar and such and placing everything) so that I basically build what's really a straight SWT app, but also contains views and perspectives.
None of these seem like particularly good solutions to this problem, so I was wondering what others would suggest--are any of the above reasonably possible to implement cleanly, or do I really have to pick either "build with views and editors and only put stuff inside them" or "build with SWT widgets entirely, and ignore views and editors and perspectives". I *really* would like to use views/perspectives, though--a lot of our functionality is precisely the sort of things they do well, and I don't want to reinvent the wheel unless I have to.
Dave
|
|
|
|
| Re: combining "SWT stuff" with "view/perspective stuff" [message #489741 is a reply to message #489633] |
Mon, 05 October 2009 14:01  |
| Eclipse User |
|
|
|
Thanks, Paul. Option 1 was my choice, too. Of course, given that one of the requirements that our product-marketing department has is that the app does not look overly "Eclipse-like" (it's going to be a commercial enterprise client for fairly non-technical users, so "Eclipse-like" isn't a good thing for them, whereas for me as a developer it's just fine), I'm also going to have to do some stuff with a custom presentation. I've tried working my way through various presentation examples I've run across online (documentation is a bit lacking for those, so we'll see what finally comes out.
Thanks!
Dave
|
|
|
Powered by
FUDForum. Page generated in 0.45479 seconds
Home