SketchUp Ruby API Extension Library

[Jim]

Any ideas on how to create a test suite for these methods? Is it needed?

[RickW]

I think my vote is for one file per class/module.
I see it as either you have the skx extension - or you haven't.

Code: Select all

# One file per object
votes += 1

# One big skx file
rick = "not so sure about that"

[thomthom]

I didn't intend one large skx file, but one file per class/module - instead of one file per method and one folder per class/module.

[ScottLininger]

Any ideas on how to create a test suite for these methods? Is it needed?

For now, I think we can move forward without a test suite. We have some internal tools that we might be able to share... I'll check.

Unit tests are a wonderful, wonderful thing, and eventually we will thank ourselves if we build them. But we can get away without 'em for a bit.

[Jim]

It seems my basing skx directory structure on Facets structure was premature:

From the facets readme file:

the extension methods are no longer stored on a per-method basis. While dividing the extension methods up on a per-method basis had certain advantages, not the least of which was a simple organization, it proved too granular --more "subatomic" than "atomic". With 2.0 we have address this issue. All the extension methods have now been organized into small tightly related groups.

Now if you get in and look at many of the files in facets, they contain a single line requiring the 'tightly related groups' file. This is not what I intentioned.

So, I do not have an issue consolidating what is already there into fewer files containing related methods.

Is anyone suggesting a single file? It may be an option for 'core' methods that provide essential methods and API fixes.

[thomthom]

I don't think I want one large file. But one per class/module sound like a natural way to keep related (grouped) methods organized. It's easier to get an overview of the skx library as well, if they are all stored in the skx root rather than in many sub folders.

[ScottLininger]

I don't think I want one large file. But one per class/module sound like a natural way to keep related (grouped) methods organized. It's easier to get an overview of the skx library as well, if they are all stored in the skx root rather than in many sub folders.

I agree.

[Jim]

I've asked Csaba for a separate forum for this project, so hopefully soon we can have more than one topic...

[thomthom]

I've asked Csaba for a separate forum for this project, so hopefully soon we can have more than one topic...

Good idea.