Friday, July 31, 2009

Mooshabaya SRS - 31st of July

We submitted the Software Requirement Specification for Mooshabaya this night. Just created a site for Mooshabaya here, so that we can create the documents collaboratively in a wiki. The project can be found here in sourceforge as well.

Thursday, July 30, 2009

Log in Screen Issue - Ubuntu

Last night I was working with some Localized applications in Tamil Language in Ubuntu 9.04.
For that I had changed my keyboard settings to ta-IN using System > Preferences > Keyboard, and choose Tamil India. For the first time, I forgot to switch back to the English Keyboard before I log out.

Today, at the log in screen, I tried to enter my user name. To my bad, it was entering Tamil characters, which made logging in impossible. I changed the language there at the log-in screen, but it just changed the log-in screen interface language, not the input language.

I tried to recover using CD, and failed. Similarly when I tried to go to the console using Alt+Ctrl+F1, still the keyboard input to the username field must have been in Tamil, thus giving diamonds instead of the letters. Finally in the Grub, I choose somewhat earlier version of gnome-terminal before the update to the later Ubuntu version, as the log in option, where I was unable to log in, yet still able to log in using the console (Alt+Ctrl+F1), as the keyboard was still EN-US there.

Then after some serious examination of the web and bugging my pals, I found the solution.
In /etc/default/console-setup
I found the two parameters were set to refer to India and Tamil.

sudo vi /etc/default/console-setup

I modified them to refer to EN-US.

After saving the console-setup file, I restarted the computer. Then I was able to type in EN-US, and I successfully logged in.

Now I will make sure my keyboard settings is not Tamil or Arabic before I log out, to prevent this issue repeating again. Seems sticking to EN is mostly the safe.

[Update as on Nov 2009]
Since Ubuntu Karmic Koala has the input language and keyboard as a setting option in the log in window itself, it seems this issue has been fixed for Karmic Koala.

Tuesday, July 28, 2009

Testing: GSoC2009Unicode

With the assistance of Sum1 and dom, I was able to fix the issue in Preference dialog Language listing. Now I could see all the languages listed, so that I can test the Abiword Unicode Windows Application in Ubuntu/Wine, or Windows in non-latin languages. As mentioned in my proposal, I will use Arabic and Indic Languages for testing. I will be able to fix the bugs in the dialogs more effectively, henceforth.

So I thought of sharing some screeshots, depicting my progress.

Abiword ANSI Windows program in Arabic.

Abiword Unicode Windows program in Arabic. [In Ubuntu/Wine]

Abiword Unicode Windows program in Arabic. [In Windows XP]

Abiword Unicode Windows Preference Dialog in Arabic.

Menubar in Crotian:

After the port, the [non-latin] special characters of the language were displayed properly.

Wednesday, July 22, 2009


When I was running a GUI application in IDEA8, I was continuously getting the error message:
(:10099): Gtk-WARNING **: Attempting to add a widget with type GtkButton to a GtkComboBoxEntry (need an instance of GtkEntry or of a subclass)

(:10099): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed

(:10099): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

(:10099): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

(:10099): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

(:10099): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

in the IDEA output window.

I later found that this issue is listed here in IntelliJIDEA bug database.

Finally I was able to fix the issue by simply switching back the operating system theme to the default one [Earlier I had Mac4Lin], though smarter solutions may exist.

Monitoring a workflow in XBaya

Initial Steps
SVN Checkout the xbaya source code.
mvn idea:idea from the source root to create an IntelliJ IDEA project from the pom.
Start Tomcat and Run StartMessenger of the WS-Messenger.
Quick installation steps for WS-Messenger can be found here.
Open the XBaya project file and modify the default broker url to http://localhost:8080/messenger/ in

