Widgets versus Objects

from WinCustomize Forums
I was wondering. After playing with DesktopX widgets and objects, I have discovered that most objects are also made into widgets. What is the optimal configuration? Is it less memory to run it as an widget than running it as an object. What are the advantages and disadvantages of running either, both, or neither? I just am interested in what other people have found to be true. I have a few objects that don't have a widget, but all of my widgets also have objects. I just want my system to run optimally, so what do you all think?
desktopx
2,740 views 11 replies
Reply #1 from WinCustomize Forums Top
objects need desktopx running
widgets need desktopx installed
gadgets need a pc
Reply #2 from WinCustomize Forums Top
I make all objects ( if possible ) into a widget. With widgets you dont need desktopx to be running..an object requires desktopx to be running and for people like me that have older computers..it saves resources. But, I can run 20 widgets at a time if I want..hit f 10 they all hide. They use no resources on hide mode..also..if you make an object an widget..then you can use the hue slider and transparency that is in a widgets properties. Unless an object is made with specifific color changes and transparency..you wont have this option ..but a simple import export back as a widget changes that.

Plus..it takes very little time to do this.
DeskScapes - Bring your desktop background to life.
Reply #3 from WinCustomize Forums Top
They use no resources on hide mode


Not true at all, unfortunately. There may be an initial drop in the RAM use when you hide them, but they still continue to use a few megs of RAM and the virtual memory use will be pretty much constant.

For me the biggest thing is that if I import numerous widgets as objects and run DesktopX there is the potential for significantly less RAM use. Say I have 5 widgets running, each averaging 2-5 megs of RAM. That is anywhere from 10-25 megs, but if I run DesktopX and import them all there will be one process that will be as low as 2-3, perhaps 6 megs of RAM (plus less virtual memory, less handles and fewer GDI objects). Some widgets work better as widgets, but most import very well, and this can be used to save system resources as well as saved as a desktop that can instantly load all my widgets in one click.
Reply #4 from WinCustomize Forums Top
objects need desktopx running
widgets need desktopx installed
gadgets need a pc


Gadgets also need Windows.
Reply #5 from WinCustomize Forums Top
if I run DesktopX and import them all there will be one process that will be as low as 2-3, perhaps 6 megs of RAM (plus less virtual memory, less handles and fewer GDI objects). Some widgets work better as widgets, but most import very well, and this can be used to save system resources as well as saved as a desktop that can instantly load all my widgets in one click.


So then what you are saying is that it is more resource efficient to run as many widgets that will run as an object and to leave objects, objects. If that is the case then would you need to check the checkbox in widget properties to startup automatically?
Reply #6 from WinCustomize Forums Top
Yes, it is more resource efficient if you really want to be cautious with resource use. As I said, some widgets really work better as widgets, as they really need their right click menus. But most import just fine and you end up running mulitple widgets under one process.

To be fair though, most widgets use a pretty trivial amount of RAM and such, so unless you are running lots it isn't that big of a deal. Oh, and if you are importing them and running them you don't need to have each one start up automatically. Just have DesktopX.exe run at start up and all those imported widgets will load on their own.
Reply #7 from WinCustomize Forums Top
Thanks for the advice. I totally understand what you mean about some widgets needing their right click menu. I tried with a recycle bin widget to import it, but then I couldn't empty the bin, so I had to delete the import and start it as a wisget. The other thing I like about running widgets imported is that they don't show up in the first page of the task manager that way, and also don't appear in the startup folder, thereby not producing task bar icons. Again, thanks for the advice. Joe
Reply #8 from WinCustomize Forums Top
Might work for you to have desktopX running..but for me..it puts a drag on my computer . I prefer to just run widgets without desktopX. Im sure you all have more RAM than I do so its not a problem. This is why I dont use DesktopX themes..Maybe when I get a new computer with tons of Ran I can enjoy those too.
Reply #9 from WinCustomize Forums Top
Most widgets will have under their properties the option to adjust accessability, Taskbar, SysTray, or none. Selecting none will keep the widget from creating a SysTray icon or TaskBar slot.

If you are using a lot of widgets, importing them as objects may save resources, but if you only run a couple, go with running as a widget (I say) so you can access all their options.
Reply #10 from WinCustomize Forums Top
More important is the aims of the two sections. What should happen is that finished solutions should be uploaded as Widgets. People can still import them into DesktopX to learn how they were created if they want to, but they can also be run immediately for convenience.

The Object library should be more focussed at tutorials, samples and tools that others can use in the creation of widgets.

Hope this helps
Reply #11 from WinCustomize Forums Top
The Object library should be more focussed at tutorials, samples and tools that others can use in the creation of widgets.


That makes sense Martin, except for the fact that some functionality can not be easily accessed when the object is turned into a widget. I've made several objects that have configurable shortcuts, with some scripting built in to add a shortcut, change the name, etc. But when it comes to setting the target, there's no convenient way to do it other than the built-in DX dialog, and that becomes unavailable with a widget.

This became evident the first time I released one of those kinds of objects as a widget, and I ended up having to tell people they had to import them as objects in order to set them up.

A simple addition to the properties and methods exposed to widgets could correct this.