Originally this article formed one article with Ruby Inox Part 6: Widget as everything had to evolve concurrently of each other. But decided later to split them up into separated article to underline the importance of the xxxBase line of classes and there major difference to the xxxNative line of classes.
Posts Tagged ‘Inox’
Ruby Inox Part 6: Widget
2009
05.28
05.28
We are steering toward a graphical user interface. In this article we lay out the firt visual stone, the Widget or more precisely the class WidgetBase.
A major cleanup of the code written so far is already planned and notice that these minor changes will be reflected only on github and no article will be posted until Inox becomes useable/stable.
Ruby Inox Part 5: Component
2009
05.22
05.22
Something promised is something due. Only two days have passed since my last post, Ruby Inox Part4: Property. Two days human time span is like a decade of internet time span. Some bits stayed the same and some changed. Notable changes were made to the module Actions and the module Properties, stepping closer to the final goal.
In this article its all about Components!
Brain damaged assertions chain
2009
05.21
05.21
After a while, when I am coding and have already lost any notion of time, I realize that I was debugging or changing my code all over again; repeating myself really badly for several hours.
The assertions in my code were the parts that I repeated the most and lost a lot of time fine tuning how they should behave, reports errors. And way too much time spend asserting that the assertions asserted correctly.
Ruby Inox Part 4.1: Property
2009
05.21
05.21
In Ruby Inox Part 4: Property I described I would like to see properties in a GUI toolkit. Since then I worked hard to stabilized the code and the module Property profited from the experience gained by rethinking the way of the Actions module should work.
Ruby Inox Part 3.1: Actions
2009
05.21
05.21
Here is a short update for the Ruby Inox Part3: Actions article. Some stuff worked out just fine, some stuff had to be changed to facilitate subclassing.
Ruby Inox Part 4: Property
2009
05.19
05.19
Last time, we took a look at Actions. A standard way to handle callbacks and actions is an absolute requirement for some frameworks like a Graphical user interface toolkit.
One aspect of such toolkits is that they relay heavily on an uniform way to handle objects; we have actions, we still need an uniform way to define and handle properties of objects.
A more restrictive way is required than that offered by ruby.
Ruby Inox Part 3: Actions
2009
05.11
05.11
Here is the pursuit of a series of related articles started by Ruby Inox Part1 where I set out to accomplish every task set by the creator. Promptly followed by his first instructions of implementing a simple Point class.
Althought I left out to publish on this site the specification and implementation of the Size class and Rect class, as they are very similar to that of the Point class; you can find the source on GitHub.
Let’s jump straight to the next challenge: Actions
Ruby Inox Part 2: A Point class
2009
05.07
05.07
Alright, the journey begins. I received the first specification! If you don’t know what this is about perhaps you missed out the story. The first part of the story nor the sotry itslef is relevant for understanding the code that follows. Just a way to keep it interesting and mysterious, until something working comes out of box. Now let me continue the story:
First the creator explained me that after years of debate he settled down on ruby as language for Inox. He then asked me to implement a Point class. At first I objected as why such a class would be of any use and why not represent a point as an array [x, y].
Ruby Inox Part 1: Bootstrap
2009
05.07
05.07
Once upon a time, there was a young and brave developer who liked challenges. Bored by smaller quests, he set out to create the perfect system. Through the years the ideas grew with his knowledge; Inox steadily mutated to other forms.