kumosan & battleshooter,
I think we might need to put this in the "To Do in the Future" basket. Whilst it did compile OK, on p431 using QT4-4.6.2, when I tried running the package on Lupu it gave an error to the effect that it couldn't find sqlite. And I don't see the point in trying to compile different versions of programs for different puppy releases. Also, the minimal QT4 library package, for the compiled program to run, was of the order of 7Mbytes...it goes against the grain of puppy's mean & lean philosophy.
What do you think?
Comicmaster
Did you use the new 0067? 0066 had problems creating its config files, which are based on sqlite. This definitely is fixed on 0067.... when I tried running the package on Lupu it gave an error to the effect that it couldn't find sqlite.
If it still has sqlite problems, you could check 'ldd ComicMaster'. It should look like
Code: Select all
libQtCore.so.4 => /usr/local/Trolltech/Qt/lib/libQtCore.so.4
libQtGui.so.4 => /usr/local/Trolltech/Qt/lib/libQtGui.so.4
libQtSql.so.4 => /usr/local/Trolltech/Qt/lib/libQtSql.so.4
libQtXml.so.4 => /usr/local/Trolltech/Qt/lib/libQtXml.so.4
libQtNetwork.so.4 => /usr/local/Trolltech/Qt/lib/libQtNetwork.so.4
Also, the minimal QT4 library package, for the compiled program to run, was of the order of 7Mbytes...it goes against the grain of puppy's mean & lean philosophy.
Interesting. As I said, I am not a puppy user, so I don't know much about this distro. Can you use KDE 4 on puppy? If not ComicMaster really might be a bit overkill.
When it comes to simply reading a digital comic now an then, there are certainly better readers out there, e.g. QComicBook. ComicMaster's strength is the additional stuff. Functionality to manage comic collections. Rename image names in archives, remove/add/rotate/reorder pages. Compare two releases. Export comics as pdf or resize them for mobile readers. Limited default database support based on sqlite. Extensive, but largely untested postgreSQL database support as plugin.
ComicMaster was never intended to be mean & lean. So it really might strain certain distributions. I would not put it on a stick. Sorry.
kumosan,
Yes I compiled v0067 successfully, for p431, but it wouldn't work for p501. It could be that I need to re-compile qt4...maybe I'll have another attempt later.
I wasn't saying that ComicMaster is too big. In short, I came to puppy because I was annoyed by the bloatware of windows, and puppy generally tends to favour small apps, and small support libraries. Often someone will ask if app xyz can be compiled, but when you look at the dependencies, they'll often be bigger, or of a similar size, to the basic puppy .iso! And QT4 is getting to the stage of bloatware.
Yes I compiled v0067 successfully, for p431, but it wouldn't work for p501. It could be that I need to re-compile qt4...maybe I'll have another attempt later.
I wasn't saying that ComicMaster is too big. In short, I came to puppy because I was annoyed by the bloatware of windows, and puppy generally tends to favour small apps, and small support libraries. Often someone will ask if app xyz can be compiled, but when you look at the dependencies, they'll often be bigger, or of a similar size, to the basic puppy .iso! And QT4 is getting to the stage of bloatware.
I hear that from time to time. That Qt 4 is becoming bloatware. I disagree. Sure, Qt is not small, but in many situations it is all you need. I have worked on many projects. Some were open source, others were paid commercial projects. When those projects were based on Qt, Qt usually was the only dependency. No other non-standard libs necessary.muggins wrote:Often someone will ask if app xyz can be compiled, but when you look at the dependencies, they'll often be bigger, or of a similar size, to the basic puppy .iso! And QT4 is getting to the stage of bloatware.
No further xml libs, no further database libs, no boost, no graphics libs.
Of course, the advantage of a lib exists only when there are many applications, which use the lib. Installing full Qt for a single app might feel a bit strange, but this certainly is not Qt's fault.
As long as Qt stays modularized as it is now, I would not even call it bloat if it triples its size. There is even a tool, which is not build by default, (qconfig), which allows an even finer control what Qt compiles in and what not. For instance, if your program does not need certain language support, those languages can be 'switched off'. Or if you don't need QString, you can remove this class from Qt. The tool looks a bit like the Qt linux kernel config. Handles all the dependencies and tells you what else you would lose when you switch off feature 'xx'. This tool is mostly used for embedded projects.
You might have noticed, I love Qt. Always wince a bit when someone calls it bloated.