that's a very interesting question because i struggled with this one. displaying the website ip was very important to me because it's your first protection against phishing and dns poisoning. nanny browsers keep checking your surfing constantly and comparing it to blacklists, this is error-prone and list can be outdated or the server down not to mention takes significant bandwidth and can slow your browsing but showing the ip needs a savvy user who can tell when something is fishy
you can display the ip with the macro but this has many limitations, first it will not be constant or realtime becaus it will display it once and if you hover on a link or menu or mouse movement the ip will be replaced by the website or kmeleon own commands.. using the macro will also need to be linked to kmeleon events or triggered by the user so it isn't practical at all so using internal macro for this task was no good
autoit was the answer to this problem working independently from any km command.
since kmeleon is a true win api application; that made controls readable and potentially writable to autoit script language which is heavily focused on windows api
here's a demo:
(note the control id and classes in the autoit window info)
and the statusbar which itself can be dissected into 3 ctrls
compare that with bogus interfaces like firehoax
the only real part of firefox is the titlebar
everything else you see in firefox, tabbar, toolbar..statusbar, scrollbar..are no bars at all, they are make-believe ui. in programming terms firefox is a joke interface, of course since it's more or less html that makes it very easy to change anything in firefox's so-called 'interface', anything you can do to an html page you can do to a firefox
now autoit only needs to read the urlbar text to know the address of the site:
ControlGetText ("[CLASS:KMeleon Browser Window]", "", 1001)
-1001 is the urlbar ctrl id
then it parses that address to get its ip and writes it to the statusbar
ControlSetText("[CLASS:KMeleon Browser Window]", "", 59393, $sdisplay)
-59393 is the text section of the statusbar
because it no longer needs parameters from the macro, this makes the script very fast and realtime..it automatically detects if you have left to another website(urlbar text change) and sets the new ip..and memory usage is so low it's barely noticeable
adding the time to the script is no easy and may have bad effects because autoit is no clock and doesn't have an easy way to constantly read the system clock and display it.. it has macros to fetch current hour and minute but that will change every second or at least every minute if you're not going to display seconds. this will make the script focus more on the time instead on the urlbar site and will increase memory usage
in case of clock+browser, javascript is far more practical like script there:
http://www.bloke.com/javascript/Clock/statusclock.html
(note the statusbar)
but it will override liveip meaning each will be struggling for the statusbar space and the one with more refresh rate(clock in that case) will win.
the js will need to be injected in the macro and set to event onload(every new page).. i think it's doable but the clock refresh rate needs to be same as liveip so the display time is split 50/50 between them.. i'll test a few things