Ok.
On Mon, Apr 16, 2012 at 7:26 AM, Daker Fernandes Pinheiro <
daker.pinhe...@openbossa.org> wrote:
> My team in INdT has been researching about theming/styling of Qt
> Components.
> I’ve synthetised what we’ve been done and some of our aims and ideas:
>
> http://codecereal.blogspot.com.br/201
My team in INdT has been researching about theming/styling of Qt Components.
I’ve synthetised what we’ve been done and some of our aims and ideas:
http://codecereal.blogspot.com.br/2012/04/qml-themingstyling.html
On 04/13/2012 06:45 AM, Alan Alpert wrote:
> On Fri, 13 Apr 2012 02:30:08 ext Charl
On Fri, 13 Apr 2012 02:30:08 ext Charley Bay wrote:
> >
> IMHO, it seems like this "theming" and "styling" thing should be so much
> *easier* with QML. But, I'm not seeing approaches (yet) on these lists
> that will work for us.
>
> This is not a complaint: The QML declarative paradigm is new,
>
>
>
> A theme manager will make the things much more simpler and clear for the
> user and
> when it comes to add support for other platforms. ,
> Let me try explain more:
>
> >From user perspective: themes>
>
> >From developer perspective who wants to add support for another platform
>
>
On Thu, 12 Apr 2012 17:46:21 ext BogDan wrote:
> > From: Alan Alpert
> >
> > To: development@qt-project.org
> > Cc:
> > Sent: Thursday, April 12, 2012 6:20 AM
> > Subject: Re: [Development] Qt5 missing features
> >
> > On Thu, 12 Apr 2012 11:28:
> From: "lars.kn...@nokia.com"
> To: alex.wil...@nokia.com; development@qt-project.org
> Cc:
> Sent: Thursday, April 12, 2012 10:15 AM
> Subject: Re: [Development] Qt5 missing features
>
> On 4/12/12 6:05 AM, "ext Alex Wilson"
> wrote:
>
> From: Alan Alpert
> To: development@qt-project.org
> Cc:
> Sent: Thursday, April 12, 2012 6:20 AM
> Subject: Re: [Development] Qt5 missing features
>
> On Thu, 12 Apr 2012 11:28:43 ext Lincoln Ramsay wrote:
>> On 04/12/2012 11:00 AM, ext Alan Alpert wrote:
>>
On 4/12/12 6:05 AM, "ext Alex Wilson" wrote:
>On Wednesday, April 11, 2012 07:25:41 pm ext BogDan wrote:
>> the problem with QML desktop components is that
>> not all controls are touch friendly (e.g. lists, editbox, etc.), even
>>they
>> have Android look the feel is not the right one. As I said
On Thu, 12 Apr 2012 13:44:53 Lincoln Ramsay wrote:
> On 04/12/2012 01:20 PM, Alan Alpert wrote:
> >> If there was a "standard API" defined for a "components" and each
> >> platform provided something that was source-compatible with this API
> >> then that would work too (without indirection) but I
On Wednesday, April 11, 2012 07:25:41 pm ext BogDan wrote:
> the problem with QML desktop components is that
> not all controls are touch friendly (e.g. lists, editbox, etc.), even they
> have Android look the feel is not the right one. As I said, I believe is a
> waste of time to have 3 completely
On 04/12/2012 01:20 PM, Alan Alpert wrote:
>> If there was a "standard API" defined for a "components" and each
>> platform provided something that was source-compatible with this API
>> then that would work too (without indirection) but I haven't seen anyone
>> suggesting that a platform's "compon
On Thu, 12 Apr 2012 11:28:43 ext Lincoln Ramsay wrote:
> On 04/12/2012 11:00 AM, ext Alan Alpert wrote:
> > One thing I don't understand in this discussion is this theme manager
> > concept (like QStyle).
>
> ...
>
> > Why exactly do we need this level of indirection
>
> Because of this:
>
> im
On 04/12/2012 11:00 AM, ext Alan Alpert wrote:
> One thing I don't understand in this discussion is this theme manager concept
> (like QStyle).
...
> Why exactly do we need this level of indirection
Because of this:
import Widgets 1.0
As opposed to this:
//import MeeGoWidgets 1.0
//import Symbi
On Wed, 11 Apr 2012 19:25:41 ext BogDan wrote:
> >> - platform theme APIs, current APIs are good but not enough, BTW
> >>"KeyboardSchemes" enum doesn't seems to used and IMHO doesn't contain
> >>very cross platform values :). For several months I struggle to create a
> >>style plugin for Android, I
On Wednesday 11 April 2012 11:40:15 BogDan wrote:
> There is no QMenu::show, and this is the problem !:)
QMenu::show() calls QWidget::show(), which simply calls
QWidget::setVisible(true). And this one is virtual, case closed ;)
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
__
- Original Message -
> From: "morten.sor...@nokia.com"
> To: development@qt-project.org
> Cc:
> Sent: Wednesday, April 11, 2012 11:51 AM
> Subject: Re: [Development] Qt5 missing features
>
>
> On Apr 11, 2012, at 9:57 AM, ext BogDan wrote:
>
Hi Morten,
>> - platform menu APIs. Current APIs are not enough for Android platform (same
>> for Mac OSX?), I need a way to *manage* from platform plagin the menubar and
>>the context menus, meaning that Qt must show/hide the menu(bar) using the
>>platform plugin. There where two proposals [2], [
On Apr 11, 2012, at 9:57 AM, ext BogDan wrote:
> Hi Girish,
>
> I know that almost all QPA API are internal, I'm using them from the
>
> very begging :) !
>
>
>The problem is sometime if you want to create a clean API you also
>
> must to change other APIs which are public. Let me gi
w!
Cheers,
BogDan.
- Original Message -
> From: Girish Ramakrishnan
> To: BogDan
> Cc: "development@qt-project.org"
> Sent: Wednesday, April 11, 2012 12:42 AM
> Subject: Re: [Development] Qt5 missing features
>
> Hey BogDan,
>
> On Mon, Apr 9, 2012 at
On Apr 9, 2012, at 8:02 PM, ext BogDan wrote:
- platform menu APIs. Current APIs are not enough for Android platform (same
for Mac OSX?), I need a way to *manage* from platform plagin the menubar and
the context menus, meaning that Qt must show/hide the menu(bar) using the
platform plugin. Ther
On Tuesday 10 April 2012 Christoph Feck wrote:
> Instead of rushing half-baked APIs, the 5.0 release should be a solid
> base from which new and well designed APIs can be launched. The less
> APIs are included into 5.0, the lower the frustation will be when it
> is later discovered that they are il
On Apr 11, 2012, at 1:20 AM, ext Christoph Feck wrote:
> Instead of rushing half-baked APIs, the 5.0 release should be a solid
> base from which new and well designed APIs can be launched. The less
> APIs are included into 5.0, the lower the frustation will be when it
> is later discovered that
On Monday 09 April 2012 20:02:49 BogDan wrote:
> First and foremost congrats for Qt5 alpha release, it is great to
> see Qt moving forward.
> [...]
> IMHO both QML and classic widgets should use a single theme manager
> to draw the widgets, of course every single platform should be able
> to creat
Hey BogDan,
On Mon, Apr 9, 2012 at 11:02 AM, BogDan wrote:
> IMHO these features are too important to miss the opportunity to include them
> in Qt5.0.
> Kindly please consider to include these features in final Qt5.0, I don't know
> if it will be a second chance to include them without any compro
Hello,
First and foremost congrats for Qt5 alpha release, it is great to see Qt
moving forward.
Back in December I tried to merge current android port but I quickly gave up
because Qt 5 didn't seem to be too stable and it didn't had all the features
I was looking for[1], these days I briefly chec
25 matches
Mail list logo
