-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login


Sponsoring


-
- Content .- Fans  .- Knowledge Base  . 

KFormDesigner

   0.3.2  

KDE Development Tool

Score 79%
KFormDesigner
zoom


KFormDesigner
zoom


KFormDesigner
zoom


Link:  Link
Depends on  KDE 3.1.x
Downloads:  3966
Submitted:  Jul 29 2004
Updated:  May 14 2005

Description:

KFormDesigner is meant to be Qt Designer replacement for KDE. It provides almost all Qt Designer features (except code entering) and uses Qt Designer UI file format. It also has new features, such as editing widget contents inside forms, without dialogs, or dynamic resizing of widgets to fit its contents when you edit it.

Being a KPart, it can be used eg inside Konqueror (or with any app that supports KParts) to view UI files.

One can extend it by writing plugins (called factories) to manage more widgets, and control a lot of things about this widget (editing, menu items, shown properties, etc.).

It is developed inside Kexi Project (http://kde-apps.org/content/show.php?content=12365).
So if you have installed Kexi, you already have KFormDesigner. The version inside Kexi is always the more up-to-date.

**** About installation ******
If kformdesigner don't appear in your path after installation, try running './configure --prefix=your_kde_prefix'. To know your kde prefix, run kde_config --prefix.

**** About KDevelop Plugin ****
It is not compiled by default. If you want to compile it, 'cd kdevdesigner_plugin' and then 'make', etc.
To make it appear in KDevelop, you have to modify your kde file associations after installing. In the 'Embedded' tab, make 'Form Designer KDevelop Plugin' first in the list. It should then appear in KDevelop instead of Qt Designer.



Please let me know if you have made a binary package of KFormDesigner, I'll add a link in this page.




Changelog:

**** v0.3.2 10/28/2004 ****************
* Support for sub forms, ie form embedded inside another form. By now, you have to enter .ui file path manually, but a dialog will soon appear (when new property editor will be finished)
* New actions: "Select All", "Clear Contents"
* Major code cleanup
* Other fixes and improvements

**** v0.3.1 08/27/2004 ****************
* Added a KDevelop plugin (in kdevdesigner_plugin)
* Fixed all actions activation, including undo/redo actions.
* Some fixes in Connection Dialog by Jaroslaw Staniek .
* New 'Unique Form Mode': only one form is shown at a time
* User can save the form when closing it
* Undo/Redo menu item now also have command name
* Renamed libs and files
* Some other fixes

**** v0.3 07/31/2004 ****************
* KFormDesigner is now a KPart.
This will allow its integration into KDevelop (which is just a matter of days) and Kommander.
It also allow KFormDesigner to embed eg in Konqueror to preview UI files.
* Added needed icons in tarball
* Some little fixes

**** v0.2 07/29/2004 ****************
* First standalone version




LicenseLGPL
(Source code)
(Mandrake 10 RPM)
Send to a friend
Subscribe
Other  Apps  from cpasteur
Report inappropriate content



goto page:  1  2 

-
.

 Very good

 
 by Sebien on: Jul 30 2004
 
Score 50%

Butifull work !

But QT4 was means (as one of its goals) to make QTDesigner integratable in KDevelop (for example) and other tools...

Why fork a new one instead of wait for that ?

Because it can use KDE icons and technologies ? Good point, but have you discussed with QT to make it easy to intergrate KDE technology and change icons instead of "re-make the wheel" (better, as I can see) ?


Reply to this

-
.

 Re: Very good

 
 by anonymous on: Jul 30 2004
 
Score 50%

oeBiFQQTMbwk
Home

I'd completely agree on that. Why inventing the wheel a second time?


Reply to this

-

 Re: Very good

 
 by cpasteur on: Jul 30 2004
 
Score 50%

Thank you very much.

As a short answer, I would say because Qt Designer is not good enough, at least at code level. Ever tried to read (and understand) its code?

First, KFormDesigner is the form plugin in Kexi, and we couldn't wait for Qt4 Designer to be released (not before 2005). And who knows when KDE 4.0 will be out?

We also wanted to make something not only for developers, but also for users who don't know anything about Qt.
So we could have started a QT Designer fork, but imho this software really has a bad design and lot of hardcoded stuff. And there are some mistakes that could have been avoided easily (cannot move widgets inside layout, very limited factories...)

So we decided to start our own form designer, which would have a better design, with the fewer widget specific code in core and also new features missing in Qt Designer.

It will be a second form designer for KDE, which will also integrate into KDevelop and stay compatible with Qt Designer. Imho, it is not a bad thing for the user, as the competition will improve both apps, and give users the choice.


Reply to this

-
.

 thomas12777

 
 by thomas12777 on: Jul 30 2004
 
Score 50%

errr... don't get me wrong, but i never had any problems to understand the qt designer code (reading itself isn't a big deal since i mastered elementary school :)
could you just give a simple example how to create messy code?
(e.g. click here, group there voila!)

