[Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

Michael Brasser michael.brasser at live.com
Wed Apr 30 18:04:55 CEST 2014


Hi Thomas,
If you are interested I prototyped something somewhat similar a while back, see:
https://codereview.qt-project.org/3356https://codereview.qt-project.org/3357https://codereview.qt-project.org/3358

Regards,Michael

> From: Thomas.Hartmann at digia.com
> To: Simon.Hausmann at digia.com
> Date: Wed, 30 Apr 2014 13:25:35 +0000
> CC: development at qt-project.org
> Subject: Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]
> 
> Hi,
> 
> the original idea was to get rid of the need to write Java Script to change a state (state = "newState") and find
> a declarative way to change states. The rest then came naturally.
> 
> Kind Regards,
> Thomas Hartmann
> ________________________________________
> From: Hausmann Simon
> Sent: 30 April 2014 11:38
> To: Hartmann Thomas
> Cc: development at qt-project.org; Alan Alpert
> Subject: Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]
> 
> On Wednesday 30. April 2014 11.11.39 Hartmann Thomas wrote:
> > Hi,
> >
> > > Can you elaborate a bit with an example what this means?
> >
> > Some rough ideas were discussed here:
> >
> > http://lists.qt-project.org/pipermail/development/2013-June/011572.html
> 
> Ahh, replacing arbitrarily complex "when" bindings?
> 
> That sounds like a good idea. Thanks for the explanation :)
> 
> 
> Simon
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20140430/bfb409ee/attachment.html>


More information about the Development mailing list