Comments for Manuel Selva's Eclipse blog

Comment on Java Fields Accessibility (and not Visibility!!!) / Public – Private – Protected …. by RcK17

RcK17 — Mon, 30 Nov 2009 10:06:07 +0000

Thanks

Comment on JFace’s Viewers Usage Thoughts by Michael Golovanov

Michael Golovanov — Sat, 28 Nov 2009 05:24:39 +0000

In addition to great ideas of other folks: you can use AOP (aspect oriented programming) to mixin tree related stuff on original model object

Comment on JFace’s Viewers Usage Thoughts by Manuel

Manuel — Fri, 27 Nov 2009 07:44:34 +0000

Hi, thanks to all for your positive and constructive feedbacks !!!

I’ll investigate all directions you mentioned in order to consolidate my JFace and Gef knowledge.

Thanks again
Manu

Comment on JFace’s Viewers Usage Thoughts by Miles Parker

Miles Parker — Fri, 27 Nov 2009 07:08:46 +0000

Sounds like a job for GEF! In fact you’ve described one of the best use cases. I think that one way to think about GEF edit parts is precisely as you say — a “view model”. And an overlooked aspect of GEF is that it can be useful without any 2d content at all — just use the tree model. Sound like overkill? Perhaps, but if you think your usage is likely to grow to become more complex you’ll be ready — and GEF implementation really isn’t that much more complex than TreeProviders.

p.s. it’s really nice when people post general issues like this as it gives us a chance to step back a bit and thing about high level usages.

Comment on JFace’s Viewers Usage Thoughts by Del Myers

Del Myers — Thu, 26 Nov 2009 18:09:13 +0000

It really depends. One problem with building a view model is that you have to be careful about what objects you return to the viewer. If there are any other views in the workbench that respond to selections that are related to your original model, then making a simple view model just won’t work.

When I’m faced with that situation, I will sometimes create an internal view model that is contained inside the content provider which keeps a map to the original POJOs so that they can be returned by “getChildren” etc.. The internal view model is built on demand and stored with the content provider. You can clear it when the provider is disposed. This solution only works when there is a 1:1 relationship between content provider and viewer, though–which is the way that you really should do it.

The data binding may work as well. It could be a good alternate solution. I’ve never really worked with data binding myself.

Comment on JFace’s Viewers Usage Thoughts by Boris Bokowski

Boris Bokowski — Thu, 26 Nov 2009 17:32:50 +0000

Thinking about the static structure of your tree is only the first – and easiest – step. It gets much more complicated as soon as you add dynamics, in the sense that your tree’s items, and its shape, change over time. (Calling viewer.refresh() doesn’t scale.)

My recommendation would be to use parts of the data binding framework – have a look at ViewerSupport.bind (and its implementation, if your use case is covered by the simple helper API). Here’s a snippet that shows how you can use it: http://tinyurl.com/yefrj97

The basic idea here is that a tree is composed of a number of observable lists, one for each parent node, containing the child nodes. If you can provide a factory that creates an observable list for a given parent node, or returns null if the given node is a leaf, then that’s all we need for the content side of a dynamic tree. If there is any computation involved, you can worry about that computation at the level of “how do I compute the observable list of children for a given parent node”.

(An observable list is a java.util.List with additional methods for adding and removing listeners. It will fire events as elements are being added or removed. One simple implementation is WritableList.)

Comment on Linux / Eclipse / GTK by Gergo

Gergo — Tue, 10 Nov 2009 18:59:45 +0000

> Also, have you seen any clear definition of what GTK version Eclipse/SWT
This seems the best so far:
http://www.eclipse.org/swt/faq.php#gtkstartup

Comment on Linux / Eclipse / GTK by Gergo

Gergo — Tue, 10 Nov 2009 18:54:16 +0000

Oh, so that’s feasible – great to know.
I’ve run into GTK/GDK crash on an old system, which is RHEL4 at this time.
So I was wondering, as a last resort bundle a custom-build GTK/GDK with my product.

Do you still remember, what are the .so files SWT requires, and which is the minimum subset of source packages that build these?

Also, have you seen any clear definition of what GTK version Eclipse/SWT requires? The best I’ve found so far are the Release notes – but that’s not too concise.

Thanks a million,
Gergo

Comment on JFace Bug 9262 by Russell Thamm

Russell Thamm — Fri, 23 Oct 2009 04:41:50 +0000

Thanks Manuel,

fortunately I realised pretty quickly about the bug (thanks to Javadoc).

I had no idea how to fix it until I read your post.

Comment on How do you handle OutOfMemoryError ?? by Angelo

Angelo — Fri, 25 Sep 2009 12:03:34 +0000

Hi Manuel, try increasing your heap size. You check the link below on how to do this on eclipse

http://javasprint.blogspot.com/2009/07/eclipse-shorcut-icon.html