27 June 2012

Installing Ruby 1.9.3 In Ubuntu 12.04

Do note that the ruby1.9.1 package is for Ruby 1.9.3 (with Ubuntu 12.04). The version number at the end of the package name is for the ABI version of Ruby (1.9.1) that the package covers.

  1. Install ruby1.9.1 package for the Ruby language (also installs the libruby1.9.1 package that contains the standard Ruby library)
  2. Install ruby1.9.1-dev package in order to install gems that use native extensions

11 June 2012

Installing Rails 3.2.3 In Ubuntu 10.04

Ruby needs to be installed before installing Rails. It is highly recommended that Ruby 1.9.2 or greater is used.

  1. Install Rails as a Ruby Gem – gem install rails -v 3.2.3
  2. Add the following PPA as a package repository – ppa:chris-lea/node.js
  3. Install the required python-software-properties package
  4. Update the package manager
  5. Install the nodejs package
  6. Install sqlite3 package
  7. Install libsqlite3-dev package
  8. Install the sqlite3 gem – gem install sqlite3 -v 1.3.5


Notes


It is highly recommended that the Rails documentation is generated in order to have an offline Rails API reference. Do the following to create the API reference:

  1. In your home directory run this command – rails new sample_app
  2. Navigate to the newly created directory
  3. Run the following command to generate the documentation – rake doc:rails
  4. Move the generated documentation from doc/api to your Documents directory
  5. Rename the moved documentation directory to rails-3.2.3-api-doc
  6. In the rails-3.2.3-api-doc directory create a shortcut to index.html on your desktop, or view index.html in the web browser and bookmark it

27 May 2012

Installing Ruby 1.9.3 In Ubuntu 10.04

Prerequisites for installing Ruby 1.9.3 via RVM are that GIT and Curl is installed.


Installing RVM


  1. Download and run RVM install script - sudo bash -s stable < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer )
  2. Add all users who need to use Ruby to the RVM group
  3. Logout and login
  4. Update RVM so that the rvm command can be run - rvmsudo rvm get head
  5. Reload the terminal (shell) - source ~/.profile
  6. Test to see if RVM was installed and configured properly - type rvm | head -1
          Terminal should output the following, rvm is a function



Installing Ruby 1.9.3


  1. Install Ruby 1.9.3 – rvm install 1.9.3
  2. Set the default version of Ruby to use to 1.9.3 – rvm use 1.9.3
  3. Test to see if the Ruby interpreter runs with the correct version – ruby -v


Installing OpenSSL And Readline Packages


  1. Install libssl-dev Ubuntu package
  2. Install OpenSSL RVM package - rvm pkg install openssl
  3. Reinstall Ruby with OpenSSL support - rvm reinstall 1.9.3 --with-openssl-dir=$rvm_path/usr
  4. Install libreadline6-dev Ubuntu package
  5. Install Readline RVM package - rvm pkg install readline
  6. Reinstall Ruby with Readline support - rvm reinstall 1.9.3 --with-readline-dir=$rvm_path/usr


Notes


Before starting on the installation of RVM you may need to change a setting in Gnome Terminal if it is used. In Gnome Terminal goto Edit → Profile Preferences. Within the shown dialog select Title and Command tab. Ensure that Run command as login shell is checked.

05 June 2011

Visage Development/Support Survey

I have created a survey on improving the development and support for the Visage language. If you can help out with completing the survey that would be highly appreciated. The more results that can be collected from the survey the more complete the picture will be on improving Visage. Please get as many people as you can involved with completing the survey.


15 January 2011

Visage Roadmap

Based on what information I could gather from the discussions, Visage Issue DB, blog posts a clear enough picture has emerged on which to create a roadmap for Visage. Do note that the roadmap below is subject to change, some guesses have been made, and may not be entirely accurate.


Visage 1.0 (Beta 1) – 20 February?

  • Android 2 (eg 2.1, 2.2, and 2.3) and JavaFX 1 (eg 1.3) support
  • Default properties
  • Angle data type
  • Length data type (covering screen metrics, and metric measuring system)
  • Colour data type

Visage 1.0 (Beta 2) – 20 April?

  • Required properties
  • General built-in locale system for strings (locale lookup via fxproperties files)
  • Cascading properties
  • Map data type
  • Updated Android 2 library

