1 Sep
2008
1 Sep
'08
10:11 a.m.
I'm crossposting to dev because it's interesting for xwiki developers
We thought already of this for attached files. But indeed it would be
good for scripts.
So we could have an export option where the attached file, the wiki page
content is separated from the XML to make it editable.
To be able to do that for script files, we first need to have this meta
field that tell us it's a script (and also that requires programmers
rights for example).
Ludovic
David Ward wrote:
Paul,
On Fri, Aug 29, 2008 at 3:19 PM, Paul Libbrecht <paul(a)activemath.org> wrote:
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Here's a tiny idea:
currently all the files that need programming rights are velocity or groovy
files.
Well... let them be considered as such!
- the archive or the file-sync-storage should call them .vm or .gvy
- they should not be in XML format but in raw source format
- say, for CreateResources/SimpleWikiResource, that would be a file called
SimpleWikiResource.vm in CreateResources directory
- of course, such pages would be loaded with programming rights so
give-prog-rights should not exist anymore
Because they are raw files, we're loosing abilities such as attachments and
a few other things that the XML format can represent (e.g. parent file).
Unfortunately they would lose quite a few things:
- parent page (as you mentioned, which is used for the bread crumbs)
- page title (also used for the bread crumbs, as well as other places)
- rights (** quite important for restricting access, allowing access
for some, etc.)
- attachments (which sometimes hold images for that page)
- objects (which sometimes hold various things)
But we're gaining:
- IDE friendliness (huge to my taste)
- auto-programming-rights
Yes, the IDE friendlyness (plus MUCH better version control
possibilities) is a big item on my list.
One could even add a file-type .xwk for wiki
source files (no programming
rights).
Oh, and one should agree on an encoding here... guess what I propose utf-8.
Yes, UTF-8 is probably the best encoding.
You can see the thoughts I put down a while ago at
http://dev.xwiki.org/xwiki/bin/view/Design/AlternativePageStore
David
--
_______________________________________________
curriki-devs mailing list
curriki-devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/curriki-devs