Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Curate samples #353

Closed
PragTob opened this issue Jul 25, 2013 · 12 comments
Closed

Curate samples #353

PragTob opened this issue Jul 25, 2013 · 12 comments

Comments

@PragTob
Copy link
Member

PragTob commented Jul 25, 2013

I believe it would be good to curate the samples before the rc1 is released. People will look at samples to get a grasp of shoes, therefore they should be as understandable as possible :-)

What do I mean by curate?

  • Make them clearer to understand - rename some variables/methods or maybe even extract some methods or eventually add some comments.
  • make the sample names clearer - nobody knows what sample15 is, but with a better name one might know that. If you rename them make sure to also rename them in samples/README
  • Delete duplicated samples - over time for one reason we amassed some samples that essentially do the same, find them and delete one of them!

Thanks!

@plexus
Copy link
Member

plexus commented Jul 25, 2013

👍

On 25 July 2013 11:27, Tobias Pfeiffer notifications@github.com wrote:

I believe it would be good to curate the samples before the rc1 is
released.

What do I mean by curate? Make them clearer to understand. So e.g. rename
some variables/methods or maybe even extract some methods. Also eventually
add some comments.

People will look at samples to get a grasp of shoes, therefore they should
be as understandable as possible :-)


Reply to this email directly or view it on GitHubhttps://github.com//issues/353
.

@rjack1201
Copy link

Would this include renaming the files themselves to something more meaningful than samplexx.rb?

@fism88
Copy link
Contributor

fism88 commented Jul 25, 2013

Renaming the files would be extremely helpful too with trying out the samples and learning from them

@PragTob
Copy link
Member Author

PragTob commented Jul 25, 2013

Yeah right on! Just like the other simple-, good- and expert-* :-) You are of course right, samplexx.rb isn't quite the best naming :-D

@fism88
Copy link
Contributor

fism88 commented Jul 26, 2013

What are the requirements for a sample file name to be prefixed with simple, good, or expert? I assume simple is low complexity and expert is high, but I'm not sure about good.

@PragTob
Copy link
Member Author

PragTob commented Jul 26, 2013

I would say good is in the middle ;-) However I would not worry about renaming samples too much right now. We've more important stuff to do to get an alpha out atm :-)

@plexus
Copy link
Member

plexus commented Jul 26, 2013

Might be worth including choes-contrib in this discussion. Most of the samples are also included there. Do we want to keep it as a separate project?

@wasnotrice
Copy link
Member

I took some first steps toward cleaning up samples in 803fa5c. Also opened issues for all the samples I could find that weren't working properly. We still could use some renaming and elimination of duplicates.

Another task here is to guide us away from the "adjusted" samples so that we can run their unadjusted friends. We are close on many of these. I believe these were originally adjusted by @ashbb for green_shoes.

Even another way to help would be to collect a set of screenshots of working samples (even Shoes 3 snapshots???), so that someone new to the project could verify that the sample is functioning as expected. Some of them are...surprising.

@plexus
Copy link
Member

plexus commented Jan 3, 2014

The simple/good/expert distinction still stems from _why IIRC. It's a bit
arbitrary. There's a browser app in shoes-contrib that allows you to run
these, and it shows them as three categories. We don't necessarily have to
stick to this naming.
On 02 Jan 2014 19:28, "Eric Watson" notifications@github.com wrote:

I took some first steps toward cleaning up samples in 803fa5chttps://github.com/shoes/shoes4/commit/803fa5ceb3bebdd7f1375f4361fcc75342fdabcf.
Also opened issues for all the samples I could find that weren't working
properly. We still could use some renaming and elimination of duplicates.

Another task here is to guide us away from the "adjusted" samples so that
we can run their unadjusted friends. We are close on many of these. I
believe these were originally adjusted by @ashbbhttps://github.com/ashbbfor green_shoes.

Even another way to help would be to collect a set of screenshots of
working samples (even Shoes 3 snapshots???), so that someone new to the
project could verify that the sample is functioning as expected. Some of
them are...surprising.


Reply to this email directly or view it on GitHubhttps://github.com//issues/353#issuecomment-31490538
.

@PragTob
Copy link
Member Author

PragTob commented Jan 3, 2014

👍 on getting the adjusted ones out there :-)Dunno if they were adjusted for green-shoes, quite some of them were adjusted for shoes4 specifically.

Also tehre are some snapshots already in the snapshots folder, I agree that screenshots would be good!

@PragTob
Copy link
Member Author

PragTob commented May 10, 2014

Also there are some duplicated ones in there (clocks, calculators, the font example) - get those out as well :)

@PragTob
Copy link
Member Author

PragTob commented Jan 8, 2015

Updated to be more clear about what's happening and added the Newcomer Friendly tag

rodenmonte pushed a commit to rodenmonte/shoes4 that referenced this issue Sep 10, 2016
PragTob added a commit that referenced this issue Sep 12, 2016
Renamed samplexx.rb files appropriately (Issue #353).
@jasonrclark jasonrclark modified the milestones: 4.0.0.rc1, 4.0.x Aug 20, 2017
@jasonrclark jasonrclark modified the milestones: 4.0.x, 4.0.0 Nov 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants