Channels ▼

Jonathan Erickson

Dr. Dobb's Bloggers

Day 2 or Day 3: Qt Dev Days in Munich Is History

October 15, 2008

Luckily I didn't upset anymore apple carts at Qt Developer Days in Munich, which means I got to hang around for the final day and catch a couple of interesting sessions.

One session was Eike Ziller's demonstration of "Project Greenhouse," a very nice IDE for cross-platform Qt development. Eike made it clear at the outset that Qt Software (formerly Trolltech) isn't trying to out Eclipse Eclipse, or out Visual Studio Visual Studio. (Qt is an Eclipse member, if I recall.) But what they Eike and team is doing with the IDE is providing a development environment to foster and support real cross-platform applications development. The IDE will likely go into Alpha within the next could of weeks, and be a real tool after the first of the year. If you are a Qt developer, you'll want it, I suspect. If your not, I suspect you'll still wanting to know what it is about. It has some nice features.

The second session I enjoyed was a talk that Martin Scherbaum of basysKorn presented as part of the "Qt for Embedded Linux" track. What I found most interesting are the "lesson learned" in project that involved translating real-world industrial controls into embedded widgets. I'll try to sum up.

1. Design. Find a designer who is able to understand software developers and development. A designer who has experience in technical design.

2. Usability. Be realistic about limitations. Always put function before "fanciness". There's always a trade-off between the two.

3. Implementation. Stick with standard platforms, in this case Qt. Don't get to customized.

4. Optimizations. Check on all possible different devices the software will run on. Don't make assumptions. Start your testing with the weakest device.

If you're interested in seeing the outcome of this project, check it out here .




 

 

Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 


Video