Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
rene7705 wrote: In response to critiques about my download size, I've removed scenejs and the artwork for my own site-logos from the zip. The size is now 38mb, down from 54mb. I think it took about a minute at about 470kb/sec. I'm also using 7-zip now, I hope it opens better on non-windows OSes. It worked fine with unzip on linux. -- Per Jessen, Zürich (11.9°C) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
Just tried to load it up on my iPad and the load time was okay... Little slow. But your navigation is completely non functional on my iPad... Might want to look into that since mobile devices are becoming more and more common. Jason Pruim -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Sun, Mar 18, 2012 at 1:24 PM, Jason Pruim li...@pruimphotography.comwrote: Just tried to load it up on my iPad and the load time was okay... Little slow. But your navigation is completely non functional on my iPad... Might want to look into that since mobile devices are becoming more and more common. Jason Pruim I wish I had the money for an real iPad, so I could test it properly. What part of the navigation doesn't work? Do the links in the content work?
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Sun, Mar 18, 2012 at 10:58 AM, Per Jessen p...@computer.org wrote: rene7705 wrote: In response to critiques about my download size, I've removed scenejs and the artwork for my own site-logos from the zip. The size is now 38mb, down from 54mb. I think it took about a minute at about 470kb/sec. I get much better datarates, around 1.5 to 2mb/s... But then again, the server is in europe, and so am I. But I guess a minute is OK... I'm also using 7-zip now, I hope it opens better on non-windows OSes. It worked fine with unzip on linux. Cool :) I hope it works on macOS too! :)
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Sun, Mar 18, 2012 at 1:34 PM, rene7705 rene7...@gmail.com wrote: On Sun, Mar 18, 2012 at 1:24 PM, Jason Pruim li...@pruimphotography.comwrote: Just tried to load it up on my iPad and the load time was okay... Little slow. But your navigation is completely non functional on my iPad... Might want to look into that since mobile devices are becoming more and more common. Jason Pruim I wish I had the money for an real iPad, so I could test it properly. What part of the navigation doesn't work? Do the links in the content work? BTW folks, I also tested it on my samsung smartphone, and my site doesn't work on it yet. Compatibility (also with non-desktop devices) will remain high on my priority list.
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Mar 18, 2012, at 8:34 AM, rene7705 rene7...@gmail.com wrote: On Sun, Mar 18, 2012 at 1:24 PM, Jason Pruim li...@pruimphotography.comwrote: Just tried to load it up on my iPad and the load time was okay... Little slow. But your navigation is completely non functional on my iPad... Might want to look into that since mobile devices are becoming more and more common. Jason Pruim I wish I had the money for an real iPad, so I could test it properly. What part of the navigation doesn't work? Do the links in the content work? From what I can tell its the links on the top... The ones in the Content seem to work but I didn't check all of them. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Sun, Mar 18, 2012 at 1:41 PM, Jason Pruim li...@pruimphotography.comwrote: On Mar 18, 2012, at 8:34 AM, rene7705 rene7...@gmail.com wrote: On Sun, Mar 18, 2012 at 1:24 PM, Jason Pruim li...@pruimphotography.com wrote: Just tried to load it up on my iPad and the load time was okay... Little slow. But your navigation is completely non functional on my iPad... Might want to look into that since mobile devices are becoming more and more common. Jason Pruim I wish I had the money for an real iPad, so I could test it properly. What part of the navigation doesn't work? Do the links in the content work? From what I can tell its the links on the top... The ones in the Content seem to work but I didn't check all of them. It won't be easy for me to debug the menu and button components (links on the top), as I have no friends or family with an iPad i think. But i'll ask around.
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Mar 18, 2012, at 8:54 AM, rene7705 rene7...@gmail.com wrote: On Sun, Mar 18, 2012 at 1:41 PM, Jason Pruim li...@pruimphotography.comwrote: On Mar 18, 2012, at 8:34 AM, rene7705 rene7...@gmail.com wrote: On Sun, Mar 18, 2012 at 1:24 PM, Jason Pruim li...@pruimphotography.com wrote: Just tried to load it up on my iPad and the load time was okay... Little slow. But your navigation is completely non functional on my iPad... Might want to look into that since mobile devices are becoming more and more common. Jason Pruim I wish I had the money for an real iPad, so I could test it properly. What part of the navigation doesn't work? Do the links in the content work? From what I can tell its the links on the top... The ones in the Content seem to work but I didn't check all of them. It won't be easy for me to debug the menu and button components (links on the top), as I have no friends or family with an iPad i think. But i'll ask around. One piece of advice that I have been given is to make everything work at its most basic structure first... Then add the fancy stuff to make it be what you want. That way as you develop and grow with what you know you can add features but your site will work fine without The fancy stuff. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Sun, Mar 18, 2012 at 1:38 PM, rene7705 rene7...@gmail.com wrote: On Sun, Mar 18, 2012 at 1:34 PM, rene7705 rene7...@gmail.com wrote: On Sun, Mar 18, 2012 at 1:24 PM, Jason Pruim li...@pruimphotography.comwrote: Just tried to load it up on my iPad and the load time was okay... Little slow. But your navigation is completely non functional on my iPad... Might want to look into that since mobile devices are becoming more and more common. Jason Pruim I wish I had the money for an real iPad, so I could test it properly. What part of the navigation doesn't work? Do the links in the content work? BTW folks, I also tested it on my samsung smartphone, and my site doesn't work on it yet. Compatibility (also with non-desktop devices) will remain high on my priority list. And another thing I'll put on my to-do list is some way to detect slow links and mobile devices, to send over much lighter artwork (no 2mb logo when you're on a slow/metered link)..
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
rene7705 wrote: On Sun, Mar 18, 2012 at 10:58 AM, Per Jessen p...@computer.org wrote: rene7705 wrote: In response to critiques about my download size, I've removed scenejs and the artwork for my own site-logos from the zip. The size is now 38mb, down from 54mb. I think it took about a minute at about 470kb/sec. I get much better datarates, around 1.5 to 2mb/s... But then again, the server is in europe, and so am I. I'm in Europe too, but your server is about 20 hops away. 470kb/s is pretty good on my 6Mbit downstream though. -- Per Jessen, Zürich (8.2°C) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, 16 Mar 2012 19:57:38 +0100, rene7705 rene7...@gmail.com sent: I could waste a lot of text on what I've accomplished during the last months, but the easiest thing is if you have a (another) look at (the source of) http://mediabeez.ws I seem a bit late to this party, but just wanted to say that the artwork is quite impressive, although I doubt I'd have really much use for the code parts. -- Tamara Temple aka tamouse__ May you never see a stranger's face in the mirror -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On 18 Mar 2012 at 16:39, Tamara Temple tamouse.li...@tamaratemple.com wrote: On Fri, 16 Mar 2012 19:57:38 +0100, rene7705 rene7...@gmail.com sent: I could waste a lot of text on what I've accomplished during the last months, but the easiest thing is if you have a (another) look at (the source of) http://mediabeez.ws I seem a bit late to this party, but just wanted to say that the artwork is quite impressive, although I doubt I'd have really much use for the code parts. I don't like: a) menus that just spring into life because you happen to mouse near them. You should have to sick to activate a menu. b) bright flashy distracting items on a website. Like the OP's menus. -- Cheers -- Tim -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On 18 Mar 2012 at 17:06, Tim Streater t...@clothears.org.uk wrote: I don't like: a) menus that just spring into life because you happen to mouse near them. You should have to sick to activate a menu. Damned autocorrect. s/sick/click/ -- Cheers -- Tim -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Sun, 2012-03-18 at 17:17 +, Tim Streater wrote: On 18 Mar 2012 at 17:06, Tim Streater t...@clothears.org.uk wrote: I don't like: a) menus that just spring into life because you happen to mouse near them. You should have to sick to activate a menu. Damned autocorrect. s/sick/click/ -- Cheers -- Tim -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php I would say it depends on the situation. Forcing an extra click rather than a mouse over (or activation by tabbing to the element) could be an issue for some disabilities, but having said that, relying on a mouse over only is a big no too, as there are plenty of people who are unable to use a mouse well, if at all; we're talking old arthritic users, or people without the use of their hands, for example. That's why, for navigation, I'd rely on the standard links to do the work, and then, as others have mentioned on this thread already, enhance that with script. Add extra menus that can be triggered to show for multiple events (hover, activation by tabbing in, etc) -- Thanks, Ash http://www.ashleysheridan.co.uk
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, 2012-03-16 at 22:11 +0100, rene7705 wrote: On Fri, Mar 16, 2012 at 10:08 PM, Tommy Pham tommy...@gmail.com wrote: On Fri, Mar 16, 2012 at 1:45 PM, Stuart Dallas stu...@3ft9.com wrote: As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. That may be so, but when my 100Mbit/s connection finally managed to download the file it took about 4 minutes, which is nowhere near 2MB/s. Your homepage takes 7 seconds to load - that's unacceptable in the real world, especially when you're talking about a server that's (and I'm only guessing here) not under heavy load. Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ Yup... I think rene forgot the fact is if each client requests pull 1MB/s , his upload has to be at least 120MB/s for 100 simultaneous clients' connections. Last time I check in ISP services, that bandwidth falls within OC-12+ category If ya'll would take a closer look at my site, you'd see that most of the size is in artwork. If you want a simple site, use simple artwork. It's _not_ my code's size that's any problem, as I mentioned earlier. Enough for now, I'll look at this list tomorrow again. Time for partying with the live mix at frequence3.fr now.. Just adding my own two pennies to this lot. It does seem a little irresponsible to create such a large (in size) website, especially when you consider that in many countries people don't have high-speed or unlimited access. Even the UK has lots of areas with only basic Internet access via dial-up lines, and plenty of people rely on mobile dongles to connect, which are most often metered and slow. On to the technicals of what you wanted us to look at, because I think this thread has become slightly derailed from the original question. * The 'Home: Downloads, Blog' link at the top doesn't work for me at all. I'm using Fx 3.6 on Fedora 14 * The drop-down menu appears odd, with some items appearing over the others * The products menu at the top does nothing when clicked on * Other 'pages' take a long time to load in Sorry, but it really doesn't look very professional when basic things (like links) don't work at all. I'd hate to have any kind of disability because I doubt any screen readers would work, and using your site with only a keyboard would probably be just as impossible. That might seem like harsh feedback, but I do have quite a strong view on accessibility. -- Thanks, Ash http://www.ashleysheridan.co.uk
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, Mar 16, 2012 at 10:17 PM, Govinda govinda.webdnat...@gmail.comwrote: Everyone makes valid points.. and depending on ones perspective, certain of those points are more important than others... but, because of my nature anyway, I want to just say thanks to rene7705 for bothering. He is not trying to take anything.. but just share his creative process, in case it is fun for anyone, or useful for anyone. He undoubtedly wants to improve too.. but there is the middle step where positive reinforcement is the most pertinent thing. Rene, don't mind the tones here.. we all get paid to scrutinize, so it can be hard to snap out of that critical mindset sometimes. -Govinda Thanks..
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, Mar 16, 2012 at 11:13 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 20:53, rene7705 wrote: On Fri, Mar 16, 2012 at 9:45 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 20:36, rene7705 wrote: On Fri, Mar 16, 2012 at 9:29 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 18:57, rene7705 wrote: Hi Folks.. I could waste a lot of text on what I've accomplished during the last months, but the easiest thing is if you have a (another) look at (the source of) http://mediabeez.ws I think you'll like my opensourced work :) Feedback is appreciated. I'm also having trouble downloading the ZIP file (Chrome 17.0.963.79 on OSX - not that the browser will have anything to do with this problem at all). The download starts, gets to a few MB and doesn't get any further. And 52MB? Since I can't actually see what it contains it's hard to judge, but right off the bat... is your artwork necessary for the thing to work? What external libraries are you using? Just from looking around the site there are a few things that jump out... * The dropdown menus are incredible jittery, certainly nowhere near production-ready. * The background image gets squished according to the dimensions of the browser window. * Your homepage weighs in at massive 2.6MB. Nuff sed! I suggest you take the focus off the way it looks and concentrate on what it does. Tabs with animated backgrounds remind me of websites from the late 90s. You may have developed an incredible framework here, but I don't know because it's buried under 50MB of other stuff that I almost certainly don't care about, and that's before I've even been able to download it. ok.. That being unable to download the zip file correctly is something I'll take up with my hosting provider tomorrow. I've downloaded it in full and opened it OK in winrar just now, btw. The zip-file is created with winrar on windows 7, and according to Floyd Resler has to get it's extension changed to .rar, then decompressed with Stuffit Expander. Also something to look into soon, btw. That would explain why every zip decompression utility I've tried thinks it's corrupt. As for my menu being jittery, it's not jittery on any of the windows browsers I tested. And I have no mac-book available to me, not even from friends and family who are all on windows (on my recommendation btw ;) Are you ready for the shocking truth... not every computer in the world runs Windows, so unless you've developed this purely for the friends and family you've convinced to do so you may want to rethink your approach to testing. As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. That may be so, but when my 100Mbit/s connection finally managed to download the file it took about 4 minutes, which is nowhere near 2MB/s. Your homepage takes 7 seconds to load - that's unacceptable in the real world, especially when you're talking about a server that's (and I'm only guessing here) not under heavy load. Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). Okay, I don't wanna get into an argument here.. Shame, because I'd love to see you try to defend a position that promotes wasting resources just because they're there. This is not a new thing - ever-increasing computing resources have always led to this short-sighted view in the inexperienced, but trust me when I say you'll regret it when you're paying for the bandwidth being used by thousands of people simultaneously using a site that's using your framework. Why do you think other libraries such as jquery recommend minifying their code before deployment, and then serving it via gzip? Every bit and byte counts, especially as you scale up. The javascripts are currenlty being served unminified via gzip, because minifying them all the time creates too much overhead for me. If you want them minified you can easily do that yourself. Anyway, I'm not trying to get into an argument (it's rare that I do), but I do recommend that you take in what I've said on this issue. The size of the data you're sending down the pipe matters if you want your library to be used for anything serious, and no amount of artwork or pretty pictures will distract anyone for long. The download size will hardly be an issue for site operators, whom i seriously suspect will be on faster links. And the usage size doesn't have to be large, as mentioned earlier. Rest assured, all the javascript for my animated
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Sat, Mar 17, 2012 at 10:55 AM, Ashley Sheridan a...@ashleysheridan.co.ukwrote: ** On Fri, 2012-03-16 at 22:11 +0100, rene7705 wrote: On Fri, Mar 16, 2012 at 10:08 PM, Tommy Pham tommy...@gmail.com wrote: On Fri, Mar 16, 2012 at 1:45 PM, Stuart Dallas stu...@3ft9.com wrote: As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. That may be so, but when my 100Mbit/s connection finally managed to download the file it took about 4 minutes, which is nowhere near 2MB/s. Your homepage takes 7 seconds to load - that's unacceptable in the real world, especially when you're talking about a server that's (and I'm only guessing here) not under heavy load. Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ Yup... I think rene forgot the fact is if each client requests pull 1MB/s , his upload has to be at least 120MB/s for 100 simultaneous clients' connections. Last time I check in ISP services, that bandwidth falls within OC-12+ category If ya'll would take a closer look at my site, you'd see that most of the size is in artwork. If you want a simple site, use simple artwork. It's _not_ my code's size that's any problem, as I mentioned earlier. Enough for now, I'll look at this list tomorrow again. Time for partying with the live mix at frequence3.fr now.. Just adding my own two pennies to this lot. It does seem a little irresponsible to create such a large (in size) website, especially when you consider that in many countries people don't have high-speed or unlimited access. Even the UK has lots of areas with only basic Internet access via dial-up lines, and plenty of people rely on mobile dongles to connect, which are most often metered and slow. On to the technicals of what you wanted us to look at, because I think this thread has become slightly derailed from the original question. The original comment was that I had licked HTML5 History API + caching. No-one has even commented on that part. - The 'Home: Downloads, Blog' link at the top doesn't work for me at all. I'm using Fx 3.6 on Fedora 14 True, coz that link should point to the homepage. I decided not to spread my content out over tons of pages, or to create redundant content. - - The drop-down menu appears odd, with some items appearing over the others That's by design but can be changed in the source quite easily (animatedJavascriptMenu-1.0.0.source.js) - - The products menu at the top does nothing when clicked on Same as the Home:Downloads,Blog link. - - Other 'pages' take a long time to load in Strange, they don't here, and it should drop to 0 once the cache is filled up. - Sorry, but it really doesn't look very professional when basic things (like links) don't work at all. I'd hate to have any kind of disability because I doubt any screen readers would work, and using your site with only a keyboard would probably be just as impossible. You can probably use the links in the content to get around the site. Sorry the menu isn't accessible with keyboard, but that's something I don't feel like making my problem right now. I want to create content sites with these components, not get stuck in code issue after code issue. But hey, if you want to improve the components, and send me the result back, I'll surely credit you where appropriate. That might seem like harsh feedback, but I do have quite a strong view on accessibility. Ok. As I said, the content links can be used to browse around. Not ideal, but it will do imo.
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
In response to critiques about my download size, I've removed scenejs and the artwork for my own site-logos from the zip. The size is now 38mb, down from 54mb. I'm also using 7-zip now, I hope it opens better on non-windows OSes.
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On 17 Mar 2012, at 10:54, rene7705 wrote: On Fri, Mar 16, 2012 at 11:13 PM, Stuart Dallas stu...@3ft9.com wrote: Why do you think other libraries such as jquery recommend minifying their code before deployment, and then serving it via gzip? Every bit and byte counts, especially as you scale up. The javascripts are currenlty being served unminified via gzip, because minifying them all the time creates too much overhead for me. If you want them minified you can easily do that yourself. Write a script that does the minifying, and everything else necessary to create a distribution file. Do you really think someone manually runs jquery through the minifier whenever they create a new release? As it happens, they use make: https://github.com/jquery/jquery/blob/master/Makefile It seems you're pretty new to all this, and I appreciate that, but you show little to no willingness to learn from the people on this mailing list, despite asking for feedback. Anyway, I'm not trying to get into an argument (it's rare that I do), but I do recommend that you take in what I've said on this issue. The size of the data you're sending down the pipe matters if you want your library to be used for anything serious, and no amount of artwork or pretty pictures will distract anyone for long. The download size will hardly be an issue for site operators, whom i seriously suspect will be on faster links. And the usage size doesn't have to be large, as mentioned earlier. This comment shows how little you understand about the world from your haven of high-speed internet. Part of the beauty of the internet is that it allows people to disseminate information on a shoestring. I guarantee that 90+% of the people behind the billions of websites in the world access the internet through what you would probably consider a stone age connection. It may surprise you to know that two thirds of the people on the planet do not have any access to the internet at all: http://www.internetworldstats.com/stats.htm Just remember one thing: If you see something obviously wrong, why not send me the fix? I will, if you pay me. Open source developers don't do what they do just because it's there, at least not for the most part. They do it because their goals align with those of the project, or because the project presents a particular challenge. What are your goals for this project? Why did you develop it instead of using an existing library/framework? Here's why I won't be sending you any fixes… * There doesn't appear to be anything your library does that makes it stand out from the thousands of similar libraries that already exist, many of which are far more mature and have large numbers of contributors. * It's a very, very long way off being suitable for usage as a black box. * I see absolutely no value in using your library, either personally or professionally, never mind contributing to it. * Your attitude to the most basic and important advice you've been given practically guarantees that getting involved would be incredibly frustrating and fruitless. Oh, and in case it wasn't clear, you'd need to pay me *a lot*! I don't mean any offence, and I really do applaud your efforts, but in my opinion you need a sharp dose of reality. I encourage you to continue to work on your library because this sort of thing is usually a great learning experience, but don't expect people to help you out when your response to the most basic advice is that's too much overhead for me. Add the fact that you didn't even respond to the very serious security issues I raised and you can't possibly be surprised if nobody wants anything to do with it. Oh, and it doesn't matter if that particular code is not actually used because it's likely indicative of the overall quality of the rest of the library. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Sat, Mar 17, 2012 at 2:07 PM, Stuart Dallas stu...@3ft9.com wrote: On 17 Mar 2012, at 10:54, rene7705 wrote: On Fri, Mar 16, 2012 at 11:13 PM, Stuart Dallas stu...@3ft9.com wrote: Why do you think other libraries such as jquery recommend minifying their code before deployment, and then serving it via gzip? Every bit and byte counts, especially as you scale up. The javascripts are currenlty being served unminified via gzip, because minifying them all the time creates too much overhead for me. If you want them minified you can easily do that yourself. Write a script that does the minifying, and everything else necessary to create a distribution file. Do you really think someone manually runs jquery through the minifier whenever they create a new release? As it happens, they use make: https://github.com/jquery/jquery/blob/master/Makefile It seems you're pretty new to all this, and I appreciate that, but you show little to no willingness to learn from the people on this mailing list, despite asking for feedback. Anyway, I'm not trying to get into an argument (it's rare that I do), but I do recommend that you take in what I've said on this issue. The size of the data you're sending down the pipe matters if you want your library to be used for anything serious, and no amount of artwork or pretty pictures will distract anyone for long. The download size will hardly be an issue for site operators, whom i seriously suspect will be on faster links. And the usage size doesn't have to be large, as mentioned earlier. This comment shows how little you understand about the world from your haven of high-speed internet. Part of the beauty of the internet is that it allows people to disseminate information on a shoestring. I guarantee that 90+% of the people behind the billions of websites in the world access the internet through what you would probably consider a stone age connection. It may surprise you to know that two thirds of the people on the planet do not have any access to the internet at all: http://www.internetworldstats.com/stats.htm Just remember one thing: If you see something obviously wrong, why not send me the fix? I will, if you pay me. Open source developers don't do what they do just because it's there, at least not for the most part. They do it because their goals align with those of the project, or because the project presents a particular challenge. What are your goals for this project? Why did you develop it instead of using an existing library/framework? Here's why I won't be sending you any fixes… * There doesn't appear to be anything your library does that makes it stand out from the thousands of similar libraries that already exist, many of which are far more mature and have large numbers of contributors. * It's a very, very long way off being suitable for usage as a black box. * I see absolutely no value in using your library, either personally or professionally, never mind contributing to it. * Your attitude to the most basic and important advice you've been given practically guarantees that getting involved would be incredibly frustrating and fruitless. Oh, and in case it wasn't clear, you'd need to pay me *a lot*! I don't mean any offence, and I really do applaud your efforts, but in my opinion you need a sharp dose of reality. I encourage you to continue to work on your library because this sort of thing is usually a great learning experience, but don't expect people to help you out when your response to the most basic advice is that's too much overhead for me. Add the fact that you didn't even respond to the very serious security issues I raised and you can't possibly be surprised if nobody wants anything to do with it. Oh, and it doesn't matter if that particular code is not actually used because it's likely indicative of the overall quality of the rest of the library. -Stuart Thanks for taking the time to explain your critiques. It's just that I don't put out my software completely free to next be overflowed with more work based on relatively vague descriptions of what would be wrong with it. I put it out there so more experienced programmers can send me improved versions. If you don't feel like doing that for free, that's your right of course. The relatively crappy code in /code/sitewide_rv/lib_fileSystem.php is certainly not indicative of the quality of the rest of the library, I'll guarantee you. Just take a look at the output of get_animatedJavascriptWidgets_javascript.php in the source of my http://mediabeez.ws, and you'll see that that code is indeed of higher quality. As for minifying the javascripts, it would take me another day, maybe 2, to build a script for that. And I don't think it would matter much, all the animatedJavascriptWidgets JS is gzipped 25kb and if I shave 5kb off that (upper estimate) then I don't consider that worth the effort, at this particular time. I have other
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
[snip] As for minifying the javascripts, it would take me another day, maybe 2, to build a script for that. And I don't think it would matter much, all the animatedJavascriptWidgets JS is gzipped 25kb and if I shave 5kb off that (upper estimate) then I don't consider that worth the effort, at this particular time. I have other things (content creation and compatibility) I want to get done atm. [/snip] Really? A day or two? Minifiying also tends to reduce code size by 50% or more depending on the author. If you only get a 25% reduction it is time to take a look at your coding practices. [snip] I wrote this library because I have been unable to find anything like it on the interwebs. I put it out for free because I think it's cool to give something back to the opensource community. But, again, I'm not interested in having my priority list hijacked by experts who won't bother just to give me back the fix. [/snip] Put it on Github and see how many free labor….uh, er…code fixers you can attract. Giving back to the community is a great thing, it is why many expert PHP coders are on this list. They are already providing you with fixes that you aren't listening to regardless of the language that these fixes are couched in. Community is about give and take and you have started your foray into the community by disallowing take. Good luck! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On 17 Mar 2012, at 15:02, rene7705 wrote: The relatively crappy code in /code/sitewide_rv/lib_fileSystem.php is certainly not indicative of the quality of the rest of the library, I'll guarantee you. Just take a look at the output of get_animatedJavascriptWidgets_javascript.php in the source of my http://mediabeez.ws, and you'll see that that code is indeed of higher quality. Curious example you've decided to highlight there. A few thoughts... * It appears to be serving static javascript content. Why is PHP involved at all here?!? * It's using a hell of a lot more memory than it needs to by loading said static content into a variable rather than simply including the files directly. * The animatedThemes function appears to be loading and decoding json only to re-encode it again before output. Err, why? I wrote this library because I have been unable to find anything like it on the interwebs. I'm somewhat unclear on exactly what problem this library is attempting to solve. The site says video-enabled [stuff] which sounds like nothing more complicated than animated images. Am I missing something? I put it out for free because I think it's cool to give something back to the opensource community. Which is fantastic and should definitely be encouraged, but if you're not interested in feedback don't ask for it. But, again, I'm not interested in having my priority list hijacked by experts who won't bother just to give me back the fix. I couldn't care less about your priority list if my life depended on it. You asked for feedback; I gave you feedback. Everything I do I do for at least one of the following three reasons, in descending order of importance... * It interests me. * It benefits me in some way, now or in the future. * I'm being paid for it. Sorting out the issues with your code doesn't meet any of these motivations. Giving you feedback met two out of the three, which Mr Loaf asserts as !bad. One of those fell away when you responded to said feedback by defending your code as if it were intimately attached to your body. The last remaining motivation is hanging by a thread. Have a nice day. Thanks, I will. You have a nice day too. Snap. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On 16 Mar 2012, at 18:57, rene7705 wrote: Hi Folks.. I could waste a lot of text on what I've accomplished during the last months, but the easiest thing is if you have a (another) look at (the source of) http://mediabeez.ws I think you'll like my opensourced work :) Feedback is appreciated. I'm also having trouble downloading the ZIP file (Chrome 17.0.963.79 on OSX - not that the browser will have anything to do with this problem at all). The download starts, gets to a few MB and doesn't get any further. And 52MB? Since I can't actually see what it contains it's hard to judge, but right off the bat... is your artwork necessary for the thing to work? What external libraries are you using? Just from looking around the site there are a few things that jump out... * The dropdown menus are incredible jittery, certainly nowhere near production-ready. * The background image gets squished according to the dimensions of the browser window. * Your homepage weighs in at massive 2.6MB. Nuff sed! I suggest you take the focus off the way it looks and concentrate on what it does. Tabs with animated backgrounds remind me of websites from the late 90s. You may have developed an incredible framework here, but I don't know because it's buried under 50MB of other stuff that I almost certainly don't care about, and that's before I've even been able to download it. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, Mar 16, 2012 at 9:29 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 18:57, rene7705 wrote: Hi Folks.. I could waste a lot of text on what I've accomplished during the last months, but the easiest thing is if you have a (another) look at (the source of) http://mediabeez.ws I think you'll like my opensourced work :) Feedback is appreciated. I'm also having trouble downloading the ZIP file (Chrome 17.0.963.79 on OSX - not that the browser will have anything to do with this problem at all). The download starts, gets to a few MB and doesn't get any further. And 52MB? Since I can't actually see what it contains it's hard to judge, but right off the bat... is your artwork necessary for the thing to work? What external libraries are you using? Just from looking around the site there are a few things that jump out... * The dropdown menus are incredible jittery, certainly nowhere near production-ready. * The background image gets squished according to the dimensions of the browser window. * Your homepage weighs in at massive 2.6MB. Nuff sed! I suggest you take the focus off the way it looks and concentrate on what it does. Tabs with animated backgrounds remind me of websites from the late 90s. You may have developed an incredible framework here, but I don't know because it's buried under 50MB of other stuff that I almost certainly don't care about, and that's before I've even been able to download it. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ ok.. That being unable to download the zip file correctly is something I'll take up with my hosting provider tomorrow. I've downloaded it in full and opened it OK in winrar just now, btw. The zip-file is created with winrar on windows 7, and according to Floyd Resler has to get it's extension changed to .rar, then decompressed with Stuffit Expander. Also something to look into soon, btw. As for my menu being jittery, it's not jittery on any of the windows browsers I tested. And I have no mac-book available to me, not even from friends and family who are all on windows (on my recommendation btw ;) As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least..
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
rene7705 rene7...@gmail.com wrote in message news:CADegSEbpRnu47ub-XHyGF8JyK9BBcr7R=p157tO3R_k3+8RH=g...@mail.gmail.com... As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. You don't care about size reduction?? You think the entire world is going to move to faster nets in the next couple of years even??? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, Mar 16, 2012 at 9:42 PM, Jim Giner jim.gi...@albanyhandball.comwrote: rene7705 rene7...@gmail.com wrote in message news:CADegSEbpRnu47ub-XHyGF8JyK9BBcr7R=p157tO3R_k3+8RH=g...@mail.gmail.com... As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. You don't care about size reduction?? You think the entire world is going to move to faster nets in the next couple of years even??? Yep, that's what I observed so far, not just here in .nl btw. And I expect that trend to continue as they're now putting fibre to the home in the first neighborhoods here.
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On 16 Mar 2012, at 20:36, rene7705 wrote: On Fri, Mar 16, 2012 at 9:29 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 18:57, rene7705 wrote: Hi Folks.. I could waste a lot of text on what I've accomplished during the last months, but the easiest thing is if you have a (another) look at (the source of) http://mediabeez.ws I think you'll like my opensourced work :) Feedback is appreciated. I'm also having trouble downloading the ZIP file (Chrome 17.0.963.79 on OSX - not that the browser will have anything to do with this problem at all). The download starts, gets to a few MB and doesn't get any further. And 52MB? Since I can't actually see what it contains it's hard to judge, but right off the bat... is your artwork necessary for the thing to work? What external libraries are you using? Just from looking around the site there are a few things that jump out... * The dropdown menus are incredible jittery, certainly nowhere near production-ready. * The background image gets squished according to the dimensions of the browser window. * Your homepage weighs in at massive 2.6MB. Nuff sed! I suggest you take the focus off the way it looks and concentrate on what it does. Tabs with animated backgrounds remind me of websites from the late 90s. You may have developed an incredible framework here, but I don't know because it's buried under 50MB of other stuff that I almost certainly don't care about, and that's before I've even been able to download it. ok.. That being unable to download the zip file correctly is something I'll take up with my hosting provider tomorrow. I've downloaded it in full and opened it OK in winrar just now, btw. The zip-file is created with winrar on windows 7, and according to Floyd Resler has to get it's extension changed to .rar, then decompressed with Stuffit Expander. Also something to look into soon, btw. That would explain why every zip decompression utility I've tried thinks it's corrupt. As for my menu being jittery, it's not jittery on any of the windows browsers I tested. And I have no mac-book available to me, not even from friends and family who are all on windows (on my recommendation btw ;) Are you ready for the shocking truth... not every computer in the world runs Windows, so unless you've developed this purely for the friends and family you've convinced to do so you may want to rethink your approach to testing. As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. That may be so, but when my 100Mbit/s connection finally managed to download the file it took about 4 minutes, which is nowhere near 2MB/s. Your homepage takes 7 seconds to load - that's unacceptable in the real world, especially when you're talking about a server that's (and I'm only guessing here) not under heavy load. Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
Stuart Dallas stu...@3ft9.com wrote in message news:292A87F4-AEE0-449E-BF90-45e3a0b70...@3ft9.com... Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). Here! Here! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, Mar 16, 2012 at 9:45 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 20:36, rene7705 wrote: On Fri, Mar 16, 2012 at 9:29 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 18:57, rene7705 wrote: Hi Folks.. I could waste a lot of text on what I've accomplished during the last months, but the easiest thing is if you have a (another) look at (the source of) http://mediabeez.ws I think you'll like my opensourced work :) Feedback is appreciated. I'm also having trouble downloading the ZIP file (Chrome 17.0.963.79 on OSX - not that the browser will have anything to do with this problem at all). The download starts, gets to a few MB and doesn't get any further. And 52MB? Since I can't actually see what it contains it's hard to judge, but right off the bat... is your artwork necessary for the thing to work? What external libraries are you using? Just from looking around the site there are a few things that jump out... * The dropdown menus are incredible jittery, certainly nowhere near production-ready. * The background image gets squished according to the dimensions of the browser window. * Your homepage weighs in at massive 2.6MB. Nuff sed! I suggest you take the focus off the way it looks and concentrate on what it does. Tabs with animated backgrounds remind me of websites from the late 90s. You may have developed an incredible framework here, but I don't know because it's buried under 50MB of other stuff that I almost certainly don't care about, and that's before I've even been able to download it. ok.. That being unable to download the zip file correctly is something I'll take up with my hosting provider tomorrow. I've downloaded it in full and opened it OK in winrar just now, btw. The zip-file is created with winrar on windows 7, and according to Floyd Resler has to get it's extension changed to .rar, then decompressed with Stuffit Expander. Also something to look into soon, btw. That would explain why every zip decompression utility I've tried thinks it's corrupt. As for my menu being jittery, it's not jittery on any of the windows browsers I tested. And I have no mac-book available to me, not even from friends and family who are all on windows (on my recommendation btw ;) Are you ready for the shocking truth... not every computer in the world runs Windows, so unless you've developed this purely for the friends and family you've convinced to do so you may want to rethink your approach to testing. As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. That may be so, but when my 100Mbit/s connection finally managed to download the file it took about 4 minutes, which is nowhere near 2MB/s. Your homepage takes 7 seconds to load - that's unacceptable in the real world, especially when you're talking about a server that's (and I'm only guessing here) not under heavy load. Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). -Stuart Okay, I don't wanna get into an argument here.. Rest assured, all the javascript for my animated widgets combined is about 25kb. The artwork for simple animations is about 100kb per button/menu-item theme. The fact that I demo how to put video on a button and thus end up with nearly a dozen button themes that are about 2MB each, is just taking advantage of the fast links that are available in much of the world. About me testing only on windows, you're right about that and I'll see if I can do something to improve my testing regime. For now i'm dependent on your patience and bugreports tho. And I had no idea winrar made such crappy zip files, I'll look into a replacement very soon.
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
Is this a Fun Friday trolling? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, Mar 16, 2012 at 1:45 PM, Stuart Dallas stu...@3ft9.com wrote: As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. That may be so, but when my 100Mbit/s connection finally managed to download the file it took about 4 minutes, which is nowhere near 2MB/s. Your homepage takes 7 seconds to load - that's unacceptable in the real world, especially when you're talking about a server that's (and I'm only guessing here) not under heavy load. Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ Yup... I think rene forgot the fact is if each client requests pull 1MB/s , his upload has to be at least 120MB/s for 100 simultaneous clients' connections. Last time I check in ISP services, that bandwidth falls within OC-12+ category -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On Fri, Mar 16, 2012 at 10:08 PM, Tommy Pham tommy...@gmail.com wrote: On Fri, Mar 16, 2012 at 1:45 PM, Stuart Dallas stu...@3ft9.com wrote: As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. That may be so, but when my 100Mbit/s connection finally managed to download the file it took about 4 minutes, which is nowhere near 2MB/s. Your homepage takes 7 seconds to load - that's unacceptable in the real world, especially when you're talking about a server that's (and I'm only guessing here) not under heavy load. Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ Yup... I think rene forgot the fact is if each client requests pull 1MB/s , his upload has to be at least 120MB/s for 100 simultaneous clients' connections. Last time I check in ISP services, that bandwidth falls within OC-12+ category If ya'll would take a closer look at my site, you'd see that most of the size is in artwork. If you want a simple site, use simple artwork. It's _not_ my code's size that's any problem, as I mentioned earlier. Enough for now, I'll look at this list tomorrow again. Time for partying with the live mix at frequence3.fr now..
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
Everyone makes valid points.. and depending on ones perspective, certain of those points are more important than others... but, because of my nature anyway, I want to just say thanks to rene7705 for bothering. He is not trying to take anything.. but just share his creative process, in case it is fun for anyone, or useful for anyone. He undoubtedly wants to improve too.. but there is the middle step where positive reinforcement is the most pertinent thing. Rene, don't mind the tones here.. we all get paid to scrutinize, so it can be hard to snap out of that critical mindset sometimes. -Govinda -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Got HTML5 History API + caching LICKED, I think, grin
On 16 Mar 2012, at 20:53, rene7705 wrote: On Fri, Mar 16, 2012 at 9:45 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 20:36, rene7705 wrote: On Fri, Mar 16, 2012 at 9:29 PM, Stuart Dallas stu...@3ft9.com wrote: On 16 Mar 2012, at 18:57, rene7705 wrote: Hi Folks.. I could waste a lot of text on what I've accomplished during the last months, but the easiest thing is if you have a (another) look at (the source of) http://mediabeez.ws I think you'll like my opensourced work :) Feedback is appreciated. I'm also having trouble downloading the ZIP file (Chrome 17.0.963.79 on OSX - not that the browser will have anything to do with this problem at all). The download starts, gets to a few MB and doesn't get any further. And 52MB? Since I can't actually see what it contains it's hard to judge, but right off the bat... is your artwork necessary for the thing to work? What external libraries are you using? Just from looking around the site there are a few things that jump out... * The dropdown menus are incredible jittery, certainly nowhere near production-ready. * The background image gets squished according to the dimensions of the browser window. * Your homepage weighs in at massive 2.6MB. Nuff sed! I suggest you take the focus off the way it looks and concentrate on what it does. Tabs with animated backgrounds remind me of websites from the late 90s. You may have developed an incredible framework here, but I don't know because it's buried under 50MB of other stuff that I almost certainly don't care about, and that's before I've even been able to download it. ok.. That being unable to download the zip file correctly is something I'll take up with my hosting provider tomorrow. I've downloaded it in full and opened it OK in winrar just now, btw. The zip-file is created with winrar on windows 7, and according to Floyd Resler has to get it's extension changed to .rar, then decompressed with Stuffit Expander. Also something to look into soon, btw. That would explain why every zip decompression utility I've tried thinks it's corrupt. As for my menu being jittery, it's not jittery on any of the windows browsers I tested. And I have no mac-book available to me, not even from friends and family who are all on windows (on my recommendation btw ;) Are you ready for the shocking truth... not every computer in the world runs Windows, so unless you've developed this purely for the friends and family you've convinced to do so you may want to rethink your approach to testing. As for my files and homepage being Huge, yep, it's made for the future or current fast internet connections. Frankly, size reduction is not on my agenda. I'll wait for the nets to become faster still. And the server should spit it out at 2MB/s at least.. That may be so, but when my 100Mbit/s connection finally managed to download the file it took about 4 minutes, which is nowhere near 2MB/s. Your homepage takes 7 seconds to load - that's unacceptable in the real world, especially when you're talking about a server that's (and I'm only guessing here) not under heavy load. Anyway, your comment about waiting for the nets (sic) to catch up so it can cope with your bloat has convinced me to not bother looking any further into your project, but I wish you the best of luck with it (you're gonna need it). Okay, I don't wanna get into an argument here.. Shame, because I'd love to see you try to defend a position that promotes wasting resources just because they're there. This is not a new thing - ever-increasing computing resources have always led to this short-sighted view in the inexperienced, but trust me when I say you'll regret it when you're paying for the bandwidth being used by thousands of people simultaneously using a site that's using your framework. Why do you think other libraries such as jquery recommend minifying their code before deployment, and then serving it via gzip? Every bit and byte counts, especially as you scale up. Anyway, I'm not trying to get into an argument (it's rare that I do), but I do recommend that you take in what I've said on this issue. The size of the data you're sending down the pipe matters if you want your library to be used for anything serious, and no amount of artwork or pretty pictures will distract anyone for long. Rest assured, all the javascript for my animated widgets combined is about 25kb. Good for you. You might want to produce a download that doesn't include the optional stuff so you can show how small it is, and provide examples that show off what it can do using just that code. Incidentally, a little over 2MB of your homepage is the logo. 2MB for the logo? Seriously?? The artwork for simple animations is about 100kb per button/menu-item theme. 100kB is not a simple animation, that's a mini-movie.
