23 Aug
2016
23 Aug
'16
10:51 a.m.
To be extra-clear, let me explain my workflow when I design an application
in XWiki.
- First, I write my code directly in an instance of XWiki.
- When it's ready, I export all the pages related to my application in a
XAR.
- Then, I uncompress my XAR inside my repository.
- I clean the XML files using mvn xar:format.
- I commit.
And when I fix something, I do it directly in the wiki, then export the
page in a XAR, uncompress it in my repository, clean the xml files manually
(reverting the changed dates, etc...).
What I don't want is to be forced to manually remove the source code from
the XML to put it in the other file every time.
Thanks,
2016-08-23 10:45 GMT+02:00 Guillaume Delhumeau <
guillaume.delhumeau(a)xwiki.com>gt;:
Hello Paul.
I think it's an interesting idea (and I know this is not the first
proposal in that way).
But do you also consider the opposite use-case: editing some code in the
wiki, and then export a XAR containing the metadata in an XML and the
content in a plain text file?
Otherwise, it makes it harder to fix some code in the wiki directly before
committing it in the repository.
Thanks,
2016-08-22 15:59 GMT+02:00 Paul Libbrecht <paul(a)hoplahup.net>et>:
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
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/bro
wse/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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project