UX meets Code: the work in progress thread
 

After a long discussion we have an agenda more or less settled. Now it's time to make things concrete and prepare the weekend. The more you prepare in advance the better use you will make of your Long Weekend and the easier will be for people to help you out.

http://wiki.maemo.org/Maemo-Barcelon.../UX_meets_Code

At the end I am proposing 6 projects for main focus and plenty more time for no-agenda, which means more time for work without any main activity taking the little stage.

Arabella is coordinating the UX meets Code and she will explain you in more detail what is the idea with these 6 projects. Basically we want to concentrate efforts aiming to get a clear Before/After result, and improve the developer/UX documentation based on all the learnings.

For the rest of developers with projects in your hands: go to the wiki page and add yourselves! Explain or link to the relevant information about your project, where you are and what are you trying to achieve. The better you explain the situation to a potential UX specialist the easier for them will be to help you straight away.

Re: UX meets Code: the work in progress thread
 

Great, I was thinking to prepare some material to help UX experts better understand what I am trying to achieve, what is missing in Xournal and my ideas so far to solve those.

I'll work on it this week end.

EDIT: below I've thrown in some info.

Aniello

Re: UX meets Code: the work in progress thread
 

As Daniel already mentioned, the maintainers of the two projects that are scheduled for Sunday have their departing flights early, which might be a problem if you require us to be physically available during the session.

Quim suggested we propose something here: If it's still possible to change the schedule at this point, making Saturday change topics with Sunday could help. Aniello (from Xournal) leaves on Monday according to the travel page.

Re: UX meets Code: the work in progress thread
 

Hi thp-

Does anyone know about the developers of Mappr? Are they also leaving on Monday as well? I don't want to run into the same problem if we switch days and then we can't work on Mappr...

Re: UX meets Code: the work in progress thread
 

So far I've found the installs for four of the six applications: gPodder, liqbase, Maemo-Mapper, and Xournal.

Trying to track down MaStory and video editor, anyone know where I can find more info for these?

The reason I am asking for more information is I want all of us to have a chance to install and play with the most updated versions before suggesting further UX improvements.

Re: UX meets Code: the work in progress thread
 

MaStory should be in the extras. http://maemo.org/packages/view/mastory/

EDIT: I think the video editor does not exist yet.

Re: UX meets Code: the work in progress thread
 

From this post it looks like "Mardy" is working on the Fremantle port of Maemo Mapper, but I was not able to find him on the travel page. Maybe the person that represents Mapper can tell you more :)

AFAIK Video Editor for Maemo 5 does not exist yet, but according to Quim, PiTiVi is the application that is being used as a basis for the Video Editor.

Re: UX meets Code: the work in progress thread
 

He's a Nokian by the info in the registration page, should be easier to track from inside :D.

Re: UX meets Code: the work in progress thread
 

MaStory is available in Extras or here: http://maemo.org/downloads/product/Maemo5/mastory/

Re: UX meets Code: the work in progress thread
 

I can speak for Xournal.
Latest version is of course the one in extras-devel.

Xournal is a port of the well know desktop application with the same name. You may want to play with Xournal on a regular Linux desktop to see how many tools and settings are missing from the UI (and that I want to bring back in the Maemo 5 version).

All of the code is there, what's missing are the UI elements.

They can be easily grouped in Tools, Journal and Settings main 'areas'.

I've thought of several ways to bring them back:

* a button on the toolbar that brings up a new window with Tools elements. The window has a menu that would let users switch to the Journal window or the Settings window back and forth.

* different toolbars with different actions on them. Clicking on a button will select that action (like it does now), clicking a selected action would bring an "option" setting dialog for that particular action.
Each toolbar would have a visual way to indicate you can switch between different toolbars (for example '<' and '>')

* no toolbars at all, screen fully dedicated to the notes.
Sliding the finger from the border will make a toolbar/<whatever UI element> slide from the border (like the Mouse mode in Browser).
This new UI element will then either follow the "different toolbar" solution or the "stackable windows" one.

Aniello