New API doc - typos and questions
-
REPOST: from Mon MAR 08, 2010
The web page has still not been fixed.
API - Release Notes webpage error
http://code.google.com/apis/sketchup/docs/releases.htmlThe H2 Heading "What's new in SketchUp 7" is not displayed as a H2 heading.
The error is caused by a missing '>' (greaterthan character) on the end of the preceeding <P> element closing tag, which is now: '</P'
ie, snippit from current HTML source (line 378):` %(#804000)[<p class="post"> </p
<h2>What's new in SketchUp 7</h2>]`
"What's new in SketchUp 7" should be rendered the same as:
"What's new in SketchUp 7.0 M1"
Adding a screenshot:
-
The above error on the API Release Notes webpage no longer applies since the release of Sketchup v8.0 ...
... because all mention of Maintainance Releases have been scrubbed from the page, including the fixes, functionality and new methods that were introduced by the MR.
Example (see above,) Sketchup 7.0MR1 added the get_glued_instances instance method to the Sketchup::Face class, but now readers (especially those new to using the SUAPI,) will not know this by looking at this page. They'd need to notice the version on the right, of the method defintion, on the Face class page. [ie: SketchUp 7.0.10247 (M1)+]
Did anyone save an offline archive of the API Release Notes Page ?? ( Can you attach copy to this thread if so, please. )
-
sigh ... I only hope this is because of some restructure of the API site. Better poke a Googler just in case to make sure that info will be available somewhere.
-
@thomthom said:
... just in case to make sure that info will be available somewhere.
Isn't there an web archive kept by Google somewhere.. built by bots ??
-
@thomthom said:
I only hope this is because of some restructure of the API site.
I also. I'd like to see the page remade like the SU Application Release Notes page, with expanding sections for each release.
-
@dan rathbun said:
@thomthom said:
... just in case to make sure that info will be available somewhere.
Isn't there an web archive kept by Google somewhere.. built by bots ??
Yes, found it (Google caches their own pages): Release Notes - Google SketchUp Ruby API - v7
Not knowing when this cached page will be replaced (possibly the 1st of next month,) here's an offline snapshot:
Release Notes - Google SketchUp Ruby API - v7.zip -
Guys, thanks for the heads up, you can blame this one on ScottL
but also he was the one that corrected it, so I guess he is even.Should be fixed shortly.
Simone. -
Just saw the updates.
Scott even sneaked in a UTM class - which apparently has been there since SU6?? -
WOW! no replies for almost a year! Things must really have improved on the SketchUp API side of things .......just kidding!
I noticed Google is buying Motorola or 12.5 Billion today http://www.telegraph.co.uk/technology/google/8702132/Google-buys-Motorola-Mobility-in-12.5bn-deal.htmlLooks like they ran out of money once again, still can't afford to hire someone to get rid of the typos in the API.
-
@tomot said:
WOW! no replies for almost a year!
Hey Tomot,
I'm still listening.
We have been making incremental fixes now and then. I'll take this ping as a useful reminder to check the thread for things we still need to do...
-
What would your preferred channel for API documentation issues be? This thread or the comment pages on the API pages?
-
@thomthom said:
What would your preferred channel for API documentation issues be? This thread or the comment pages on the API pages?
Reporting issues via the code.google.com comments tool (which you can find at the bottom of every documentation page) is better, because it warns other users right on the page.
-
Yea.. but the formatting sucks!
-
@dan rathbun said:
Yea.. but the formatting sucks!
...of course if you prefer to post nicely formatted stuff to this thread, that's cool, too!
-
@unknownuser said:
@dan rathbun said:
Yea.. but the formatting sucks!
...of course if you prefer to post nicely formatted stuff to this thread, that's cool, too!
And there is some other wee issues, it quickly wraps the comments into pages, after 10 pages. And it's not always obvious.
The biggest problem is if you have your browser set to prefer a language over English, then you'll be presented with an empty comment page. (I think the comments are all gone.) Every time I have to install a new system, or use another computer here in Norway, and the preferred language is set to Norwegian I cannot see any of the comments.
I have to rearrange the preferred languages to English before I get the comments because the API doc pages forcefully redirect me to a so-called localised version for my language, even though everything is still in English.
So I can imagine there's many people not aware of the comments at the bottom of the API pages. -
It would be better to have INLINE (expandable) comment block beneath each method. I know you guys can do this because you did it on the Release notes pages.
Also expandable sample code block under each method.
Basically it needs to be more like a wiki page. Jim experimented a bit with this on his code site page.
-
@unknownuser said:
@dan rathbun said:
Yea.. but the formatting sucks!
...of course if you prefer to post nicely formatted stuff to this thread, that's cool, too!
HOW! ??
I don't think it takes markup... or does it?
If so. What kind? git markup? bbCode? what? -
@Scott.. on the subject of the API... see this thread:
http://groups.google.com/group/sketchupruby/browse_thread/thread/112f655ea6067034/2c575f2d2113a894#2c575f2d2113a894Wouldn't it be better to have a DC
playsound()click function appended to the the DC class? -
@dan rathbun said:
It would be better to have INLINE (expandable) comment block beneath each method. I know you guys can do this because you did it on the Release notes pages.
? Inline comment on the release notes?
-
@thomthom said:
@dan rathbun said:
It would be better to have INLINE (expandable) comment block beneath each method. I know you guys can do this because you did it on the Release notes pages.
? Inline comment on the release notes?
Yes, instead of random (newest first,) ordered comments at the page bottom...
... a poster would click an add note button WITHIN each method section. The note would be wrapped in a collapsed DIV or SPAN that is INLINE with the method section.
At the bottom of each method would be a "plus" button that has a title "Read Notes (current_num)"
If the user wished to get more info on that SPECIFIC method, they can click the "+" button, and the collapsed DIV would expand.
The same could be true for Community Contributed Sample Code Snippets. Each method could have a collapsed "snippets" section, that works in the same manner.
For an example of what I'm talking about.. see the Sketchup Release Notes page.
Advertisement