Archive for the ‘Ruby’ Category
2009
12.19
Tags: Ruby, Shoes, test class, test method, test test, _why
Posted in Internet, Ruby | No Comments »
I’ve set out to create a new uniform GUI, but soon found about Shoes. I had to do little bit more of googling. Now that I found THE toolkit I craved for I read about one of the creator “_why” which suddenly disappeared, from internet.
In the past I wouldn’t have bothered much about it, but with the new changes taking place in the internet world like cloud computing, where all our thoughts, photos, videos; lifes are online. We all have to remember that behind every line of text, except for the lines created from bots or spammers; there are human beings behind them.
This link is dedicated to him: _why
This link is dedicated to Shoes: Shoes
2009
12.18
Tags: Code, Component, GUI, OO, Ruby, Toolkit
Posted in Ruby | No Comments »
Ruby is incredibly adaptable to a multitude of environments, operating systems and GUI toolkits. It can become cumbersome to procrastinators like me who tend to be in search for the one true way to fit it all. Note that I call it unified ruby GUI vs standard ruby GUI, because I don’t think that a true standard toolkit would make the world happy. My humble expectations are:
- can be installed as gem and uses gem
- supports*: windows, mac os x, gnome, kde, web-interface
- *using the preferred toolkit** of that platform
- **no other dependencies should be added
- simple things should be simple
- complicated things should be possible
(more…)
2009
05.28
Tags: Component, GUI, Inox, OO, Part 5, Ruby, Ruby Inox, Toolkit
Posted in Ruby | No Comments »
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.
(more…)
2009
05.22
Tags: Component, GUI, Inox, OO, Part 5, Ruby, Ruby Inox, Toolit
Posted in Ruby | No Comments »
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!
(more…)
2009
05.21
Tags: Assert, Chain, Debug, Inox, Ruby, Ruby Inox
Posted in Ruby | 1 Comment »
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.
(more…)
2009
05.21
Tags: cross language, Inox, Inox Property, module, oo model, Ruby, Ruby Inox, Ruby Inox Property
Posted in Ruby | No Comments »
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.
(more…)
2009
05.21
Tags: Actions, cross language, Inox, Inox Actions, oo model, Point class, Ruby, Ruby Inox Actions
Posted in Ruby | 1 Comment »
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.
(more…)
2009
05.19
Tags: cross language, Inox, oo model, Point class, Ruby
Posted in Ruby | 2 Comments »
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.
(more…)