Hi,

Thinking about a little reorg for some of the monitoring related classes...

I'd like to put the ECAL event display in its own separate package, as it has a significant amount of code and its place in monitoring-drivers I realize now doesn't make all that much sense.  I would probably use the top-level package name "org.lcsim.monitoring.ecal.eventdisplay" so the package name is clear.  Right now it is kind of ambiguous e.g. all the event display stuff is directly under "org.hps.monitoring.ecal" along with mostly unrelated packages like the Drivers.

This will allow me to also include it as a dependency in monitoring-app so it can be directly controlled through the monitoring GUI which I think is probably desirable.  It will also allow other modules to easily depend only on the ECAL event display without pulling in other undesired deps.

Somehow I also need to deal with the fact that there is some functionality defined only in monitoring-app that Driver classes will probably want to use such as strip charts and the new system monitoring capabilities.  Otherwise, Drivers for monitoring will be split between monitoring-drivers and monitoring-app which is kind of messy.

We could pull out the monitoring related utilities such as the aforementioned strip chart and system monitoring capabilities into a monitoring-util module which monitoring-drivers could depend upon.

I may also make a number of new modules from monitoring-app packages, but I don't have to ask anyone about this because I wrote all that code.  :)

I'm not going to touch any else's code/packages until I get some feedback on this.  Maybe some of the details could be discussed in the next software meeting...

--Jeremy

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1