Tested on HTC P4350 Herald with stock WM6 unbranded.
The purpose of this is to have the handheld tell me what time it is in the way I choose.
I first made a mortscript to do that (http://xdaforums.com/showpost.php?p=2450016&postcount=659), but I wanted it to have the dignity of a stand-alone app (I have nothing against mortscripts though, they're brilliant). Since my experience with developing for windows, and even more so developing for windows mobile, == NULL, I looked (once again) for ways to get all set up and learn very quickly.
After being reminded for the nth time (it's an every-six-months or so process, recursive) that no, you don't infact learn c++ quickly, even less some newish language you've never seen before, I stumbled onto PPL, what I would think of as a script interpreter with a fairly easy to use IDE.
The result of my few hours of fighting with PPL is attached below for the joy of all children and elderly people.
Installation:
Place the contents of the zip in a folder wherever you like on the device, then link buttons or shortcuts at leisure to vasquez.exe.
Settings:
The file setup.exe modifies the few settings for the app.
Actor - which sounds set to use (only default available for now);
Format - hh mm only for now, to be joined by "o'clock", "and a half", "quarter to" and so on;
AM/PM - use am/pm or not where appropriate;
12/24 - use a 12 or 24 hours cycle.
Note that using 24 hours the AM/PM setting is ignored.
Bottom Line:
PPL, while easy to use and learn, has its downs:
1) an app that would have taken a few kbs requires instead more than 2mb, because of having to pack the interpreter together with the code (only to be expected really);
2) it takes a while to run the app (each exe being ~1.2mb) and it feels oddly wrong having to wait a few seconds for such a settings menu to appear (you'll see what I mean if you try).
It is my intention to develop this further, although I'd much prefer to rewrite it "properly" using Cwhateversappropriate or .NET or dunnowhat.
But first I'll have to find someone to tutor me through the setting up stage because I always stop before even starting. (Anyone ? Hih, hih. )
Thanks for bearing with my rambling.
The purpose of this is to have the handheld tell me what time it is in the way I choose.
I first made a mortscript to do that (http://xdaforums.com/showpost.php?p=2450016&postcount=659), but I wanted it to have the dignity of a stand-alone app (I have nothing against mortscripts though, they're brilliant). Since my experience with developing for windows, and even more so developing for windows mobile, == NULL, I looked (once again) for ways to get all set up and learn very quickly.
After being reminded for the nth time (it's an every-six-months or so process, recursive) that no, you don't infact learn c++ quickly, even less some newish language you've never seen before, I stumbled onto PPL, what I would think of as a script interpreter with a fairly easy to use IDE.
The result of my few hours of fighting with PPL is attached below for the joy of all children and elderly people.
Installation:
Place the contents of the zip in a folder wherever you like on the device, then link buttons or shortcuts at leisure to vasquez.exe.
Settings:
The file setup.exe modifies the few settings for the app.
Actor - which sounds set to use (only default available for now);
Format - hh mm only for now, to be joined by "o'clock", "and a half", "quarter to" and so on;
AM/PM - use am/pm or not where appropriate;
12/24 - use a 12 or 24 hours cycle.
Note that using 24 hours the AM/PM setting is ignored.
Bottom Line:
PPL, while easy to use and learn, has its downs:
1) an app that would have taken a few kbs requires instead more than 2mb, because of having to pack the interpreter together with the code (only to be expected really);
2) it takes a while to run the app (each exe being ~1.2mb) and it feels oddly wrong having to wait a few seconds for such a settings menu to appear (you'll see what I mean if you try).
It is my intention to develop this further, although I'd much prefer to rewrite it "properly" using Cwhateversappropriate or .NET or dunnowhat.
But first I'll have to find someone to tutor me through the setting up stage because I always stop before even starting. (Anyone ? Hih, hih. )
Thanks for bearing with my rambling.