On 4/27/2020 3:55 AM, Sam Ruby wrote:
On Sun, Apr 26, 2020 at 10:08 PM Patricia Shanahan <p...@acm.org> wrote:
On 4/24/2020 12:42 PM, Sam Ruby wrote:
...
But what you can do is develop, and test, CGI scripts. If you get
something interesting working, submit a pull request so that we can
take a look at it.
Have fun!
For optimum fun I would like an environment in which I can play freely,
with no worries about corrupting production files.
There seem to me to be two strategies for getting that. One is to create
a simple playpen of my own, with an svn repository and some other toys.
The other is a create a fully local Whimsy test environment. That has
the advantage that I can play with relevant libraries, as well as basics
of Ruby and CGI.
What do you think?
That partially depends on what you plan to work on.
If it is a mostly standalone tool that interacts with SVN, I would
suggest the full local Whimsy environment, just don't implement the
"svn commit" part yet.
If it is the board agenda tool, I'd suggest taking a look at the
node.js implementation. By the next board meeting, I'll have a video
walkthrough.
Although ultimately I want to learn both, I need to pick one of node.js
or Ruby to learn first. As I see it, there are likely to be more
volunteers who already know Javascript, so it would be better for me to
start on the rest of Whimsy, but what do you think?
If it is something that updates LDAP, I don't think you will get very
far without the existing libraries, so again I would suggest the full
Whimsy environment. But given that you aren't "root" or in the
secretarial team, the damage you can do there is very limited.
--
This email has been checked for viruses by AVG.
https://www.avg.com
- Sam Ruby
--
This email has been checked for viruses by AVG.
https://www.avg.com
