| Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 9 | |
<<< text/html: EXCLUDED >>>
Helen Muller <helen20020918@yahoo.co.uk> writes: > Hi, Qt people, > > I'm using Qt 3.03 on red hat 7.3. I want to reuse some Dialog interfaces built on Qt 1.45. Those dialog > files are in form of *.kdevdlg. I don't know how to correctly open them under Qt Designer 3. As my > understanding of Qt documents, I have to transfer *.kdevdlg files to *.ui form. Or there is no way to > reuse these dialog interface, I have to build again? I don't know the .kdevdlg file type, but to me it sounds more like a KDE developer dialog file (maybe I am wrong). The reason that also makes me think so is that AFAIK Qt designer was not implemented for Qt 1.45. Are you 100% sure that kdevdlg files are Qt 1.45 Designer files ? Exactly what documentation (a specific URL) do you refer to ? > > Regards, > > Qt Learner You don't wanna call yourself that. Another member on the list uses this alias, and you don't want to be mixed up with him. Jarl
<<< text/html: EXCLUDED >>>
Helen Muller <helen20020918@yahoo.co.uk> writes: > That *.kdevdlg is actually called Qt/KDE Dialog file. I checked the original project, it > was implemented under Kde1.2/Qt1.45. What exactly is "the original project" ? Is it implemented in KDE1.2 ? or Qt1.45 ?, i.e. is it implemented by the KDE developers ? or by trolltech developers ?. > In this enviroment, when you click "View->Dialog Editor" In what environment? In what application do you click that? > a "KDevelop Dialog Editor" window appears. If you choose to generate Qt/KDE Dialog, a kdevdlg file is > named and saved, then an empty dialog form will be in the right half of the window... It sounds almost > the same as Qt Designer 3, exept the extend name of the dialog file. It may sound like Qt Designer 3, but if you read the manual for Borland JBuilder or any other gui IDE, that manual will probably also sound like Qt Designer 3. Please answer my questions above, and I will try to straighten things out for you. > > When I tried to see the kdevdlg file under KDE2.1/Qt3 , there is no > from displayed, only some texts. Qt Designer 3 doesn't support to > open this file, With what application did you try to "see" it? and with what intentions did you try to see it? What do you mean by "there is no from displayed" ? > > Since I'd like to reuse the kdevdlg files, in fact those dialog > interfaces, is it possible to recovery the form? Well. I told you already, I don't know the origin of these files. so when you have described how you ended up having those files in the first place, I may be able to help you? > > I didn't find exact documents that explains kdevdlg files. In "Qt3.0 > changes", it writes about *.pro file. I tried to generate a pro > file, then open it. but I haven't work out the pro file yet. > > Helen > > P.S. I saw many mail titles sent by or related with Qt Learner, > then I guess it's a popular and modest way to ask question. Actually > I didn't read every mail. If you actually read his emails, you would be ashame trying to adopt his behaviour. He is (in my opinion) on big anoyance on this list. Jarl
Am Mittwoch, 25. September 2002 15:42 schrieb Helen Muller: > Hi, Qt people, > > I'm using Qt 3.03 on red hat 7.3. I want to reuse some Dialog interfaces > built on Qt 1.45. Those dialog files are in form of *.kdevdlg. I don't know > how to correctly open them under Qt Designer 3. As my understanding of Qt > documents, I have to transfer *.kdevdlg files to *.ui form. Or there is no > way to reuse these dialog interface, I have to build again? I don't know about QT1.45 but read the KDevelop Manual Chapter 12. There is described how to use ui files generated with QDesigner in your KDevelop projects. Regards Michael
> I'm using Qt 3.03 on red hat 7.3. I want to reuse some Dialog interfaces > built on Qt 1.45. Those dialog files are in form of *.kdevdlg. I don't know > how to correctly open them under Qt Designer 3. As my understanding of Qt > documents, I have to transfer *.kdevdlg files to *.ui form. Or there is no > way to reuse these dialog interface, I have to build again? KDevelop used its own dialog editor when it was still using Qt1: when Qt didn't provide any dialog editor of its own. That was about 3 years ago IIRC. Since Qt2, Qt provides its own dialog editor (designer) and kdevelop has dropped that functionality. You're right that you'd have to convert kdevdlg files to ui form, but I don't think there's any existing converter for it. But try at least searching for it in the search engines -- I didn't so you may be lucky. My best bet is that you should recreate the dialogs in Qt Designer and just drop the kdevdlg files. If you want to visualize those files, you must get your hands on Qt 1.45 library and use it to compile kde 1 libraries as well as kdevelop 1.0 or 1.1 (dunno exactly which one). Or you may use precompiled kde1 and qt1 compatibility libraries and just compile that early kdevelop version. Then use that kdevelop to open them. Otherwise, you may be able to just read them in any text editor and try to decipher the widget names and their nesting. Again, the kdevelop for kde2 and kde3 doesn't support those early dialog files AFAIK. Cheers, Kuba Ober PS. Don't use "Qt Learner" alias. The original Qt Learner was at the very beginning of the learning curve and asked many basic questions which are explained in readily available materials (like Qt documentation and examples). And it seems he/she never looked into the Qt sources which are provided with a purpose :_) So his alias reminisces of not exactly perfect experience the list had with him/her.
<<< text/html: EXCLUDED >>>
>> You're right that you'd have to convert kdevdlg files to ui form, but I >> don't think there's any existing converter for it. But try at least >> searching for it in the search engines -- I didn't so you may be lucky. > I think I have found the answer. Thanks so much! > http://docs.maraudingpirates.org/kdevelop/index-8.html Wrong I was :-) Apparently those who use kdevelop most never read its manual ;-)) For benefit of others: yes, there's a script called kdevldg2ui which converts old dialog definition files (from kde1 era) to .ui files. Cheers, Kuba Ober
Hello Helen.
Please post to the mailing-list next time.
Helen Muller <helen20020918@yahoo.co.uk> writes:
>
>
> "the original project" is an application programmed by KDE1.2/Qt1.45. Now I
I suppose you mean "programmed for/on/to KDE1.2/Qt1.45", it is
probably programmed by some developers, i.e. humans.
> open this application by KDevelop 2.1. From the file treeview, there is a
> Dialogs folder including kdevdlg files. When I clicked one kdevdlg file, I
> supposed that I would see a form(dialog interface) with Buttons, LineEdit etc,
> but a text file displayed with the comments as follows:
OK, it sounds like (but you haven't stated this clear!) that you are
trying to port a KDE1.2/Qt1.45 application ("the original project") to
a non-KDE (Qt-only) Qt3 application. Is that correct? If that is
correct could you reveal the name of the project or some more
information about this project?
It sounds like kdevdlg are KDeveloper (version for KDE 1.2) dialog
files. I will now assume that kdevdlg are KDeveloper dialog files! at
least the name makes sense that way; KDEVeloper DiaLoG!
Now. The problem may be that these files may not be compatible by later
versions of KDeveloper and you shall certainly expect them to be
supported by *any* version of Qt designer.
If there is any chance that the kdevdlg files can be interpreted by
any other applications than KDeveloper for KDE1.2 I think you are
better off trying to find the answer on a KDE developer mailing list,
or by directly mailing the developer(s) of KDeveloper for
KDE1.2. While you are at it you may ask the developers of these
applications if there are any conversion utilities for kdevdlg files.
Jarl
<<< text/html: EXCLUDED >>>
Helen Muller <helen20020918@yahoo.co.uk> writes: > You're right, I should ask the KDE developer mailing list for my > question. But when I met the problem at the begining, when I'm quite > new to the Qt Designer 3, I can not generalize the problem, and > didn't realize that I sent to a wrong mailing list. That's OK, no harm done. Jarl
<<< text/html: EXCLUDED >>>