Great work! I look forward to giving it a try when you finish the last stretch of the journey.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]
OK guys the GPE-PIM suite for Desktop is finally ready!!!
I did it!
Libschedule finally fixed!
Now, please help me to test it!! Logically already did some test on my PC before porting it.
Before testing it, remember 3 important things.
1) Test it at your own risk, because the code changes i made is on a foreigner code so i doesn' t know the all functions links to the library as i worked only in a very limited range.
Theese are the code changes i made.
GPE-ANNOUNCE:a)Deleted the BUZZER device management, as there' s not BUZZER device on Desktop nor on the Zauri.
b)Deleted the VolumeReset function, because has an hardware implication to read the Volume state from the Sound Device. It points to the wrong Memory Address and gives the
"Unable to get the volume" message so it's useless.
It only means that at the end of GPE-Announce message the volume remains how it was set from GPE itself and does not return to the state before Announce woke up.
c) As karlto told me, i reduced the Automatic raise range volume to the 80% than the original 100%.
This to make GPE-Announce not give noises when it wakes up.
You can logically contact me to compile a louder Announce if you like.
d) Raised the sound playing time to 30 SEC instead of 20 for the Automatic issue.
That' s my taste i thought 20 is few to wake up HIHIHIHI!
Logically can change this too.
LIBSCHEDULE:There' s a
#define HAVE_AT in the
atd.c code, that makes you choose from to different implementations of the
AT daemon.
One is related to the Ipaq Family port of AT, that is completely deifferent from the Desktop one and from the Zauri one.
The other is related to the Desktop normal AT daemon.
So i compiled libschedule with the
#HAVE_AT definition enabled and made some fixes to the Makefile to make the deifinition work.
The real problem is for the Zauri.
It has another ATD implentation that is the port of the normal AT daemon without some features.
This makes the normal AT libschedule commands fail and gpe-calendar freeze.
So i have to see what functions can be and what not in the code. This ports to a complete ridefinition of the code and a little more study of the atd.c file. :-(
2) Remember to put a file called
alarm.conf in your
.gpe dir as i said in the previous post:
In this file there must be three lines
:
enable 0 -> 0 means volume on, 1 means silent
automatic 0 -> if 1 raise automatically the level to the maximum and after 20 sec goes down
level 0 -> is a range from 0 to 100 of the Volume that remains static
3) Remember that all the packages i build are completed with the headers to compile things by yourself. This is true for the Zauri ipks too.
This because they are very little in size so it' s only a comfort to have all toghether.
4) Sorry for my English, i' m trying to enhance it.
But i think that only writing here is a good training. Hope logically that you understand!
OK i have finished, i'm very happy that GPE-PIM now fully works on the Desktop.
So i can migrate from Thunderbird to it.
3 things i love 1 is the atd implementation, 2 is the sqlite one, 3 is the portability of the config files without the need of a synchronization.
Now i would like to get the things better when i have time.
I.E. writing to the GPE-PIMS authors about the things i made and make some enhancement with them. So i can understand better the things than stuying the code by myself.
I would like GPE-Announce to sound better it' s a little noisy, maybe an MP3 implementation would be a COOL thing.
I would like the GPE-Contacts to wake up a mail utility to write mails directly from it.
And the main thing is to have GPE-Contacts control a GPRS module via Gammu or Gnokii.
I' m moving to do it, but now i really don' t have time. :-(
So try the packages and let know!!! I will put them online on my PC asap.
Here are the PKGS [a href=\"ftp://217.133.58.241]ftp://217.133.58.241[/url]
Enjoy!!
BYEZ! :-)
