Version: (using KDE Devel) The New Class dialog expands long outside a 800x600 screen. Possibly other dialogs too. Cheers, Frans
This will most probably never get fixed
On Thursday 18 March 2004 14:40, Amilcar do Carmo Lucas wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=76707 > a.lucas tu-bs de changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- Component|general |cppsupport > > > > ------- Additional Comments From a.lucas tu-bs de 2004-03-18 14:40 ------- > This will most probably never get fixed Cool. Why? Frans
Will you fix it? I have no reason to, I have 1024x1280 displays. And I guess all other KDevelop developers do too.
On Friday 19 March 2004 13:29, Amilcar do Carmo Lucas wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=76707 > > > > > ------- Additional Comments From a.lucas tu-bs de 2004-03-19 13:29 ------- > Will you fix it? > > I have no reason to, I have 1024x1280 displays. And I guess all other Right, 1280x1024. > KDevelop developers do too. Well, you need to open your eyes a little. First of all, this is not my IMHO - it is what the KDE UI Guidelines says. http://developer.kde.org/documentation/standards/kde/style/basics/windows.html#win_size That means it has been discussed and agreed upon. And that's why people demand KDE applications to follow it and knock developers on the head with it if they do not. I can explain why the guidelines says so. There is a lot of users who run 800x600. Don't have the "it works for me, and those who don't like it can STFU and go somewhere else"-mentality one sometimes stumbles over in open source development. One of the reasons to why I am into open source is it leverages technology so everyone can enjoy the benefits with technology without having to live up to certain criteria, for example economical. Developing countries, or simply just non-programmers don't necessarily have two large monitors in multihead configuration. Leaving out 800x600 means leaving out users. I think it can be wise to talk to your belly button: When KDevelop can't run in 800x600 it locks out users, contributors, supporters etc. The same applies for KDE which KDevelop is a large part of. In the end, some other software instead of KDevelop/KDE is chosen. Remember, there is (apparently) a lot of 800x600 users, and especially in the areas where open source is currently expanding. And it's not only about being possible to run in a certain resolution. It is in general preferred to have small windows - it means more flexibility, does not consume as much space exposes much information in one go for example. BTW, it expands outside 1024x768 too. You may very well put it on your TODO as I just have done, but don't say "it doesn't matter", or "perhaps it does matter but not for Me" because it is either plain wrong or morally doubtable. Frans
CVS commit by aclu: Maid the Layout a bit better for users with small screens. Don't be fooled by the first line of the diff, the heigth actually got smaller! CCMAIL: 76707@bugs.kde.org M +1 -19 cppnewclassdlgbase.ui 1.31 --- kdevelop/languages/cpp/cppnewclassdlgbase.ui #1.30:1.31 @@ -10,5 +10,5 @@ <y>0</y> <width>510</width> - <height>610</height> + <height>698</height> </rect> </property> @@ -381,21 +381,4 @@ </property> </widget> - <spacer row="6" column="0"> - <property name="name"> - <cstring>spacer13</cstring> - </property> - <property name="orientation"> - <enum>Vertical</enum> - </property> - <property name="sizeType"> - <enum>Expanding</enum> - </property> - <property name="sizeHint"> - <size> - <width>20</width> - <height>16</height> - </size> - </property> - </spacer> <widget class="KLineEdit" row="0" column="1"> <property name="name"> @@ -1289,5 +1272,4 @@ <includehints> <includehint>klineedit.h</includehint> - <includehint>klineedit.h</includehint> <includehint>classgeneratorconfig.h</includehint> </includehints>
I agree 100% with you. But I did not code that dialog. I just expressed my point of view that the developer that coded that dialog will most probably not fix it. We (developers) already provide you (users) with KDevelop. Could you help out a little bit also?
On Friday 19 March 2004 17:43, Amilcar do Carmo Lucas wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=76707 > > > > > ------- Additional Comments From a.lucas tu-bs de 2004-03-19 17:43 ------- > I agree 100% with you. > But I did not code that dialog. > > I just expressed my point of view that the developer that coded that dialog > will most probably not fix it. > > We (developers) already provide you (users) with KDevelop. Could you help > out a little bit also? I'm doing some KCM stuff ATM, but I have put it on my TODO. Cheers, Frans
CVS commit by dymo: Advanced subclassing option in C++ New Class Wizard can be used for classes in the persistant class store. This means that if the PCS for Qt library is built then advanced subclassing from Qt classes is possible in the wizard. PS: at last i've implemented that, i have been missing this feature from the times of kdevelop 3.0.0 alpha3 ;) Also some bugfixes (in this and previous commits): BUG: 69524 BUG: 76707 BUG: 92047 M +2 -2 cppnewclassdlg.cpp 1.58 M +52 -4 storeconverter.cpp 1.2 M +4 -0 storeconverter.h 1.2