ruby-****@sourc*****
ruby-****@sourc*****
2013年 3月 23日 (土) 02:28:13 JST
-------------------------
REMOTE_ADDR = 70.49.48.128
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-dancr-rbcatut
-------------------------
@@ -15,7 +15,7 @@
* 12.3 ((<Ruby Cairo Tutorial|tut-gtk2-dancr>)) (this page)
* 12.3.0 ((<Intro To Ruby Cairo Tutorial|tut-gtk2-dancr-rbcatut#Intro To Ruby Cairo Tutorial>))
- * 12.3.0.1 ((<Establishing Gtk-Cairo Framework To Run The Tutorial Example Code|tut-gtk2-dancr-rbcatut#Establishing Gtk-Cairo Framework To Run The Tutorial Example Code>))
+ * 12.3.0.1 ((<Establishing Gtk-Cairo Framework To Run the Tutorial Example Code|tut-gtk2-dancr-rbcatut#Establishing Gtk-Cairo Framework To Run the Tutorial Example Code>))
* 12.3.1 ((<Cairo's Drawing Model|tut-gtk2-dancr-rbcatut#Cairo's Drawing Model>))
* 12.3.1.1 ((<Nouns|tut-gtk2-dancr-rbcatut#Nouns>))
* 12.3.1.2 ((<Verbs|tut-gtk2-dancr-rbcatut#Verbs>))
@@ -43,7 +43,7 @@
{{br}}
-=== Establishing Gtk-Cairo Framework To Run The Tutorial Example Code
+=== Establishing Gtk-Cairo Framework To Run the Tutorial Example Code
(12.3.0.1){{br}}
A great number of the examples that introduce Cairo code at the beginning of almost all contemporary Cairo tutorials try to avoid unnecessarily discussing how Cairo cooperates with the X, or any other Window system. Plain C/GTK Cairo library includes a number of functions which allow you create ((*cairo context*)) independently of any particular back-end, and then bind it to a backend of your choice, however, currently you can not do the same Ruby Gtk/Cairo. Before we continue this discussion let's refresh our memory about what these backends are.