https://github.com/tauu/xournal

and includes build instructions based on your blog entry.
(With this page being included as the source of the instructions.)

Thanks for porting xournal to windows!

I’m glad you’re liking Xournal, but I did not create it and this is not its website. You might want to check out Xournal’s website and post to the mailing list for feature requests.

http://xournal.sourceforge.net/
http://lists.sourceforge.net/lists/listinfo/xournal-devel

Please, is there any way to make the cursor bigger? When projecting, its hard to follow the cursor.

Another suggestion that could make Xournal much useful is to simplify the shortcuts, as Shift+Ctr+P needs two hands…

Thanks.

the file you need is “config” — text edit it (with notepad, if nothing else) to suit.
(not a lot of options, although)

hope it helps

I recently decided to try to go “predominantly paperless” (ie., to do all my many notes and scribbles – that I usually make when I’m thinking and planning etc – all on the PC). I looked around, and settled on a modestly-priced Wacom (Bamboo Pen) Tablet together with Xournal software. I also looked at Jarnal and NoteLab too, but I prefer Xournal. So far, it seems stable enough.

Given that I run only Windows, I just wanted to say, “A BIG thank you Dirk!” for going to the trouble of sharing the above and making it possible for this humble non-programmer to be able to use this nifty piece of software.

Much appreciated.

I’m not sure if that’s the right place to post this question but I don’t know where else. I installed xournal on my Lenovo tablet (with Windows 7) and I have some problems:
-The handwriting is very pixelated (in MS Journal it’s smooth)
-I cannot use the eraser tip of my stylus
-In the options menu, the following are not highlighted: Use XInput, Eraser Tip, Pressure sensitivity

I hope someone can help me, since if wasted more than 2 hours to find the solution
to these problems.

Thanks!

I have not idea if it exists some specific mailing list for gtk and win.

I’ll hope to found someone interested to fix the problems.
Anyway I think that the right way to work is:
- fix the GtkWindow initialization and
- implement the gdk_window_input_shape_combine_mask
- implement the gdk_cursor_new_from_pixmap that you have workarounded.

I don’t think that a patch approach can allow to a serious development
and then I think that the right way to follow is publish bug reports
to the gtk team

The gtk fix for win32 it is out of my planes.
I am a free software supporter and I have tried to build Ardesia
for windows only to see my program run on it and to demonstrate the porting feasibility.

This task for me is closed even if I don’t know how fix some things.

I have other priority in the development.

I’m pretty sure that have Ardesia running with the mainstream Ubuntu distro it is more useful for my purposes.

I have seen that the windows user often prefer shareware software and I can not think that it is easy to make visible a tool that it run under Windows.

There are for win some tools similar to Ardesia;
I know them (e.g. Easy Whiteboard, pointtofix…) and
I have tried to do better and I think to have reached the goal.

We’ll see, it is possible that the win32 porting will be postponed

An other very interesting porting is in the MacOsX direction, for this operating system there are not similar tools and there are a lot of designers that love this platform.

Bye