XBaya Workflow Composer
Component -> Add Local Directory [add a directory containing the wsdls which are the wsdl's of the services deployed in Axis2]
Using the components, create a workflow [Say a simple arithmetic addition workflow].
Monitoring -> Configure Monitoring; Use a valid string for topic, and uncheck the Pull Mode.
Monitoring -> Start Monitoring
Workflow -> Run Workflow.

Give suitable values for the parameters. If it is an addition function, give two integer values for param0 and param1.

XBaya will monitor the workflow and will indicate the Time, Component, Status, and Message.

Results can be seen in the idea output as below.

Increase can be seen in the incoming message number and subscriptions/unsubscriptions in the broker [http://localhost:8080/messenger], and the Total successful outgoing message number of the delivery thread of WS-Messenger [http://localhost:12347/].

Friday, July 10, 2009

Commits to gsoc2009unicode, after the mid evaluation

TODO: Save files with international file names. bug 10146.
TODO: Typing in unicode only languages. [Currently boxes are displayed, in the editing area, instead]
TODO: Table column size.
TODO: Insert Image Dialog.

27718 - Porting Win32 Page Setup Dialog. Final commit that comes under GSoC 2009.
27691 - Porting xap_Win32Dlg_ListDocuments.
27684 - Fixing Merge Cells Dialog to Unicode. Testing is being done using Arabic(BiDi Text), Tamil(Indic Text), and Croatian languages.
27592 - Porting ap_Win32Dialog_ListRevisions.
27575 - Fixing the crash in the Document History dialog.
27550 - Porting ap_Win32Dialog_MarkRevisions.
27530 - Porting ap_Win32Dialog_Paragraph.
27509 - Porting ap_Win32Dialog_MailMerge.
27499 - Fixing ap_Win32Dialog_PageNumbers.
27498 - Porting ap_Win32Dialog_MergeCells.
27496 - Porting ap_Win32Dialog_SplitCells.
27455 - Porting ap_Win32Dialog_Background.
27450 - Reverting commit 26655, which gave problems in accessing documents and urls.
27449 - Porting ap_Win32Dialog_HdrFtr.
27385 - First commit after the testing started in Arab.
27378 - Porting ap_Win32Dialog_FormatFrame.
27377 - Porting ap_Win32Dialog_Tab.
27375 - Porting ToggleCase.
27362 - Porting Format Footnotes.
27350 - Fixing ut_Win32Uuid for Unicode only build.
27349 - Porting ap_Win32Dialog_Columns.
27322 - Porting Annotation; This port is incomplete and ofcourse annotation has some bugs.
27273 - Modifying the functions of the classes, as unicode only versions, which are missed in the earlier commits.
27254 - Porting ap_Win32Dialog_Field.
27237 - Porting xap_Win32DialogHelper.
27235 - Fixing the Toolbar.
27232 - Porting xap_Win32Dlg_DocComparison.
27231 - Fixing some earlier omissions in Win32 Graphics classes.
27201 - Open files with international file names. bug 12222.

Commits till the mid evaluation are listed here.

[This post will be updated as I progress further in my project]

Monday, July 6, 2009

Mooshabaya Project Proposal - 6th of July

Mooshabaya [මූෂාභය] targets to generate Mashups to describe the composed workflows, by modifying Xbaya Workflow Composer, which currently exports the composed workflows into BPEL and Jython. Though Mooshabaya focuses and uses XBaya as its workflow composer, it can easily be generalized to be compatible to any other workflow composer. Mooshabaya will find the services from WSO2 Registry, which governs SOA deployments, and the composed workflows are deployed into a Mashup Server as mashups. We will use WSO2 Mashup Server to deploy the mashups in our project.

Mooshabaya also can store the messages as tuples, instead of variables which are the default storage elements of the mashups. In that scenario, the project can work collaboratively with the project bissa "Scalable and Hierarchical tuple space" to form M2SC "Mora Middleware for Scalable Computing", where the use case is a common use case shared by both Mooshabaya and Bissa.

Mooshabaya Project Proposal can be found here.