JFace and features not part of Eclipse

Today I sit down and thought it is time to provide features JFace won’t provide (some of them are marked as later or are refused) in an own project named at.bestsolution.jface. Well 2 features I already had around somewhere in my workspaces:

  • TableViewer working with multiple instances of the same object
  • Dialog which could restore it’s values because it’s only hidden

All people interested in the work could as always fetch the sources from my companies SVN-Server. At the moment this plugin only depends on JFace but it’s likely that this will change in future and org.eclipse.swt.nebula and at.bestsolution.jface32 will be added as dependencies. I haven’t thoroughly tested because I never use it in my daily work so the QA is your part😉

How much can happen within one week?

Back from holiday I see JFace’s new viewer API evolving from week to week and getting more stable and userfriendly but some parts are not as smooth as they should be some work has to spent. The most markable things changed is that the caching of column-indices is gone completely.

Another important news is that Boris sorted out some VIRTUAL-Table bugs. As of this writing I have integrated all those changes to at.bestsolution.jface32 project. Simply fetch all changes from my companies (BestSolution Systemhaus GmbH) public SVN-Repository.

At the moment all things from JFace HEAD are integrated and because Tod, Boris and I all think that my widget-independency work can go in as is I’ve already integrated it. JFace integration will follow at the beginning 3.3M3 timeframe.

And last but not less important a new API-function has been added to set multiple filters at once this should avoid us to use all those nasty hacks to avoid flickering, … .

I think I’ll release a first version of the plugin with M2.

Finally to a new JFace project providing snippets to all show common JFace. The new project has been approved by the eclipse PMC and can be found in eclipse’s CVS with contribution from Tod and myself