D M German venit, vidit, dixit 15.05.2012 02:51: > > hi everybody, > > Aniello> When I was thinking of the best way to adapt Xournal to scale > Aniello> (and before Xournal++ appeared), I was thinking of splitting > Aniello> the logic from the UI and make them communicate by means of > Aniello> some sort of IPC. I was literally thinking of putting the > Aniello> Xournal logic into a little daemon (UI-agnostic) and have the > Aniello> UI communicate with it via Unix sockets or shared memory or > Aniello> similar framework. Having the logic separated could also make > Aniello> it easier, later on, to add support for a collaborative > Aniello> version. The UI would not need to care too much about what is > Aniello> going on or being drawn onto the canvas. > > I guess the main question I would have for you is why switch UI? Is the > goal to make it more platform independent? Why? I guess it needs to > scratch the itch of some developers, and for the time being, my only > requirements are android and X11. If there was a way to guarantee that > the work I do helps an android clone I'll be happy to help. > > I personally think that the long term plan is xournal++. > > I see the benefit of xournal++, but I have to balance the benefits vs > the drawbacks: > > - xournal works very well > - restructuring its going to take effort > - restructuring its going to insert bugs > > so yes, it will be useful to do that, but I think the main challenge is > where to find the cycles to do this. > > In the last month I dedicated a good number of hours to Xournal. It is > so good (for my needs) now that I have been able to create presentations > with embedded images without any problems or crashes (it even allows > cut-and-paste of images from gimp to xournal--thanks Leo for that). It > is still not perfect, but it is getting there. And it is making my paper > reviewing easier, by having some simple niceties that I have been > missing (such as searching in PDFs and backgrounds in notes). > > I guess what I am trying to say is that we can all work together do > continue development, but we can do it in different fronts according to > our interests. > > For example, I can help with everything that involves non-UI (I am not > very good at UI programming). I can help with the XOJ ,and PDF backends, > both reading and writing. > > But for a rewrite, I really think we should put our efforts behind > Andreas work.
The problem I see is that there is no agreement about the direction. As a consequence, right now it's easier to extend (or fix, where necessary) xournal than to work on xournal++. Various branches with extensions are floating around. I think the main direction should be: - For xournal, focus on fixes (e.g., to keep the tablet support up to date, keep it in compilable state when distros upgrade). - For xournal++, work on stability and compatibility with xournal, where compatibility means: -- read and write the same xoj -- produce the same pdf (module library differences) -- support the same features (strokes, text,...) Of course it's sexier to work on collaborative editing, extended image embedding and what not in xournal++, but that only splits the user base and makes no focussed use of the limited developer resources. If everyone agrees that a rewrite in c++ is due (as it seems) then xournal enhancements should be restricted to a an agreed-upon minimum, say image inclusion and command line processing (-A); and, if possible, made in parallel to xournal++ in a compatible way. Just my two Euro-cents ;) Michael ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Xournal-devel mailing list Xournal-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xournal-devel
