| [science-iwg] e3 or e4 |
|
Hello, I am working on a new project* which will be part of the science working group and might eventually be used at sites other than ours by using the feature as a component in a different product. On our site all RCP-based applications now
use an e4 target. I have to make a decision on some of the user interface classes as to if I allow a dependency on e4. If I stick with everything as e3 it all runs on our e4 targets and is fine but I am limited with a few features. If I make e4 dependencies
I restrict reuse to only those organisations with e4 targets. What do you think I should do? Keep things e3 or allow e4 dependencies which might limit those still on e3? There may be some people on long term support whom will stick with e3 for long periods… but whether they would every need to use
a scanning API is not clear. Matt * for scanning hardware, basically a truly open version of the Generic Data Acquisition software which Diamond Light Source has been using for some time.
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |