On Fri, Feb 01, 2013 at 10:51:16AM +0000, Martyn Taylor wrote:
On 01/31/2013 09:09 PM, Jeremy Perry wrote:
>This is really cool Angus. From the beginning we have known that mobile and alerts is
naturally important to WM -- It's suggested in the original wireframes. The interface
we've been building has been designed with mobile in mind - though we had not
considered the connection issue you point out. Anyhow, Jarda has some awesome wires to
share soon that show how a responsive front end will give us an optimized experience
mobile phones, at least while on the same network.
This sounds awesome. I can envision many mobile applications that consume
various services offered by Aeolus. Having something like
"mobile-converge-ui" would be really fantastic (proving we choose to go down
the html5, css3, js route, which I would recommend).
I wonder how much work converting our current converge-ui to target mobile
devices would be.
I have a very little understanding for the idea of creating a mobile
We need a complete wireframe of how the conductor UI should look like,
we need to fix most of the workflows in conductor and then we have the
winged monkey UI to work on.
Also there are things such as Sencha Touch and other mobile web
frameworks that can be used w/o reinventing the wheel.
I would love if we could concentrate more on getting things done rather
than splitting forces between more and projects.
Seems to me people are sort of escaping the work on conductor and seek
every opportunity to work on something else ;-)
Martin Povolny <mpovolny(a)redhat.com>