See into S60
» Subscribe
» Favorite Links
» What is S60?
» Freeware & Trials
» S60 devices
» Hints and tips

» About this blog
» Blognotes (15)
» Bugs and Workarounds (2)
» Build tools (1)
» Carbide.c++ 1.1 (4)
» Carbide.c++ 1.2 (8)
» Carbide.c++ 1.3.x (1)
» Carbide Plug-Ins (2)
» CodeWarrior (2)
» FAQ (5)
» Future directions (21)
» General (44)
» Off-topic (4)
» On-device debugging (11)
» Performance Investigator (2)
» Product features (15)
» Product releases (16)
» Screencast (8)
» Support (23)
» Tool setup (5)
» UI Designer (8)
» Usability (11)
» Work in Progress (11)
» Write-build-debug (4)
» Tommi's Reports from Wonderland
» Voice of S60
» Creating Carbide C++
» S60 Multimedia Blog
» The Convergence Zone
» Web Browser for S60 Blog
» Consumed by S60
» Java for S60
» Mobile Web Server
» Mobile Security
» See into S60
» Business2GO
» Nokia Podcasting Application Blog
» Simplifying debugging with TRK over the Bluetooth
» Eclipse 3.4M7
» Online Carbide documentation push
» Panic Debugging
» Screencast: Carbide Perspectives
» May 2008
» April 2008
» March 2008
» February 2008
» August 2007
» May 2007
» April 2007
» March 2007
» February 2007
» January 2007
» December 2006
» November 2006
» October 2006
» September 2006
» August 2006
» July 2006
» June 2006
Subscribe
Links
May 09, 2008 Online Carbide documentation push Posted by L. Frank Turovich at 10:27 AM | Categories: Future directions, Off-topic, Product features, Support, Usability

One of the more ambitious ideas I have for the next release of Carbide is to throw all of the public Carbide docs onto a website using the Eclipse Infocenter. One of the drivers to do this is to make the information available to Google searches. Most people, including myself, have developed the habit of simply doing a Google search for anything we want and simply ignoring our local resources. In many cases I believe that people sometimes actually forget that they have product documentation on their machine. And let's face it, searching the web has become both a habit and the way things are done.

When I actually thought a bit about my behavior and why I preferred a Google search over simply opening the help system on my computer I realized that it was the chance that a more interesting link would appear in the search results. One that would grab my interest and add another small bit of interesting trivia into my knowledge base while pretending to actually complete my task. In short, its fun to learn new things and the web makes it so easy to find interesting tidbits to savor.

So, to make it easier for Carbide users to find the information they want, it behooves us to make it available on the web. So over the next few Agile sprints we'll do a setup of the Infocenter, figure out how to merge it into our build process so it gets updated automatically, then do some internal testing before releasing it to the beta group for pounding. The end result is that by the time the next release of Carbide is available, the Online Carbide Help (working title) site will be public and in use.

Lots of work but I think a Carbide 'feature' you will appreciate.

But I need to know, do you think this is a useful feature to push for? Will it make the docs more helpful to you? How often might you use something like this? Am I imagining the impact this will have? Am I a megalomaniac to think this might be useful? Have I finally gone too far?

Inquiring minds want to know.



Permalink |

Comments

I think this is a very good idea and I hope it will be implemented.

By the way, when is the Beta for the new Carbide scheduled to start? :-)

Posted by: Stelian Iancu | May 10, 2008 04:47 AM

The exact time of the next Carbide beta cycle has yet to be determined. There are a few reasons for that:

One is that we really want to wait until Eclipse 3.4 goes final before releasing any public 'beta' for testing. Lots of Eclipse and CDT changes to resolve before we will feel comfortable with a release.

Second is that we are looking at doing 'milestone' releases at the end of specific Agile sprints to introduce new features as they become workable to users. Again, we don't want to release features just to release them but to get some hard testing on them so we can eradicate any issues as early as possible.

Keep an eye on this blog and the Beta Group pages for more information as it becomes available.


Posted by: L. Frank Turovich | May 11, 2008 11:58 PM


Post a comment







«Back to previous page