On 02/01/2013 02:50 PM, Martin Povolny wrote:
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
> 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.
Thing like Sencha Touch and
JQuery mobile offer libraries for creating
standard elements and mobile type pages using js and html5. Converge UI
is more about creating a uniform style and look and feel across projects
such as Katello and Conductor and builds on top of things like standard
I would love if we could concentrate more on getting things done rather
than splitting forces between more and projects.
I would say given that we would
like to create mobile applications like
Jeremy and Angus suggested, then having a uniform look and feel across
the many possible applications would
a) make development easier
b) make it look like it fits in with the the rest of Aeolus projects,
like conductor and Katello.
Seems to me people are sort of escaping the work on conductor and seek
every opportunity to work on something else ;-)
I don't think anyone is
escaping the work on conductor, but merely
seeing the potential that our many applications can offer and suggesting
possible avenues that could help better the project and develop more
community interest. There are 1001 things we could be working on,
conductor is one of them. But it's all about priorities, "What do real
companies actually want?" If the answer is conductor and nothing else,
then I agree we should put the majority of our effort there, if it's
mobile applications then we should make it possible to create mobile
applicaitons. The problem is that we really don't know. Hence my
previous email to this thread.
6-9 month ago people were saying pulling Tim into it's own component was
wasted effort. But already, it has potential to be migrated into the
MIQ products. IMO Conductor is not the be all and end all of Aeolus.