The point is that we don't want to add new "concepts" to Qt if not strictly necessary.<br>The idea I keep in my mind is "We are going to adapt Qt to hildon, not rewriting hildon with Qt".<br>I hope that the other people understand this too. Then we need to discard something... <br>
<br>If we want to add the features that you mentioned before, well most probably we need to add new APIs...<br><br>BR,<br>Antonio<br><br><div class="gmail_quote">On Mon, May 25, 2009 at 12:58 PM, Murray Cumming <span dir="ltr"><<a href="mailto:murrayc@murrayc.com" target="_blank">murrayc@murrayc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>On Mon, 2009-05-25 at 12:25 +0300, Antonio Aloisio wrote:<br>
<br>
> While we are on the subject of Qt looking like Maemo without<br>
> API<br>
> changes, how are you dealing with the need for Maemo-specific<br>
> API such<br>
> as that in HildonWindow:<br>
> <a href="http://maemo.org/api_refs/5.0/beta/hildon/HildonWindow.html" target="_blank">http://maemo.org/api_refs/5.0/beta/hildon/HildonWindow.html</a><br>
><br>
> This trick is possible because Maemo applications have menus, toolbars<br>
> as any normal<br>
> desktop application. Okay they look different, but we can instruct Qt<br>
> to give them the looks that<br>
> we want...<br>
> The same thing happens for the other official supported Qt platforms<br>
> (mac, s60 ans so on)<br>
<br>
</div>Yes, I know that's the Qt philosphy, but repeating it doesn't answer my<br>
question. For instance:<br>
<br>
I guess, Qt windows can't usually have markup in their titles, so you'd<br>
be changing the documented behaviour (therefore subtly changing the API)<br>
if you parsed the regular title as markup, instead of offering separate<br>
API:<br>
<a href="http://maemo.org/api_refs/5.0/beta/hildon/HildonWindow.html#hildon-window-set-markup" target="_blank">http://maemo.org/api_refs/5.0/beta/hildon/HildonWindow.html#hildon-window-set-markup</a><br>
(I think that the new API should be added to upstream GTK+ instead<br>
anyway.)<br>
<br>
I guess, Qt windows don't usually have a concept of "activated by the<br>
window manager":<br>
<a href="http://maemo.org/api_refs/5.0/beta/hildon/HildonWindow.html#hildon-window-get-is-topmost" target="_blank">http://maemo.org/api_refs/5.0/beta/hildon/HildonWindow.html#hildon-window-get-is-topmost</a><br>
(This is presumably something different than gtk_window_is_active():<br>
<a href="http://library.gnome.org/devel/gtk/unstable/GtkWindow.html#gtk-window-is-active" target="_blank">http://library.gnome.org/devel/gtk/unstable/GtkWindow.html#gtk-window-is-active</a> )<br>
<br>
Also, I doubt that the Qt menu and toolbar API easily supports the idea<br>
of one-single "edit" toolbar, introduced in Maemo 5:<br>
<a href="http://maemo.org/api_refs/5.0/beta/hildon/HildonWindow.html#hildon-window-set-edit-toolbar" target="_blank">http://maemo.org/api_refs/5.0/beta/hildon/HildonWindow.html#hildon-window-set-edit-toolbar</a><br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div><a href="mailto:murrayc@murrayc.com" target="_blank">murrayc@murrayc.com</a><br>
<a href="http://www.murrayc.com" target="_blank">www.murrayc.com</a><br>
<a href="http://www.openismus.com" target="_blank">www.openismus.com</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><br><a href="http://www.brainyquote.com/quotes/authors/w/walt_disney.html" target="_blank">Walt Disney</a> - "I love Mickey Mouse more than any woman I have ever known."