Kexi: kformdesigner/formeditor

Hi, what's the state of the kformdesigner these days?
We really need a report designer in kplato, and since our requirements are 
similar to kexi I wonder if using kformdesigner would be a possibility?
--

-- 
Mvh
Dag Andersen

Re: Kexi: kformdesigner/formeditor

Dag Andersen said the following, On 2007-03-02 09:45:

> Hi, what's the state of the kformdesigner these days?
> We really need a report designer in kplato, and since our requirements are 
> similar to kexi I wonder if using kformdesigner would be a possibility?

KFormDesigner is used exclusively for creating forms. There were plans to 
extend it to reports (very old initial code that reuses KFormDesigner is in 
koffice/kexi/plugins/reports/) but I guess it KOffice's text engine will be 
reuses before.

As you know, integer-based calculation of Qt3 can make printouts very 
different comparing to what you can see in the preview/design view.

For more info go to #kexi, it looks like you have to deal with tabular data 
model too, so maybe extending so Kexi's simple printouts can be a solution. 
But note, all this is still Qt3 code.

--

-- 
regards / pozdrawiam, Jaroslaw Staniek
  Sponsored by OpenOffice Polska (http://www.openoffice.com.pl/en) to work on
  Kexi & KOffice: http://www.kexi-project.org, http://www.koffice.org
  KDE3 & KDE4 Libraries for MS Windows: http://kdelibs.com, http://www.kde.org

Re: Kexi: kformdesigner/formeditor

PS: I mean simple printouts like:
http://kexi-project.org/pics/1.0/simple_printouts.png

--

-- 
regards / pozdrawiam, Jaroslaw Staniek
  Sponsored by OpenOffice Polska (http://www.openoffice.com.pl/en) to work on
  Kexi & KOffice: http://www.kexi-project.org, http://www.koffice.org
  KDE3 & KDE4 Libraries for MS Windows: http://kdelibs.com, http://www.kde.org

Re: Kexi: kformdesigner/formeditor

Fredag 02 marts 2007 11:26 skrev Jaroslaw Staniek:
> Dag Andersen said the following, On 2007-03-02 09:45:
> > Hi, what's the state of the kformdesigner these days?
> > We really need a report designer in kplato, and since our requirements
> > are similar to kexi I wonder if using kformdesigner would be a
> > possibility?
>
> KFormDesigner is used exclusively for creating forms. There were plans to
> extend it to reports (very old initial code that reuses KFormDesigner is in
> koffice/kexi/plugins/reports/) but I guess it KOffice's text engine will be
> reuses before.
I was sort of hoping it was possible to tag along to quickly get a working, 
but-not-perfect solution that eventually would end up with full koffice 
compliance :)
>
> As you know, integer-based calculation of Qt3 can make printouts very
> different comparing to what you can see in the preview/design view.
>
> For more info go to #kexi, it looks like you have to deal with tabular data
> model too, so maybe extending so Kexi's simple printouts can be a solution.
Yes most reports will be tabular.
> But note, all this is still Qt3 code.
Ok, thanks.
--

-- 
Mvh
Dag Andersen

Tablet in KOffice2

Hello fellow KOffice hackers.

Boudewijn and myself have been talking about the ideal way to handle tablets 
in KOffice. Or, better said, how to handle the fact that a user can have more 
then just a mouse.

See http://wiki.koffice.org/index.php?title=Flake/Tools_And_Pointers for the 
gory details.

Most of the essential features are implemented in KOffice trunk now.

For the people that work with a tablet and want to try this, there are some 
issues in Qt that I want to make people aware of.
* Qt4.2.2 makes us switch back to mouse as soon as the tablet leaves the 
canvas.  This means that you can't access the tool-options :(
This is fixed in 4.3-rsync already. I made a workaround for qt-copy [1]

* Qt4.2.2 basically makes it impossible to drag a shape from the 
shape-selector using the tablet input device.  Technically you get 
tabletEvents instead of DnD events.
I see that this is largely fixed in 4.3-rsync. There is some uglyness left 
that I sent a test application and a long explanation to qt-bugs for. I 
really don't want to dig into X11 and events stuff myself :)

Other then those I found no problems and trunk basically works the way we 
discussed.

Many thanks fly to Axel Jäger for the Graphire4 he sent me a couple of days 
ago, which was, and is, very useful to actually see what I'm doing!

Re: Tablet in KOffice2

On Friday 02 March 2007, Thomas Zander wrote:

> Other then those I found no problems and trunk basically works the way we
> discussed.
>
> Many thanks fly to Axel Jäger for the Graphire4 he sent me a couple of days
> ago, which was, and is, very useful to actually see what I'm doing!

Yay!

--

-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi

_______________________________________________
koffice-devel mailing list
koffice-devel <at> kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

Karbon printing problems

The short story is that this will not print correctly:

http://home.earthlink.net/~tyrerj/files/OG/ogp_open_window_logo.karbon

The long story is that this isn't a simple problem.  It appears to me 
that the error occurs when preparing the PostScript file.

Since InkScape does almost exactly the same thing, it appears that the 
problem may be with PostScript.

--

-- 
JRT

Re: Karbon printing problems

James Richard Tyrer wrote:

CORRECTION, I have tried so many things today that I have become a bit 
confused.

> The short story is that this will not print correctly:
> 
> http://home.earthlink.net/~tyrerj/files/OG/ogp_open_window_logo.karbon

Actually, the problem is that it can't be converted to a vector 
PostScript file.  If you print it with a bit map, it works.

So, with Karbon, this problem occurs when saving as EPS.
> 
> The long story is that this isn't a simple problem.  It appears to me 
> that the error occurs when preparing the PostScript file.

Normally, you would expect that when you print a vector format to 
PostScript that you would get a vector format PostScript file.  Which is 
what is needed here so that the image can be enlarged.

> Since InkScape does almost exactly the same thing, it appears that the 
> problem may be with PostScript.

Note that InkScape gives you the choice of vector or bitmap PostScript. 
  This is a good feature.  Also, it allows you to set the DPI for a 
bitmap  image.  Also a good feature.

IAC, you get exactly the same vector PostScript problem with InkScape.
> 

koffice

SVN commit 638851 by rempt:

Refactor KoCanvasController to use QAbstractScrollArea and port Krita to
the new situation. This will break every other KoCanvasBase implementation.
 Please look at http://wiki.koffice.org/index.php?title=Flake/Canvas
for the rationale behind this move and for porting tips. Krita's qpainter
canvas hasn't yet received the optimizations this move makes possible, but
those are easy now.

Also: a unittest for KoZoomHandler.

CCMAIL: koffice-devel <at> kde.org

 M  +2 -2      krita/image/kis_image.h  
 M  +1 -1      krita/image/kis_projection.cc  
 M  +0 -1      krita/ui/CMakeLists.txt  
 M  +1 -1      krita/ui/kis_abstract_canvas_widget.h  
 M  +20 -17    krita/ui/kis_canvas2.cpp  
 M  +9 -3      krita/ui/kis_canvas2.h  
 M  +1 -7      krita/ui/kis_doc2.cc  
 M  +8 -0      krita/ui/kis_opengl_canvas2.cpp  
 M  +3 -0      krita/ui/kis_opengl_canvas2.h  
 M  +29 -59    krita/ui/kis_qpainter_canvas.cpp  
 M  +2 -2      krita/ui/kis_qpainter_canvas.h  
 M  +5 -3      krita/ui/kis_shape_layer.cc  
 M  +1 -1      krita/ui/kis_shape_layer.h  
 M  +2 -2      krita/ui/kis_tool.h  
 M  +10 -7     krita/ui/kis_view2.cpp  
 M  +7 -1      krita/ui/kis_view2.h  
 D             krita/ui/kis_view_converter.cpp  

Re: koffice

On Saturday 03 March 2007 16:32, Boudewijn Rempt wrote:
> SVN commit 638851 by rempt:
>
> Refactor KoCanvasController to use QAbstractScrollArea and port Krita to
> the new situation. This will break every other KoCanvasBase implementation.
>  Please look at http://wiki.koffice.org/index.php?title=Flake/Canvas
> for the rationale behind this move and for porting tips. Krita's qpainter
> canvas hasn't yet received the optimizations this move makes possible, but
> those are easy now.

Nice work :D
I just ported KWord and I get the feeling painting is faster!

[little later]
I finished porting kword, karbon and the apps that depend on kopageapp to use 
this.
I think thats all of them :)

Cheers!
--

-- 
Thomas Zander

_______________________________________________
koffice-devel mailing list
koffice-devel <at> kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel