Software is often made more localisation-friendly by keeping human-language text strings well separated from the core software. When IOTBS is used with a multilingual website, it would be better to take all the English-language text right out of the .js files. This includes the text used to create the controls, the alternate stylesheet titles (which are human-readable), and so on.

Of course one way to do this would be to simply partition the javascript files, and move this text out into a number of separate alternative .js files, but this would be messy and would degrade performance because of the additional http requests.

A better way, and one compatible with the spirit of the "integration" IOTBs variant, might be for the js to optionally read the human readable text from some elements in the HTML of the particular page. In fact, reading the text of alternate stylesheet titles from the js would be a very good thing, getting rid of the redundancy of defining this in the .js too.

What do you think?

Cecil Ward.

I'll look into it, and if it proves feasible (which I think it probably will) look at an update to add this functionality.

Thanks for the tip :^)

Line: 175
Char: 2
Error: 'document.getElementById(...)' is null or not an object
Code: 0

Line 175 points to the following code, what could be wrong with it do you think? (its the original, ive not edited anything)

    //outer form
    this.attrs = { 'action' : '' };
    this.form = this.createElement('form', this.attrs);
    document.getElementById(divid).appendChild(this.form);

Thanks in advance for helping!

xxx

Okay, well it's looking for the container element defined by the first argument in the new bodySwitcher constructor:

new bodySwitcher('screen-switcher', 'Screen styles', 'no', '');

In that example, it would a div or other element with the ID "screen-switcher". So does the element defined in your case actually exist?

Yes, i am using (once)...

<td id="screen-switcher"></td>

The error appears here (the switcher is on all pages)...

oaserv.co.uk

Ive double checked the code and it all appears fine.

Do you have a print switcher? If you're just using a single switcher you can just take it out.

But (there's always a but) I'm having problems in opera 8.53 (the only opera version I've tested)
I first noticed when using print options the background of whatever current screen option is being inherited, !important doesn't help. I thought this might be my coding but when i tested your examples on this site the same thing is happening, and sometimes it doesn't load/display the switching options at all.
It completely crashed on my site so no switching options where available.

Thanks for any help
Jon

Thought it might be Nortons pop up blocker interfering but it looks fine onscreen & still having the same probs offline.

Thanks
Jon

Currently the cookie stores as www.mysite.com, id like it to store as just mysite.com

Any geniuses around to get that working?!?!

Thanks for any help with this!

XXX

Not great news :-(

Do you have any idea how i could manually send the information accross two sub-domains, perhaps use php to check for an existing cookie and then set another?

If so, do you have an example of what it might take to work.

Thanks once again for the reply, really appreciate your help!

xxx

What you could look at is JSON, which does allow cross-domain scripting I believe via some detail of its implementation (that's as much as I know - info at http://www.json.org/js.html)

But it's not simple by any means! I would suggest you might be better off re-assesing your original situation - if you want to unify accesses through http://www.domain.com/ and http://domain.com it would be easier just to setup a redirection on the server (or maybe use mod_rewrite) to silently redirect both addresses to one - whichever you prefer.

Then use the options and reload the page when selected is big or small, and tell me if it is correct. Thank you!

<style type="text/css" media="screen, projection">@import url(../etc.css);</style>
<script type="text/javascript" src="../iotbs2-key-directors-load.js"></script>
<script type="text/javascript" src="../iotbs2-directors.js"></script>
<script type="text/javascript" src="../iotbs2-core.js"></script>
<link rel="stylesheet" type="text/css" id="screen-switcher-stylesheet" href="../stylesheets/screen-switcher-default.css" media="screen" />

etc etc.

If I try the switcher on any of these pages I get a Javascript error 'The system cannot locate the resource specified'.
Do I need to change something in the scripts themselves?
Cheers, thanks in anticipation!

The problem is that the default css MUST be the first to work properly. This is a limitation.

There is any way to put the default css as the second or the third in the list? (I used the director's cut and standard mode)

Bye

I'll look into that again, and schedule it for the next version update.