I was able to put a hildon color chooser instead of that ugly color picker we had before.
I need now to correctly process GdkColor instead of RGB guint colors that Xournal uses.
Dunno if I should make Xournal switch to GdkColor or keep guint rgb values...
We'll see.
Xournal looks great now.
The toolbar and the main window are both hildonized.
Notice the black color selector button.
I am trying the iinstall from http://maemo.org and it seems t either take forever or has stalled out...I don't know which.
EDIT:
Well, it's apparently just slow as snot...the progress bar just made a big jump. So I can say the package install from the Maemo site seems to work so far...
After that, I will take my time to clean the code.
Few mods and it's already too much of a mess there and the more I add stuff to the Maemo port the more I think I should make my patches cleaner.
This comes also from the fact that I intend to bring my patches upstream.
To support this, this morning I also found an interesting e-mail from Denis Auroux (original Xournal author) suggesting me the very same thing and also some ideas on how to improve pressure usage on our port.
He also was kind enough to explain further about the ghostscript dependency:
Originally Posted by
ghostscript dependency: not replaced by poppler-utils, but you did
the right thing by making it optional and not recommended. Xournal uses
ghostscript specifically if you use the "Load background" command in the
Journal menu and select a PS or PDF file (those are then rendered as
bitmaps using gs) -- and only for this. (This is sufficiently rarely
used that one shouldn't force people to get ghostscript. On Tablet PCs
it's commonly installed, and hard disks are larger, so there it makes
more sense).
Moreover, I am not looking for private beta-testers, that's why I put the .deb files on-line available to everyone.
Bear in mind that these versions are for beta-testing, may be ready for the end-user, but I am experimenting a lot and things can change drastically (bost mostly on the UI land).
When the maemo extras upload starts working, I will upload a stable version and the updates to that version will be slower and only for main changes.
I will continue, tho, to release work-in-progress packages on my own server.
But I believe I won't have too much to play with after the first versions of the port will be released.
Yesterday night, right before closing my eyes for sleeping, a quite cool idea came up to my mind.
I like a lot the backgroung feature, so I was thinking to integrate the GPS into that.
That is, annotating a map of where you are at that moment.
I plan to ask Maemo-mapper author about the code for maps retrieval, but I plan to suggest him to cooperate about writing a map-server for Maemo.
A daemon specifically designed to handle different map sources and provide tiles on-demand/tile caching.
We'll see what he thinks about it.
I am trying the iinstall from http://maemo.org and it seems t either take forever or has stalled out...I don't know which.
EDIT:
Well, it's apparently just slow as snot...the progress bar just made a big jump. So I can say the package install from the Maemo site seems to work so far...
On the Downloads section of maemo.org there is the old version of Xournal, i.e. 0.4.1
Oh, by the way, if you save the preferences and look at the .xournal/config file, you can experiment with your own pressure modifier values:
# minimum width multiplier
width_minimum_multiplier=0
# maximum width multiplier
width_maximum_multiplier=1.5
I think minimum= 0 and maximum = 2 should be fine.
For left-handed people:
# interface has left-handed scrollbar (true/false)
interface_lefthanded=true
Originally Posted by Denis
modifying pressure sensitivity settings (width_minimum_multiplier=...
and width_maximum_multiplier=...) (the conversion is done linearly so
that zero reported pressure in the GDK event gives a stroke of width
width_minimum_multiplier times the nominal pen width, while reported
pressure 1 gives width_maximum_multiplier times the nominal width).
These should be set so that a reasonable amount of pressure produces
a multiplier close to 1. The minimum multiplier can't be less than zero.
From what people seem to report about lines being too thin, you should
try setting min=0, max=2, or maybe min=0.5, max=1.5.