Thanks


Reply to this

-

 Re: Very good

 
 by cpasteur on: Jul 30 2004
 
Score 50%

I'm not talking about the UI files generated by Qt Designer or the code generated by uic. There's no problem with both.
I'm talking about Qt Designer source code, which is imho a real mess, badly designed and hard to read.


Reply to this

-
.

 Re: thomas12777

 
 by jstaniek on: Jul 31 2004
 
Score 50%

I can add here some examples of whynon-developers can be cofused with QtDesigner (as a component for creating simple forms):

- Class names: "Q" prefix is not necessary unless you know you develoiping with Qt Framework

- Redundancy in widgets set: eg. QPushButton and KPushButton: why anybody should care what to choose? KDE user will, undoubtely, pick a KPushButton, as well as savvy KDE developer

- Menu/actions system: KDE has KXMLGUI framework, KActions, Human Interface guidelines. Icons are most often provided by factories instead of embedding in .ui files.

- Adding a code: KJSEmbed and Python are coming into standard KDE toolset. QtDesigner prefers C++ way of doing things (and even QSA is only for extending apps functionality).


regards,
Jaroslaw Staniek / Kexi Team

Reply to this

-
.

 Re: Re: Very good

 
 by Sebien on: Jul 30 2004
 
Score 50%

OK.

I then wish you a good time with this project.

Since KFormDesigner is a KDE porject I would prefer it over QtDesigner (more beatifull, and KDE integrated).

Have you planned (ie. call the mainteners/programers) to integrate it / make it integratable into Kommander ?
Would be very good...


Reply to this

-

 Re: Re: Re: Very good

 
 by cpasteur on: Jul 30 2004
 
Score 50%

I haven't talked yet to Kommander developers, but I may do it soon.

This could be a good idea, but this would require some work, as Kommander is a fork of Qt Designer, that adds scripting possibilities.


Reply to this

-
.

 Re: Re: Re: Re: Very

 
 by Sebien on: Jul 31 2004
 
Score 50%

But it would be consistent over all KDE.
And KDE then would have *one* library to make/edit dialogs, as it has one editor: KatePart (which is very well too).

OK a fork is good (especially this one) but a lot aren't very good, for me.


Reply to this

-

 Re: Re: Re: Re: Re: Very

 
 by cpasteur on: Jul 31 2004
 
Score 50%

I've sent a to Kommander-devel mailing list. They're very interested in using KFormDesigner, they had already thought about it.
But they have a lot of work right now with kde3.3, so they won't use KFD until KDE4.0. (see there http://momo.creolmail.org/pipermail/kommander-devel/2004-July/thread.html)

So KFormDesigner will soon be used in Kexi, KDevelop and Kommander, as a standard in KDE.


Reply to this

-
.

 Re: Re: Re: Re: Re:

 
 by Sebien on: Jul 31 2004
 
Score 50%

> But they have a lot of work right now with kde3.3, so they won't use KFD until KDE4.0.

It's comprehensible !

Good news to now have a std FormDesigner :)

Keep up the good work.
@+



-
.

 Re: Re: Re: Re: Re:

 
 by jstaniek on: Jul 31 2004
 
Score 50%

One correction: KFD is not a fork of Qt Designer. KFD is an fully original work with no code taken from Qt Designer. Thus, it was possible to release it under Library GNU Public License (not GPL). LGPL is a standard license for KDE components.


regards,
Jaroslaw Staniek / Kexi Team

Reply to this

-

 Re: Very good

 
 by adymo on: Jul 31 2004
 
Score 50%

KDevelop can't wait for Qt4 too. That's why we have our own Qt Designer fork (kdevdesigner) which integrates with KDevelop and that's why we are very interested in KFormDesigner progress. I think KFormDesigner integration with KDevelop will happen very soon (it's just the matter of implementing KInterfaceDesigner::Designer interface).


Reply to this

-

 Can't install (SuSE)

 
 by robamler on: Aug 19 2004
 
Score 50%

This application looks really great, but unfortunately I can't install it on my SuSE 9.1 system. I ran "./configure", "make", "su" and "make install" and no error occured. But when I then tried to run "kformdesigner", bash couldn't find this application. So I added "/usr/local/kde/share/apps/kfd_part" and "/usr/local/kde/share/apps/kformdesigner/" to my path. When I now run "kformdesigner", I get:

kformdesigner: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file kfd_mainwindow.rc

And an error-window pops up, saying:

"Could not find the KFormDesigner part. Please check your installation."

Running "kformdesigner" as root doesn't help either.

Please excuse me if I'm just asking a dump question, but I couldn't find an answer anywhere on the web. Further, I couldn't find any compiled package of kformdesigner for SuSE (I only found some for Mandrake). If somebody has found a SuSE-rpm, please inform me.

Thanks a lot.


Reply to this

-

 Re: Can't install (SuSE)

 
 by cpasteur on: Aug 19 2004
 
