I was in such a rush yesterday I'm not sure exactly what I did, but my posts didn't show up for some reason.
NBD (er, "no worries") Morris- as I mentioned, so far you're half of the demand, and the other half is running a copy of the current plugin, and is happy for the moment. I need to do the NET programming for the final version anyway... if I do a one-off version modified for NET time, that might satisfy your immediate needs for your site, it will need to be tested anyway, and satisfying the immediate demand will cut me a little slack on delivering a more comprehensive, ready-for-prime-time version. Want to play with a prototype? The "°" thing didn't work out- works as part of the mask, but not in a string returned from Javascript. No problem, I found the symbol in the Unicode tables and used that. Gotta say, still not a fan of the system. I admit I haven't read all the material you linked to yet, so I'll keep an open mind... Still, one NET degree = 4 minutes or 240 seconds, that's fine. There are 60 NET "seconds" in a NET degree, so each NET minute evaluates to 4 conventional seconds, which seems at least a bit confusing. Then we divide that into 60 for NET seconds, and we end up with each NET "second" being two-thirds of one-tenth of a conventional second... might have helped if they'd picked other names, and maybe 4- (conventional) second increments are fine enough for most use, but displays that DO show NET seconds are going to be whirring too fast to really see. Mostly because of that, it's difficult to compare the NET seconds ouput to anything, so I left the math section of the program "fluffed out" a bit to make it more readable in case you want to check it. Degrees and minutes match up fine. I'd recommend the seconds not be used in a real-time display, cranking the refresh up high enough to make the display "work" could be a real drain. Using all three segments in a timestamp is no problem, of course. I didn't really use the math example you sent in the applet, didn't follow all of it and don't much see the point in a program doing sub-calculations that result in a constant, but no doubt the result they get is correct. Based on the website examples and yours I've left-padded the segments out with zeroes, but apparently it's not always displayed that way. I've looked at the output in different fonts, and I think for most purposes it looks better without a space between the segments, but let me know what you think on both points. The math part and output formatting is done for NET time, hopefully today I'll have a chance to tackle the mask string handling. The first version was written in a hurry, I was never been happy with it, and it needs to be modified anyway to handle multi-character delimiters to return UTC datetime strings. If I can get the UTC "delta" working as well... that's about 80 percent of the "broader" scope I outlined. The rest is just some conditional looping in case there are different time zones needed for the same mask (besides local time). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
