Sign in

E-mail *, (xx@domain.com)
Password *

Register | Forgot password

Recent blogs

RSS - Blogs
March 9, 2010
State of OSGi in the Java world
March 4, 2010
Reach more people with Google Translate
March 3, 2010
Get My Advice
February 26, 2010
What? Where!?!
February 11, 2010
Split it!

All Blogs...


About cars and software

March 20, 2008

Have you ever noticed how cars seem to be getting less hardware and more software?

I have a confession to make. Cars mean little to me, but I do like gadgets. So when I bought my car years ago, I decided to maximize on the number of electronic gadgets in it. So I ended up with a car that:

  • automatically darkens the rear view mirror when lights behind get too bright,
  • automatically adjusts the windscreen wiper speed depending on the rain,
  • automatically turns on the warning lights when breaking too hard and too fast on the highway and
  • automatically lowers the side mirror when the gear is in reverse so you can see the sidewalk.

And much more. Great isn't it? Okay, so it doesn't have whisper mode or super pursuit mode, but still!


One day I noticed something very funny and recognizable about the car. For one, the light switch only has two settings: "Automatic" and "On". "Automatic" in this case translates to "when the starterkey is turned on", meaning it is basically the same as "On". Lights off is not an option in this car. Second, the navigation system has a display option to choose the preferred color, one of which is "night". In fact, to top it off, there is an option to make the color switch "Automatic".

Nothing short of brilliant, I would say! When I close my eyes, I can already see the processes at the manufacturer.

Team 1 is working on the navigation system and is about to hit the milestone "Colored interface". Only one thing to decide: how to implement "Automatic night colors". Time of day is a bad choice. Light sensors might be it, but sometimes give freaky effects. Why not follow the car lights settings?
if (automaticNightColors && lights.isOn()) {
  navigation.setColor(NAV_COLOR_NIGHT);
}
Team 2 is working on the lights and is confronted with the requirement "automatic lighting". Light sensors give bad results. Some countries consider it more safely to drive with the lights on at daytime, others even have legal requirements to do so. After careful consideration, it is decided to implement this as:
if (starterkey.isOn()) {
  lights.setOn(true);
}

Even though both teams did an outstanding job, the result is a bit funny for me as end user. I have to manually switch to night colors in my car because the "Automatic" setting always renders the screen nice and dark. Regardless of the time of day, amount of light or any other circumstance that might make me want to go all night goggly.


The other day I noticed something similar in the WCB design guidelines. The document has been written to help us get the best out of our WCB's. One of the guidelines says to put a "readme.txt" and "changelog.txt" in your WCB and example files are provided. On the other end of the spectrum are the Maven archetypes to help us get started on a WCB in the best possible way. Two very helpful incentives to get good WCB's.


There's one missing link though... How to get your .txt files into the WCB?

It took some attempts and some asking around, but finally I found out that you have to place them as:

<WCB top directory>/src/main/resources/readme.txt
<WCB top directory>/src/main/resources/changelog.txt

But the goodness does not stop there!

Other than for my car's navigation system, I can assist in getting rid of this particular oversight.

Just hop over to the Issue Tracker and help us improve GX WebManager, like I did. Isn't life great?

Greetings,


Patrick


About the Author

Return to all blogs

 

Patrick Atoon

Patrick Atoon has gained nuff respect as one of the most experienced web architects in the GX Webmanager community or even the global hip hop community for that matter.

Read all Patricks blog entries

Other blog entries:

February 26, 2010
What? Where!?!
September 3, 2009
Do the Right Thing
June 18, 2009
wm:link secrets
March 2, 2009
Server side represent! (Part 2)
February 4, 2009
Server side represent!
January 15, 2009
Making cache
December 9, 2008
Like A Version
August 19, 2008
Stop making sense
August 4, 2008
Namaste!
July 7, 2008
Japanese encore (日本のアンコール)


Share:

del.icio.us
digg
Technorati
Slashdot
Reddit
YahooMyWeb
NewsVine
ekudos
© 2010 GX creative online development B.V.

Disclaimer

This website (GXdeveloperweb.com) may discuss or contain opinions, (sample) coding, software or other information that does not include GX official interfaces, instructions or guidelines and therefore is not supported by GX. Changes made based on this information are not supported.  GX will not be held liable for any damages caused by using or misusing the information, software, instructions, code or methods suggested on this website, and anyone using these methods does so at his/her own risk. GX offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this website, including any liability resulting from incompatibility between the content of this website and the materials and services offered by GX. By using this website you will not hold, or seek to hold, GX responsible or liable with respect to the content of this website.