Let me start by saying it seems like a great resource, and I appreciate the time and effort that I'm sure went in to getting this up (not to mention writing all of that code in the first place). One issue though, having to include a 20 line copyright notice any time I use some code seems a bit overboard. It's one thing to require attribution if I'm republishing something or downloading an entire script; it's another to require it when I cut and paste 10 lines of code.
Amazing tools. I left my Organizational Behavior class this evening...after giving a group presentation on Google. I logged in to see what was new, after the Doodle4Google vote. Thank you Mark Pilgrim for giving me a foot in the door of something big. My father would be proud of me, at one time he was a Fuller Brush Man.
I don't see how these 8000 lines of code do anything besides bloating the application and causing compatibility problems.
How can one make a simple two-column page with tree widget *so complicated*? It doesn't have to preserve any state, it doesn't have to do partial updates of the content pane.
Why don't you use standalone pages (with normal non-javascript links) and dynamically load subtrees of the index in the left column?
Very cool, fills up a need that every web developer has.
However, on the Doctype homepage it is stated that all content falls under a Creative Commons 3.0 BY license, but the footer at every page still states '(c)2008 Google'. That's a bit confusing imho...
Good stuff, Looking forward to browsing through the stuff. The only thing I find funny is that Mark Pilgrim calls Safarai a tier 1 browser? Huh? In what way?
The resources on XSS alone make this invaluable. It's an excellent guide for web developers!
It's amazing that it takes a Google to make this information comprehensive and easily accessible, with explanations in plain English! There's a lot of information out there on this topic, but usually confined to summaries, that can be uh, summed up as, "validate input".
Thank you - did I say that already? Thank you for all your hard work.
This has great potential, but editing appears to be broken. I edit a page while signed into my Google account and get either a 500 error or an update collision error (when clearly there is no collision).
Looks promising but... the layout is really awful, and doesn't seem like it could grow to a wikipedia level, mainly because the layout is really forced.
The first articles are to google centered,I can understad that, but by example, if you say how to do that thing, and it relays to some google code, include the code in the page it self is really awkward, maybe a different page for that google code library would be better and the "how to do that" page could be named "how to do that with google library", but where would you fit that in the fixed hierarchy?.
Looks promising but currently you lack the freedom of others "Knowledge base solutions" a.k.a. mediawiki
I tried to edit Javascript window.close and the system let me to write but not to check in. But I obtain an error about another user editing at the same time and check it in before. I neither see my changes nor other user's.
I think it's great that Google is stepping up and building a cross-browser repository of web developer documentation. However, I am concerned that the documentation appears to be significantly incomplete and also has many errors. For example, the compatibility table for every single HTML element listed appears to be wrong, this is just one of many errors I spotted with only a cursory examination.
In addition, the Google JavaScript library appears to be rather quirky and a lot of the code I looked at seems to be poor quality.
While I hope Google Doctype succeeds in becoming a world class reference, but in its current state I cannot recommend either the documentation or the JavaScript library.
I filed some of the bugs I found here, but there seemed to be so many basic problems that I couldn't justify a thorough review or the resources to test things myself and fix the docs.
This is excellent! Finally the developers of the world are uniting for a great cause which will make all of our lives easier. Look forward to learning and contributing.
Dear Mr. Pilgrim, could you perhaps make doctype required reading for people coding at Blogger? From what I have seen so far they seem to be pretty clueless.
Alternatively point them to my blog for some introductory reading.
Of course they would already know about their lamentable shortcomings if they read their own "somethings broken" forum.
why I have this error? 403. That’s an error. Your client does not have permission to get URL /p/doctype/wiki/Welcome?tm=6 from this server. That’s all we know.
Very cool. I look forward to the future of this and I will perhaps add some references of my own! thanks for your hard work
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteLet me start by saying it seems like a great resource, and I appreciate the time and effort that I'm sure went in to getting this up (not to mention writing all of that code in the first place). One issue though, having to include a 20 line copyright notice any time I use some code seems a bit overboard. It's one thing to require attribution if I'm republishing something or downloading an entire script; it's another to require it when I cut and paste 10 lines of code.
ReplyDeleteThe sample code is stored in Subversion; instructions on downloading it are here: http://code.google.com/doctype/downloading.html
ReplyDeleteI will endeavor to make that more clear in each of the individual articles that reference sample code.
Oh, I will absolutely be using this. Thanks to all involved!
ReplyDeleteAmazing tools. I left my Organizational Behavior class this evening...after giving a group presentation on Google. I logged in to see what was new, after the Doodle4Google vote. Thank you Mark Pilgrim for giving me a foot in the door of something big. My father would be proud of me, at one time he was a Fuller Brush Man.
ReplyDeleteThats a cool tool. Congrats.
ReplyDeleteI don't see how these 8000 lines of code do anything besides bloating the application and causing compatibility problems.
ReplyDeleteHow can one make a simple two-column page with tree widget *so complicated*? It doesn't have to preserve any state, it doesn't have to do partial updates of the content pane.
Why don't you use standalone pages (with normal non-javascript links) and dynamically load subtrees of the index in the left column?
very cool news for developers
ReplyDeleteWikipedia of Code. I don't like how the examples open in the same page, it breaks the convinence of it.
ReplyDeletegoogle for president!
ReplyDeletebrilliant - thanks a bunch
ReplyDeletegoogle rules by serving !
ReplyDeletecool thing!
ReplyDeleteVery cool, fills up a need that every web developer has.
ReplyDeleteHowever, on the Doctype homepage it is stated that all content falls under a Creative Commons 3.0 BY license, but the footer at every page still states '(c)2008 Google'. That's a bit confusing imho...
That will do!
ReplyDeleteI love how the css properties include browser compatibility notes and everything! Thanks! It will definitely help.
Thanks Google !
ReplyDeleteGood stuff, Looking forward to browsing through the stuff. The only thing I find funny is that Mark Pilgrim calls Safarai a tier 1 browser? Huh? In what way?
ReplyDeleteWow. THANK YOU!
ReplyDeleteThe resources on XSS alone make this invaluable. It's an excellent guide for web developers!
It's amazing that it takes a Google to make this information comprehensive and easily accessible, with explanations in plain English! There's a lot of information out there on this topic, but usually confined to summaries, that can be uh, summed up as, "validate input".
Thank you - did I say that already? Thank you for all your hard work.
This has great potential, but editing appears to be broken. I edit a page while signed into my Google account and get either a 500 error or an update collision error (when clearly there is no collision).
ReplyDeleteWow! It has potential but there is definately a lot of building to do. We'll see where the growth is in 2-3 months.
ReplyDeleteLooks promising but... the layout is really awful, and doesn't seem like it could grow to a wikipedia level, mainly because the layout is really forced.
ReplyDeleteThe first articles are to google centered,I can understad that, but by example, if you say how to do that thing, and it relays to some google code, include the code in the page it self is really awkward, maybe a different page for that google code library would be better and the "how to do that" page could be named "how to do that with google library", but where would you fit that in the fixed hierarchy?.
Looks promising but currently you lack the freedom of others "Knowledge base solutions" a.k.a. mediawiki
Muy bueno siempre google imnovando
ReplyDeleteI tried to edit Javascript window.close and the system let me to write but not to check in. But I obtain an error about another user editing at the same time and check it in before. I neither see my changes nor other user's.
ReplyDeleteNeeds to get better.
I think it's great that Google is stepping up and building a cross-browser repository of web developer documentation. However, I am concerned that the documentation appears to be significantly incomplete and also has many errors. For example, the compatibility table for every single HTML element listed appears to be wrong, this is just one of many errors I spotted with only a cursory examination.
ReplyDeleteIn addition, the Google JavaScript library appears to be rather quirky and a lot of the code I looked at seems to be poor quality.
While I hope Google Doctype succeeds in becoming a world class reference, but in its current state I cannot recommend either the documentation or the JavaScript library.
I filed some of the bugs I found here, but there seemed to be so many basic problems that I couldn't justify a thorough review or the resources to test things myself and fix the docs.
http://code.google.com/p/doctype/issues/list
You must be new here.
ReplyDeleteThis comment has been removed by a blog administrator.
ReplyDeleteThis is excellent! Finally the developers of the world are uniting for a great cause which will make all of our lives easier. Look forward to learning and contributing.
ReplyDelete@Brad Fults: i have the same problem. It either takes ages to update a page (easily around 2-3 minutes) or i get 'collision errors'.
ReplyDeleteDear Mr. Pilgrim,
ReplyDeletecould you perhaps make doctype required reading for people coding at Blogger? From what I have seen so far they seem to be pretty clueless.
Alternatively point them to my blog for some introductory reading.
Of course they would already know about their lamentable shortcomings if they read their own "somethings broken" forum.
why I have this error?
ReplyDelete403. That’s an error.
Your client does not have permission to get URL /p/doctype/wiki/Welcome?tm=6 from this server. That’s all we know.