Alex schrieb:
Marco Schuster wrote:
On Sun, Aug 16, 2009 at 5:04 PM, Alex <mrzmanwiki@gmail.com mailto:mrzmanwiki@gmail.com> wrote:
I think this would be a good idea. I've actually been considering something like this for my tools. My idea was to use multiple files. One would be for issues that would affect every tool, like if the webserver was going to be down. Others would be for issues that may only affect a couple tools, like one of the DB-servers being down, or high replag on a server. That way tools that don't need DB access or aren't significantly affected by high replag won't have unnecessary notices but the tools that do need it can still have the notice.Why so difficult? Put it into a div structure:
<div id="notice"> <!-- *global* stuff goes here --> </div> <div id="notice-s1"> <!-- *s1* related stuff goes here --> </div> <div id="notice-s2"> <!-- *s2* related stuff goes here --> </div> <div id="notice-s3"> <!-- *s3* related stuff goes here --> </div>
This way you can selectively choose to display the status of components relevant to the specific tool.
Marco
I considered that as well, but figured it would likely be more difficult. It'll require every tool that uses it to have an extra stylesheet to hide all the notices that shouldn't be displayed. Additionally, it means the notice is going to be constantly filled with half a dozen empty divs, or the people updating it will have to remember what IDs to use for each notice.
Don't think too much in html. Some tools won't produce HTML but RSS, XML, TEXT, PDF or sth. How are they supposed to handle this? I'll opt for simple & plain text.
Peter