The MCP is on Object Desktop!
Thursday, February 27, 2003 by Frogboy | Discussion: WinCustomize News
If you check Object Desktop CM/SDCentral you will see the MCP Core module. (MCP = Master Control Program).
This is a new component that will eventually be integrated into SDCentral when you install it.
What does it do? In a nutshell it manages (or will manage) the running Object Desktop components and eventually be opened up so that third parties can make use of it as well. And it only uses 156K of RAM so it has virtually no overhead.
For example, one part of MCP is called the Startup Manager. A program that supports the MCP will let the MCP control its launch when you boot your machine.
For years now, you boot your machine and if you have DesktopX and ObjectBar (for instance) set to load on start up what happens? You see your explorer desktop and then a bunch "stuff" happening that looks really crummy and confusing as these programs alter your desktop and worse, slow down your boot time.
With MCP, when you logon to your machine it coordiantes your various programs that are trying to load so that they load quicker and when you see your desktop, it is already set up how you want.
The first Object Desktop component to use MCP is ObjectBar 1.6A which is now available for download. You'll need to install the MCP/ObjectBar and then reboot to see its effects.
The MCP has many other capabilities such as managing system hooks. Eventually there will only need to be a couple system hooks total rather than each program having its own (slowing down the system). If third parties make use of this, it will allow users to customize their computers much more thoroughly without a system hook speed hits.
The next beta of DesktopX 2 will also make use of this. And we hope for WinStyles to be able to make use of this so that when you apply a new theme, it can be done without the user having to see a bunch of inelegant desktop switching occuring.
We hope you like it. There's a lot of exciting new technologies about to be released onto Object Desktop this year. This one is one of the more interesting ones we think.
This is a new component that will eventually be integrated into SDCentral when you install it.
What does it do? In a nutshell it manages (or will manage) the running Object Desktop components and eventually be opened up so that third parties can make use of it as well. And it only uses 156K of RAM so it has virtually no overhead.
For example, one part of MCP is called the Startup Manager. A program that supports the MCP will let the MCP control its launch when you boot your machine.
For years now, you boot your machine and if you have DesktopX and ObjectBar (for instance) set to load on start up what happens? You see your explorer desktop and then a bunch "stuff" happening that looks really crummy and confusing as these programs alter your desktop and worse, slow down your boot time.
With MCP, when you logon to your machine it coordiantes your various programs that are trying to load so that they load quicker and when you see your desktop, it is already set up how you want.
The first Object Desktop component to use MCP is ObjectBar 1.6A which is now available for download. You'll need to install the MCP/ObjectBar and then reboot to see its effects.
The MCP has many other capabilities such as managing system hooks. Eventually there will only need to be a couple system hooks total rather than each program having its own (slowing down the system). If third parties make use of this, it will allow users to customize their computers much more thoroughly without a system hook speed hits.
The next beta of DesktopX 2 will also make use of this. And we hope for WinStyles to be able to make use of this so that when you apply a new theme, it can be done without the user having to see a bunch of inelegant desktop switching occuring.
We hope you like it. There's a lot of exciting new technologies about to be released onto Object Desktop this year. This one is one of the more interesting ones we think.
Nomad529
Reply #2 Thursday, February 27, 2003 11:32 PM
Reply #2 Thursday, February 27, 2003 11:32 PM
~ Fantastic!! Can't wait to see how this develops and is incorporated into everything. 
BoddhiC
Reply #3 Thursday, February 27, 2003 11:50 PM
Reply #3 Thursday, February 27, 2003 11:50 PM
Could be very cool once all of the SD app's (and main 3rd party skinned apps) use it. Neat idea 
eidylon
Reply #5 Friday, February 28, 2003 9:07 AM
Reply #5 Friday, February 28, 2003 9:07 AM
Havent tried it yet. Like the throw-back to TRON though.
rockafire1
Reply #6 Friday, February 28, 2003 10:32 AM
Reply #6 Friday, February 28, 2003 10:32 AM
Wow, this sounds like one more step in making the skinning process seamless. I can never stand having things come up and then get skinned. If you'll be able to boot up with everything already skinned that's really great.
da_zman20
Reply #8 Friday, February 28, 2003 1:42 PM
Reply #8 Friday, February 28, 2003 1:42 PM
kinda makes you wonder... why doesn't microsoft think of these things??? 
AlexUnderCover
Reply #9 Friday, February 28, 2003 4:38 PM
Reply #9 Friday, February 28, 2003 4:38 PM
This is incredibly exciting. Just when I think Stardock can't top themselves they innovate yet again. What a great idea. Keep up the great work! 
bussie
Reply #10 Friday, February 28, 2003 6:33 PM
Reply #10 Friday, February 28, 2003 6:33 PM
Hi there,
I have installed it together with the latest OjbectBar release, but i don't see any difference.
How do you or must you configure this?
Greets,
Chris
I have installed it together with the latest OjbectBar release, but i don't see any difference.
How do you or must you configure this?
Greets,
Chris
Frogboy
Reply #12 Friday, February 28, 2003 9:40 PM
Reply #12 Friday, February 28, 2003 9:40 PM
There's nothing to configure. If you have ObjectBar set to load on start-up it then when you boot your machine, ObjectBar will already be running before you get to your desktop.
Thomas Thomassen
Reply #13 Saturday, March 1, 2003 8:23 AM
Reply #13 Saturday, March 1, 2003 8:23 AM
aah! so THAT's what it is! maybe I should have it a go then..
amdavies
Reply #14 Saturday, March 1, 2003 9:30 AM
Reply #14 Saturday, March 1, 2003 9:30 AM
same thought as u Thomas only does a prog i dont use tho atm 
only does a prog i dont use tho atm 
ElectronicMan
Reply #15 Monday, March 3, 2003 1:07 AM
Reply #15 Monday, March 3, 2003 1:07 AM
this s great, its good that stardock is improving all components. Only one thing, and i don't know if someone has already tell something like this, but at the same time all components give a better look to windows also loses compatibility with the rest of software, example: games that uses 3D capabilities, some CAD programs have problems with shadows of WindowFX, or certain also with WindowsBlinds. I know its difficult to make compatible with all different hardware, but the effort of Stardock also has to be that his components are transparent to any software that runs perfectly without ObjectDesktop Suite. Well, that s my opinion. 
Emmitt_Nervend
Reply #16 Tuesday, March 4, 2003 12:57 AM
Reply #16 Tuesday, March 4, 2003 12:57 AM
Actually, as a ODN subscriber for a few years, I respectfully disagree E-man.
There is NO way Stardock can insure its components will work with all apps, there are just too many. Another part of the problem is programs who don't stick 100% to the Windows APIs. Many authors will use "unofficial/undocumented" calls to make their app run faster/better, or simply to take a shortcut in the coding.
I think allowing us to exclude such apps in the setup of Stardock components works very well. I have a number of apps, for instance, that only want the titlebar skinned; skinning the UI makes them unusable. Being able to tailor the components for them lets me retain as much of look I'm going for as I can.
I also find that list of exclusions gets smaller with each release!
There is NO way Stardock can insure its components will work with all apps, there are just too many. Another part of the problem is programs who don't stick 100% to the Windows APIs. Many authors will use "unofficial/undocumented" calls to make their app run faster/better, or simply to take a shortcut in the coding.
I think allowing us to exclude such apps in the setup of Stardock components works very well. I have a number of apps, for instance, that only want the titlebar skinned; skinning the UI makes them unusable. Being able to tailor the components for them lets me retain as much of look I'm going for as I can.
I also find that list of exclusions gets smaller with each release!
goodmorphing
Reply #17 Tuesday, March 4, 2003 1:03 AM WOW... This is way cool! Thanks. I was wishing something like this would happen!
Reply #17 Tuesday, March 4, 2003 1:03 AM
WOW... This is way cool! Thanks. I was wishing something like this would happen!
Ian Hanschen
Reply #18 Tuesday, March 4, 2003 3:33 PM
Reply #18 Tuesday, March 4, 2003 3:33 PM
ElectronicMan: WB4 fixes problems with 3d games, etc. We've worked pretty hard to make sure it's a lot more compatible.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Thursday, February 27, 2003 11:09 PM