On 28 July 2014 19:29, Tomaz Canabrava <[email protected]> wrote: > On Mon, Jul 28, 2014 at 1:27 PM, Lubomir I. Ivanov <[email protected]> > wrote: >> On 28 July 2014 19:19, Tomaz Canabrava <[email protected]> wrote: >>> On Mon, Jul 28, 2014 at 1:16 PM, Lubomir I. Ivanov <[email protected]> >>> wrote: >>>> On 28 July 2014 19:03, Anton Lundin <[email protected]> wrote: >>>>> Just a note here from how we thought. >>>>> >>>>> The scope of this GSOC project is to produce a usable downloader app >>>>> for android and one pre-req for that is a usable touch friendly ui. >>>>> >>>>> The current Android port of subsurface is unusable as a ui, but it >>>>> works as a technical product. It needs a better ui for touch. >>>>> >>>> >>>> i haven't followed previous discussions; can you elaborate on why it's >>>> unusable? >>>> is it more of a cosmetic issue or perhaps QWidget based things like >>>> QTreeView (divelist) do not work at all? >>> >>> The UI becomes too small to be used on a phone and it's not stetically >>> appealing to be used on Tablet. >>> >> >> hmm, how about allowing only one view at time: profile, divelist, >> diveinfo etc and increasing the font sizes? >> the "one view at a time" thing, is the mobile way of doing it because >> of resolution restrictions. > > QML can takes care of that, I'v already created a Subsurface QML > interface just for fun and it was almost easy to do. :) >
and can be done in C++ based on our current UI - just show the "view" that is needed? for a recent Qt / POC project i completely ditched QML in favor of C++ because i wanted a more direct QGraphicsScene interaction. QML only provided the "quick" part in terms of instantiating UI elements, but not the control and performance i wanted. lubomir -- _______________________________________________ subsurface mailing list [email protected] http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
