2 Sep
2016
2 Sep
'16
11 a.m.
Hello Guillaume,
Guillaume Delhumeau
<mailto:guillaume.delhumeau@xwiki.com>
29 August 2016 at 11:03
Paul, your comment makes me think about https://xkcd.com/927/ :)
Good point!
Let's drive this quietly indeed.
Now, as far as I can see, all the previous attempts where made by
individuals. Nothing have been really discussed and designed by the whole
team. Which is why I believe this new attempt could be the good one.
Agree.
Moreover, Vincent is not starting form scratch but on
the Fabio's project.
On a language that I find largely inferior to the previous
one since
it's whitespace dependent as Python is which all developers I met find
very doubtful. But well... that's personal.
We only need to make some improvements on it.
About my expectations:
* I need a format that gives the same result when I export my content
after
having imported it (bijection).
Please clarify here: do you need that for all
projects of everyone of
just for the projects you intend to work with?
(that relates to the claim that we can have "source and push" projects
to be different form "source bijection wiki")
* I would prefer having it respecting the Nested Page
hierarchy (ie: no
space concept).
* Easy to edit with whatever text editor. Maybe using a correct suffix to
enable the syntax highlighting easily: for example I usually edit my
content inside a file holding the ".vm" extension so my editor knows I
will
write some Velocity code in it.
+1
I also claim that freedom in the extensions is better.
I never write code from scratch in my file system. But
if I had to, I
suppose the hierarchy that Vincent suggests would be too complex. It might
be a problem for the developers who have written XFF and the NodeJs tools
which have code to be imported in XWiki, but does not have output filter
now.
So you want freedom in the directory layout?
This might make sense to join to other build systems btw... (e.g. the
package task that includes a JS compilation or some documentation
generation).
Paul