Am 17.01.2011 19:43, schrieb Bob McElrath:
> Denis Auroux [aur...@math.berkeley.edu] wrote:
>> 2. The existing xournal code is completely tied into libgnomecanvas and  
>> GTK+, which unless I'm mistaken don't run in Android. (But... how long  
>> before there is a GTK+ Android port? After all, that's how the Windows  
>> and Mac ports operate, rather than porting to the native OS. Is this a  
>> realistic prospect or am I being unrealistic? -- after all GTK+ is not  
>> too lightweight...). Andreas' code rewrite should be quite a bit better  
>> structured than my code, from what I understand, even if it is not  
>> platform-independent yet. So it's probably the place to start for a  
>> future Android port.
> A brief perusal of google tells me this is unlikely.  I do not see people
> porting complex libraries to android, in general.  Android has its own
> java-based graphics stack.
> http://developer.android.com/reference/android/graphics/package-summary.html
I disagree with you, e.g. VuDroid uses a C PDF library for rendering.

http://code.google.com/p/vudroid/

It is much more work to port the complete Xournal, and then you have
always the problem that you have to maintain each code twice, and this
is to much work...

> Here is a tutorial that implements the very basics necessary for xournal:
> http://www.tutorialforandroid.com/2009/06/drawing-with-canvas-in-android.html
>
> I think the UI implications of having multiple (GTK/Android) widget sets would
> be enough of a nightmare for people to avoid such a thing.  I don't know 
> whether
> the gnomecanvas library (alone) can be ported, that would help.
No GTK widgets, only cairo.

Cairo does not depend on GTK, cairo can also be used with e.g. QT or
without any other framework.

> So it would seem that an android app may be a complete rewrite of the canvas 
> and
> UI pieces.
I did this yet. I splitted the complete source code into Model View
Control (more ore less, my target is now a working version, not a good
modulation and portability...)

> In terms of a "xournal library" I think the only thing that could be
> extracted is the .xoj file handling.  The page itself in structs Page and Item
> are deeply dependent on Gnome/GTK.
In c++ is it possible to do a good abstraction, with inheritance etc.
MVC Pattern, Observer Pattern, Factory Pattern and so you can split up
the application so its possible to run the "same" application on Android
with Java Interface and on Linux with GTK.



> --
> Cheers,
> Bob McElrath [ Heidelberg University, Theoretical Physics ]
>
> "If you wish to make an apple pie from scratch, you must first invent the
> Universe." -- Carl Sagan
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand 
> malware threats, the impact they can have on your business, and how you 
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Xournal-devel mailing list
> Xournal-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xournal-devel


------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Xournal-devel mailing list
Xournal-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xournal-devel

Reply via email to