Skip to main content
update header style, add jquery tag
Source Link

index.html: ###index.html:

funcs.js: ###funcs.js:

jsmenucontent.js: ###jsmenucontent.js:

index.html:

funcs.js:

jsmenucontent.js:

###index.html:

###funcs.js:

###jsmenucontent.js:

added 72 characters in body
Source Link
SirPython
  • 13.5k
  • 3
  • 38
  • 93

Theme-swap functionality will be done via a better-looking div<div> at the top of the page, but for right now, it's just thrown on the button. TheThe theme preference should persist through page refreshes via cookiethrough the use of cookies. I'm

I'm going to do five different themes, each in two different sizes, since the site is very bad in 800x600800x600 and still quite bad in 1024x7681024x768.

The page will eventually display via <noscript> for those that don't have JSJavaScript turned on, but for right now, it'll just display a message that says "Please turn JavaScript on!":

Please turn JavaScript on!

  1. Non-JSJavaScript page is displayed with <noscript>
  2. If JSJavaScript is enabled, it loads the theme-preference from cookies.
  3. JSJavaScript then applies the preferred theme via AJAX fetching the appropriate theme (skin[x].htmlskin[x].html) and the content of the page ([page_name.html][page_name.html]).

index.htmlindex.html:

funcs.jsfuncs.js:

jsmenucontent.jsjsmenucontent.js:

Theme-swap functionality will be done via a better-looking div at the top of the page, but for right now, it's just thrown on the button. The theme preference should persist through page refreshes via cookie. I'm going to do five different themes, each in two different sizes, since the site is very bad in 800x600 and still quite bad in 1024x768.

The page will eventually display via <noscript> for those that don't have JS turned on, but for right now, it'll just display a message that says "Please turn JavaScript on!"

  1. Non-JS page is displayed with <noscript>
  2. If JS is enabled, it loads the theme-preference from cookies.
  3. JS then applies the preferred theme via AJAX fetching the appropriate theme (skin[x].html) and the content of the page ([page_name.html]).

index.html:

funcs.js:

jsmenucontent.js:

Theme-swap functionality will be done via a better-looking <div> at the top of the page, but for right now, it's just thrown on the button. The theme preference should persist through page refreshes through the use of cookies.

I'm going to do five different themes, each in two different sizes, since the site is very bad in 800x600 and still quite bad in 1024x768.

The page will eventually display via <noscript> for those that don't have JavaScript turned on but for right now, it'll just display a message that says:

Please turn JavaScript on!

  1. Non-JavaScript page is displayed with <noscript>
  2. If JavaScript is enabled, it loads the theme-preference from cookies.
  3. JavaScript then applies the preferred theme via AJAX fetching the appropriate theme (skin[x].html) and the content of the page ([page_name.html]).

index.html:

funcs.js:

jsmenucontent.js:

deleted 254 characters in body; edited title
Source Link
Jamal
  • 35.2k
  • 13
  • 134
  • 238

Test my skin Skin/theme swap! Thoughts/comments?

Let me know if it breaks or simply doesn't work! I would love experts to review it. I'm good enough to make stuff work, for the most part, but whether or not there is a better approach takes someone with much more wisdom than myself!

PS: I've noticed a bug that happens once in a blue moon, but I think that's because the browser might be doing parallel work and one script gets too far ahead of the other. I'll have to research it more, but I think it's good enough right now to ask for opinions.

PSS: The page will eventually display via for<noscript> for those that don't have JS turned on, but for right now, it'll just display a message that says "Please turn JavaScript on!"

  1. Non-JS page is displayed with   <noscript>
  2. If JS is enabled, it loads the theme theme-preference from cookies.
  3. JS then applies the preferred theme via via AJAX fetching the appropriate theme theme (skin[x].html) and the content of of the page ([page_name.html]).

Here's theThe code. It's not completely isn't perfect yet, and I'll definitely have to remove the use of another person's image as the background for the second skin, but it's almost done. About half of the code deals with merely re-positioning the elements when the window is resized. For the sake of brevity, some code is not shown. I apologize for its length.

index.html:index.html:

funcs.js:funcs.js:

jsmenucontent.js:jsmenucontent.js:

Test my skin/theme swap! Thoughts/comments?

Let me know if it breaks or simply doesn't work! I would love experts to review it. I'm good enough to make stuff work, for the most part, but whether or not there is a better approach takes someone with much more wisdom than myself!

PS: I've noticed a bug that happens once in a blue moon, but I think that's because the browser might be doing parallel work and one script gets too far ahead of the other. I'll have to research it more, but I think it's good enough right now to ask for opinions.

PSS: The page will eventually display via for those that don't have JS turned on, but for right now, it'll just display a message that says "Please turn JavaScript on!"

  1. Non-JS page is displayed with  
  2. If JS is enabled, it loads the theme-preference from cookies.
  3. JS then applies the preferred theme via AJAX fetching the appropriate theme (skin[x].html) and the content of the page ([page_name.html]).

Here's the code. It's not completely perfect yet, and I'll definitely have to remove the use of another person's image as the background for the second skin, but it's almost done. About half of the code deals with merely re-positioning the elements when the window is resized. For the sake of brevity, some code is not shown. I apologize for its length.

index.html:

funcs.js:

jsmenucontent.js:

Skin/theme swap

Let me know if it breaks or simply doesn't work. I've noticed a bug that happens once in a blue moon, but I think that's because the browser might be doing parallel work and one script gets too far ahead of the other. I'll have to research it more, but I think it's good enough right now to ask for opinions.

The page will eventually display via <noscript> for those that don't have JS turned on, but for right now, it'll just display a message that says "Please turn JavaScript on!"

  1. Non-JS page is displayed with <noscript>
  2. If JS is enabled, it loads the theme-preference from cookies.
  3. JS then applies the preferred theme via AJAX fetching the appropriate theme (skin[x].html) and the content of the page ([page_name.html]).

The code isn't perfect yet, and I'll definitely have to remove the use of another person's image as the background for the second skin, but it's almost done. About half of the code deals with merely re-positioning the elements when the window is resized. For the sake of brevity, some code is not shown. I apologize for its length.

index.html:

funcs.js:

jsmenucontent.js:

Irrelevant content and links that don't work anymore. Could possibly use further edits.
Source Link
Loading
added 164 characters in body
Source Link
Michael
  • 323
  • 4
  • 9
Loading
added 360 characters in body; added 91 characters in body; deleted 32 characters in body; deleted 1 characters in body
Source Link
Michael
  • 323
  • 4
  • 9
Loading
added 6314 characters in body
Source Link
Michael
  • 323
  • 4
  • 9
Loading
added 95 characters in body
Source Link
Michael
  • 323
  • 4
  • 9
Loading
added 140 characters in body; added 68 characters in body; deleted 44 characters in body
Source Link
Michael
  • 323
  • 4
  • 9
Loading
added 223 characters in body; added 236 characters in body
Source Link
Michael
  • 323
  • 4
  • 9
Loading
Source Link
Michael
  • 323
  • 4
  • 9
Loading