Moderator
Posts: 2451 from 2003/2/24
Been thinking a bit about the splitting the panels of from Ambient:
Quote:
Kronos wrote:
That is the point here, making the panels it's own app that access Ambient.library to parse prefs-files and start apps while providing a prefs-group to Ambient (so it's still all just one pref window).
At 1st I thought to make the main prefs-pane a mcc so I could reside in the Panel distribution but still be called by Ambient to show up in the general prefs.
Panel app would then just read the prefs file via functions provided by an "ambient.library" with everything staying separated by binaries and tasks.
The issue here is that panel objects both defined in the Ambient binary and external classes will supply their own sup prefspane. No issue as it is all just 1 Ambient task, put across different tasks that sound like a way to disaster.
Basically both the main panel app and every external class would have to act as an library called by Ambient (either directly or by calling into the panel app) which should work, but just feels wrong....
