Qt5 on subsurface-android

[Tomaz Canabrava]

Em 25/03/2014 06:17, "Venkatesh Shukla IIT BHU" <
venkatesh.shukla.eee11 at iitbhu.ac.in> escreveu:
>
> On Tue, Mar 25, 2014 at 1:25 PM, Robert Helling <helling at atdotde.de>
wrote:
>>
>>
>> On 25.03.2014, at 06:46, Venkatesh Shukla IIT BHU <
venkatesh.shukla.eee11 at iitbhu.ac.in> wrote:
>>
>> Hi,
>>
>> > Subsurface on the desktop is purely C/C++ based and uses Qt5.
>>
>> No, all except the very brave currently use Qt4.
>>
>> > For its android port, is it necessary to employ Qt5 for user interface
building?
>> > On one hand, it gives the advantage of having just one code base and
run it on both the desktop and mobile environments.
>> > On the other hand, the user interface is ugly and functionally
useless. In the present condition, it cannot be used for mobile devices.
Having a single code base for both environments fail as the UI elements
would need to be changed to adapt to mobile environment. Also, it may
inhibit other android developers ,who are comfortable in Java and xml, and
don't know Qt.
>> > So, wouldn't it be more prudent to have the following approach?
>> >
>> > 1. Have the UI made in Java and Xml. As far as I know, all the UI
elements used in present Subsurface can be migrated to android.
>>
>> I think this is unlikely to happen. Today, it has been pretty much one
year that we started moving from gtk to Qt. This was one year with a lot of
hard work (in particular by Tomaz) and now we can say we have about reached
feature parity. The whole point of using Qt is that you can code for
several platforms at once without being too far from the native look and
feel. This is not what I would say about Java on the desktop.
>
>
> I think I have been unclear in my suggestions. I do not suggest that the
whole subsurface UI should be migrated to  java. Rather, the subsurface
port for android have Java and xml UI.

Then if we need to create an app for iOS we would need to create yet
another interface. Java and XML ia *not* the way to go, yes - it's easier
if the developer is used to do android, but it's harder to keep feature
parity.

If you wanna create an android port, use QML plus c++,  this way we can
reuse vast majority of the code for desktop on the Android port, and make
it usable too.

_______________________________________________
> subsurface mailing list
> subsurface at hohndel.org
> http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20140325/ecb0fd98/attachment.html>