[GCompris-devel] gcompris [Sailfish OS]

[JAZEIX Johnny]

Hi,

There are also some "hidden" uses of Dialogs in src/core/core.js.

The uses that I can remember are:
* Display welcoming message for first use;
* Bar progression when downloading voices/words.

Just for your test on sailfish, I think you can only remove the dialog 
and the import on main.qml (I think the other ones will be loaded 
dynamically when needed and you won't need them for testing).

I don't know how Dialogs look on Heebo (didn't find screenshots) but, 
for my part, I was thinking on something "simple" as 
https://techbase.kde.org/File:Quitdialog.png with some customization 
possible (have button with icons and set the central item as we want).
If someone think of other ways on seeing how dialogs should be, don't 
hesitate :).

I hope I didn't forget uses of Dialogs in GCompris.

Johnny

On 01/16/15 22:43, Alex Smirnoff wrote:
> Hello.
> I have a good experience in Qt, including UI definition, Javascript 
> and more.
>
> But I could find nothing but FileDownload and ShowMessage dialogs, 
> that use QtQuick.Dialogs.
> And yes, you are right, they are looking awful. It is like someone 
> comes  in a beautiful sliding world and says: hey you are on a Desktop 
> - do not forget it man :-)
>
> All other dialogs is not a real window based dialogs, but pages. So 
> nice. That what I meant before. (This is very similar the way Sailfish 
> uses. Good so far).
>
> So, Bruno, please give me access to wiki or reserve this job for me by 
> your self.
> I will reimplement these two using something similar to GTK version of 
> Gcompris or, for example, Heebo, or anything you say me to do. (I am 
> not a designer at all, could not design them myself).
>
> But first of all, I will temporary throw them both away in the version 
> prepared by Johnny  for SailfishOS and try to build/install/run it again.
>
>
>
>
>
>
> 2015-01-16 10:04 GMT+01:00 Johnny Jazeix <jazeix at gmail.com 
> <mailto:jazeix at gmail.com>>:
>
>     If you still want to do it, it is still not hard to do (even if you
>     d'ont have a lot of experience in Qt and Qml) :-). As Bruno says, we
>     don't have to hurry so we can take our time to think of the best way
>     of doing it and if you are interested at developing it, we will help
>     you doing it.
>
>     If you don't want/can't, don't worry, someone else will do it ;-).
>
>     Johnny
>
>     2015-01-16 9:57 GMT+01:00 Alex Smirnoff <smirnoff.al at gmail.com
>     <mailto:smirnoff.al at gmail.com>>:
>     > Understood.
>     > I just thought I could help in this way, because that is the
>     only way I see
>     > right now.
>     > Never mind.
>     > If you see how can I help here, please tell me.
>     >
>     > Alex.
>     >
>     > 2015-01-16 1:11 GMT+01:00 Bruno Coudoin
>     <bruno.coudoin at gcompris.net <mailto:bruno.coudoin at gcompris.net>>:
>     >>
>     >>
>     >> Le 15/01/2015 12:28, smirnoff.al at gmail.com
>     <mailto:smirnoff.al at gmail.com> a écrit :
>     >>>
>     >>> Good.
>     >>> Could you  already say who will do it?
>     >>>
>     >>> I could try to fullfil this task.
>     >>> I mean, remove all imports of dialogs and add imports from
>     custom ones.
>     >>> The first version of custom dialogs could be just copy past
>     from qt ones
>     >>> with slight changes.
>     >>>
>     >> Hi,
>     >>
>     >> I don't thing we have to hurry up and do a dialog version
>     derived from the
>     >> Qt code. This would lead to an extra step and now that we
>     decided that
>     >> having custom dialogs is our goal lets just do this.
>     >>
>     >> It will take less time to do the right thing directly than
>     coding it
>     >> twice.
>     >>
>     >> Bruno.
>     >
>     >
>     >
>     >
>     > --
>     > Alex Smirnov
>
>
>
>
> -- 
> Alex Smirnov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/gcompris-devel/attachments/20150119/64b38193/attachment.html>