When you start MoI V3
 1-8  9-28  29-35

Previous
Next
 From:  Michael Gibson
3712.29 In reply to 3712.28 
Hi vodkamartini, there is actually quite a bit more UI involved than it first appears, since there are 111 bits of command UI.

> QT or WPF

Well, one huge problem with WPF is that it would lock me even more tightly into being Windows only.

Native Qt is a possibility, but after looking into it there are several parts that I don't like - the overall design of it shows that it's really primarily meant to be driven from C++ code (like having code that directly creates widgets).

For tweaking it is a lot easier for a "power user" to edit an .htm file than it is for them to edit some C++ code and compile it in order to make changes or plugins.

Qt does have a method to load UI configurations from .ui files, but when I looked into that the .ui files were kind of like direct XML data dumps of C++ objects, they did not seem particularly easy to edit directly in a text editor.

One of the nice benefits of HTML is that it is very easy to edit in a text editor, it's easier to write simple UI that may include some little bits of script code along with it for UI-specific logic, which greatly helps in keeping a separation between UI stuff and core C++ code stuff. Also HTML is much more widely used and more likely familiar to a wider range of people than the Qt UI XML data file format.

So although I'm sure that it would be possible to whip up something close to MoI's UI in native Qt, I'm very dubious that it would be possible to keep the same level of really easy authoring/customizing that comes with having the UI made up of all user-editable .htm files. This aspect of UI authoring will become more interesting in the future with MoI when I have more emphasis on extensions and plugins.

MoI's UI also has some features that I have not seen in Qt applications like the ability to scale the UI up or down freely, and easy translation by just creating a single Strings.txt file... There would likely be some pretty big stumbling blocks trying to bring 100% of MoI's UI functionality over.


It's just easier to experiment with layout-driven things with HTML, having a flexible HTML based UI was especially crucial in the earlier stages of MoI when the UI was not all finalized, the flexibility really helped me to be able to experiment with things and actually come up with the current UI.


- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  vodkamartini
3712.30 In reply to 3712.29 
Regarding that, QT 4.7 introduces a new declarative UI (QML). Sorta like XAML, but in javascript.

http://labs.trolltech.com/page/Projects/Graphics/Kinetic/DeclarativeUI

QT also includes a WebKit module that might be worth a look.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
3712.31 In reply to 3712.30 
Hi vodkamartini,

> Regarding that, QT 4.7 introduces a new declarative UI (QML).
> Sorta like XAML, but in javascript.

Yeah I've looked at that a bit - it's totally brand new though, which scares me off a bit just in general. For example because it's new there really isn't much chance that very many people would already be familiar with that syntax, unlike HTML.

Also the general focus seems to be on making spinny whizzy animations with it, I'm not sure if much effort has been spent on using it for more regular application UIs.

Qt 4.7 is actually not even in final release yet, it's currently in beta.


> QT also includes a WebKit module that might be worth a look.

That is actually what I've been looking at - it's the easiest way to actually build WebKit without having to install a huge simulated UNIX environment (Cygwin).

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  neo
3712.32 
Music To My Ears...I now must be a lot of work involved but I'm sure Michael could pull it off...
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  igor
3712.33 In reply to 3712.31 
In my opinion from a commercial point of view i think HTML UI will be in a more favorable position as it will enable users to more easily author their extensions given the fact that Michael will soon be unable to follow all the requests and may concentrate on the geometric core and the supporting api and sdk so that everyone might build own uis and features relevant to ones core business and Michael will maintain just a basic app..

sounds like a suggestion..))
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
3712.34 In reply to 3712.33 
"""""Michael will soon be unable to follow all the requests """"""""''

Michael is "Growing help" right now. As long as he waters and feeds it every day, all the forum requests will be handled with the same care!!! lol
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
 From:  Michael Gibson
3712.35 In reply to 3712.33 
Hi igor, yup that's one of the ideas behind using an HTML based UI in the first place - that it is more familiar to a wide range of people and that tends to make it easier for people to customize things or author new pieces of UI.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged
 

Reply to All Reply to All

 

 
 
Show messages:  1-8  9-28  29-35