mcrossley wrote:I'm not convinced that a <#moonday> tag will solve every thing, because the length of a lunation varies by a day or two. Better to create a series of images at set illumination percentages, and use the existing percentage tag. Otherwise things get slightly more complex.
I'm wanting to make it possible to show those images at about the right time for now. Cumulus would, in making a web tag, dictate the pace at which it's progressing through the sequence. So then the images reflect the output from your station as best they can and that is what I am trying to do. At present, I can roughly guess/deduce which 8 images to use out of the bunch and in time (as I learn more about it) that choice can and will be better made. However, far better to have the greater number of images to work with if that is possible, and I accept it may not be possible.
Now as to what you suggested; that sounds like making it even more complex, but I'd be happy to have a stab at modelling and rendering a set for that. How many do you envisage needing to suit your proposition?
Bearing in mind if it's not an automatically generated webtag then I have to have some means of changing the required image, some sort of script, that will need access to some file or other on the web page, and then I would have to retrieve an extra file every so often, read its content and set an image accordingly.
At present I just have Cumulus processing and sending one extra text file as it does it's normal web run. Using web tags I can simply include any extra data I need like that. Doing it externally, the program doing it would need to chose it's moment to do it's stuff.
Oh, and then the reading software (pagescraper plugin in Samurize) would have to grab it without there being a file lock on it too! Now maybe it's that I'm a novice but that's starting to sound pretty blooming complex! Of course I could be dead wrong about that, but that is just how it strikes me right now.