Visage 1.0 (Stable) – 20 June?

  • Annotations support
  • Generics support
  • JavaFX 2 support
  • Basic tooling for Visage (eg programmer's text editor)

Post Visage 1.0

  • Basic built-in lookup system using cascading properties?
  • RTS (Reusable Type System)
  • Declarative functions
  • Add a more open license (BSD type one)
  • Application controller?

JavaFX 2 support will likely be delayed as much as possible to allow time to properly support the platform. Hopefully JavaFX 2 will be ready in time for its beta release. Some of the mentioned points may appear in earlier or later Visage releases. Main themes for Visage 1.0 is support for multiple development platforms (currently Android and JavaFX), enhanced property support, stronger platform API support, and additional data types.

03 January 2011

Other Languages For Web Platform

When one thinks of a development platform one would expect that multiple languages would be able to access the platform APIs. With the web platform this isn't the case. Only JavaScript is supported across most web browsers which means it is the only official language for the web platform. Any other language that wants to access the browser/web APIs must go through JavaScript which isn't an acceptable situation. Increasingly more and more languages are going down the compile to JavaScript route. Hence it provides a clear indication that developers want to develop front end web applications in a language other than JavaScript.

Considering how JavaScript has no real competition since there are no other languages embedded in the web browsers it is time that this changed. I am surprised that the current situation of JavaScript only for web development has gone on for this long. Why are no other major browser makers incorporating other languages? For a start a browser maker like Google or Mozilla could incorporate a language like Visage for instance.

It comes as no surprise that JavaScript has undergone very little change due to the lack of competition (think no languages). When some of the details for JavaScript 2 were released there were few big changes made to the language. Imagine if JavaScript had actual competition, think of how much more improved JavaScript would be with the next major version.

The best way to incorporate other languages in a browser would be to have something similar to byte code running in a virtual machine (VM). As such any language that wants to access the browser/web API would need to be compiled first, unless there is an alternative way. Using a VM instead of embedding each language would help to keep the download size of each browser to a minimum. Naturally compile time would be the main bottleneck unless it is kept to a minimum. Now this would be a worthwhile challenge for Google (a fast performing browser VM)!

By incorporating a VM instead of embedding languages in a browser any language would be able to run in the browser (provided it runs in the VM), without requiring a separate runtime to be installed. For the future of web development this would be the next big evolution (not referring to Web 3.0) moving forward. If this is to work then the same system needs to be used by every major browser maker.

What browser makers will take up the challenge of incorporating other languages by implementing a cross platform virtual machine? Even though the challenge is great all it takes is for one browser maker to get the ball rolling.

16 December 2010

Android Support With Visage

Visage has achieved what no other language has done (except Java) with supporting Android without the need for wrapper APIs/libraries and a separate runtime. Most languages that run on Android require the use of ASE (Android Scripting Environment). ASE provides very limited support for the Android APIs, and worse acts as a wrapper which greatly limits performance, and heavily restricts what languages have access to in terms of Android functionality.

Already there is excitement with Visage supporting Android directly like Java without the need for extra baggage. One downside is that the Visage compiler has to do two compiles, one from Visage source code to Java byte code, and the other from Java byte code to Dalvik byte code. This means that performance is not going to be adequate for advanced Android applications, but simple applications will run okay. In time performance will improve as further tweaks are made to the compiler until it gets to the point where there is only a single compile (from Visage source code to Dalvik byte code). When that time comes Visage will have performance comparable to Java.

Another downside is that Visage does not support Android APIs that make use of generics. In time the situation will be rectified since generics support in Visage is top priority. Hence it will be about a month or two before the support appears. As such it will not be possible to create advanced Android applications for the moment. Some genericised APIs will have alternatives that can be used until the support is present.

Guessing from how much of the Android APIs will be supported by Visage based on the total classes/interfaces/enums it comes to roughly 84%, which is surprisingly high considering much of the Android API is genericised. With the proper support the total supported Android APIs would come to about 95-98%. At a very high percentage this would make Visage a very attractive alternative to Java for Android development. With that level of support very little functionality would be unavailable when it comes to developing Android applications.

It remains to be seen what Visage language features can be utilised on Android. Not all features will be available but that will change as the Android support improves. Currently Visage for Android has not be made publicly available yet. Expect a public release within the next few weeks or so.

Next year will be the year that Visage makes its mark on Android development. Finally a viable programming language is emerging for Android development, which goes far beyond creating hello world type applications.