API bugs
-
Is there a "maintained" list of known API bugs? Unless there is no need for one, maybe someone could start one here. With input from others, they could update it from time to time. Would be helpful for us beginners who may be banging our heads against the wall:-) Good idea?, bad idea?, too hard to do?, too much work for someone? Anyway, just a thought.
-
New API doc - typos and questions
Top sticky in the developer forum. -
And TBD got plans for a more refined list: http://forums.sketchucation.com/viewtopic.php?f=180&t=24327#p208372
-
Hi Thomas, I saw that, and actually went through all 15 pages once, most of which I can not recall, and at my stage of understanding, do not have a good grip of. Just thinking how nice it would be if all the methods were alphabetically listed on the first post. Maybe if SUCF had something like wiki, knowledgeable posters could edit the top post. Again, just thinking out loud.
-
I think that is more or less what TBD is going for.
Maybe instead of documenting the errors, what about just making our own API from scratch (of course largely borring the real API as a base). But make it our own so we can add our own, detailed examples, snippets, etc. That could be cool.
Chris
-
That would be nice. I can't even keep track of the help I get from my own posts. "Now Chris mentioned I should do....", "where the #$%^ is that post" :-). Maybe I will have to add them to a sub-folder in my browser's "favorites" listing.
-
@chris fullmer said:
But make it our own so we can add our own, detailed examples, snippets, etc. That could be cool.
yup. that is the idea. to have one place where you can find all the info needed for developing SU Ruby scripts:
- the correct API help,
- workarounds,
- small snippets that can be easy copy/paste in your code,
- examples,
- fast searching,
...
I will make a mindmap of what I have in mind and create the github/bitbucket so we can start working on it. hope to have it done next week.
-
You Rock Tavi! I'll be following this closely.
I also would like to have a section for template script files for starting new scripts. I have some ideas of templates that use basic rDoc structure, or not, use the menu system, use a loader script, use toolbars, etc.
Plus it will be nice to be able to put down example code and have other coders looks over it now and in the future to make sure the cr@p I'm telling people is semi-true
Those are my thoughts so far,
Chris
-
Yea, template snippets would be nice.
Advertisement