Score 50%

The problem seems to be that you didn't installed it in the good directory. You should check where other apps are installed, which imho is not in /usr/local/ (the default), but in /usr/local/kde.
Try running './configure --prefix=/usr/local/kde' and 'make install' again. This should solve your problem.


Reply to this

-

 Re: Re: Can't install (SuSE)

 
 by robamler on: Aug 20 2004
 
Score 50%

Thank you for your help. I finally managed the installation by choosing "/opt/kde3" as prefix. So, to all "SuSE 9.1 Personal"-users that may read this post: type "./configure --prefix=/opt/kde3".


Reply to this

-
.

 Re: Re: Re: Can't in

 
 by jstaniek on: Aug 21 2004
 
Score 50%

To all SuSE users: All version of this distro have /opt/kde3 prefix for KDE3.

To all users: run:

kde-config --prefix

..to see what your prefix really is :)


regards,
Jaroslaw Staniek / Kexi Team

Reply to this

-
.

 very nice

 
 by soulrebel on: Aug 31 2004
 
Score 50%

looks great. i think its great to see a new qt-designer! being dependant on commercially developed software always sucks (doesnt matter if its open source or not), and i'd always prefer the community based app. i hope trolltech goes bankrupt some time after qt4.0 and the community takes over ;) . well maybe not, but i seriously think we should get independant of those companies sooner or later, and substituting their software with new community based software is the first step. thank you! ;)
i havent tested kformdesigner yet, but can you tell me whether it makes the uis the kde or the qt way (i dont know whether there is a difference really but there is kde widgets and qt widgets and qt projects and kde projects)? i am working on x-platform qt apps, just wanted to ask if that matters.
dont wanto realise that after couple of weeks of work the app wont compile on windoze anymore...
thanks


Reply to this

-

 Re: very nice

 
 by cpasteur on: Aug 31 2004
 
Score 50%

Being part of Koffice, and so of the KDE project, KFormDesigner uses by default KDE widgets.
The file format used is compatible with Qt Designer, so it would be easy to add an option to use only Qt widgets. However, that's not one of my priorities. If you wan't do it, you're of course invited to do it.


Reply to this

-
.

 Support Custom UI

 
 by gsbarbieri on: Sep 1 2004
 
Score 50%

Could you please improve the support for external widgets?

Maybe the hand-coded widgets is hard to to, but I don't see why can't I just specify the widget .ui and it will embedded it in the editing document, so it'll be a full WYSIWYG UI editor.

Gustavo


Reply to this

-

 Re: Support Custom UI

 
 by cpasteur on: Sep 1 2004
 
Score 50%

I don't really understand your questions. Are you talking about custom widgets (ie not QT nor KDE widgets)? Or are you talking about subforms, ie embedding a form (so a ui file) inside another form?

Loading widgets as you said by just giving a class name is afaik really hard to do, or even impossible.

Sub forms could be done easily (there are already subforms in Kexi).


Reply to this

-
.

 Re: Re: Support Cust

 
 by gsbarbieri on: Sep 2 2004
 
Score 50%

I was talking about sub forms as new widgets.

I agree that using a new hand-crafted widget (using direct paint for example) is hard.

But having the possibility to use forms in other .ui file as components for other forms are a great feature!


Reply to this

-

 Re: Re: Re: Support Cust

 
 by cpasteur on: Sep 4 2004
 
Score 50%

The version of KFormDesigner in KDE CVS (so inside Kexi) now supports subforms as Kexi do, and so outperforms Qt Designer even more now.

This will be included in the next release I'll make here.


Reply to this

-

 i like it

 
 by code on: Oct 30 2004
 
Score 50%

i like your program, but can you make a feature where you can show the code it would generate? you have Preview Form, can't you make a Preview Source too?


Reply to this

-

 Re: i like it

 
 by cpasteur on: Oct 30 2004
 
Score 50%

Implementing this feature would not be very difficult, however, I doesn't really see the interest..
And, are you talking of the .ui file source, or of the code generated by uic form the ui file?


Reply to this

-

 great stuff

 
 by mobtek on: Jan 12 2005
 
Score 50%

this is great stuff, keep up the good work! I was getting annoyed with QtDesigner :)

cheers PetevdM


Reply to this

goto page:  1  2 

Add commentBack






-
-
Do you like or dislike Ubuntu Unity?
 Yes, unity is alien technology!
 It is less confusing than Gnome 3 default, shell.
 Granny thinks it is much more usable than Gnome 2
 Canonical is embarrasing itself with this split project
 Gnome 3 default shell is much better
 I dislike Unity, Gnome 3 default shell is alien technology!
 None of the above, I like the 2Gb for free and Apple alike behavior. Will post a comment instead

resultmore
 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Apps
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
Events RSS   

Participate
Groups
Forum
Add App
Public API
About KDE-Apps.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2003-2014 KDE-Apps.org Team  
All rights reserved. KDE-Apps.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.