SketchUp Ruby API Suggestions
-
@unknownuser said:
After using the SketchUp Ruby API for some time, I've come across I few things I'd like to see done differently, or to be added. Here's my WIP list of suggestions.
This is just as much organisation for me as it is getting this information out. I've kept it somewhat organized and well described, but there's still a lot of work to be done. Also, if I never do anything nothing will get done, so here's me doing something.
-
@unknownuser said:
@unknownuser said:
After using the SketchUp Ruby API for some time, I've come across I few things I'd like to see done differently, or to be added. Here's my WIP list of suggestions.
This is just as much organisation for me as it is getting this information out. I've kept it somewhat organized and well described, but there's still a lot of work to be done. Also, if I never do anything nothing will get done, so here's me doing something.
Interesting way to organise it. And I fully agree that the info needs good organisation. I began to write down my notes in a Google Docs document that is publicly readable: https://docs.google.com/document/d/1hwEivitbEwU-Lbnkia9K0HOEKlXkYrV3uVPcqeZZofw/edit?usp=sharing
Only thing about the .rb files in your repo - I'd think it'd be good to have a note at the top that warns people from trying to use it in production - as that'd lead to clashes. Just because there are all kind of people that come across this with different expriences and might not know best practices.
-
That document's really interesting - do you mind if I add some of it to the repo (credit where due, ofc)?
-
Go ahead! I'm happy to create a buzz and discussion over this. The more people chime in with specifics over the API the better feedback for the SketchUp team.
I began on the document in advance of Basecamp 2012 and passed it around to as many as I could - including the SU team.
I'll probably be forking your repo and making my own notes as well. I really would like the community to make more use of GitHub and the likes for collaboration.
-
Great! Especially since so many issues are scattered over the forums (or burried miles deep under newer bug reports). I sometimes feel by reporting bugs we create the most awesomest bug collection, but the goal shouldn't stay purely contemplative, shouldn't it also be about realizing solutions?
This way we can collaborately work on it and "prototype" API fixes and suggest extensions.
Also there are so many subtle small issues/infos/experiences that would best be placed directly in the code or at the corresponding method in the API documentation (which we can't edit) – or in this github project.
Advertisement