[PyQt] Qt Contributors Summit

[Erik Janssens]

- my concern is that we will need to build our apps using a
  software open gl, simply to be able to use them without difficulties
  for a large user base.  and how this will impact the performance
  of remote desktop and citrix.  Unfortunately, it's not up to me to    
  dictate the users of my app to use VNC or something else.

- what I mean by QML scene assembly, is how the various 
  QDeclarativeComponents are assmbled in a QML file.

  for example in my apps I use :

  form_display = ['first_name', 'last_name', 'birthdate']

  this single line will generate me a form with all the fields
  bound to the underlying data model.

  will I be able to do the same with QDeclarativeComponents without
  going through javascript translations and QML files.

  maybe my understanding of Qt Quick is still lagging, all
  clarifications are more then welcome ?

- I agree there is certainly value in replacing the QWidgets, 
  especially the use of anchors instead of layouts.  But in our
  case the whole GUI is generated from the model, and this is
  perfectly possible with QWidgets.  It would be a large step
  back if we had to craft our GUI by hand in some kind of
  wysiwyg editor.

On Wed, 2011-06-08 at 14:46 +0300, Attila Csipa wrote:
> On Wednesday 08 June 2011 12:50:59 you wrote:
> > - the OpenGL requirement : will this still work decent through remote
> >   desktop and citrix.  imho this is important for business
> >   applications.
> 
> There is no OpenGL *requirement*. It will certainly made in a way that allows 
> extensive OpenGL optimizations (esp with Wayland and similar solutions in 
> mind). Lighthouse IIRC already has a VNC plugin, XCB (which you can tunnel), 
> this kind of shows you that remote connections are by no means in danger, the 
> only question is their speed - Qt's focus is AIUI not on that ATM, so more of 
> a 'we take patches' level.
> 
> > - QML / Qt Components : having played a bit with it, I certainly
> >   see its value, BUT, I'm afraid of having certain functionality
> >   not available through C++ and hence not through PyQt. (like
> >   assembling QML scene).
> 
> Can you be more specific ? What do you mean under QML scene assembly ? If you 
> are trying to dynamically generate QML, you're sorta doing it wrong - it only 
> sounds like you're trying to put stuff in QML that shouldn't be there (or that 
> way) in the first place.
> 
> >   for PyQt applications, I see little to no value in writing a
> >   part of the app in Javascript/QML, on the contrary, it would
> >   increase complexity.  After all we have been writing our gui in a
> >   dynamic language for years now.
> 
> I used Python+QML in a couple of experiments - my personal opinion is it's 
> way, way easier to work with QML (esp if you're willing to build your 
> components - until Nokia makes a stable release) than it ever was with QWidget 
> stuff. I would say this is a question of way of thinking - you're not writing 
> *part of the app*, you're writing the UI.
> 
> 
> Best regards,
> Attila Csipa