Library Directory Structure

[Jim]

There seems to be a consensus forming that organizing related methods into a single file is the preferred way people want to work with the library. That's OK with me.

Currently, there is a a folder for each Sketchup class, and individual methods reside in their own files in the folders.

Are we agreed on switching to one-file-per-sketchup-class? If so, I will get started on it.

[Chris Fullmer]

I think so, I'd say go for it!

Chris

[thomthom]

Are we doing this Review thing? Adding new methods to a review folder before they are verified to be put into the main?
(Isn't there a code review functionality for this? If I get this right, you add files to a new head/trunk/branch (whatever the name is) and then Request Code Review?) So that we don't need a separate folder - just merge the changes as they are accepted?

[Jim]

Are we doing this Review thing? Adding new methods to a review folder before they are verified to be put into the main?

I'm not sure. I was thinking too that I wouldn't mind having my own 'jim' folder in the repo to keep experimental files, and things I might want to ask someone to look at.

I like the idea of a 'review' folder, you know everything in there is pending and needs reviewed. I don't know if it is needed and will only clutter up the folder.

[Chris Fullmer]

I also like the idea of the review feature. I feel like I tried to use it and failed miserably so far. So when you guys figure it out, let me know.

I'm also making some "major" changes to citygen and finding that I am undesratnding the importance of keeping a clean version of citygen and then my messed up version separate. Little by little this will make sense to me....

Chris

[thomthom]

Chris: how did you create the Bezier branch?

[Chris Fullmer]

I Tortoise, on the Synch window, there is a place to enter the branch name. I just entered "bezier" in there.

But then I tried to request a review of the "bezier" branch, but it wouldn't recognize the path. Jim thought maybe its a googlecode problem, something they don't have fully implemented. I figured it just had to do with how I tried to do it - user error.

Chris

[thomthom]

"Target Revision"?

[Jim]

Branching seems a rather ambiguous concept. When you clone a repository, make any change, and commit it - that is a branch because your clone is now different than the original.

What you did with 'bezier' is create a named branch. I don't know how to use them, or how they might benefit.

[Jim]

Well, that went about as well as could be expected. That means it DID go well and the repo has been updated.


http://code.google.com/p/skx/source/browse/

[thomthom]

Is there no way to get rid of the old folders?

[Jim]

Is there no way to get rid of the old folders?

I thought I did. They are gone for me, anyway.

When I rename files, I use the mercurial commands hg rename to rename them.

Code: Select all

$ hg rename entities/all_entities.eb entities.rb


When I renamed the last filein the folder, the folder was gone from my working directory.

I don't know why you still have them, or if you should just delete them. But I think you could. mercurial doesn't track folders, just files.

You can always make a quick clone and see what happens.

[thomthom]

The folders in my own library are done.
But it's the Google Browse view that still lists them.

[Jim]

I'm not sure if that is because of Google Code, or because those folder exists in the history. I do know if you clone the repository at this changeset, you do not get the empty folders.