The way I was thinking of is like a link to various type of
At present, you can build a desktop shortcut to run the hub, or not. You
use a default scene, or not. Specify a given location for you config
use the default.
So I figure, why not use a config file to determine what toolsets /
are setup? We use a database 4GL system at work, which, depending on
config file, determines what version and what data is used.
LWAVE.EXE -oLay -Mycolr1 <<- Run in "layout mode"
LWAVE.EXE -oMod -LWColr <<- Run in "Modeller Mode"
LWAVE.EXE <<- Run default
'full' integrated setup.
Each config file would hold pointers to neccesary plugins etc, just like
At present, there really isn't anything to stop you have ZIP files of
configurations, each with given plugins and looks set up. Then you just
the one you want to use. Of course, I'm not saying there is any point at
present in doing this, but it *could* be done. ;-)
>I cannot understand you here - imho this way means having 2 different
>one in the current way (2 separated modules), and another completely
>different with a merged environment (and maybe different sub-tabs). Can
>explain your idea a little in depth?