The default is a search command; type anything and hit “enter” key, you get back the search results as you would perform on a typical Google search. Many of the commands have aliases as well and the alias is as simple as a single letter. For example “l youtube” takes you to the Youtube website. It is the equivalent as typing youtube in Google search page and pressing “I’m Feeling Lucky”. Try Goosh, am sure you will like it.

Thanks to my friend Rajesh Kannan for bringing Goosh to my notice.

RescueTime is a site that I came up recently through stumbling. There is a good and a bad side to me finding this site. The bad part first. One year ago this was my idea. But as you might know ideas are to be put into action soon, otherwise either it will not see the light or there will be someone else who will envision the same idea and probably would implement it. The second case was what happened to me. OK now the good part is this tool really helps me take a look at the time I spend everyday on the various applications on my laptop. I wish I had this tool ten years back so that my time management would have been much better. RescueTime has a desktop service that can be downloaded and sits on your computer tray. It constantly monitors the active applications you are in and keeps sending information to its website. The website aggregates this data and presents a graphical report on the dashboard. You can tag the applications you used, so that RescueTime can group the time under different categories. For example, I use work, learning, research etc. Another key feature is that you can set goals like how many productive hours you want to put everyday. RescueTime will tell you if you met that goals and sends a weekly report by email.

RescueTime comes in two flavors - a personal edition and team plus edition. Both of them are free except for team plus edition, up to 5 users it is free. A team plus edition will allow you to compare time with the group time which helps in setting team level benchmarks. What RescueTime will not know of course is your idle time or time that you were in meetings. But I am practicing to capture this as well. Since I use Google calendar for my schedule, before I go to the meeting I activate the Google calendar window. This gets captured by RescueTime and gets tagged under Meetings. It would be good if RescueTime can export this data in different formats that can be imported into Timesheet systems or if it can integrate with Timesheet systems. That would really save a lot of time or when people forget to fill the timesheets and later when they fill it is only approximate or partial just because they don’t remember what they did after a day (that’s natural). RescueTime is a fantastic product to take a look at how you spend your time, do better time management, set goals and cut down on time wasters like checking mail every now and then or on the instant messengers. Of course only if you would want to make better time management consciously; no tool would do that by black magic.

Download JBoss start/stop Script

Some items you have to change in the script to work for your environment.

• PIDFILE - File containing the process id. Change it to a location where you want to have this file.
• STARTJBOSS - Command to start JBoss. Scan through this command in entire and make sure you have added the parameters necessary for your environment, set the minimum and maximum JVM heap, and also the server you want to start. You can get this information from the server log when you run JBoss using the run.sh script. The script assumes you have Java executable in the path.
• LOGFILE - The server’s log file. Change it to a location where you want to have this file.

Additionally you might want to change line 32 to the right version of JBoss you are using. Make sure this line reflects exactly what you see in the server log at the end when JBoss completes starting the server. If it doesn’t match, this script will go in infinite loop.

An additional benefit I got after writing this script was to have our automated build scripts using Ant to deploy the applications on any box using the SSHExec tasks. Really cool and time saving.

Disclaimer - The script herein provided to you is “AS IS” without any warranties of any kind. The script has not been thoroughly tested under all conditions. I, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

• dead(a): not circulating or flowing; “dead air”; “dead water”; “stagnant water”
• not growing or changing; without force or vitality

If you look at it from a career perspective, it is easy to get into being stagnant. One doesn’t need to do anything beyond what he is expected. The person will be in the flow but at a point will become stagnant, in more business terms a commodity. You are no more worth than millions of others who are in the pool. Standing out or being uniquely recognized and becoming successful is to swim against the commodity pool. As you keep moving against, you will raise to a lesser commodity pool.

Taking the same analogy of a river, if I have to take the example of river Ganges, it has many tributaries flowing through many cities North East India until it reaches the Ganges Delta and flows into the Bay of Bengal, north eastern part of the Indian Ocean. But the source of Ganges is a 19 mile stretch glacier in the Himalayas called the Gangotri glacier. The origin of yet another major river in India called Cauvery is Talakavery, which is a spring. The source of any river is unique and distinct.

