Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2010/ch2 S20 st

2010-09-09T02:02:47Z

Gbchidam:

*[[CSC/ECE 517 Fall 2010/ch1 1a vc]]

*[[CSC/ECE 517 Fall 2010/ch1 S10 MS]]

*[[CSC/ECE 517 Fall 2010/ch1 1a br]]

*[[CSC/ECE 517 Fall 2010/ch1 S10 MM]]

*[[CSC/ECE 517 Fall 2010/ch1 S23 GP]]

*[[CSC/ECE 517 Fall 2010/ch1 S6 aa]]

*[[CSC/ECE 517 Fall 2010/ch1 1e bb]]

*[[CSC/ECE 517 Fall 2010/ch1 n 00]]

*[[CSC/ECE 517 Fall 2010/ch1 1c JF]]

*[[CSC/ECE 517 Fall 2010/ch1 S10 GP]]

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-09T02:02:01Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Ruby Toolkits =

== Standard Inbuilt Toolkit Library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
But Tk does not support native widgets and provides only a basic look and feel as compared to the other toolkits.

== Thirdparty Toolkits ==
There are a number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and internationalisation support. It is a mature toolkit with a license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a look and feel similar to that of web applications. It is not built atop [http://www.gtk.org/ GTK], [http://en.wikipedia.org/wiki/Qt_(framework) Qt], etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. However it lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for [http://www.macruby.org/ MacRuby] and Swing for JRuby.

Swing is the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =
No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =
As mentioned earlier, choice of a toolkit depends solely on a developer's requirements. However, this section aims to compare some existing toolkits to better highlight their advantages and disadvantages. The toolkits discussed above all have cross-platform support and a free open-source license. All libraries, except the 'Tk' library, support a neat look and feel. Although all libraries support a wide range of widgets and features, Shoes offers a very simple interface providing ease of use which is useful for small scale projects. Additionally Shoes is extremely popular and has a very strong user community. Overall, if API style and simplicity is important, Shoes would be a good choice. For large applications, which require complex and rich features, wxRuby would be a good choice.

= References =
*[http://www.pressure.to/ruby_gui_survey/ruby_gui_survey_2008_report.pdf The 2008 Ruby GUI Survey]
*[http://www.perfectxml.com/syngress/ruby/Page1.asp Chapter 2 from Ruby Developer’s Guide]
*[http://wonko.com/post/a_brief_comparison_of_cross-platform_gui_toolkits_from_rubys_per Comparison of cross-platform toolkits]

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T16:03:58Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Ruby Toolkits =

== Standard Inbuilt Toolkit Library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
But Tk does not support native widgets, it is ugly looking and the code also looks ugly.

== Thirdparty Toolkits ==
There are a lot number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and Internationalisation support. It is a mature toolkit with license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a Web feel. It is not built atop [http://www.gtk.org/ GTK], [http://en.wikipedia.org/wiki/Qt_(framework) Qt], etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. It has a simple interface and has cool graphics. It lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for [http://www.macruby.org/ MacRuby] and Swing for JRuby.

Swing, the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =
No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =
Tk doesn't have a proper documentation, whereas all other toolkits discussed above have a proper web based documentation.
All the toolkits discussed above have cross-platform support.
Except the standard 'Tk' library all other toolkits have a neat look and feel.
All the toolkits discussed above have a free open-source license.
All the toolkits have a wide range of features except that since Shoes is meant to have a very simple interface, it lacks some of the robust widgets.
Shoes provides a very good community support, since it is one of the most popular toolkits.
Overall, if API style and simplicity are more important, Shoes can be a better choice. Similarly, if more importance is given to the range of features offered, then wxRuby can be a better choice.
Choosing a particular toolkit solely depends on the user's requirements.

= References =
*[http://www.pressure.to/ruby_gui_survey/ruby_gui_survey_2008_report.pdf The 2008 Ruby GUI Survey]
*[http://www.perfectxml.com/syngress/ruby/Page1.asp Chapter 2 from Ruby Developer’s Guide]
*[http://wonko.com/post/a_brief_comparison_of_cross-platform_gui_toolkits_from_rubys_per Comparison of cross-platform toolkits]

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T16:02:58Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Ruby Toolkits =

== Standard Inbuilt Toolkit Library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
But Tk does not support native widgets, it is ugly looking and the code also looks ugly.

== Thirdparty Toolkits ==
There are a lot number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and Internationalisation support. It is a mature toolkit with license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a Web feel. It is not built atop [http://www.gtk.org/ GTK], [http://en.wikipedia.org/wiki/Qt_(framework) Qt], etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. It has a simple interface and has cool graphics. It lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for [http://www.macruby.org/ MacRuby] and Swing for JRuby.

Swing, the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =
No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =
Tk doesn't have a proper documentation, whereas all other toolkits discussed above have a proper web based documentation.
All the toolkits discussed above have cross-platform support.
Except the standard 'Tk' library all other toolkits have a neat look and feel.
All the toolkits discussed above have a free open-source license.
All the toolkits have a wide range of features except that since Shoes is meant to have a very simple interface, it lacks some of the robust widgets.
Shoes provides a very good community support, since it is one of the most popular toolkits.
Overall, if API style and simplicity are more important, Shoes can be a better choice. Similarly, if more importance is given to the range of features offered, then wxRuby can be a better choice.
Choosing a particular toolkit solely depends on the user's requirements.

= References =
*[http://www.pressure.to/ruby_gui_survey/ruby_gui_survey_2008_report.pdf The 2008 Ruby GUI Survey]
*[http://www.perfectxml.com/syngress/ruby/Page1.asp Chapter from Ruby Developer’s Guide]
*[http://wonko.com/post/a_brief_comparison_of_cross-platform_gui_toolkits_from_rubys_per Comparison of cross-platform toolkits]

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T16:01:15Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Ruby Toolkits =

== Standard Inbuilt Toolkit Library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
But Tk does not support native widgets, it is ugly looking and the code also looks ugly.

== Thirdparty Toolkits ==
There are a lot number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and Internationalisation support. It is a mature toolkit with license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a Web feel. It is not built atop [http://www.gtk.org/ GTK], [http://en.wikipedia.org/wiki/Qt_(framework) Qt], etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. It has a simple interface and has cool graphics. It lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for [http://www.macruby.org/ MacRuby] and Swing for JRuby.

Swing, the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =
No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =
Tk doesn't have a proper documentation, whereas all other toolkits discussed above have a proper web based documentation.
All the toolkits discussed above have cross-platform support.
Except the standard 'Tk' library all other toolkits have a neat look and feel.
All the toolkits discussed above have a free open-source license.
All the toolkits have a wide range of features except that since Shoes is meant to have a very simple interface, it lacks some of the robust widgets.
Shoes provides a very good community support, since it is one of the most popular toolkits.
Overall, if API style and simplicity are more important, Shoes can be a better choice. Similarly, if more importance is given to the range of features offered, then wxRuby can be a better choice.
Choosing a particular toolkit solely depends on the user's requirements.

= References =
[http://www.pressure.to/ruby_gui_survey/ruby_gui_survey_2008_report.pdf The 2008 Ruby GUI Survey]
[http://www.perfectxml.com/syngress/ruby/Page1.asp Ruby toolkits]
[http://wonko.com/post/a_brief_comparison_of_cross-platform_gui_toolkits_from_rubys_per Comparison of cross-platform toolkits]

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T16:00:19Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Ruby Toolkits =

== Standard Inbuilt Toolkit Library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
But Tk does not support native widgets, it is ugly looking and the code also looks ugly.

== Thirdparty Toolkits ==
There are a lot number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and Internationalisation support. It is a mature toolkit with license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a Web feel. It is not built atop [http://www.gtk.org/ GTK], [http://en.wikipedia.org/wiki/Qt_(framework) Qt], etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. It has a simple interface and has cool graphics. It lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for [http://www.macruby.org/ MacRuby] and Swing for JRuby.

Swing, the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =
No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =
Tk doesn't have a proper documentation, whereas all other toolkits discussed above have a proper web based documentation.
All the toolkits discussed above have cross-platform support.
Except the standard 'Tk' library all other toolkits have a neat look and feel.
All the toolkits discussed above have a free open-source license.
All the toolkits have a wide range of features except that since Shoes is meant to have a very simple interface, it lacks some of the robust widgets.
Shoes provides a very good community support, since it is one of the most popular toolkits.
Overall, if API style and simplicity are more important, Shoes can be a better choice. Similarly, if more importance is given to the range of features offered, then wxRuby can be a better choice.
Choosing a particular toolkit solely depends on the user's requirements.

= References =
[http://www.pressure.to/ruby_gui_survey/ruby_gui_survey_2008_report.pdf The 2008 Ruby GUI Survey]
[http://www.perfectxml.com/syngress/ruby/Page1.asp]
[http://wonko.com/post/a_brief_comparison_of_cross-platform_gui_toolkits_from_rubys_per]

CSC/ECE 517 Fall 2010/ch2 S20 st

2010-09-08T15:14:30Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:57:55Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Ruby Toolkits =

== Standard Inbuilt Toolkit Library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
Tk does not support native widgets, it is ugly looking and the code also looks ugly.

== Thirdparty Toolkits ==
There are a lot number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and Internationalisation support. It is a mature toolkit with license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a Web feel. It is not built atop [http://www.gtk.org/ GTK], [http://en.wikipedia.org/wiki/Qt_(framework) Qt], etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. It has a simple interface and has cool graphics. It lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for [http://www.macruby.org/ MacRuby] and Swing for JRuby.

Swing, the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =

No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =

= Conclusion =

= References =

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:50:31Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Ruby Toolkits =

== Standard Inbuilt Toolkit library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
Tk does not support native widgets, it is ugly looking and the code also looks ugly.

== Thirdparty Toolkits ==
There are a lot number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and Internationalisation support. It is a mature toolkit with license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a Web feel. It is not built atop [http://www.gtk.org/ GTK], [http://en.wikipedia.org/wiki/Qt_(framework) Qt], etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. It has a simple interface and has cool graphics. It lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for [http://www.macruby.org/ MacRuby] and Swing for JRuby.

Swing, the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =

No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =

= Conclusion =

= References =

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:46:46Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Toolkits =

== Standard Inbuilt Toolkit library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
Tk does not support native widgets, it is ugly looking and the code also looks ugly.

== Thirdparty Toolkits ==
There are a lot number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and Internationalisation support. It is a mature toolkit with license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a Web feel. It is not built atop [http://www.gtk.org/ GTK], [http://en.wikipedia.org/wiki/Qt_(framework) Qt], etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. It has a simple interface and has cool graphics. It lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for [http://www.macruby.org/ MacRuby] and Swing for JRuby.

Swing, the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =

No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =

= Conclusion =

= References =

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:44:28Z

Gbchidam:

'''''GUI Toolkits for Ruby'''''

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not bound to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby.

= Toolkits =

== Standard Inbuilt Toolkit library ==
The [http://www.tkdocs.com/tutorial/index.html 'Tk' library] is provided along with the standard Ruby distribution. Tk is an open source, platform independent toolkit. It is well-suited for cross-platform application development. Tk provides a number of widgets commonly needed to develop desktop applications such as button, menu, canvas, text, frame, label etc.

Tk is perfectly functional and easily available. Bindings are built-in to some ruby distros. Tk is easily customizable and configurable
Tk does not support native widgets, it is ugly looking and the code also looks ugly.

== Thirdparty Toolkits ==
There are a lot number of toolkit libraries for Ruby provided by third-party vendors. Mostly these are wrappers around toolkits written in C and C++. Many of these toolkits may not support cross-platform application development. Some of the thirdparty toolkits are [http://www.fxruby.org/ FxRuby], wxRuby, [http://ruby-gnome2.sourceforge.jp/ ruby-GNOME2], etc.

[http://wxruby.rubyforge.org/wiki/wiki.pl wxRuby] is an open-source GUI toolkit for Ruby. WxRuby is a Ruby binding and wrapper for the [http://www.wxwidgets.org/ WxWidgets] C++ classes. It allows you to use all the features of WxWidgets from your Ruby programs without having to touch any native APIs or without having to use another language. You'll gain all of the benefits, including native look and feel and an easy installation. It provides a range of widgets and Internationalisation support. It is a mature toolkit with license compatible for open-source and commercial use.

== Exclusive Ruby Toolkit ==
Shoes is a library implemented exclusively for Ruby. It is one of the most popular toolkits for Ruby.
Shoes creates native applications with a Web feel. It is not built atop GTK, Qt, etc., but rather directly on the relevant native API (Win32 on Windows, for example). Shoes has a lot of potential and has a rich widget set. Not designed for serious, large-scale GUI applications, Shoes applications tend to be small, useful and clever programs, either for online or offline use. Things in Shoes are also drastically simplified and the learning curve is very shallow. It has a simple interface and has cool graphics. It lacks many of the more robust widgets common in other toolkits.

== Environment Specific Libraries ==
Recent Ruby implementations have their own GUI facilities provided by toolkits associated with the environment. Some of them are Cocoa for MacRuby and Swing for JRuby.

Swing, the GUI library that is bundled with every installation of a Java runtime environment. If you run JRuby, then you can use Swing.
[http://jruby.org/ JRuby] is essentially the Ruby interpreter, except this version is written entirely in Java. JRuby features some of the same concepts, including object-oriented programming, and duck-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs.

= Selecting the appropriate Toolkit =

No single toolkit can be considered the best among available toolkits for Ruby. Users should select an appropriate toolkit based on their own requirements.

The following are some of the parameters that can be considered before choosing a toolkit.

* Web-based documentation
* Availability for relevant platforms
* Appearance / aesthetics
* Licence compatible with open source use
* Range of features / widgets
* Community support
* Speed / performance
* Internationalisation support
* Licence compatible with commercial use
* Accessibility features

= Comparison of Toolkits =

= Conclusion =

= References =

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:20:16Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:19:36Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:17:22Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:16:52Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T08:07:21Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:56:41Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:56:06Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:55:16Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:50:01Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:48:52Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:43:21Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:40:23Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:37:25Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:28:20Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:03:53Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T07:02:01Z

Gbchidam:

File:Toolkit-classification.jpg

2010-09-08T07:01:14Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T06:26:37Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T06:25:39Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T06:07:33Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T05:54:26Z

Gbchidam:

= GUI Toolkits for Ruby =

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not binded to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby, right from traditional to the most popular toolkits.

= Introduction =

= Overview =

== Standard Toolkit ==
== Shoes ==

= Summary =

= Conclusion =

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T05:53:49Z

Gbchidam:

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form. Actually, the Ruby interpretor is not binded to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby, right from traditional to the most popular toolkits.

= Introduction =

= Overview =

== Standard Toolkit ==
== Shoes ==

= Summary =

= Conclusion =

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T05:53:12Z

Gbchidam: /* Conclusion */

= Introduction =

= Overview =

== Standard Toolkit ==
== Shoes ==

= Summary =

= Conclusion =

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T05:52:47Z

Gbchidam:

= Introduction =

= Overview =

== Standard Toolkit ==
== Shoes ==

= Summary =

= Conclusion =

Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form.
Actually, the Ruby interpretor is not binded to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby, right from traditional to the most popular toolkits.

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T05:46:00Z

Gbchidam: /* Introduction */

= Introduction =
Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form.
Actually, the Ruby interpretor is not binded to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits for Ruby, right from traditional to the most popular toolkits.

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T05:45:24Z

Gbchidam:

= Introduction =
Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form.
Actually, the Ruby interpretor is not binded to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits, right from traditional to the most popular toolkits.

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T05:44:15Z

Gbchidam:

= Introduction =
Traditionally, Ruby is a command line tool. Most Ruby commands are entered as text in a terminal and provide output to the user in the text form.
But, actually Ruby interpretor is not binded to any program development environment. Ruby programs can be typed in any editor and there are a lot of libraries to provide Graphical User Interface (GUI). This article discusses various GUI toolkits, right from traditional to the most popular toolkits.

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T03:39:34Z

Gbchidam:

= Introduction =

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T03:38:39Z

Gbchidam:

CSC/ECE 517 Fall 2010/ch1 S10 GP

2010-09-08T02:24:46Z

Gbchidam:

Test page

CSC/ECE 517 Fall 2010/ch2 S20 st

2010-09-08T02:24:23Z

Gbchidam:

*[[CSC/ECE 517 Fall 2010/ch1 S10 MS]]

*[[CSC/ECE_517_Fall_2010/ch1_1a_br]]

*[[CSC/ECE 517 Fall 2010/ch1 S10 GP]]

User talk:Gbchidam

2010-09-08T02:23:41Z

Gbchidam: CSC/ECE 517 Fall 2010/ch1 S10 GP

== CSC/ECE 517 Fall 2010/ch1 S10 GP ==

Test page

User:Gbchidam

2010-09-08T02:15:10Z

Gbchidam:

test page