Spogg is learning Ruby...
Posted: Sat May 19, 2018 10:58 am
Hi guys.
Over the past few weeks I’ve been spending a lot of my FlowStone time learning about Ruby. It’s been fascinating!
Once it started to somehow come together, I realised that what others have said is absolutely true. It’s an amazing and useful extension to FlowStone and I love it on so many levels now. Why didn’t I do this before? I guess fear generated by looking at code and feeling overwhelmed. But it was a good experience, and I must thank tulamide for his mini-tutorials and some personal help he gave me.
Of course it’s a never-ending expedition and I’m still in the baby-steps stage, but it’s been a fruitful journey so far.
For anyone curious about what Ruby can offer I would recommend having a go. Here is the collection of books and information I found and used:
https://www.dropbox.com/s/bd6b7g1494ihr ... y.zip?dl=0
If anyone can add to this collection, that would be great. There are many Ruby books and tutorials out there, so maybe I missed something good.
I’ve added my comments to the books’ file names, only for my own reference, but you’ll make your own judgements of course. What’s good is that all the books have their own individual approaches to the same information. I would say none are perfect, but reading the same stuff presented in different ways proved useful to me.
The first information I studied was the FS User Guide, chapter 8. It made little sense at first but gave me a feel for how FlowStone implements and integrates Ruby. Then, once I had a better understanding of Ruby, I went back to the User Guide and have found it invaluable for making stuff.
Speaking of making stuff, I exercised my developing skills by making a 16-step MIDI sequencer (attached) which contains several RubyEdit modules I made or modified. This seems to work ok and is a bit of fun to play with. For me it’s a mini-celebration of where I’ve got to so far but, if anyone feels like it, I would love to get some comments, criticism or suggestions as to how the code could be improved. For example, each step has its own method for output and I’m sure this isn’t ideal, even though it works ok.
Cheers
Spogg
Over the past few weeks I’ve been spending a lot of my FlowStone time learning about Ruby. It’s been fascinating!
Once it started to somehow come together, I realised that what others have said is absolutely true. It’s an amazing and useful extension to FlowStone and I love it on so many levels now. Why didn’t I do this before? I guess fear generated by looking at code and feeling overwhelmed. But it was a good experience, and I must thank tulamide for his mini-tutorials and some personal help he gave me.
Of course it’s a never-ending expedition and I’m still in the baby-steps stage, but it’s been a fruitful journey so far.
For anyone curious about what Ruby can offer I would recommend having a go. Here is the collection of books and information I found and used:
https://www.dropbox.com/s/bd6b7g1494ihr ... y.zip?dl=0
If anyone can add to this collection, that would be great. There are many Ruby books and tutorials out there, so maybe I missed something good.
I’ve added my comments to the books’ file names, only for my own reference, but you’ll make your own judgements of course. What’s good is that all the books have their own individual approaches to the same information. I would say none are perfect, but reading the same stuff presented in different ways proved useful to me.
The first information I studied was the FS User Guide, chapter 8. It made little sense at first but gave me a feel for how FlowStone implements and integrates Ruby. Then, once I had a better understanding of Ruby, I went back to the User Guide and have found it invaluable for making stuff.
Speaking of making stuff, I exercised my developing skills by making a 16-step MIDI sequencer (attached) which contains several RubyEdit modules I made or modified. This seems to work ok and is a bit of fun to play with. For me it’s a mini-celebration of where I’ve got to so far but, if anyone feels like it, I would love to get some comments, criticism or suggestions as to how the code could be improved. For example, each step has its own method for output and I’m sure this isn’t ideal, even though it works ok.
Cheers
Spogg