Hello fellow developers,
many of you are developing XAR-packaged resources. The exchangeability
of these archives is one of the precious aspects of XWiki, I believe.
However, if one see all the many GitHub-contributed xar packages, the
source is not there: it's in a Wiki with which one would "open it". A
pity since much of the content is code.
I'd like to propose to allow XARs to be built form source code which is
true source that one edits.
Code files with their proper syntax coloring, editors, auto-completion,
search. Media-files that are edited with our tool of choice by a simple
double-click and not a complex pull, edit, and replace.
Thus, my proposal is to allow inclusions within the XML files.
Inclusions should be of type:
- text to include page content or object properties (e.g. css of cssx
objects)
- attachments to include attached objects
My current setup is documented
here:http://jira.xwiki.org/browse/XWIKI-13643
It does binaryInclude to generate base64 and textInclude to generate
XML-text.
Thus, I can advertise a github project which is a macro and whose
complex function is in a velocity file that is in a .vm file. However, I
do not need to explode everything, e.g. the text-content describing the
macro or (in this case too small) translation set.
What do you think?
Should I rather generate complete attachment elements (name, length,
modif date, ...) instead of doing a binaryInclude that just generates
base64 ?
Is fetching files for inclusion beyond the boundaries of the project of
any use? (it is currently prohibited for safety)
thanks in advance.
Paul