You'd have to screw with either memory/swap/process-scheduling optimizations, or modify hildon, either Hildon Desktop or Hildon Status Menu... You may be able to also modify python...

This is assuming of course that the code is already optimized, which it may or may not be. *Shrug* I just don't think there's much you can do because the choppiness is presumably the new clock being loaded or swapped in/out. Either you do that, or you keep all the clocks loaded in memory, and not swapped, which, well, would take up more ram than ideal I suspect.

Whitewolf: That was the point of his link. If you understand what the link says, you understand what the custom line is there for. I don't think there's a simple way to explain it beyond %h = hour, %d = day, etc.

Les Garten: The clock settings aren't in the status menu anymore, they're in the Settings menu. Other than that... Try to reinstall, see if it works better this time around? I can't really say much else unless it refuses to work upon reinstall, at which point it's time to evaluate what your other installed things are.

- Edit -

Alright, as you guys can see here, I'm messing around with cloning the WiFi signal applet as a set of bars on the right-most side of the clock, mimicking the signal bars of the cellphone signal. Now, how does everyone feel about that? Would you prefer a number, 1-10 (and X if unconnected/unloaded), or do you all think signal bars are better? (It would still show ten levels - the gray bars go up for 1-5, then white bars cover those from 6-10.) (If I know what I'm doing by then I may make a more precise cell-phone signal applet to do the same for the normal one - show gray/white bars, allowing for ten levels, instead of just white bars for five levels.)

Meanwhile, if I used the signal bar clone to display signal, it lets me try to put other info in the space under it (like, encryption type, maybe? IDK. Whatever makes sense and I can figure out how to get the info for.)