search

codementum / experimentr

Backend (Node.js, redis), frontend (js), and analysis (R) for web-based visualization studies.
29 stars 16 forks source link

Consider changing wording of hold() and release() #53

Closed connorgr closed 8 years ago

connorgr commented 10 years ago

A less confusing wording might be enableNextBtn() and disableNextBtn().

codementum commented 10 years ago

Agree. @tacitia -- any thoughts?

tacitia commented 10 years ago

To me the wordings were not self-explanatory at first, but they started to make a lot of sense once I looked at what the functions do. I also think hold() and release() have the merits of being succinct. I'm inclined to think that this won't be a problem as long as there is an API, but that's just my 2 cents.

On Thu, Nov 14, 2013 at 1:22 PM, Lane Harrison notifications@github.comwrote:

Agree. @tacitia https://github.com/tacitia -- any thoughts?

— Reply to this email directly or view it on GitHubhttps://github.com/codementum/experimentr/issues/53#issuecomment-28508703 .

codementum commented 10 years ago

I'm also swayed by the succinctness side. It's possible that we add functions in the style that @connorgr suggests that simple call hold() and release() as a first step.

Later, if we have better documentation or tutorial pages, we can introduce the hold and release concept there.