W
T
Travis Newbury
windandwaves said:
Liked the look and feel a lot. Things broke without JavaScript, but I
use JavaScript so no complaints from me about that. I did not like the
feedback page. It looked odd. Nothing wrong with it, I just did not
like the look of it.
S
Saxman
windandwaves said:
I found it sluggish. Quite a lot of content to download.
P
Paul Watt
windandwaves said:
The graphics took a while to load, but when they did, it looked good and
professional.
(2Mb connection BTW)
E
Ed Mullen
windandwaves said:
Nice look. Some problems with text scaling. See:
http://edmullen.net/temp/nz1.jpg
--
Ed Mullen
http://edmullen.net
http://mozilla.edmullen.net
http://abington.edmullen.net
Friends help you move. Real friends help you move the bodies.
P
Philip Ronan
"windandwaves said:
The home page loaded really slowly for me too (2 MB broadband). This
isn't so much a problem with your site, but the server you hosted it on.
Here are the ping results from my desktop:
This is just dreadful. For comparison, the average round trip delay to
www.ford.co.nz (picked at random) was 51 ms (and no lost packets either).
Design-wise it looks fine apart from the sucky contact page.
Good luck
W
windandwaves
Ed said:
Thanks Ed,
Yes, I am aware of that... That was a compromise with the designer.
Thanks a million everyone for the feedback. Much appreciated.
J
Jonathan N. Little
windandwaves said:
Maybe with broadband you will not noticed this but your very long
expanding menu should initialize in the compact mode.
W
windandwaves
Hi JonathanJonathan said:
Thank you for your comment. I totally agree, it is just that I am not
sure how.
If I put display: none; in the css then the javascript does not open it
when it should.
I think it is a timing issue or so, but I am not sure how to fix it.
Cheers
Nicolaas
J
Jonathan N. Little
windandwaves said:
Here is how I would do it:
1 by default in your CSS have it all displayed
2 by JavaScript add link to stylesheet that redefines menu lists as
display: none (collapsed mode) That way if one has JavaScript disabled
they will still see your menu!
3 In JavaScript have flags vars initialized as FALSE for each
collapsible menus
4 With your JavaScript adds onclick handlers for menu "expander" links
to toggle flag of menu. If flag is TRUE then for associated menu, by the
id, set display property to "block", or if FALSE set to "none".
W
windandwaves
Hi Dudes
If you visit www.photowarehouse.co.nz again.... Do you find the menu
loads faster now? I have added a bit of script that is supposed to
action before the body onload thing is ready.
Thanks
Nicolaas
If you visit www.photowarehouse.co.nz again.... Do you find the menu
loads faster now? I have added a bit of script that is supposed to
action before the body onload thing is ready.
Thanks
Nicolaas
P
Philip Ronan
"windandwaves said:
Your site is as slow as ever. And the ping response is even worse now.
------------------------------------------------------------------
$ ping -c 3 www.photowarehouse.co.nz
PING www.photowarehouse.co.nz (210.48.108.38): 56 data bytes
64 bytes from 210.48.108.38: icmp_seq=1 ttl=48 time=368.436 ms
--- www.photowarehouse.co.nz ping statistics ---
3 packets transmitted, 1 packets received, 66% packet loss
round-trip min/avg/max/stddev = 368.436/368.436/368.436/0.000 ms
------------------------------------------------------------------
You have to get away from this useless hosting company you're with at
the moment. It really is unbelievably crap. Jiggling around with the
menu script is not going to solve your problems.
Oh, and the contact page still sucks. It looks ugly and the pre-filled
text boxes are very irritating. Use labels.
B
Bergamot
windandwaves said:
Seems to be even slower loading than it was yesterday. The menu is still
15 screens long - way too much info for good usability.
Doesn't help me a bit, since I usually run with JS disabled.
B
Blinky the Shark
Bergamot said:
I call those "toilet paper" pages, named after the long roll.
W
windandwaves
Philip said:
Pinging www.photowarehouse.co.nz [210.48.108.38] with 32 bytes of data:
Reply from 210.48.108.38: bytes=32 time=21ms TTL=52
Reply from 210.48.108.38: bytes=32 time=25ms TTL=52
Reply from 210.48.108.38: bytes=32 time=21ms TTL=52
Reply from 210.48.108.38: bytes=32 time=24ms TTL=52
Ping statistics for 210.48.108.38:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 25ms, Average = 22ms
It seems fast here in New Zealand and we are targetting a New Zealand
audience.
I have taken it up wit the hosting company to hear their side of the
story.
Thanks a million for this
Will be fixed
W
windandwaves
Bergamot said:Seems to be even slower loading than it was yesterday. The menu is still
15 screens long - way too much info for good usability.
Doesn't help me a bit, since I usually run with JS disabled.
Hmmm, yes, we discriminate against those folk at the moment. Sorry.
That is good feedback. I guess at least it works with JS (albeit
sluggish).
J
Jonathan N. Little
windandwaves said:
Nope still slow, and having the menu fully expanded upon init is
distracting. Here is a little demo as to how you could start with the
menu closed, and support if the visitor has JavaScript disabled. In the
demo the style and JavaScript is in the head, but you would have them in
external files. Not that the body markup pristine and does not have any
JavaScript, but it is assigned upon loading....
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>template</title>
<style type="text/css">
#sm1,#sm2,#sm3 {
display: block;
}
</style>
<script type="text/javascript">
var buf='<style type="text/css">#sm1, #sm2, #sm3 { display: none;
}</style>';
document.write(buf);
</script>
<script type="text/javascript">
var menus=new Array('m1', 'm2', 'm3');
function toggle(e){
var me;
if(!e) var e=window.event;
if(e.target) me=e.target; // W3C
else if(e.srcElement) me=e.srcElement; // MSIE
if(me.nodeType == 3) me=me.parentNode; // Safari bug on elements
with TEXT
var id='s' + me.id;
var submenu=document.getElementById(id);
me.flag =! me.flag;
if(me.flag) submenu.style.display="block";
else submenu.style.display="none";
}
function initMenus(){
for( var i=0; i<menus.length; i++){
var menu=document.getElementById(menus);
//alert('Init ' + menus + ' which is ' + menu.tagName );
menu.flag=false;
if(menu.addEventListener){
menu.addEventListener('click', toggle, false);
}
else if(menu.attachEvent){ //MS IE support
menu.attachEvent('onclick', toggle);
}
}
}
// attach event after page loads
if( window.addEventListener ) {
window.addEventListener('load',initMenus,false); //legacy
} else if( document.addEventListener ) {
document.addEventListener('load',initMenus,false); //proper
} else if( window.attachEvent ) {
window.attachEvent("onload", initMenus); //IE only
}
</script>
</head>
<body>
<ul>
<li><a href="#" id="m1">Menu 1</a>
<ul id="sm1">
<li>Submenu 1.1</li>
<li>Submenu 1.2</li>
<li>Submenu 1.3</li>
</ul>
</li>
<li><a href="#" id="m2">Menu 2</a>
<ul id="sm2">
<li>Submenu 2.1</li>
<li>Submenu 2.2</li>
<li>Submenu 2.3</li>
<li>Submenu 2.4</li>
</ul>
</li>
<li><a href="#" id="m3">Menu 3</a>
<ul id="sm3">
<li>Submenu 3.1</li>
<li>Submenu 3.2</li>
</ul>
</li>
<ul>
</body>
</html>