To reach success and growth in career is to swim against the current, to constantly grow and change and not be stagnant. Growth is not possible until one exerts additional effort to do things beyond what is expected. When one tries to do things beyond what is expected, there will be hurdles and blocks as in the current that pushes the water in the river. Sure, swimming against the current is difficult, but when you make it you get towards a point, a unique identity and are in a pool of lesser commodity.

So what did you do/learn beyond what is expected out of you?

To be more exact, our application consisted of a Flex model folder containing action scripts common across the other Flex modules. So this had to be set as a run time shared library (RSL) rather than packaging it along with other modules. Packaging with other modules would make it work, but it becomes bulky and performance degrades because the model classes are loaded for each Flex package. To make it a RSL while building the flex components, the model has to be referred as RSL using the attribute in the task. We did this but only got the error mentioned above “RSL Error 1 of 1″. We were clueless at this point and tried out combination of attributes while compiling using mxmlc.

Our only hope remained in identifying what makes the build done by the flex builder make it work and the difference between the parameters it uses and what we use. We knew this because the size of SWF generated out of a Flex builder build was very different from the size that came out of our ant build. Because the build properties are GUI based, how to get what configuration flex builder uses and how it translates to the appropriate compiler options? After exploring the available compilation parameters with mxmlc, we found out the parameter -dump-config would dump the configuration used in a file. We added this parameter to the compiler parameters in the Flex compiler options as shown below in the screen.

We compared the configuration that flex builder used versus what we had been using in the mxmlc task, only to find out there wasn’t much difference except for few of the compile time properties which was also present in the flex.config file we were using. The same RSL attribute was present making the model package as reference. We were back to square one wondering what could be the difference and what we are missing. After two days of struggle, a careful re-examination of the configuration in Flex builder when referring the model package in other packages revealed something. Take a look at the snapshot below.

The “Auto extract swf: true” was something that we could not find a translation when using the compc ant task and we could not find any documentation mentioning this in the flex ant tasks documentation. We were able to confirm that something is happening here again because of the size difference between what Flex builder generated versus what our ant build generated. There must be a way to produce the package exploded rather than having it packaged as one SWF, just like an exploded war file. Fortunately there was option to do this with the compc task when the directory attribute is set to true and the output attribute holds a directory value. When we were able to do this everything got revealed. Here is a snapshot of the directory structure.

A look at the files that got generated told us that the SWF that contained the model was having a name of “library.swf”, and when this directory was packaged and added as RSL, there is a mismatch in the reference. The flex runtime binary is looking for MyModel.swf while the only file present is library.swf. That should be the reason for the RSL Error. Also the size when Flex builder built the package was exactly equivalent to the size of the library.swf file present above. So that answers what “Auto extract swf: true” configuration does.

So our ant script was ready, we used one compc task to generate an exploded model directory. Picked the library.swf and copied it to the war with “MyModel.swf”. Another compc task to generate the model packaged so that we can refer it only for compilation for other flex models. Once we did this, everything worked perfectly. So here is the sample ant code (right click and save as, then open in an editor) that made the trick.

Hope this is useful for someone struggling with similar situation and it saves the head cracking time. If someone has found out an easier approach to this please pass that on, we would be happy to learn.

Thanks to Hari Shetty of Jiffle for pointing this link.

Here is a link to a blog article “Event Order” which explains the problem, and the solution to it. Thanks to my friend and colleague, Narayanan who sent me this link when we faced the problem handling such a situation while developing Jiffle.

The lunch break at Barcamp degraded the whole flow, as the meal at Google was sumptuous with so many varieties that the venue became like a food show people trying out everything. To top it off the distribution of the ‘goodies’ (the freebies for the participants) happened after lunch and it became more chaotic. After this there were very few who still retained the energy to listen to more sessions. Nevertheless, since Barcamp is organized by, run by, presented by and attended by users it was an event that brought people together from various sectors and helped in networking.

For those of you who want to look at my presentation here is the link to SlideShare. For those of you who want to see everything in one picture here is my mind on the topic. Couple of photos here at Flickr. Thanks Harish for capturing the moments.

If any of you would like to discuss about the topic or have any questions, feel free to drop me a mail via rramesh at techmasala dot com.

By the way if you are wondering what’s Barcamp, click here.