Hi, On Jan 19, 2011, at 2:21 PM, ext tbp wrote:
> On Tue, Jan 18, 2011 at 11:04 PM, Andre Poenitz > <[email protected]> wrote: >> I am afraid you have to go through the process outlined >> at http://qt.gitorious.org/qt/pages/QtContributionGuidelines. >> >> Most of that process is one-time only, so it's not as scary >> as it looks on first sight. > I thank you for taking the time to review. > Once one knows where to poke & prod, such code is trivial; i realize > i've miserably failed to ask the right questions, plus it was a major > tactical error to even mention coding conventions. > > Warm thread reset. > > The left dock/pane is not only getting prettier & fancier by each > release but also thicker. To put that into the right dimensions: Since 1.0.0 the "left pane" has grown by 2 pixels (I've checked). Status bar, menu bar and the bar below the menu bar haven't changed size at all. > That's part of a general trend where screen > estate devoted to code (one would argue that is the primary purpose) > keeps on shrinking for various reasons. It annoys me to no end, that > much is obvious, but that's a very personal opinion. > > What form of optional diet would be deemed acceptable for inclusion? > [ ] status bar > [ ] menu bar > [ ] left pane (perhaps making it dynamic to mimic other IDE? i don't > like the idea very much but...) I've nothing against optionally hiding any of these in principle, but care needs to be taken (at least) of: * what to do with progress indicators if the "left pane" is hidden * what happens to the target popup if the "left pane" is hidden * how to show the Locator if the status bar is hidden (doesn't need to always be visible, but needs to be become visible when triggered) * how to get the menu bar back using non-keyboard means when it was hidden IMO a patch for hiding any of the parts above would need to answer/implement solutions to their corresponding questions as well, before being considered for Qt Creator upstream. Br, Eike > Pushing my luck i would even dare to ask if making those options more > persistent (perhaps also triggered by entering, ie, fullscreen mode) > is negotiable. > > Because, frankly, i'm certainly not going to bother jumping through > that many hoops if chances to land it, one way or another, are slim to > none: my crude patch is good enough for me as-is. > >> Do you mean you want to be able to select a widget in a running >> application and examine the data of the widget including parents and >> children? That works again (as of yesterday or so ;-}) using the >> "Select Widget to Watch" entry in the context menu of the Locals and >> Watchers view. > Ah. Thanks. Then all i need is a time machine :) > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt-creator -- Eike Ziller Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
