Perhaps if OpenSolaris handles these issues well, it would provide yet more arguments to use when approaching the various COSE/CDE contributors and TOG about opening up CDE, as would the progress of OpenMotif.
Just in the last couple of days, there was a question in comp.unix.solaris about how to programmatically enable/disable CDE screensavers. I had to say that while I might be able to figure it out (some undocumented functions in libDtSvc again), I wouldn't recommend it because I couldn't be sure that the underlying over-the-wire behavior of dtstyle talking to dtwm and/or dtsession was committed, i.e. for all I knew dtstyle was only guaranteed to work when running the same place as dtstyle/dtsession. So they decided to go in the direction of disabling the CDE screensavers entirely, and using some standalone screensaver like xscreensaver where they needed application interaction with the screensaver. I mention that as yet another example that there is continuing interest (other than just me), even if not high volume, in such areas of CDE as programmatic access to anything that (for example) dtstyle can do, and that there are still some who are developing applications with the expectation that at least in the near future, the primary environment in which they will be used will still be CDE. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
