[Qt-interest] Very simple question regarding QUiLoader

[Patric]

MessageGirish@
Ah, I see. But you said that the form can be serialized, is there a method for that ? 

Tony@
Thank you for answer also, I actually decided not to use plugins, after I have read so much about plugins, I started to think if I really need them... 
I was wondering if I need QUiLoader, but maybe I don't need it either. 

So I think maybe the best choice here is just to do my UI statically. I will create different forms for the tabs and add them dynamically with QTabsWidget (it has nice methods for that). 
When there is new device out, I'll just create few more tabs and create an update package. 
It was hard to imagine the design of the product, it's hard when you don't have experience with something and don't know what it is capable of. 

Best regards, 
Patric

  ----- Original Message ----- 
  From: Tony Rietwyk 
  To: qt-interest at trolltech.com 
  Sent: Thursday, June 04, 2009 9:40 AM
  Subject: Re: [Qt-interest] Very simple question regarding QUiLoader


  Patric wrote:
    Hello, 
    my question is simple. When to use QUiLoader. 
    I think that the only difference is that at compile time, there'll not be the need of constructing the ui class (the class with the setupUi method). This is delayed for runtime. 
    I saw the examples for QUiLoader, I think they can be done without it also. If I have two forms and I want to change them in a UI, instead of loading them into widgets at runtime I always can just call "widget2.show()" instead of widget1.show(). 
    But I may be wrong. Sorry if my question is too simple or something, I'm just wondering. 

    Regards,
    Patric 
  Hi Patric, 

  I don't think you need to worry about UILoader, if you are going to use plugins to provide the tabs for each device.  The plugin interface would include something like: 

      void populateTabs(QTabWidget *parent);

  So the plugin just creates the widget for each tab and adds them.  

  Think of how printer setup dialogs are done on windows - each company provides two dlls one for the printer driver, and the second is effectively a plugin for the setup.  The user doesn't need to alter the setup screen itself, just use it.  

  When you issue a plugin for a new or updated device, it will know how to create its own widgets.  

  Hope that helps, 



  __________ Information from ESET NOD32 Antivirus, version of virus signature database 4098 (20090522) __________

  The message was checked by ESET NOD32 Antivirus.

  http://www.eset.com



------------------------------------------------------------------------------


  _______________________________________________
  Qt-interest mailing list
  Qt-interest at trolltech.com
  http://lists.trolltech.com/mailman/listinfo/qt-interest



  __________ Information from ESET NOD32 Antivirus, version of virus signature database 4098 (20090522) __________

  The message was checked by ESET NOD32 Antivirus.

  http://www.eset.com




__________ Information from ESET NOD32 Antivirus, version of virus signature database 4098 (20090522) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20090604/a62e00bc/attachment.html