Flowstone Guru Blog

[tulamide]

also like myco stated ( in kortezz' nesting thread ) it would create a class with just ins and outs..

That's why I mentioned it. They are overhead which adds to the load times. And if less connectors reduce load times, well, then using them would be the exact opposite of what most people want.

does it make sense to put these in the first level and use wireless links for it? i mean everytime i use a float with the value 1 FS needs to create a float variable and save it somewhere, wouldn't it be better to have it just one time? or doesn't this matter because its just a float?

I don't think that you would see any significant decrease in loading times from less variables, but if (again) connectors play a heavy role in loading times, yes, then it would be better to use them like you would use gloabls in classic non-visual programming, probably collecting them all in a module on the top layer and routing each of them to its own wireless module output. But, remember, this is only of relevance when we're talking of hundreds or thousands of uses.

I guess it would have to be tested.

[tulamide]

A new article is out!

Ruby Stripped, Part 2: Objects

[KG_is_back]

Thanks tulamide, your articles about ruby changed my view on programming in ruby. The DSPcode2 wouldn't be possible (at least from my side ) without them.

[RJHollins]

Big THANKS for the edumacation tulamide !

These are new concepts for me ... plenty to think about for sure.

My implementation of Ruby is more along the lines of BASIC syntax ... or less I haven't even scratched the surface ... but what little I have used [often times provided by the 'resident' GURU's on the forum - thank-youverymuch -- It has saved from some overly complex GREEN solution.

Oh ... in the very intro of RUBY, I avoided it like the plague ... but the realized power I now view as a fantastic FS addition.

Thanks for taking the time to do these ... I really hope you are able to do more tutorials like this. [even if they're just a mini topic] ... just being made aware of something previously unknown helps !!!

[Exo]

Thanks tulamide

[primate]

yup, many thanks. between this forum and the fsguru blog there are so many great resources.

this ruby update is ideal for me, the distance between my ambition and my ability in ruby is enormous. thanks for taking the time to share some knowledge, much appreciated. I had started to think that the fsguru blog had been abandoned, nice to see new posts. The developers toolbox has been really handy.

[tulamide]

Thank you guys! I appreciate it very much

[Exo]

Another article from me... Ruby by Example: Creating a Simple Button

I don't focus on the details of Ruby too much in this, it is meant to show Flowstone specific stuff and be a guide on how to approach the basics of GUI programming in the Ruby component.

[tulamide]

Another article from me... Ruby by Example: Creating a Simple Button

I don't focus on the details of Ruby too much in this, it is meant to show Flowstone specific stuff and be a guide on how to approach the basics of GUI programming in the Ruby component.

Wow, that's great! Assuming the series goes on like this I highly recommend it for everybody who wants to take the first step to Ruby. I like the attention to detail. It bothers me for quite some time now that the examples from DSPr are so -sorry to say that- sloppy. It was nice to see that you thought about declaring variables in the init method, instead of letting the GC do a lot of work.

I know it doesn't really belong here, but I'm afraid I will forget about it: All the classes and methods that DSPr introduced to Ruby are only partly documented. That leads to unneccessarily bloated code. For example, a color, once declared can be changed afterwards with two class instance methods (getARGB and ... sorry can't recall the setter currently). No need to declare lots of colors per redraw. Also, a brush or pen can be given a new color after declaration by just using the method setColor. The same is true for a pen's width (setWidth/getWidth). Unfortunately this is not consistent. The Font class, for example, doesn't offer any methods. Well, sorry if this is too much for this thread. Just wanted to say it once.

[Exo]

Thanks tulamide

Thanks for the extra info, this is good to know and of course better to use than always recreating new objects.

It is a shame that these things are not very consistent or fully documented. I will make an effort to use these in my next tutorial. Knowing this I could also have created the LinearGradientBrush in the init method and just changed the colour in the draw method, but I might go back and change that...or come to think of it maybe that won't work because gradient would require to set two colours.