[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kpaint
From:       Michael Thaler <michael.thaler () ph ! tum ! de>
Date:       2003-09-09 7:31:26
[Download RAW message or body]

On Tue, Sep 09, 2003 at 03:07:31AM +0200, kde-devel-request@mail.kde.org wrote:

> The manager class does not represent the GUI in this case, it is meant has a 
> common place to hold the currently selected tool and manage instances of the 
> tools.  See the state and flyweight design patterns for more info.

You are right. I now understand how it works. One question comes to
mind: I want to change the manager class, so that it opens a config
dialog if the user double-clicks on the tool. However, with
KRadioAction this does not work because there is only the signal
activated. And the user double-clicks on the tool, the sighnal is
only sent once (which makes perfect sense).

I think it should be possible to use KWidgetAction and plug in
QPushButtons. Then one also has to set a ButtonGroup and set the
buttons to toggle-buttons. (I did not try yet). The disadvantage is
that these actions cannot be plugged into menus and so a second set of
actions for the menus has to be created.

Another way would be to create a toolbar object and plugin the buttons
without using XMLGUI, like it is done in karbon.

Are there any suggestions how this is done correctly? Are there any
other ways how to do this?

> I don't know what GPaint is, obviously it affiliated with gnome, but I don't 

It's the Gnome Paint program. It's similar to KPaint. It has some
functionality KPaint does not have and lacks some of KPaints
functionality. It's not that great.

> > It would be nice if you can give me some hints how to setup a Makefile
> > so that I can get started. I think I will set up my own CVS version,
> > because I don't know if I get my inteded changes working and I don't
> > know how much time I find for that. And I do not want to work on an
> > official KDE application right now:-)
> 
> Guess that rules out Krita :)

At least as long as I am not a little bit more familiar with qt and
kde. I looked at the Karbon Code because I wanted to know how they do
there UI and I think the KOffice code is really too complex for me...

I also ripped out the icons from karbon and coppied it to kpaint and I
intend to paint the missing one's, because karbon's icons really look
nicer. 

Take care,
Michael
-- 
We shall not cease from exploration, and the end of all our exploring 
will be to arrive where we started and know the place for the first time.

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]