Re: [OT]: Python GUI editor

Date : Mon, 7 Aug 2006 16:10:51 +0100
To : XSI(at)Softimage.COM
From : "Alan Jones" <skyphyr(at)gmail.com>
Subject : Re: [OT]: Python GUI editor
A standard tree view yes, but something custom like that there's
nothing out of the box. Though there are a lot of pieces that'd make
it easier to develop. Already classes in there for curves etc.

I'd rather tackle it with Qt than GTK or pretty much any other
framework I can think of.

Cheers,

Alan.

On 8/7/06, kim aldis <kim(at)aldis.org.uk> wrote:
Here's a question. I want to build a gui hierarchy viewer. Not a normal
treeview/folder viewer but something a bit more like the rendertree with
free-form nodes, multiple inputs, connections and stuff. Is there anything
in QT that would do that? Easily?



> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> Behalf Of Alan Jones
> Sent: 07 August 2006 15:32
> To: XSI(at)Softimage.COM
> Subject: Re: [OT]: Python GUI editor
>
> Interesting to hear about your experience, Patrick. I was sure I wasn't
> the only one ;-)
>
> Cheers,
>
> Alan.
>
> On 8/7/06, Patrick Boucher <patrickb(at)buzzimage.com> wrote:
> > Alan Jones wrote:
> > > ummmm yeah, but you only need a license if you're going to sell
> your
> > > application made with it and you don't want to GPL it.
> > >
> > > If it's just inhouse (or released sold/released under gpl) then
> > > there's no need for a license.
> > >
> > > Cheers,
> > >
> > > Alan.
> >
> > We had to make a platform choice such as this one a few months back
> > and this list was very helpful in making that decision... Any way
> here
> > was our reasoning.
> >
> > I'd done Perl/Tk and hadn't enjoyed the Tk experience all that much.
> > The second you got anywhere further that bread and butter it would
> all
> > break down.
> >
> > We had Wx (http://www.wxwidgets.org/) suggested. Had done a tiny bit
> > of it but didn't know how it would react on a large scale project.
> >
> > Qt was also suggested. At the time we were looking at QT 4.x and PyQt
> > 3.x. So the version mismatch was a bit of a pain. Knowing PyQt 4.x
> was
> > around the corner (the only piece missing for us to use Qt) and
> having
> > a bit of prior Wx experience, we went the Wx (with python bindings)
> route.
> >
> > Our in house guru here started writing the main application
> > (python/wx) while I wrote a support application on the web
> > (python/apache). He had issues with Wx while I had to code a form/UI
> > framework for the web. A few months pass... PyQt 4.x came out and I
> > gave it a try an evening. In the next three weeks we had moved all
> our
> > code to PyQt and QT and everything was working smoother and was
> simple
> > to code than it had ever been.
> >
> > The UI designer that comes with QT may not be perfect but it is _way_
> > better than anything else I have every seen. The on-the-fly compiling
> > of .ui files makes changing the UI a breeze without ever touching a
> > single line of code. The Api is highly object oriented and 'fits your
> brain'.
> >
> > As Alan said, especially if you're doing PyQt or in-house stuff, read
> > the license: you don't need to buy QT. So download it and have fun.
> > You can blame me afterwards if it doesn't work for you. If it does
> > work out, scotch is my thing.
> >
> > Cheers,
> >
> > --
> > Patrick Boucher
> > TD - Coder - Resident geek
> > Buzz Image Group
> > Tel 514.848.0579
> > Fax 514.848.6371
> >
> > www.buzzimage.com
> > www.xsi-blog.com
> > ---
> > Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
> body:
> > unsubscribe xsi
> >
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
> body:
> unsubscribe xsi
>



---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi

---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.