[qgil]

Now that the Telepathy dependency seems to be fixed it would be nice and useful to have a direct port of Miniature to MeeGo 1.2 Harmattan. Any takers?

[mikhas]

Nah Quim, I would not recommend that. Better have a clean & tested base this time, then have a FICS backend working, then worry about UI. One can then redo the telepathy stuff as a different backend later, no need to block on that.

[qgil]

Ok, I can still work on 'pencil' UI drafts if that is useful, as I did for the original Miniature.

PS: I hope we keep the offline mode. It was very useful and funny to play casually with friends in bars.

[qgil]

Originally Posted by timoph

As of now I'm also idling in #miniature

Me too.

[mikhas]

Originally Posted by qgil

Ok, I can still work on 'pencil' UI drafts if that is useful, as I did for the original Miniature.

You can do some "throw-away"* UI with Qt Creator and QML (or Qt Components) already. No need to do a paper and pencil UI, really. We will end up with two "teams" anyway: one focuses on backend, the other on UI. At least that's what QML promises should be easy to achieve. In my work project, we were somewhat successful with that whenever new features needed to be designed & implemented.

Originally Posted by qgil

PS: I hope we keep the offline mode. It was very useful and funny to play casually with friends in bars.

Yes, absolutely. Very useful for testing. In fact, the new code already allows that:
* local player vs local player,
* local player vs chess engine (gnuchess),
* chess engine vs chess engine.

Of course we talk about a very simple definition of "working" here, but the concepts are already implemented and working.

(* It remains to be seen how much throw-away the code really is. Perhaps it only needs some tiny fixes here and there to hook it up to the backend ;-))

[xerxes2]

Anyone thought of writing a qml ui to pychess?

[mikhas]

Originally Posted by xerxes2

Anyone thought of writing a qml ui to pychess?

pychess is GTK+ based, quite a bit of UI code, too. It's good stuff, don't get me wrong, but it might prove a bit difficult to port, as GTK+ is not really supported for MeeGo (or Harmattan).

[xerxes2]

Yeah I know that it's gtk based that's why I said that it needs a new ui written in qml. I looked at the code a bit now and it doesn't look that hard. As it's python it should not take that long. If not anyone else want to do it I "might" start working on it. I suck at graphics though but I guess if I (or anyone else) bring it up to a playable state there will be plenty more helping out polishing it.

[mikhas]

Originally Posted by xerxes2

Yeah I know that it's gtk based that's why I said that it needs a new ui written in qml. I looked at the code a bit now and it doesn't look that hard. As it's python it should not take that long. If not anyone else want to do it I "might" start working on it. I suck at graphics though but I guess if I (or anyone else) bring it up to a playable state there will be plenty more helping out polishing it.

Please try! But I fear that you perhaps underestimate the effort to get it handset (that also means touch~) ready. You will also have to change the application logic in several places (common example: need to split up a desktop view into n handset views, due to size constraints and orientation).

[xerxes2]

My target will be the N9 (4") as that is the only meego phone announced this far. If you get it to work on a 4" display I think it will work even better on bigger ones.