DesktopX 3 Journal: Day 1
Centralized scripting in action
Tuesday, February 8, 2005 by Frogboy | Discussion: DesktopX
Introduction
This is the first in a series of journals I plan to write about the evolution of DesktopX into version 3.
So let me give you a background on this because some people may think "Why so much written stuff on this thing? What's the big deal?"
DesktopX has traditionally acted as an environment where people could put objects on their Windows desktop, and then combine them together to either design a complete desktop or as a mini-application and then export them as a desktop (a DesktopX theme) or as a program for others to use (a widget).
The reason why widgets are such a big deal is that since the Macintosh was released in 1984, we've only had to two types of "things" that would show up on your desktop. You have icons, which are just little static pictures. Or you had full blown applications. There was nothing in between. They either were full blown programs or they were just pictures.
I don't normally toot our horn too much on this issue but because some other programs have tried to imply they somehow came up with this concept, DesktopX was the first program to actually deliver on the concept of having interactive content on your desktop that could be created by end users.
The idea for this isn't new. IBM, Apple, and Microsoft all wanted to have something that was more than an icon but less than a full blown program. Something that could exist on your desktop that wasn't much harder to create than an icon and was a lot less complicated to make than a traditional application.
Centralized Scripting
In DesktopX 2, a widget developer would create several objects on the desktop and then attach bits of scripting to each one based on what they wanted it to do. This made it easier to create fairly simple widgets but more complex ones were a bit of a pain because DesktopX 2.x couldn't really create new objects.
That changes in DesktopX 3. In DesktopX 3, you can control everything in your widgets from a single script. One place this makes things easier is in terms of dealing with user input. In DesktopX 2, the object being clicked on was the object that had to handle the input. This could be a pain in the butt. DesktopX 3 lets callbacks be in the same script.
So let's say you have a widget with several buttons on it. Each button is an object. In DesktopX 2, each object would have to have a script to deal with what happened when the user clicked on that button. In DesktopX 3 a new API exists:
function Object_OnLButtonUp(szObjectName, x, y, bStatus)
{
}
So now you just supply the object name and you can handle its inputs from a single script.
Reply #3 Tuesday, February 8, 2005 4:50 PM
one question: will the current method still work as well? could we use multiple scripts on seperate object?
Reply #6 Tuesday, February 8, 2005 8:44 PM
Reply #7 Wednesday, February 9, 2005 2:08 PM
Reply #8 Wednesday, February 9, 2005 10:39 PM
Reply #9 Wednesday, February 9, 2005 11:25 PM
Reply #10 Thursday, February 10, 2005 8:45 AM
Reply #11 Thursday, February 10, 2005 4:28 PM
Reply #12 Thursday, February 10, 2005 6:13 PM
System tray has nothing to do with DesktopX but rather a buggy MCP. Not that you guys want to know too much internal Stardock politics but the lead developer on MCP was recruited by Microsoft (wait for it) several months ago.
So DesktopX 2.4 and others went to this new standard but MCP hadn't been finished updating. Luckily, the lead from ObjectDock/ObjectBar has been assigned to bringing MCP back to life.
But all that aside, if you really do want to help, we need constructive feedback. Saying DesktopX "doesn't work" because your system tray object isn't displaying system try items on your theme is, a bit excessive don't you think?
Reply #13 Thursday, February 10, 2005 7:18 PM
| System tray has nothing to do with DesktopX but rather a buggy MCP. |
Ah, so you do admit it's a known issue. Thank you! Progress at last!
And as for constructive feedback, I've posted in the newsgroups with screenshots, multiple steps I've tried to correct the issue, and lots of helpful hints. Not so much as even an acknowledgment, so containing the attitude gets a bit difficult at times. I apologize.
Reply #14 Monday, February 21, 2005 5:35 PM
You could contact [email protected]. If others don't know the solution, (I certainly don't) then you can contact them. The MCP is being updated but it's a seperate piece of the puzzle. It's not part of DesktopX.
Bear in mind that MCP is the only reliable (or close to it even) solution for displaying system trays independently. It's non-trivial technology.
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 Tuesday, February 8, 2005 1:49 PM