[Wisbar Console] Nifty idea or is it just me

[psych0t1c]

Being the individualistic pseudo-poweruser I like to see myself as I had a little thing I wanted my device to do and last night a pretty nice idea crossed my mind. Actually I was fiddling with MortScript to create a timed dock that automatically closes after a few seconds (got it working, by the way).

But it occured to me that one could boost the possibilities of WA2/WAD setups extremely if one had a batch/macro/something of that type language. Something like command line parameters on steroids. This way (and maybe still in combination with MortScript) it would be possible to build volume/backlight sliders, you could have toggle switches with oh-so-many functions and possibilities etc. I am totally aware of the complexity added to creating skins, but I have to admit that is what I am after. And troubleshooting/explaining/documenting this thing (let's call it WBC for WisBar Console for the time being) would be a nightmare because not everybody has the background knowledge and coder-like type of thinking.

But maybe spme other people will also yell "Yes!" and we can make Chris think about it for a second. And maybe it is even kind of not-very-hard to do, because all that is needed is a way to launch functions and routines already present in the WA2 and WAD programs.

What I imagine is another (third product) that works kinda like MortScript. Morscript is a very small batch and automation script language. To clarify here is the MortScript script that I mentioned above (timed docks):

Run \path\desktopapp.exe, --show-dock=timeanddate
sleep 3500
Run \path\desktopapp.exe, --hide-dock=timeanddate

This is executed on a shortcut tap. It calls WAD externally, tells it to show the dock named "timeanddate", waits 3.5 seconds and then closes he dock by another external call.

Now, if somehow (via WBC) we had the possibility of altering items (replacing image files) currently in display we could make toggle switches. By querying and editing registry settings (via Mortscript) and then making changes to the Desktop we could realize status indivators. By using a set of special images with an additional overlay image (that we can relocate with external calls) we could make sliders for volume, backlightor whatever. You could monitor most any system state with a Mortscript script and have WBC add certain icons to get system warnings. Same goes for WA2, if one could actually query WA2 settings and states externally and control them externally it would be a dream.

What do you guys think?

[agiorgitis]

I think it need a lot of time to make it, for both you and Chris...
Apart from that, it's very interesting...

[psych0t1c]

Originally Posted by agiorgitis

I think it need a lot of time to make it, for both you and Chris...
Apart from that, it's very interesting...

Hmmm, not a lot of resonance regarding this. Maybe we are the only ones...

[craig139]

What exactly IS MortScript?

[Chris_McKay]

Originally Posted by psych0t1c

Being the individualistic pseudo-poweruser I like to see myself as I had a little thing I wanted my device to do and last night a pretty nice idea crossed my mind. Actually I was fiddling with MortScript to create a timed dock that automatically closes after a few seconds (got it working, by the way).

But it occured to me that one could boost the possibilities of WA2/WAD setups extremely if one had a batch/macro/something of that type language. Something like command line parameters on steroids. This way (and maybe still in combination with MortScript) it would be possible to build volume/backlight sliders, you could have toggle switches with oh-so-many functions and possibilities etc. I am totally aware of the complexity added to creating skins, but I have to admit that is what I am after. And troubleshooting/explaining/documenting this thing (let's call it WBC for WisBar Console for the time being) would be a nightmare because not everybody has the background knowledge and coder-like type of thinking.

But maybe spme other people will also yell "Yes!" and we can make Chris think about it for a second. And maybe it is even kind of not-very-hard to do, because all that is needed is a way to launch functions and routines already present in the WA2 and WAD programs.

What I imagine is another (third product) that works kinda like MortScript. Morscript is a very small batch and automation script language. To clarify here is the MortScript script that I mentioned above (timed docks):

Run \path\desktopapp.exe, --show-dock=timeanddate
sleep 3500
Run \path\desktopapp.exe, --hide-dock=timeanddate

This is executed on a shortcut tap. It calls WAD externally, tells it to show the dock named "timeanddate", waits 3.5 seconds and then closes he dock by another external call.

Now, if somehow (via WBC) we had the possibility of altering items (replacing image files) currently in display we could make toggle switches. By querying and editing registry settings (via Mortscript) and then making changes to the Desktop we could realize status indivators. By using a set of special images with an additional overlay image (that we can relocate with external calls) we could make sliders for volume, backlightor whatever. You could monitor most any system state with a Mortscript script and have WBC add certain icons to get system warnings. Same goes for WA2, if one could actually query WA2 settings and states externally and control them externally it would be a dream.

What do you guys think?

You know, I actually do have plans to do something like this in the near future. I just need to make sure that I don't violate my non-compete agreement as I write just this type of program for my fulltime job. So far, that's been the only hangup.

[psych0t1c]

Originally Posted by craig139

What exactly IS MortScript?

http://www.pocketpcfreewares.com/en/index.php?soft=1448
MortScript (formerly MortRun) is a macro type program that performs many commands. You can automate many tasks, such as, disabling your external keyboard and enabling your game pad, and vice-versa. The possibilities are endless. Using a text editor, such as UKNote, scripts must be saved with a *.mscr extension. And the author honestly states, "For beginners, this might be a bit too complicated."

[psych0t1c]

Originally Posted by Chris_McKay

You know, I actually do have plans to do something like this in the near future. I just need to make sure that I don't violate my non-compete agreement as I write just this type of program for my fulltime job. So far, that's been the only hangup.

Ohhh, great. Hope you can get the legalese sorted out...

[Gog]

This console is an interesting idea. If it also allowed me to review/edit/clone/graft my WAD objects - sort of WAD Explorer that would suit me fine.
The Gog.

[c_shekhar]

Originally Posted by psych0t1c

Being the individualistic pseudo-poweruser I like to see myself as I had a little thing I wanted my device to do and last night a pretty nice idea crossed my mind. Actually I was fiddling with MortScript to create a timed dock that automatically closes after a few seconds (got it working, by the way).

But it occured to me that one could boost the possibilities of WA2/WAD setups extremely if one had a batch/macro/something of that type language. Something like command line parameters on steroids. This way (and maybe still in combination with MortScript) it would be possible to build volume/backlight sliders, you could have toggle switches with oh-so-many functions and possibilities etc. I am totally aware of the complexity added to creating skins, but I have to admit that is what I am after. And troubleshooting/explaining/documenting this thing (let's call it WBC for WisBar Console for the time being) would be a nightmare because not everybody has the background knowledge and coder-like type of thinking.

But maybe spme other people will also yell "Yes!" and we can make Chris think about it for a second. And maybe it is even kind of not-very-hard to do, because all that is needed is a way to launch functions and routines already present in the WA2 and WAD programs.

What I imagine is another (third product) that works kinda like MortScript. Morscript is a very small batch and automation script language. To clarify here is the MortScript script that I mentioned above (timed docks):

Run \path\desktopapp.exe, --show-dock=timeanddate
sleep 3500
Run \path\desktopapp.exe, --hide-dock=timeanddate

This is executed on a shortcut tap. It calls WAD externally, tells it to show the dock named "timeanddate", waits 3.5 seconds and then closes he dock by another external call.

Now, if somehow (via WBC) we had the possibility of altering items (replacing image files) currently in display we could make toggle switches. By querying and editing registry settings (via Mortscript) and then making changes to the Desktop we could realize status indivators. By using a set of special images with an additional overlay image (that we can relocate with external calls) we could make sliders for volume, backlightor whatever. You could monitor most any system state with a Mortscript script and have WBC add certain icons to get system warnings. Same goes for WA2, if one could actually query WA2 settings and states externally and control them externally it would be a dream.

What do you guys think?

Greate psychot1c. I wish to display few texts on the desktop/VP by reding the registry values and i feel mortscript can be used to execute the WAD commands externally by using destopapp.exe . But where do I get the list of command lines relevent to WAD2 ? Can you guide me????

[speedy1979]

It sounds like you could possibly make an animated signal strength icon for wifi with mortscript. By selectively displaying buttons of a certain color representing x -db's. or something like that. psych0t1c you are a genius.