From: Carcassi, G. <car...@bn...> - 2011-08-26 17:47:23
|
>On Gabies CSS app for pvmanager, looks good. >Do bear in mind that the widget will have to be embedded >in an app that does a specific thing, like Bpm orbit table and plotting. I am master of code reusability... ;-) All of the components I write have the following 4 usable pieces: 1. Display: a component that only knows how to display a data structure, without knowing where it came from. E.g. VTableDisplay 2. Widget: gets one (or more) displays and adds the PVManager connection, and the logic of what gets display. E.g. PVTableByProperyWidget 3. View: takes a widget and turns it into an Eclipse view, that you can open independently, and allows you to set its parameters interactively. E.g. PVTableByPropertyView (which is what you saw in the screenshot) 4. OPIWidet: takes a widget and turns it into a BOY widget, so that you can create OPI screens with it. E.g. PVTableByPropertyFigure/Model/EditorPart Result: --> everything that you can do interactively you can do programmatically <--. You can get a Widget, put it in your SWT composite, and just configure it. Or you can go back to the Display, and have your own connection logic on top of it. Etc... They are also in different plugins, so you don't have to get the views (for example) if you don't want them. Gabriele |