Notices

@Wonko
Could you add
on the prerm script? I noticed that whenever I uninstall this the specified folder isn't removed also whenever I update it the clock doesn't show up. So in order to fix it I need to
apt-get remove advance-clock-plugin --purge
&
rm -rf /usr/lib/advance-clock-plugin/clocks
then I do a fresh installd

I have not installed the clock-settings-ui.

I think if you have the previous version installed, then updating to v0.11 is no problem because you still have those the new 0.11 version is missing.

Just tried a purge removal with root rightnow, then install from x-terminal, but still, nothing shown up on the status bar.

@Duy2anh
Version 0.11.1-1 should be online now.
Edit:
You can get the currently installed version number by, e.g., running (as root):
@Radicalz38
Actually, /usr/lib/advanced-clock-plugin should be a symlink pointing to /opt/maemo/usr/lib/advanced-clock-plugin.
Probably there are any leftovers from old versions either in /usr/lib/advanced-clock-plugin or /opt/maemo/usr/lib/advanced-clock-plugin.
I think I had a version where I accidentally packaged ".svn" directories.
In order to start completely from scratch try uninstalling Advanced Clock Plugin and then completely remove both directories /usr/lib/advanced-clock-plugin and /opt/maemo/usr/lib/advanced-clock-plugin.
From then on you shouldn't have any problems with updating.

@all who voted so far:
Excuse the inconvenience, I just promoted 0.11.1-1 to testing.

Maybe it is swimming now It has not reached Japan yet. I am waiting for it.

Thank you for your effort. I would like to vote for it as a replacement for the built-in one

@duy2anh

try this command on x-term....
if you already install the packages then
as root wrote this command....

dpkg --configure -a (to fixed broken packages)

if you still have the same problem the as root wrote this in x-term...

apt-get purge advanced-clock-plugin
&
apt-get purge advanced-clock-plugin-settings-ui


then update your catalog before you installing the latest version of this plugins....

The update (v0.11.1-1) just shows up now, quite a good swimmer! But to make everything clean I follow these advice before reinstalling the clock:

Nothing shown up.

Even though I haven't got the settings-ui installed.
Then:

apt-get autoremove
apt-get clean
apt-get update
apt-get install advanced-clock-plugin

The clock has been shown on the status bar!
Thank you for your kind helps.

Hoping it does not eat up all the battery and CPU.

Oh no, Conky shows an almost constant 500MHz CPU speed at 15% - 25% usage, sometimes jump to 600MHz but never under 500MHz, that is to say nothing is running but Conky and the Wifi connection. This is bad because I don't overclock my phone.

Turning off Wifi does not help, Conky still reports CPU speed 500MHz 13%-15% at lowest.

Any ideas?

Firstly, nice to see you got it working.
So I assume the dependency issues are finally eliminated.
Hence, I'll leave this version in extras-testing for your judgement.
Anyway, 0.11.1-1 would be a nice "Schnapszahl" for an initial release to extras.

With respect to the performance problems you are experiencing.
Maybe try to disable "Show Seconds" and see if this improves the situation.
Furthermore, the clock suspends once the display turns off.
I am using the clock with "Show Seconds" disabled and couldn't identify a significant decrease of battery-life yet.

What seems to be indeed problematic with respect to power consumption and thus battery life is the restart of the status menu when developing.
So repeatedly restarting the hildon-status-menu may have a strong impact on your battery-life.

Is this optified?

It is.
Though, for installing custom clocks this makes no difference as /usr/lib/advaced-clock-plugin is a symbolic link pointing to /opt/maemo/usr/lib/advaced-clock-plugin.
Only things not in opt are the icons, the desktop files and the "libs" to start the status menu plugin and the control panel UI off.

To be honest the python files for the clocks are that small that optification was not really needed.
Though, while I was at it and merging the packages I also put the directory in opt.
This should provide more flexibility for future extension.

Ok, here are a few clock ideas:

* RGB 2 digits 7 segments clock like described at http://www.jave.de/blog2/?p=36

* Base 8 mode, both regular HH:MM:SS mode and counting the seconds since midnight, using "▁▂▃▄▅▆▇█" for the digits from 0 to 7

* Binary modes (decimal encoded, regular binary, unix time, graycode variatiations etc) using using these characters for each 4 bits: ╵ ╶ └ ╷ │ ┌ ├ ╴┘ ─ ┴ ┐┤┬ ┼ (that is 0001 to 1111 in regular binary, for 0000 use an empty space of the same width)

* Same as the previous, but using these characters instead: ▘ ▝ ▀ ▖ ▋ ▞ ▛ ▗ ▚ ▐ ▜ ▄ ▙ █ (same deal with 0000)

* Like the 2 before this, but for each 8 bits, using the characters from the braille pattern block of Unicode; but also with an option for using the dot order based on the braille dot order or the more intuitive left-to-right/top-to-bottom order, and an option for displaying the time as it would be written in braille.

* This one i'm not sure if it would work, binary encoded as sum of sines, displayed as a wavy (or flat for 00000....) horizontal line, when the first bit is 1 the line will contain the curve for sine(x*(PI*(2^(1-1))), if the second bit is 1 the line will contain the curve for sine(x*(PI*(2^(2-1))), with the third being 1 you add the curve for sine(x*(PI*(2^(3-1))) and so on, with x going from -1.0 to 1.0 with as many steps as there are pixels in the set width for the clock; basiclyeach bit is twice the frequency of the previous bit with the exception of the very first that has the frequency of once per cycle. With this one you can make regular binary seconds since midnight and perhaps unix time too if there are enough pixels, and gray code variations. Perhaps when needing more bits, you could go RGB, drawing the wavy .ines additivelly on a black background, aplitting the bits evenlly over the 3 color components, or 5 (24 is 11000) for red, 6 (60 is 111100) for green and 6 for blue for a decimal encoded mode.


edit: regarding the wavy line, after ploting each line you should "normalize" the Y axis otherwise the biggest peaks and valleys will go beyond the height avaiable.

For the binnary modes above, you can also offer an RGB copositing mode option as well, and for all the RGB modes (including the 7-elements clock one) you could also offer a reverse mode (works the same but you subtract R,G and B from a white background instead of adding to a black one)