This is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I need answered for part of the project.

What I did

• Built the framework for adding tours
  • To add a tour is now a simple two step process. First, the tour text must be added to the tourList.xml file. Second, the tour must have a start point by adding "startTour(tourName)" in any function. Another option is to attach a tour using "attachTour(object, event, tourName)" to activate a tour on a certain event. That's it! Currently, I have ideas for future expansions, but keep reading to find out more.

What had issues

• The "attachTour()" function
  • For some reason when attaching a tour to the note input icons in the toolbar, the icons no longer get selected. As in, it does not run the code that selects the note length and turns the icon blue. I currently have no idea why.

What is next

• Fix "attachTour()"
  • If I can get this fixed, it will make practically every item and action be able to have a tour.
• Create a tour interface
  • Currently, this is a bunch of message boxed. However, I set the framework out nicely so I can easily add a fun/sleek/whatever interface.
• Create a few sample tours
  • This is for testing purposes, but some simple tours could showcase the functionality.

Question for the Week

For the tour interface, what would be a good idea?
Based on what I've seen, an overlay box (slightly transparent perhaps) will appear next to the item of interest. From there, the tour can be progressed, canceled, or turned off.

Thanks,

Joshua Bonn
Github: JoshuaBonn1
Current Branch: startup-tour