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.
Archive for May, 2009
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.
The Pain of change
2009
05.19
05.19
Starting this site I found it cute to have a syntax highlighter, I still want one! The pain is that I have written all my articles using Googles syntax highlighter, I thought I give it a try an let Javascript do the work.
I found some cons and I would like to switch to GESHi, and now I have to go to the troubles of refreshing all my articles.
iPhone can fart
2009
05.19
05.19
Do you now these iPhone freaks which don’t now nothing about technology, nothing about development, nothing about hardware and even less about software. I know some and when the iPhone got out they were the first people to buy one.
What some time ago frustrated me the most was that every second day someone would like to show you that he has got a new cute toy, some hot gizmo.
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.