>>> Regarding Images: >>> Having the option to not attach them (just like backgrounds) would be >>> really nice, with an element like: >>> >>> <image left="74.00" top="278.00" right="595.28" bottom="799.28" >>> filename="bg_1.png"/> >> why? >> >> The Image format I use is 100% compatible with the pach which is >> available for Xournal on sf.net > It's good to have it compatible (though that patch never made it into a > released version), but still the extension with 'filename=""' would not > break it.
Are you sure? Try it out;-) Xournal has for reading always a loop which checks every attribute, if you have an attribute more it don't read the whole file. That's the reason why I leave everything exactly the same. (Even if you change the order of attributes it don't read the files any more). For me personal I said I leave it in the first release 100% compatible with Xournal (and optional with the image patch). And if all is working, the next release will use a new fileformat which is not compatible, but contains resources and new features. (based on ZIP instead of GZip) > Not attaching images is important because of file size, especially, but > not only when you include the same image several times. I would say it's > important for the same reasons out which backgrounds can be attached or > detached. This is an argument for using attaching images... > Also, imagine using a "library" of images that you include again and > again, or a workflow where you regenerate the image and want your xoj to > use the regenerated image automatically. This is no argument for attaching images, this is in my opinion against, because the data is may inconsistent. There is a Python API for Xournal++, which is not finished yet, and at the moment only used for testing, but later you should write a Python Plugin for this, so there is for sure no inconsistency. >> For future releases I'll create a new format (e.g. based on ZIP) which >> can handle resources better. >> >>> BTW: xournalpp produced that 'filename="bg_1.png"' for the image >>> background, but the filename is "wrong". But then it does find it on >>> restart! Quite confusing. OTOH, the "resuse image" dialog for image >>> backgrounds is great and just what I would love for detached image >>> objects also :) >> I'll check this, I don't understand what you mean now, but I didn't >> really test background image yet;-) > Journal -> paper background -> Image: select "bend.png" > Save xoj. > > The xoj is: > > <?xml version="1.0" standalone="no"?> > <xournal creator="Xournal++ 0.1" fileversion="2"> > <title>Xournal document - see http://xournal.sourceforge.net/</title> > <preview>...</preview> > <page width="22.00" height="31.00"> > <background type="pixmap" domain="attach" filename="bg_1.png"/> > <layer/> > </page> > </xournal> > > Different filename. But when I close and reopen xournalpp finds it or > rather: I see now that there is a copy > > 2011-04-18-Note-15-07.xoj.bg_1.png > > in my workdir. Is that (copying background images) how it works with > xournal trunk? On the open dialog is a checkbox, "Attach to Xournal". Even on my application (but in Xournal++ it's may not working correct;-)) I'll may do the same for insert images. Andreas > Michael ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Xournal-devel mailing list Xournal-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xournal-devel