Comments on: APIs and what not to do http://theshyam.com/2010/04/apis-and-what-not-to-do/?utm_source=rss&utm_medium=rss&utm_campaign=apis-and-what-not-to-do Ramblings from the Real Shyam; You know, unlike those other fake Shyams! Sat, 28 Jan 2012 06:10:32 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Shyam http://theshyam.com/2010/04/apis-and-what-not-to-do/#comment-149 Shyam Thu, 15 Apr 2010 22:00:31 +0000 http://theshyam.com/?p=301#comment-149 I can, but thats not the point. If all I'm going to do with a GWT Tree is always wrap it, why not wrap it to begin with. And yes, SWT / JFace does it right. Completely agree on that point I can, but thats not the point. If all I’m going to do with a GWT Tree is always wrap it, why not wrap it to begin with. And yes, SWT / JFace does it right. Completely agree on that point

]]> By: Sven Meier http://theshyam.com/2010/04/apis-and-what-not-to-do/#comment-148 Sven Meier Wed, 14 Apr 2010 08:27:35 +0000 http://theshyam.com/?p=301#comment-148 Don't be too harsh on the GWT tree. You can easily implement a small wrapper which offers what you're looking for: be it a provider, TreeModel or any other pull mechanism. IMHO SWT/jFace does it right: A low level API like the GWT tree and a higher API similar to what JSF is offering. Don’t be too harsh on the GWT tree.

You can easily implement a small wrapper which offers what you’re looking for: be it a provider, TreeModel or any other pull mechanism.

IMHO SWT/jFace does it right:
A low level API like the GWT tree and a higher API similar to what JSF is offering.

]]>