Looks like an interesting project, however I'm not sure about how active it is.
On github there are 1145 stars whereas the pug templating language has 15820.
Just important to avoid jumping from one sinking ship to another ;)
https://github.com/thymeleaf/thymeleaf
https://github.com/pugjs/pug
Th
+1 for en_US
🇺🇸
Thanks,
Caleb
On 04/12/17 14:36, Manuel Smeria wrote:
> Hello,
>
> +1 for en_US
>
> Thanks,
> Manuel
>
> On Mon, Dec 4, 2017 at 3:18 PM, Eduard Moraru wrote:
>
>> +1 for en_US
>>
>> Thanks,
>> Eduard
>>
>> On Mon, Dec 4, 2017 at 2:42 PM, Alex Cotiugă
>> wrote:
>>
>>> +1 fo
not be doing.
Thanks,
Caleb
On 22/11/16 14:41, Caleb James DeLisle wrote:
If I might join in and ask, what should XWiki be used for ?
On 22/11/16 14:39, Vincent Massol wrote:
I’d never promote XWiki as a tool to replace any of the tools I’ve mentioned in
my previous reply. If you do, you’re
I kind of like this idea because it preserves the email interface for
people who want that but at the same time it allows people to interact
with it as if it were a forum.
On 23/11/16 01:27, Julio Brum wrote:
Hi,
Would not it be interesting to use google groups? For example, the Django
Project
If I might join in and ask, what should XWiki be used for ?
On 22/11/16 14:39, Vincent Massol wrote:
I’d never promote XWiki as a tool to replace any of the tools I’ve mentioned in
my previous reply. If you do, you’re doing a disservice to your users.
__
Well this is a very interesting topic of discusssion and me and the XWiki SAS
Research team
would like to do whatever we can to help evolve XWiki forward (but don't let us
get in the way!)
On 04/11/16 14:34, Vincent Massol wrote:
Hi devs,
We’ve been developing XWiki over 10 years now. I’d li
On 11/09/16 19:21, Vincent Massol wrote:
Hi Thomas,
On 11 Sep 2016, at 17:16, Thomas Mortagne wrote:
Are those jetty/hsqldb or WAR sizes ?
I’ve used
http://snippets.xwiki.org/xwiki/bin/view/Extension/Size+of+XE+Distributions
which measures the Jetty/HSQLDB packaging.
Apart from the si
Hello all,
Recently we discovered that in XWiki 8.2 the {{html}} macro cleaner now removes
tag whereas in 7.4 it did not and this has unfortunately caused problems for
the {{video}}
macro.
1. After some helpful investigation by a few XWiki developers, we have found
that in fact
the {{html}}
On 18/08/16 21:00, Vincent Massol wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see
http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensions/
* I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the
+1
On 15/07/16 16:13, Marius Dumitru Florea wrote:
Hi devs,
I'd like to propose that we use, from now on, {{html clean="false"}} when
developing applications, because:
* HTML cleaning is an extra step that can increase page loading time
* the HTML cleaner can have bugs (like any other code) or
Caleb James DeLisle wrote:
For CryptPad and the realtime infrastructure we deal with a DOM structure and
we needed to do a similar thing (for example to remove elements which are part
of the editor and not the document). We opted to use a similar strategy using
filter callbacks but we don't have
For CryptPad and the realtime infrastructure we deal with a DOM structure and
we needed to do a similar thing (for example to remove elements which are part
of the editor and not the document). We opted to use a similar strategy using
filter callbacks but we don't have lookahead capability.
Examp
I disagree with this point, as a user of web interfaces I don't care if
they look completely busted as long as I can make use of them, even if they
become unusable in 5% of the situations, that's 95% where I can use them.
Granted if we ship something that looks broken it's an embarassement but
if
Correction:
Google docs doesn't use a tree, they have a lefthand "menu" instead.
Google docs is filling me with hate and rage right now, anything they do for
UI, do the opposite.
On 08/06/16 10:16, Caleb James DeLisle wrote:
Vote layout 1, we absolutely need a tree, this is
Vote layout 1, we absolutely need a tree, this is killing us.
One of the things which *made* MS Windows was the fact that you had a tree of
folders
in the explorer. Same thing (tree) is shown in Thunderbird mail and in google
docs.
Thanks,
Caleb
On 01/06/16 17:49, Ecaterina Moraru (Valica) wr
Excellent ! This is what people really need.
Some suggestions which you might adopt if you like them (but don't let me get
in the way of you doing great stuff).
1.
"In the next couple of minutes you will discover your wiki's interface and basic
functionalities."
Should point to an icon somewh
Hello Peter,
This seems like a significant issue which should be reported in the bug
tracker (jira.xwiki.org) but I cannot understand which menu bar you are
thinking of. A video should not be necessary, your description is detailed
but perhaps you could provide a simple screen shot with an arrow
Hi Abtv,
Thanks for your help in debugging, I just wanted to remind you that this
is still very experimental code, hence the warning on the extensions page.
When you install either RTWiki or RTWysiwyg, it will install a websocket
component and realtime backend which require a wiki restart in orde
I suppose it goes without saying that I would be +1 but we should also
make note that the limit must also be reaised in the XWikiPreferences
which is not user-accessable so we can.
A. Raise it ourselves to a sane number like 100MB
B. Expose the parameter in the administration application
C. A and
Perhaps you would like to try updating to the most recent version which uses
XWiki CKEditor, when you use this version you should have realtime whenever
you select the "CKEditor" option for editing a page.
As you know from the page though, both XWiki/CKEditor and XWiki Realtime
WYSIWYG are experi
+1 because better the developers and the users run the same major version
of the JVM and I think most of the devs are already running 8.
Thanks,
Caleb
On 10/02/16 07:17, Manuel Smeria wrote:
+1
Thanks,
Manuel
On Tue, Feb 9, 2016 at 10:53 PM, Paul Libbrecht wrote:
vinc...@massol.net wrot
Done, thanks for the reminder.
P.S. There ought to be a button for this :)
On 13/01/16 14:23, vinc...@massol.net wrote:
Hi Caleb,
On 13 Jan 2016 at 14:20:02, Caleb James DeLisle
(c...@cjdns.fr(mailto:c...@cjdns.fr)) wrote:
Done: https://github.com/xwiki-contrib/api-structured-data
Thanks
Done: https://github.com/xwiki-contrib/api-structured-data
If there is consensus we can change the name later.
Thanks,
Caleb
On 13/01/16 13:30, Thomas Mortagne wrote:
Ok I was thinking about maven modules, did not noticed this rule for
contrib projects.
On Wed, Jan 13, 2016 at 1:26 PM, vinc..
t
e-mail a été envoyé depuis un ordinateur protégé par Avast.
www.avast.com
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Fri, Dec 18, 2015 at 9:36 AM, vinc...@massol.net
wrote:
Hi Caleb and Edy,
On 18 Dec 2015 at 09:02:17, Caleb James DeLisle (c...@cjdns.fr(mailto:
c...@cjdns.fr)) wrote:
Hey Ed
/15 17:35, Eduard Moraru wrote:
Hi Caleb,
On Thu, Dec 17, 2015 at 3:51 PM, Caleb James DeLisle wrote:
also be available to the application, on release. If we desynchronize
them, the application will most likely be left behind.
I interpret your words to mean: we want to keep them merged in
d, Dec 16, 2015 at 6:19 PM, Caleb James DeLisle wrote:
They're going to have distinct release cycles
This is exactly what I hope to avoid by not separating the code from the
application. This way, whatever improvements you bring to the code, will also
be available to the applicatio
They're going to have distinct release cycles so I think the least ugly thing
to do is have 2 projects.
Thanks,
Caleb
On 16/12/15 17:12, vinc...@massol.net wrote:
On 16 Dec 2015 at 16:56:57, Yann Flory
(yann.fl...@xwiki.com(mailto:yann.fl...@xwiki.com)) wrote:
Hello devs,
In order to be
Yeah, I was just kidding about this one, it's fine for me :)
On 08/12/15 13:03, Ecaterina Moraru (Valica) wrote:
:) I think you should keep it - at least is memorable :)
Thanks,
Caty
On Tue, Dec 8, 2015 at 1:48 PM, Caleb James DeLisle wrote:
On 08/12/15 12:44, vinc...@massol.net
On 08/12/15 12:44, vinc...@massol.net wrote:
Hi,
Hey new repo frenzy! Nice :)
JIRA: http://jira.xwiki.org/browse/CRAPI
LOL you gotta be trollin this time. xD
GitHub: https://github.com/xwiki-contrib/api-commandrunner
Regarding the extension name on e.x.o I’d suggest to use “Command R
On 07/12/15 16:50, vinc...@massol.net wrote:
Hi Mohamed,
On 7 Dec 2015 at 15:43:43, Mohamed Boussaa
(mohamed.bous...@xwiki.com(mailto:mohamed.bous...@xwiki.com)) wrote:
Hello devs,
I'd like a repository on xwiki-contrib for the XWikiTube application (name
of the repo: application-xwikitube
I can't imagine how I would attempt to explain a terminal (but not meaning it's
going to die soon)
page to someone who doesn't know the insides of the sausage factory.
Every page is like a file, and it's also like a folder because it can have
pages inside of it,
except for the ones that can't..
attempt at making it more
familiar to people and thus more intuitive.
Thanks,
Caleb
On 27/11/15 16:54, vinc...@massol.net wrote:
On 27 Nov 2015 at 16:41:34, Paul Libbrecht
(p...@hoplahup.net(mailto:p...@hoplahup.net)) wrote:
Caleb James DeLisle wrote:
I had just imagined an exten
I would say generally speaking the longer we wait to align our syntax
with markdown the more non-standard and irrelvant our syntax will become.
If we were building XWiki from scratch today, we would be royal fools not
to adhere to what is essentially a universal standard for syntax.
But even tho
Without jumping into the Solr v. ElasticSearch discussion, I am quite
favorable to the general idea of a big-data store complementing the RDBMS.
Especially if it might allow us to again enable stats that are more
fine-grained than those collected by piwik.
This also opens the door to possibly sto
+1 for Option 2 or 2A
As I understand, we're only talking about URL escaped / which both Tomcat and
Apache httpd will
"do things with", tomcat blocks it, Apache either blocks or *unescapes* it
depending on setup.
Thanks,
Caleb
On 16/11/15 10:21, vinc...@massol.net wrote:
Hi guys,
I think w
+1
Bonus points if you can make it only show the {{error}} if there are one or
more blockers ;)
Caleb
On 13/11/15 17:51, vinc...@massol.net wrote:
Hi devs,
I’d like to suggest a new best practice which would consist in systematically
adding blockers issues in the release notes correspondin
ke the JVM and the XWiki code and pages like
the Java
classpath. Clearly the classpath Java code is a "user" of the JVM and is not in
any
way a "derivitive work".
Thanks,
Caleb
On 10/11/15 10:12, vinc...@massol.net wrote:
On 10 Nov 2015 at 10:07:05, Caleb James De
On 10/11/15 09:59, vinc...@massol.net wrote:
Hi Caleb,
See below
On 10 Nov 2015 at 09:51:04, Caleb James DeLisle
(c...@cjdns.fr(mailto:c...@cjdns.fr)) wrote:
On 10/11/15 09:40, vinc...@massol.net wrote:
On 10 Nov 2015 at 09:23:12, Thomas Mortagne
(thomas.morta...@xwiki.com
On 10/11/15 09:40, vinc...@massol.net wrote:
On 10 Nov 2015 at 09:23:12, Thomas Mortagne
(thomas.morta...@xwiki.com(mailto:thomas.morta...@xwiki.com)) wrote:
IMO we should get rid of this old "The wiki documents (all the
documents in the default .xar archive) are distributed under Creative
I agree with Thomas, license on the wiki pages is a sticky situation
because on the one hand some of them contain significant code which
we might want to put under a copyleft license (we might not, it only
works on XWiki afterall) but at the same time we don't want to lead
users to believe that ch
I suppose you have installed the extension:
Visual Realtime Collaborative Editor (EXPERIMENTAL)
Here: http://extensions.xwiki.org/xwiki/bin/view/Extension/RtWysiwyg
Thanks for your help in testing it!
I've filed a bug on your behalf on jira.xwiki.org, you'll find it here:
http://jira.xwiki.org/
Just discovered this:
https://kiwiirc.com/client/chat.freenode.org/?nick=visitor|?#xwiki
It's a lot more modern look and feel than the webchat we have embedded on
xwiki.org
After that it's just a question of where you want to put the link or iframe.
Caleb
On 16/10/15 09:48, vinc...@massol.net
Hello folks, thank you very very much for taking the time to rank these
next steps, this is most helpful for us in deciding what we will do.
1. I made a small change to the page, adding easy to remember names to
each feature, eg TABS, HIDE_EDIT_MODES, etc.
2. Vincent I removed your change from t
+1
On 21/09/15 16:03, vinc...@massol.net wrote:
Hi devs,
I’d like that we retire the XMLRPC feature of XWiki.
Rationale:
* We now have a REST API
* The XMLRPC API is pretty old now, doesn’t support Nested Spaces, see
http://jira.xwiki.org/browse/XWIKI-1249
The idea would be to:
* Step 1: Rel
Hello All,
It's been a long time since we first discussed hardening XWiki Programming
Rights
by way of signing scripts in the wiki. As I recall the idea was spawned some
time
around 2011 in a conversation between me and Denis but it has had difficulty
getting
off the ground. Alex Busenius and
I see, +1
On 27/08/15 11:13, vinc...@massol.net wrote:
On 27 Aug 2015 at 10:34:17, Caleb James DeLisle
(c...@cjdns.fr(mailto:c...@cjdns.fr)) wrote:
Ahh ok, +1 to explosing the absolute cannonical reference, however I will point
out
that use of "this" in javascript is dan
g on where you are in the code. Better XWiki.doc.reference or
similar IMO.
Thanks,
Caleb
On 27/08/15 10:23, vinc...@massol.net wrote:
On 26 Aug 2015 at 18:23:42, Caleb James DeLisle
(c...@cjdns.fr(mailto:c...@cjdns.fr)) wrote:
A bit late to the game but can't we pass a cannonicali
A bit late to the game but can't we pass a cannonicalized absolute string to
the JS ?
eg: wiki:space.sp\.ace.sp\\ace.page
and then just warn the js devs that they should use functions to manipulate the
string representation instead of hacking it manually ?
That's what nodejs does for URLs and I
Since there has not been any other replies on this, I will volunteer to
integrate this PR and make a release of this extension with the new
functionality.
Thanks,
Caleb
On 24/08/15 12:45, Mohamed Boussaa wrote:
Hello devs,
I created a PR on the Video macro (
https://github.com/xwiki-contrib/m
Added a jira project and moved the repo on github from labs to xwiki-contrib:
http://jira.xwiki.org/browse/XRECOMMEND
https://github.com/xwiki-contrib/application-recommendations
Thanks,
Caleb
On 06/07/15 14:55, Caleb James DeLisle wrote:
> I'll take care of the leg-work for this one.
I'll take care of the leg-work for this one.
On 06/07/15 14:48, Yann Flory wrote:
> Hello devs,
>
> I'd like a repository on xwiki-contrib and a Jira project for a
> Recommendations Application (name of the repo: application-recommendations).
> This application recommends pages for the users base
ra.xwiki.org/browse/XWEBIDE or write to me.
Thanks,
Caleb
--
Caleb James DeLisle
XWiki SAS
calebjamesdeli...@xwiki.com
irc.freenode cjd 9:00-18:00 GMT+1 http://bit.ly/1suU0Lh
Satire is the escape hatch from the cycle of sorrow, hatred and violence.
#JeSuisCharlie
--
Satire is the escape hatch fr
I think I can say without justification that changing a term which is in the
XWiki developer's lexicon is going to inflict pain, however I don't see the
real pain in keeping it. Certainly other names could be better and I might
have chosen "root" to keep with unix standards of "Global Administrator
This was my main criticism of AngularJS from the beginning. Things which
try to be everything usually end up quite efficiently falling on their
faces, especially in the js world.
On 06/09/2015 10:45 AM, Marius Dumitru Florea wrote:
> You need data-binding, you look for a library that does just tha
gt; On 23 May 2015 at 17:58:51, vinc...@massol.net (vinc...@massol.net) wrote:
>
>
> Hi Caleb,
>
> On 23 May 2015 at 16:28:17, Caleb James DeLisle
> (c...@cjdns.fr(mailto:c...@cjdns.fr)) wrote:
>
>> Agreed, I can't see what that line should do, if anything.
Agreed, I can't see what that line should do, if anything.
The best it can do is add a null element to the list, kicking the value to
index 1.
As for the thinking of the author, the comment implies he didn't clarify his
thinking
about what was being done and why so I'd favor simply dropping the l
http://design.xwiki.org/xwiki/bin/view/Proposal/ExtensibleAPIforaccessingstructuredata
Thanks,
Caleb
On 04/09/2015 05:41 PM, Guillaume "Louis-Marie" Delhumeau wrote:
> 2015-04-09 17:14 GMT+02:00 Caleb James DeLisle :
>
>> I'm not sure I agree that the syntax is s
Unused afaik, +1 for "moving it to .git directory" ;)
Caleb
On 04/23/2015 09:22 AM, vinc...@massol.net wrote:
> Hi devs,
>
> With the upgrade of BouncyCastle to version 1.52 the
> xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since
> BC has removed deprecated code.
>
Reference('AnotherSpace',
> 'SomeClass'), Model.createDocumentReference('', 'MySpace', 'MyDocument')),
> function (err, obj) {
> if (err) { throw err; }
> console.log(obj.someProperty);
> });
> });
>
>
Thanks for reviewing this...
On 04/03/2015 07:03 PM, Marius Dumitru Florea wrote:
> On Fri, Apr 3, 2015 at 6:54 PM, Caleb James DeLisle wrote:
>> Well I made a "few small changes" (which expanded into eventually a total
>> rewrite).
>> Fundamentally I
+1
requirejs is insane for fishing around in the URL and making decisions
about it but webjars is insane for encoding path information in a parameter.
XWIKI-10881 is refactoring which is orthogonal to this issue.
Thanks,
Caleb
On 04/03/2015 07:09 PM, Marius Dumitru Florea wrote:
> See http://ji
for changing it.
Lets start a conversation.
Caleb
On 03/17/2015 06:11 PM, Caleb James DeLisle wrote:
> I have been meaning to review this API, I finally got a chance to do so
> and I have some suggestions for changes to it. Of course I don't want to
> take away from the spirit of th
From the attachment:
looks like it's Redhat
Here's the whole xml https://ezcrypt.it/fQAn#qeu8O6MNt8cIE2eFDHWyTuUL
tip: ezcrypt.it probably should work...
Thanks,
Caleb
On 03/20/2015 09:00 AM, vinc...@massol.net wrote:
> Hi Amrita,
>
> Unfortunately we don’t allow attachments on this list
I have been meaning to review this API, I finally got a chance to do so
and I have some suggestions for changes to it. Of course I don't want to
take away from the spirit of the idea too much but I have a few suggestions
which reflect things which I often find myself wanting to do in my application
ce we already
>>> use the EXOExtensionCode space for stuff specific to e.x.o. (specific vs
>>> what’s provided in the default Repository app). That said, we should
>>> probably provide this page in the Extension page and by default in the
>>> Repository a
eric for that or not,
> but it could be made generic I guess if not already).
>
> Thanks
> -Vincent
>
>> (Thanks to Caleb for all these suggestions.)
>>
>> On Fri, Feb 13, 2015 at 5:10 PM, Caleb James DeLisle wrote:
>>
>>> Hi all,
>&
Hi all,
Today I worked with Mohamed to release an extension (TotemApplication) to the
extension manager
and he wrote an excellent tutorial for uploading a xar file so that is is
accessible from the
extension manager.
http://www.xwiki.org/xwiki/bin/view/Drafts/ContributingExtensions
I'd like to
+1
How about:
require(['xwiki.meta', function(xm) {
console.log(xm['form-token']);
});
?
On 10/02/2014 10:58 AM, Thomas Mortagne wrote:
> +1
>
> On Thu, Oct 2, 2014 at 10:50 AM, Marius Dumitru Florea
> wrote:
>> +1
>>
>> Thanks,
>> Marius
>>
>> On Wed, Oct 1, 2014 at 4:31 PM, Guillaume "L
t if at least
> the xwiki team is satisfied globally with the jira issue tracking tool for
> themselves, it's already something valuable as it's not always the case.
>
>
>
> 2014-09-29 9:32 GMT+02:00 Caleb James DeLisle :
>
>> Nice summary of the technical costs/bene
Nice summary of the technical costs/benefits.
What I think is missing is compatibility between XWiki project and the
developer community.
For good or for ill, kids these days use github.
The days of svn, jira and tight knit developer communities are gone, devs are
their own
free agents, they co
t;
> Personally and based on all pros/cons I think the best ATM is really Option
> A. And if we really want, it’s possible to improve the cons by doing a bit of
> java coding:
> https://developer.atlassian.com/display/JIRADEV/Creating+a+Project+Template
>
> Thanks
Didn't we stop storing members of a group that way a long time ago?
(implying the LIKE queries are strictly for backward compat)
On 09/18/2014 11:14 AM, vinc...@massol.net wrote:
> Whenever you do a LIKE you need to check your indexes in your DB to tune the
> query to be fast.
>
> Thanks
> -Vinc
+1
On 09/15/2014 09:22 AM, vinc...@massol.net wrote:
> Hi devs,
>
> Since our RTF export has never worked very well (because FOP doesn't support
> RTF export too well), I think we could decide to drop RTF export when no
> office server is running.
>
> Note that I’d like to propose doing this n
really updated our checkstyle configuration since we first
>> started using it, other than minor tweaks. In the latest version of the
>> Checkstyle tool several useful checks have been added, which I'd like to
>> enable.
>>
>> On 09/12/2014 04:15 AM, Caleb Jame
Hi all,
This is partially an extension of the previous mail thread
``Checkstyle audit audit'' where in the discussion, I formed a few thoughts
about checkstyle rules which should be added and removed. Since that thread
is very cluttered now, I wanted to begin a new one specifically explaining
the
humble remarks ... :)
>
> 2014-09-09 11:00 GMT+02:00 Caleb James DeLisle :
>
>> Firstly, thank you very much for reviewing my code.
>>
>> When I was young I hated homework, my parents told me that if I spent
>> as much time on the work as I spent bellyaching about it, I&
On 09/11/2014 08:38 AM, Marius Dumitru Florea wrote:
> On Tue, Sep 9, 2014 at 12:00 PM, Caleb James DeLisle wrote:
>> Firstly, thank you very much for reviewing my code.
>>
>> When I was young I hated homework, my parents told me that if I spent
>> as much time on the
On 09/09/2014 03:22 PM, Sergiu Dumitriu wrote:
> On 09/09/14 05:00, Caleb James DeLisle wrote:
>> 1. Multiple identical string constants in a file
>
> There's another checkstyle rule, which we don't use, preventing the use
> of numbers other than for defining cons
rd", my counter is that no rule makes contributing
*easier* and as contributors are not exactly lining up at the door, any
rule that exists needs to justify itself as necessary.
On 09/08/2014 07:30 PM, Sergiu Dumitriu wrote:
> I'm gonna audit your audit audit.
>
> On 09/08/
Hi,
I just finished rewriting my WebSocket extension using Netty and it now
supports SSL. \:D/
To test my work before re-releasing I decided to enable checkstyle and see what
issues
it pointed out which were important for me to fix. It listed 78 checkstyle
errors, many
of them are very important
Update:
I forgot to mention that it is currently deployed and testable on
http://realtime.webviewers.org/
Thanks,
Caleb
On 08/08/2014 12:24 PM, Caleb James DeLisle wrote:
> Hello all,
> On behalf of XWiki SAS Research Team, I'm proud to announce that an
> early experimental
Hello all,
On behalf of XWiki SAS Research Team, I'm proud to announce that an
early experimental version of the XWiki Realtime WYSIWYG has just
been released!
You can find the code here:
http://extensions.xwiki.org/xwiki/bin/view/Extension/RtWysiwyg
and install it using the Extension Manager.
Bew
You should be able to push now.
Thanks,
Caleb
On 08/05/2014 11:53 AM, Jean SIMARD wrote:
> And my Github account...
> https://github.com/woshilapin
>
> Sorry.
> --
> Jean
>
> On mar., 2014-08-05 at 11:52 +0200, Jean SIMARD wrote:
>> Hi devs,
>>
>> Can I be added as a committer on xwiki-contrib,
ng. I’ve added this thread to
> http://design.xwiki.org/xwiki/bin/view/Proposal/JavaScriptFrameworkEvaluation
>
> Thanks
> -Vincent
>
> On 28 Jul 2014 at 16:56:21, Caleb James DeLisle (c...@cjdns.fr) wrote:
>
> Since Marius wrote the FileManager application using Angul
I don't like the idea of renaming space (again).
If new people don't understand it easily, better we find an efficient
way to educate them than to rename the concept so that old people won't
understand it either. The tragedy of renaming things is that the code
becomes unapproachable with surprises
+1 excited to see it
On 07/31/2014 07:02 PM, Guillaume "Louis-Marie" Delhumeau wrote:
> Hi devs.
>
> I propose to set Flamingo by default in 6.2.
>
> It is not fully finished though:
> - It is not HTML5 valid: http://jira.xwiki.org/browse/XWIKI-7552 &
> http://jira.xwiki.org/browse/XWIKI-10616
>
My personal opinion is that it's OK to save a bit of time and remove the
code entirely, the retro-compat documentation would in this case be
"if you use syntax/1.0, you now need to edit it using the wikitext editor".
It's not as if their data will nolonger be accessible.
Thanks,
Caleb
On 07/30/2
I'm not best to judge but my gut feeling is our TinyMCE
implementation is not being used so +1 in principle.
Thanks,
Caleb
On 07/29/2014 02:26 PM, vinc...@massol.net wrote:
> FTR it’s at
> https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwiki-platform-web/src/main/webap
Since Marius wrote the FileManager application using AngularJS
and there has been some discussion about making increasing use
of it in XWiki, I wanted to share a review by someone who uses
it in his job as their entire platform.
These are advantages and disadvantages which I determined from the ch
Oh excellent, we need more tests like this!
On 07/02/2014 01:58 PM, vinc...@massol.net wrote:
> Hi devs,
>
> Yesterday I’ve asked my wife to try out XWiki...
>
> Exercise 1
> ==
>
> I gave her the simple task of creating a wiki page with some content to
> organize a party with a list
I have not read all of the code but I'm +1 to the principle, including the
skin action change which makes logical sense.
Are you planning on pushing this into 6.1M2 ?
Thanks,
Caleb
On 06/11/2014 05:43 PM, Guillaume "Louis-Marie" Delhumeau wrote:
> Hi devs.
>
> I am implementing the Color Theme
Hi,
I'd like to propose installing the Realtime WikiText extension on myxwiki.org.
It has already been installed on webviewers.org and in XWiki SAS internal wiki.
I would like to broaden the scope to myxwiki.org and then xwiki.org.
Myxwiki.org is a special scenario because it contains many subwik
Good news indeed!
Also interesting how they implemented it, it appears to be javascript
running in rhino which is triggered by ant. It looks like they wanted
to use js build scripts but nodejs didn't exist when they started.
Thanks,
Caleb
On 06/04/2014 01:59 PM, vinc...@massol.net wrote:
> At la
On 05/28/2014 11:25 AM, Marius Dumitru Florea wrote:
> On Wed, May 28, 2014 at 12:10 PM, Guillaume "Louis-Marie" Delhumeau
> wrote:
>> 2014-05-28 10:43 GMT+02:00 Marius Dumitru Florea <
>> mariusdumitru.flo...@xwiki.com>:
>>
>>> On Tue, May 27, 2014 at 11:47 AM, Guillaume "Louis-Marie" Delhumeau
paperwork complete
http://jira.xwiki.org/browse/RTBACKEND
http://jira.xwiki.org/browse/RTWIKI
https://github.com/xwiki-contrib/realtime-backend
https://github.com/xwiki-contrib/realtime-wikitext
On 05/16/2014 02:25 PM, Caleb James DeLisle wrote:
> realtime-backend exports a (hopefully) stable
-Vincent
>
>
> On 16 May 2014 at 10:43:50, Caleb James DeLisle
> (c...@cjdns.fr(mailto:c...@cjdns.fr)) wrote:
>
>> Hi,
>> I'd like to shove these two projects over into xwiki-contrib github group.
>> One is for the backend which supports realtime-wysiwyg an
Hi,
I'd like to shove these two projects over into xwiki-contrib github group.
One is for the backend which supports realtime-wysiwyg and realtime-wiki
and the other is the realtime-wiki (text editor).
https://github.com/cjdelisle/xwiki-contrib-rtbackend
https://github.com/cjdelisle/xwiki-contrib-
+1 against wysiwyg, unfortunately the project is created but for marketing
purposes we should consider a name which is not an ugly acronym.
Thanks,
Caleb
On 05/16/2014 02:30 AM, Joshua Marks wrote:
> How about "We-type" (or (witype)
>
> -Joshua
>
> -Original Message-
> From: devs [mail
t;
> Thanks
> -Vincent
>
> On 15 May 2014 at 16:20:17, Caleb James DeLisle
> (c...@cjdns.fr(mailto:c...@cjdns.fr)) wrote:
>
>> Hi,
>>
>> xwiki-tools is a set of command line tools and a node.js library for building
>> and parsing parts of xwiki .xar fi
Hi,
xwiki-tools is a set of command line tools and a node.js library for building
and parsing parts of xwiki .xar files. It is unique in that it contains a
fairly complete model of XWiki documents, objects, and classes which is not
based on the original model in oldcore. It is capable of compiling
1 - 100 of 818 matches
Mail list logo
