Don't do it. Really -- don't do write a book. I did. I had a pretty nice sideline writing articles for DDJ, InformIT and similar, each bringing in between $400 and $1000 -- and then I got uppity and wrote a book (http://valdyas.org/python/index.html). Total income for about a year of working every evening and all weekends, ~ $400. Books don't pay, are a lot of work and you'll be badgered for years by impecunious students for free paper copies, because you're a rich author and the e-copy is so inconvenient.
Is Stefan Gehn actually a kmail developer? I don't see him in the authors list and a quick google associates him with kde multimedia, not kdepim. Anyone with an account can comment in bugzilla, but isn't necessarily authoritative.
I know it's true... I recently bought the advance reader's copy of 1634: the baltic war for $15,-- and discovered that over the past few years I've spent about a hundred dollars buying electronic books from Baen. And I've bought a couple of hardbacks, too. Just because I discovered in their free library that among the really sicko Baen authors like John Ringo there are a couple of authors that can be counted on to produce a Good Read.
And -- that hundred dollars is pure profit for Baen -- no paper costs, no distribution costs -- and a happy customer.
There's no "KDE" font system. Your problem with bitmapped fonts is with Ubuntu: it disables bitmapped fonts by default (otherwise you're going to see quite a few websites show up in grainy, pixely helvetica). The solution is to drop down to konsole level and run sudo dpkg-reconfigure fontconfig and enable bitmap fonts.
1) No, the ui hasn't been "fixed" -- in 2.0 it'll be possible to drag & drop the palettes in different constellations (Qt4 provides that out of the box). And, in 2.0, you'll have only see the palettes that belong to the active view, but that's all. I like it this way and it's the standard for KOffice. There are people who like it, there are people who hate it, but I think spending development time on making it possible to accommodate both preferences is not worth it compared to features like better filters, speed improvements and so on.
2) It should be pretty good, we spent a lot of time making it possible to draw with different pressure curves for darkness, size and opacity. It is also possible to have a different current tool for your mouse, eraser and stylus (I tend to draw with the mouse set to pan and the stylus to brush). Oh, and the "paint directly checkbox" should fix your issues with the brush tool.
3) Gimp and Krita use the same gradients, patterns and brushes. File format exchange is problematic, hence the OpenRaster effort that is being spearheaded by Cyrille Berger for Krita and Oyvind Kolas for Gegl.
I strongly suspect the version you tried was 1.4. When I see screenshots of that version in magazines, I tend to want to hide under the table. We've made a lot of progress in the past year and a half:-)
Basically, long before my involvement, KImageShop was started as a Gimp alternative because of hurt feelings over the Kimp demo hack. That was in 1999. When I bought a wacom pad in 2003 I wanted to hack on something to do natural painting and not start my own thing. So I looked around and the Krita codebase had a couple of advantages for me:
* C++, not C (I knew Java, so C++ was easier for me) * I already knew Qt (I wrote the book on PyQt) * Much smaller codebase than the gimp * lots to do (basically only the move tool worked in 2003) * helpful maintainer (Patrick Julien basically taught me C++)
Hm, if you cannot assign a different tool to the eraser tip of your stylus than to the pen tip something went wrong somewhere. We spent a lot of time making sure that every pointing device can have its own tool.
Boudewijn Rempt Krita Maintainer
Re:Yes: I, a KDE fan, can't use KWord: no Word imp
on
KOffice 1.6 Released
·
· Score: 1
It's mostly the same code. KWord and Abiword used to collaborate on a.doc import library. At a certain point we agreed to a version 2 of that library. However, only KWord actually started using it, while Abiword decided to continue with version 1. No doubt we all had our good reasons, but it's a bit sad nonetheless. The WordPerfect import library is more succesful: that is shared between OO, Abiword and KWord.
Re:Openoffice draining KOffice (Hurd effect)
on
KOffice 1.6 Released
·
· Score: 1
The KOffice applications are GPL, the shared libraries are LGPL.
Re:Openoffice draining KOffice (Hurd effect)
on
KOffice 1.6 Released
·
· Score: 2, Insightful
Well, actually, OpenOffice is mostly written in a primordial dialect of C++, comes with its own widget set (that can render using gtk or Qt) and a lot more. GTK nor Qt existed when the StarOffice people started writing their software.
Well, that's nonsense in two ways: any windows application should run under wine, whether it uses opengl or not, whether it uses Qt or not. But most importantly, if this is a Qt/OpenGL application, having it run on X11 and OS X is just a matter of compiling the thing for X11 and OS X. That's what Qt's for...
Well, firstly, you're looking at the old 1.4 version of Krita, not 1.5. In 1.5 the filter menu has been reorganized, filters have been added, and we've added a very nice filters gallery dialog that I personally always use.
Secondly, I'm not a "they", I'm a "you" -- if you've got suggestions for improvement, why not drop by on #koffice, or kimageshop@kde.org, or even mail me personally and discuss your suggestions.
If you can manage to refrain from trite phrases like "lost in the bloat" and "I will stop using it if you don't do what I want", then you will stand a very good chance of being listened to.
Boudewijn Rempt, Krita maintainer
If you've got a crash, please, please, please report it! Just mail me (that's the maintainer). If it's something complicated I may ask you to file a bug report, but most crashes I can solve very quickly. That is, if you're using the recently released beta. So much has changed since 1.4.2 that reports on that version aren't any use anymore.
In any case, my big problem when developing Krita is exactly this: developers cannot crash-test the app they develop because instinctively they know how the software is supposed to work. I'm relying on people testing the beta's and the release candidates to report me their crashes and problems.
About the slowness: we haven't tried to optimize anything yet. The OpenGL backend is quite a bit faster than the plain X11 backend, so if you can use hardware accelerated OpenGL use that.
No, I'm not claiming anything about retraining costs. I'm claiming that when discussing free graphics applications on Linux, the Gimp isn't the only option anymore. That's all. As Novell recognized: there's the Gimp, Krita and Pixel now -- and Photoshop under wine, but my experiences with that aren't very good. There's some weird bug where I can only paint straight lines...
Oh, and for your collection of Photoshop files: you're chained to Adobe for as long as you value those. You'll never be able to use free software to edit those, you've been caught in the trap. Sure, there was no alternative, I guess, but you've been trapped nonetheless.
Because from Photoshop 7.0 the file format has been closed and it's not possible to get information about it without signing and NDA and promising never ever to build something Photoshop compatible that's not commercial and closed source.
What I should do, of course, is finally begin on that OASIS spec for layered raster images that people have been bugging me about. But I've got a release to get ready first...
Yeah, we know... The name isn't all that great. So what? I didn't invent it. And it's got quite a bit of recognition by now. Wouldn't know whether it would be wise to change it at this point in the game.
But tell me... How is a spreadsheet or a wordprocessor relevant when discussing graphics applications? In any case, all applications in KOffice 1.5 are a lot better than they were in 1.4.
Slashdot Mirror
Actually, thanks to http://doc.trolltech.com/4.4/license-gpl-exceptions.html, there were no licensing incompatibilities with Qt and the Apache license.
Don't do it. Really -- don't do write a book. I did. I had a pretty nice sideline writing articles for DDJ, InformIT and similar, each bringing in between $400 and $1000 -- and then I got uppity and wrote a book (http://valdyas.org/python/index.html). Total income for about a year of working every evening and all weekends, ~ $400. Books don't pay, are a lot of work and you'll be badgered for years by impecunious students for free paper copies, because you're a rich author and the e-copy is so inconvenient.
Is Stefan Gehn actually a kmail developer? I don't see him in the authors list and a quick google associates him with kde multimedia, not kdepim. Anyone with an account can comment in bugzilla, but isn't necessarily authoritative.
I wouldnt'be able to live if konsole grabbed alt-n -- I need those keycombinations for screen :-). Shift-arrow works fine for me.
In 11, it's definitely there.
I know it's true... I recently bought the advance reader's copy of 1634: the baltic war for $15,-- and discovered that over the past few years I've spent about a hundred dollars buying electronic books from Baen. And I've bought a couple of hardbacks, too. Just because I discovered in their free library that among the really sicko Baen authors like John Ringo there are a couple of authors that can be counted on to produce a Good Read.
And -- that hundred dollars is pure profit for Baen -- no paper costs, no distribution costs -- and a happy customer.
There's no "KDE" font system. Your problem with bitmapped fonts is with Ubuntu: it disables bitmapped fonts by default (otherwise you're going to see quite a few websites show up in grainy, pixely helvetica). The solution is to drop down to konsole level and run sudo dpkg-reconfigure fontconfig and enable bitmap fonts.
Er, does IE come with a warranty nowadays?
1) No, the ui hasn't been "fixed" -- in 2.0 it'll be possible to drag & drop the palettes in different constellations (Qt4 provides that out of the box). And, in 2.0, you'll have only see the palettes that belong to the active view, but that's all. I like it this way and it's the standard for KOffice. There are people who like it, there are people who hate it, but I think spending development time on making it possible to accommodate both preferences is not worth it compared to features like better filters, speed improvements and so on.
2) It should be pretty good, we spent a lot of time making it possible to draw with different pressure curves for darkness, size and opacity. It is also possible to have a different current tool for your mouse, eraser and stylus (I tend to draw with the mouse set to pan and the stylus to brush). Oh, and the "paint directly checkbox" should fix your issues with the brush tool.
3) Gimp and Krita use the same gradients, patterns and brushes. File format exchange is problematic, hence the OpenRaster effort that is being spearheaded by Cyrille Berger for Krita and Oyvind Kolas for Gegl.
I strongly suspect the version you tried was 1.4. When I see screenshots of that version in magazines, I tend to want to hide under the table. We've made a lot of progress in the past year and a half :-)
Basically, long before my involvement, KImageShop was started as a Gimp alternative because of hurt feelings over the Kimp demo hack. That was in 1999. When I bought a wacom pad in 2003 I wanted to hack on something to do natural painting and not start my own thing. So I looked around and the Krita codebase had a couple of advantages for me:
* C++, not C (I knew Java, so C++ was easier for me)
* I already knew Qt (I wrote the book on PyQt)
* Much smaller codebase than the gimp
* lots to do (basically only the move tool worked in 2003)
* helpful maintainer (Patrick Julien basically taught me C++)
And then the ball started rolling...
Hm, if you cannot assign a different tool to the eraser tip of your stylus than to the pen tip something went wrong somewhere. We spent a lot of time making sure that every pointing device can have its own tool.
Boudewijn Rempt
Krita Maintainer
It's mostly the same code. KWord and Abiword used to collaborate on a .doc import library. At a certain point we agreed to a version 2 of that library. However, only KWord actually started using it, while Abiword decided to continue with version 1. No doubt we all had our good reasons, but it's a bit sad nonetheless. The WordPerfect import library is more succesful: that is shared between OO, Abiword and KWord.
The KOffice applications are GPL, the shared libraries are LGPL.
Well, actually, OpenOffice is mostly written in a primordial dialect of C++, comes with its own widget set (that can render using gtk or Qt) and a lot more. GTK nor Qt existed when the StarOffice people started writing their software.
Well, that's nonsense in two ways: any windows application should run under wine, whether it uses opengl or not, whether it uses Qt or not. But most importantly, if this is a Qt/OpenGL application, having it run on X11 and OS X is just a matter of compiling the thing for X11 and OS X. That's what Qt's for...
No, not all. You got the wrong end of the clue stick here.
The "Filter" is probably going to stay -- it does follow the KDE standard.
Well, firstly, you're looking at the old 1.4 version of Krita, not 1.5. In 1.5 the filter menu has been reorganized, filters have been added, and we've added a very nice filters gallery dialog that I personally always use. Secondly, I'm not a "they", I'm a "you" -- if you've got suggestions for improvement, why not drop by on #koffice, or kimageshop@kde.org, or even mail me personally and discuss your suggestions. If you can manage to refrain from trite phrases like "lost in the bloat" and "I will stop using it if you don't do what I want", then you will stand a very good chance of being listened to. Boudewijn Rempt, Krita maintainer
Er, Krita does support RAW pictures. I should know, I coded the support myself. You need to have dcraw installed, though.
And who do you think artificially manipulates the Japanese government?
You could try the klik for 1.5. beta1 -- http://klik.atekon.de/wiki/index.php/KOffice-1.5.0 _DistroTable. Simple, one-click install, no messing up of your system...
If you've got a crash, please, please, please report it! Just mail me (that's the maintainer). If it's something complicated I may ask you to file a bug report, but most crashes I can solve very quickly. That is, if you're using the recently released beta. So much has changed since 1.4.2 that reports on that version aren't any use anymore.
In any case, my big problem when developing Krita is exactly this: developers cannot crash-test the app they develop because instinctively they know how the software is supposed to work. I'm relying on people testing the beta's and the release candidates to report me their crashes and problems.
About the slowness: we haven't tried to optimize anything yet. The OpenGL backend is quite a bit faster than the plain X11 backend, so if you can use hardware accelerated OpenGL use that.
No, I'm not claiming anything about retraining costs. I'm claiming that when discussing free graphics applications on Linux, the Gimp isn't the only option anymore. That's all. As Novell recognized: there's the Gimp, Krita and Pixel now -- and Photoshop under wine, but my experiences with that aren't very good. There's some weird bug where I can only paint straight lines...
Oh, and for your collection of Photoshop files: you're chained to Adobe for as long as you value those. You'll never be able to use free software to edit those, you've been caught in the trap. Sure, there was no alternative, I guess, but you've been trapped nonetheless.
Because from Photoshop 7.0 the file format has been closed and it's not possible to get information about it without signing and NDA and promising never ever to build something Photoshop compatible that's not commercial and closed source.
What I should do, of course, is finally begin on that OASIS spec for layered raster images that people have been bugging me about. But I've got a release to get ready first...
Yeah, we know... The name isn't all that great. So what? I didn't invent it. And it's got quite a bit of recognition by now. Wouldn't know whether it would be wise to change it at this point in the game.
But tell me... How is a spreadsheet or a wordprocessor relevant when discussing graphics applications? In any case, all applications in KOffice 1.5 are a lot better than they were in 1.4.