Warning: Cannot modify header information - headers already sent by (output started at /home/cssquirrel/www.cssquirrel.com/blog/index.php:4) in /home/cssquirrel/www.cssquirrel.com/blog/wp-includes/feed-rss2-comments.php on line 8
Comments on: Comic Update: Opera’s Rough Edges http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/ opinions and news on web design Mon, 12 Dec 2011 18:22:38 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Cesar http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-31365 Cesar Mon, 18 Jan 2010 18:42:23 +0000 http://www.cssquirrel.com/?p=496#comment-31365 Ohh...the irony, the guys working behind Opera are also behind the W3C CSS Spec, it's incredible! Nice comic btw, got a good laugh out of it :D Ohh…the irony, the guys working behind Opera are also behind the W3C CSS Spec, it’s incredible!
Nice comic btw, got a good laugh out of it :D

]]>
By: The Low Down On Cascading Style Sheets | Web Design and all stuff related to it! http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30714 The Low Down On Cascading Style Sheets | Web Design and all stuff related to it! Wed, 25 Nov 2009 19:43:39 +0000 http://www.cssquirrel.com/?p=496#comment-30714 [...] CSSquirrel : Comic Update: Opera's Rough Edges: Kyle Weems [...] [...] CSSquirrel : Comic Update: Opera's Rough Edges: Kyle Weems [...]

]]>
By: VeoSotano http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30338 VeoSotano Thu, 19 Nov 2009 17:50:44 +0000 http://www.cssquirrel.com/?p=496#comment-30338 @Kyle - That's only for the plug-ins that require support to view ANY content. In my plan, since all the content (which, e.g. your search engine spider will be able to read) is written in XML -plain text-, those users who have a browser with no plug-in architecture will still be able to access all the content. Just not the rendering. Using a plug-in has the distinct advantage that you can support all browsers with a plug-in architecture - heck, even IE6! - and the rendered output will look and behave exactly the same on all plattforms (well, not everywhere. It's not the same a desktop pc with a large screen or a smartphone with touchscreen, but that will be solved by means of profiles (á la CSS-media rules) and other cool features). @Kyle – That’s only for the plug-ins that require support to view ANY content. In my plan, since all the content (which, e.g. your search engine spider will be able to read) is written in XML -plain text-, those users who have a browser with no plug-in architecture will still be able to access all the content. Just not the rendering.

Using a plug-in has the distinct advantage that you can support all browsers with a plug-in architecture – heck, even IE6! – and the rendered output will look and behave exactly the same on all plattforms (well, not everywhere. It’s not the same a desktop pc with a large screen or a smartphone with touchscreen, but that will be solved by means of profiles (á la CSS-media rules) and other cool features).

]]>
By: Kyle Weems http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30278 Kyle Weems Wed, 18 Nov 2009 17:37:16 +0000 http://www.cssquirrel.com/?p=496#comment-30278 @VeoSotano - Well, to start with, using a browser plug-in as the basis for a new presentational technique is a recipe for disaster for anyone who uses a browser that doesn't support the plug-in. I personally am not an expert enough on the topic to say whether such a technology would be superior to the current standards, or even if it was, how easy it would be to learn and deploy. But in general, most good ideas start as crazy ones. @VeoSotano – Well, to start with, using a browser plug-in as the basis for a new presentational technique is a recipe for disaster for anyone who uses a browser that doesn’t support the plug-in.

I personally am not an expert enough on the topic to say whether such a technology would be superior to the current standards, or even if it was, how easy it would be to learn and deploy. But in general, most good ideas start as crazy ones.

]]>
By: VeoSotano http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30216 VeoSotano Tue, 17 Nov 2009 22:31:49 +0000 http://www.cssquirrel.com/?p=496#comment-30216 @Kyle What do you think, how would the webosphere react to a new (and in my view, far superior) technology, deployed as a browser plug-in? Would they opose it just because it is something different than HTML5? I'm going to let out just a little bit: What I call XHS is a combination of two technologies: a new language whose syntax is derived from CSS, called HSS (Hierarchical Style Sheets) and good ol' XML for the content. The publishing of the web documents remain plain text files, and it will be an open standard every can code for. The document will be displayed using a browser plug-in, developed by the open source community. @Kyle What do you think, how would the webosphere react to a new (and in my view, far superior) technology, deployed as a browser plug-in? Would they opose it just because it is something different than HTML5?

