Re: Standard Python GUI builder?
Dietmar Schwertberger <[email protected]>
| Newsgroups | gmane.comp.python.wxglade |
|---|---|
| Message-ID | <[email protected]> |
On 28.02.2016 16:05, Igor Korot wrote: > - drop the requirement that each frame or panel has to have a sizer. >> wxPython does not require this and these sizers are absolutely >> counter-intuitive. E.g. a frame with a notebook does not need a sizer. > Yes, it does. > Because depending on the different options, you notebook might be > positioned and sized differently. Well, I can't think of a real-world example for this. When the notebook is not full page, then usually splitters are used, not sizers. Centering the structure around a use case that happens once a year is probably not a good idea. >> - structure the tool palette; have a look at Qt Designer or >> wxFormBuilder for inspiration >> - add drag and drop, cut, copy and paste to the tree view; if the GUI >> has a structure, it should be possible to edit the structure > I would argue that it is unnecessary. It is GUI RAD tool and as such you > drop everything on the GUI. However it would be nice to have Cut/Copy/Paste > from the actual GUI being designed. The lack of a structural edit tool makes it very hard to modify anything which is in sizers. Placing things on the GUI is OK for pixel-placement. But wxGlade supports only sizers, so there's a contradiction here.... Of course, for many users and simple GUIs it would be nice to have a pixel-placement mode. Regards, Dietmar ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140