Dear all,
Some months ago I wrote a patch for xournal which makes line endings
more beautiful.
I had already uploaded the patch to sourceforge
(https://sourceforge.net/p/xournal/patches/82/) (and had a little mail
exchange with Denis about it); now I just saw in some readme file that I
should
Hi,
some time ago, I wrote to this mailing list about a patch improving (a)
performance and (b) how line endings look. I didn't get any reply. Is
there no interest in this (or did just nobody feel responsible to answer
or so)?
(What's the right way in which to contribute to xournal?)
There ar
dd your feature and we can all test it.
> I can also integrate it to my "next" version of the repo.
>
> --dmg
>
> On Wed, Aug 31, 2016 at 9:50 AM, Immi Halupczok <mailto:xour...@karimmi.de>> wrote:
>
> Hi,
>
> some time ago, I wrote to this m
Am 01.09.2016 um 17:41 schrieb D M German:
>
>
> >> I've been thinking a bit more about it: As I had written before, it
> >> somewhat changes the file format (to be able to store the line width at
> >> the very beginning). However, I think that after all, it's quite bad if
> >> old versions o
I was looking at your code. I think it would be very useful to separate
conceptually the two changes, as you said before. It will also be very
useful to us that you describe (ideally in the log of the commit) a bit
in detail the changes. E.g. Motivation, how you did it, impact on
xournal (change
First of all: Denis, yes you are right in your prev mails, about how you
understand my patch.
I attached a xoj file and pdf files, one rendered by old xournal and one
by my version. Note that this xoj file has been created by an old
xournal, so the line width at the very beginning of the strok
Hi,
I now implemented Denis's idea of having an additional dummy point in
the file; it seems to work fine (though it needs more testing). What I
wasn't aware of is that it even has another advantage compared to all my
previous ideas: If one creates a file with new xournal, edits it with
old xo
Hi,
there's a whole list of other little improvements to xournal I'd like to
make, but I thought before starting, I should run them by you, to see if
they don't contradict other plans or if somebody is already working on
somthing similar; or maybe you just have suggestions:
(a) When I have
Hi,
Am 04.09.2016 um 20:25 schrieb D M German:
>
> Hi everybody,
>
> as you know, i have been developing several features of xournal. Some of
> them become integrated with xournal, others do not.
>
> But I try to keep them updated and ready to be integrated, in the chance
> that one day they beco
Another issue about the text boxes:
If we use some gtk-feature to do the wrapping of the text for us, then
there's the danger that when one rescale things, due to some roundings
happening differently suddendly the wrapping changes. Similarly,
wrapping could change when exporting to pdf... or ma
>> (e) I'm using the "touchscreen as hand tool" feature, but I'd like to
>> improve it: I'd also what that it behaves like many other touch screen
>> aware programs in the way that you can "give it a kick" so that it goes
>> on scrolling for a little while. (That's much more handy when scrolling
>
this way.
Immi
>
> (Already privileging width over height assumes a horizontal script, but
> that's something we shouldn't worry about, almost nothing works with vertical
> scripts in Linux anyway).
>
> Best
> Denis
>
> Denis Auroux
> Department of
Am 04.09.2016 um 20:17 schrieb Denis Auroux:
> Dear Immi,
>
>> (a) When I have a thin selection (which happens often if I have some
>> small text, which I select by clicking on it) and I want to move it, I
>> often accidentally resize it. Therefore, for thin selections, I'd make
>> (in start_resi
... are now implemented in my new branch scroll-gestures. Probably a lot
of tweaking and fine-tuning is still possible (and a lot of testing is
necessary), but I think it works already pretty well. It definitively
makes the hand tool and finger scrolling a lot more handy.
As I said, I made it
Dear Torsten (and others),
I'm also planning to use xournal for a lecture next term, and for that,
I might also be happy to have this side bar feature, and I'd be willing
to contribute on updating it (if necessary).
Am 12.09.2016 um 11:11 schrieb Torsten Wagner:
> Hi Daniel,
>
> thanks for kee
Hi,
I just noticed that the latest version of xournal (the master branch in
github) stores values in the config file using the current locale, which
means writing "1,5" instead of "1.5" on a German system. I saw that this
behaviour has been intentionally introduced in
"2b74a01... Fix issues wi
Am 13.09.2016 um 17:32 schrieb Denis Auroux:
> Hi Immi,
>
> Yes, this is hideous, I agree. The issue at this point is backwards
> compatibility -- existing xournal users have .config files with
> locale-dependent numeric data in it and we'd like to be able to read
> them even if they upgrade to a
Hi,
the Next branch doesn't work with filenames containing spaces. For example,
xournal "ab cd.xoj"
tries to open a file called "ab".
I tried to find out why this happens, but it looks a bit as if it's a
problem with g_option_context_parse(); I don't know why it behaves like
this.
I guess
Thanks for that.
I already fixed it.
Best,
Immi
Am 16.09.2016 um 00:54 schrieb dmg:
>
> Hi Immi,
>
> while using your code I found that I get (sometimes) an artifact
> in the PDF. It is a thin line. See the following files,
> that show a very simple XOJ file with the error.
>
> http://t
Shame on me; yes, it was just a problem with a badly made shell script
of mine. (I just double-checked: xournal itself works fine.) Sorry about
that.
Immi
Am 19.09.2016 um 02:27 schrieb D M German:
> Immi Halupczok twisted the bytes to say:
>
> Immi> Hi,
> Immi&g
Hi,
Daniel: Did you already incorporate Denis's change to the config file
into xournal-next?
Immi
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sd
I fixed the two-equal-points-crashes-xournal bug (in my repository,
branch line-widths-optimized). I did not yet do anything about the
"-nan" issue.
Immi
Am 06.10.2016 um 20:51 schrieb Denis Auroux:
> Interesting. Neither of the issues causes the stable/upstream xournal to
> crash, thou
Concerning -nan:
I can confirm that normal xournal doesn't crash, next does. And I just
tried: line-widths-optimized does not crash. (So chances are smaller
that it's my fault ;-) )
Immi
Am 06.10.2016 um 20:01 schrieb dmg:
> This is the stroke that is crashing xournal:
>
>
> -nan -na
Hi,
I'm also very interested in this feature, and I'm happy to help
integrating it into next - though I cannot guarantee yet that I'll find
time for that.
Best,
Immi
Am 09.10.2016 um 01:35 schrieb D M German:
> David van rijn twisted the bytes to say:
>
>
> David> Hello Xournal develo
Am 09.10.2016 um 00:55 schrieb D M German:
> Immi Halupczok twisted the bytes to say:
>
>
> Immi> Concerning -nan:
> Immi> I can confirm that normal xournal doesn't crash, next does. And I just
> Immi> tried: line-widths-optimized does not crash. (So chances a
Hi,
I also tried it, and I'd also like to use it (and to improve it, if I
find time). I created a new branch xournal-double in my repository
(github.com/immi-h/xournal) which is the master branch with the changes
from xournal-double merged in. (I also tried to rebase xournal-double to
master,
26 matches
Mail list logo