I’m going to let out just a little bit: What I call XHS is a combination of two technologies: a new language whose syntax is derived from CSS, called HSS (Hierarchical Style Sheets) and good ol’ XML for the content. The publishing of the web documents remain plain text files, and it will be an open standard every can code for. The document will be displayed using a browser plug-in, developed by the open source community.

]]>
By: Kyle Weems http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30215 Kyle Weems Tue, 17 Nov 2009 22:17:47 +0000 http://www.cssquirrel.com/?p=496#comment-30215 VeoSotano. Right. Sorry. I was typing too fast. :) VeoSotano. Right. Sorry. I was typing too fast. :)

]]>
By: VeoSotano http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30214 VeoSotano Tue, 17 Nov 2009 22:15:11 +0000 http://www.cssquirrel.com/?p=496#comment-30214 Hey, it's NOT VeoSanto!!! Hey, it’s NOT VeoSanto!!!

]]>
By: Kyle Weems http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30213 Kyle Weems Tue, 17 Nov 2009 21:57:47 +0000 http://www.cssquirrel.com/?p=496#comment-30213 @VeoSanto - I pull the avatars from http://www.gravatar.com/. You associate an image with the email address that you use when writing your comment, and it will pull that image instead of the default acorn. @VeoSanto – I pull the avatars from http://www.gravatar.com/. You associate an image with the email address that you use when writing your comment, and it will pull that image instead of the default acorn.

]]>
By: VeoSotano http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30205 VeoSotano Tue, 17 Nov 2009 19:01:45 +0000 http://www.cssquirrel.com/?p=496#comment-30205 @Kyle: look at it this way, WebKit is advancing rendering capabilities like no other browser (transforms, animations, 3d, etc), but those features won't be put to use until years after, or even never, just because other browsers don't jump on board. Actually, we're already bound to a single gateway for features, namely the W3C. It's just because of the different levels of implementation of each browser that we have this mess. I propose an open source project, like WebKit, but where everybody's contribution adds to the web as a whole. This way, browser makers could stop wasting time in reinventing the wheel, and focus on what makes their software special. And authors know exactaly what they can expect in how their pages will be rendered. This is part of a project of mine, which, if everything goes as planned, will change the web forever. Next to it, HTML+CSS will look like we've been living in the stone age :) If you want to have a chat, and want me to tell you more about it, well you have my email address ;) And by the way, it is VeoSotano, not VeoSanto ;) Cheers P.D. How can I have my custom avatar? If I get one, I'll stop by and add to the conversation more often, I promise :D @Kyle: look at it this way, WebKit is advancing rendering capabilities like no other browser (transforms, animations, 3d, etc), but those features won’t be put to use until years after, or even never, just because other browsers don’t jump on board. Actually, we’re already bound to a single gateway for features, namely the W3C. It’s just because of the different levels of implementation of each browser that we have this mess.

I propose an open source project, like WebKit, but where everybody’s contribution adds to the web as a whole. This way, browser makers could stop wasting time in reinventing the wheel, and focus on what makes their software special. And authors know exactaly what they can expect in how their pages will be rendered.

This is part of a project of mine, which, if everything goes as planned, will change the web forever. Next to it, HTML+CSS will look like we’ve been living in the stone age :) If you want to have a chat, and want me to tell you more about it, well you have my email address ;)

And by the way, it is VeoSotano, not VeoSanto ;)

Cheers

P.D. How can I have my custom avatar? If I get one, I’ll stop by and add to the conversation more often, I promise :D

]]>
By: Arpit Jacob http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30203 Arpit Jacob Tue, 17 Nov 2009 18:33:05 +0000 http://www.cssquirrel.com/?p=496#comment-30203 :) anything is better than IE :) anything is better than IE

]]>