xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

Re: [xwiki-devs] [ANN] XWiki.TableEdit extension now available for your ExtensionManager installing pleasure.

by Ludovic Dubost

You can go to the sandbox to see a table and should see an edit button next to the table. The code is in macro xwiki objects Le jeudi 10 janvier 2013, Dan Jones a écrit : > I imported the xar, and it created the page with two attachments... > > But I don't see any tables that can be edited. The page it created > contained no actual velocity scripts or anything. > > What did I do wrong? > > ------------------------------ > *From:* Ludovic Dubost <ludovic(a)xwiki.com <javascript:_e({}, 'cvml', > 'ludovic(a)xwiki.com');>> > *To:* XWiki Developers <devs(a)xwiki.org <javascript:_e({}, 'cvml', > 'devs(a)xwiki.org');>> > *Cc:* XWiki Users <users(a)xwiki.org <javascript:_e({}, 'cvml', > 'users(a)xwiki.org');>> > *Sent:* Wednesday, January 9, 2013 4:15 AM > *Subject:* Re: [xwiki-users] [xwiki-devs] [ANN] XWiki.TableEdit extension > now available for your ExtensionManager installing pleasure. > > Hi Caleb, > > Great stuff. I just tried it out. Installation was immediate. > > I found one issue with multilingual. Although my wiki was in mono-lingual > and french, it retrieved the english version of the sandbox document. This > might be a REST issue. > > Another issue but is probably a feature for now is that I was not able to > do calculations in the spreadsheet. I tested on Chrome. > > Ludovic > > > 2013/1/9 Caleb James DeLisle <calebdelisle(a)lavabit.com <javascript:_e({}, > 'cvml', 'calebdelisle(a)lavabit.com');>> > > > Hi all, > > > > I'm proud to announce that after a few weeks of hectic downtime I finally > > got XWiki.TableEdit extension finished. XWiki.TableEdit allows you to > edit > > wiki tables as if they were spreadsheets using the jquery.sheet > in-browser > > spreadsheet editor. > > > > Internally XWiki.TableEdit is an exiting foray into a new frontier of > > modular > > javascript, relying entirely on Asynchronous Modular Definition to load > > it's > > component parts. ( https://github.com/amdjs/amdjs-api/wiki/AMD ) > > > > XWiki.TableEdit is still in it's infancy, future plans include editing of > > spreadsheets in attachments, conversion of the loading and saving APIs to > > the > > simple REST-like JIO standard ( http://www.j-io.org/ ) so that others > can > > more > > easily develop similar editors, and porting the entire widget from > painful > > hand written javascript to simple HTML5 based on renderjs > > ( http://www.renderjs.org/ ) which can be installed in other frameworks. > > > > More information about the extension: > > > > http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+TableEdit > > > > I'd love to hear your feedback, especially browsers where it doesn't > work. > > xwiki-contrib JIRA project coming soon.. > > > > Thanks, > > Caleb > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org <javascript:_e({}, 'cvml', 'devs(a)xwiki.org');> > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > -- > Ludovic Dubost > Founder and CEO > Blog: http://blog.ludovic.org/ > XWiki: http://www.xwiki.com > Skype: ldubost GTalk: ldubost > _______________________________________________ > users mailing list > users(a)xwiki.org <javascript:_e({}, 'cvml', 'users(a)xwiki.org');> > http://lists.xwiki.org/mailman/listinfo/users > > > -- Sent from Mobile

12 years

[xwiki-devs] [proposal] 2 new xwiki-contrib projects.

by Caleb James DeLisle

Hi, I'd like to move two projects from my namespace to xwiki-contrib. The first is XWiki.TableEdit which is described better in an email which I just wrote. The other is jquery-sheet-amd which is an Asynchronous Module Definition wrapper around jquery.sheet which allows it to play nicely as an AMD module. I'd like to move both to xwiki-contrib repository since xwiki-contrib-tableedit relies on jquery-sheet-amd. WDYT? Caleb For review: https://github.com/cjdelisle/xwiki-contrib-tableedit https://github.com/cjdelisle/jquery-sheet-amd

12 years

Re: [xwiki-devs] [xwiki-users] How to make an extension which is installable by the extension manager?

by Caleb James DeLisle

Thanks for the help Vincent. I have the basics of a "My First Extension" tutorial by example. https://github.com/cjdelisle/my-first-xwiki-extension (It's very important to me that developing installable extensions be simple and intuitive) I'm trying to allow the user to deploy their extension to a local directory within their git repository and then they could push that to github or equivalent and import without having to ask that their key be included in maven.xwiki.org and deploying where they could break something. It seems to work: https://raw.github.com/cjdelisle/my-first-xwiki-extension/master/repo/org/x… Where I'm hitting a wall is on the import phase, I need to be able to import from an arbitrary m2 repo in order for this technique to work. Is this possible with the EM as it is now? Thanks, Caleb On 01/05/2013 09:34 AM, Vincent Massol wrote: > Hi Caleb, > > On Jan 4, 2013, at 8:41 PM, Caleb James DeLisle <calebdelisle(a)lavabit.com> wrote: > >> Hi, >> >> I'm looking to contribute an extension which is installable with the EM >> and I can't find any documentation on it, if there is no documentation >> I am willing to write it if someone will walk me through the process. >> >> How do I go about getting published and how are dependencies declared? > > 3 choices: > > 1) Your extension is published in a maven repo (e.g. the XWiki public maven repo at http//nexus.xwiki.org). This makes it installable directly by any XE instance. However Maven repos are not searchable so users won't be able to search for your extension and will need to enter the extension id/version in the Advanced Search. > 2) Same as 1) but you wish to have your extension searchable. For this, it should be available on extensions.xwiki.org. To do that all you need is to "Import" your extension from the maven repo. This is the "import" action on extensions.xwiki.org > 3) Your extension is NOT in a maven repo. You need to contribute it on extensions.xwiki.org and then follow the documentation to add dependencies (basically one object per dep). > > Feel free to document this. I think we could have a question mark icon on extensions.xwiki.org just after "Contribute extension" and when you click on it, it would go to a page listing what I've explained above, wdyt? > > Thanks > -Vincent > > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users >

12 years

[xwiki-devs] [Reminder] Bug Fixing Day #8 this Thursday 6th of December

by Vincent Massol

Just a reminder. See http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HXWikiDa… Thanks -Vincent

12 years

[xwiki-devs] Unable to translate strings in french

by xrichard

Hello, I'm running the new 4.4-rc-1 and I'm trying to translate the strings of the buttons rename/delete a tag which are not yet translated, see picture attached or there : http://www.hiboox.fr/go/images/informatique/tagbuttonsuntranslatable,070b8c… I have tried to change the following keys without success : xe.tag.rename=Renommer core.menu.rename=Renommer rename=Renommer core.rename.submit=Renommer. Is it a bug (no translation is possible)? Or do I miss the correct key, in this case is there a way to find easily the key to translate among all keys in the properties file? Best regards, PS : I'm willing to have a 100% french xwiki ... and I may contribute to next XWiki french translation. -- View this message in context: http://xwiki.475771.n2.nabble.com/Unable-to-translate-strings-in-french-tp7… Sent from the XWiki- Dev mailing list archive at Nabble.com.

12 years

Re: [xwiki-devs] [xwiki-notifications] xwiki-enterprise - Build # 9763 - Still Failing!

by Vincent Massol

This is a false positive. I had an error in my regex. It's fixed now. Thanks -Vincent On Jan 7, 2013, at 6:37 PM, Jenkins <build.noreply(a)xwiki.org> wrote: > Check console output at http://ci.xwiki.org/job/xwiki-enterprise/9763/ to view the results. > > Failed tests: > All tests passed > > Last build logs: > Started by upstream project "xwiki-platform" build number 3118 > Building remotely on agent-2 in workspace /home/hudsonagent/hudson_root/workspace/xwiki-enterprise > Checkout:xwiki-enterprise / /home/hudsonagent/hudson_root/workspace/xwiki-enterprise - hudson.remoting.Channel@8ca882:agent-2 > Using strategy: Default > Last Built Revision: Revision ed8777156f8c896ce9ff21d6dd37bcc18ca6e54e (origin/master) > Fetching changes from 1 remote Git repository > Fetching upstream changes from git://github.com/xwiki/xwiki-enterprise.git > ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway > hudson.plugins.git.GitException: Command "/usr/bin/git fetch -t git://github.com/xwiki/xwiki-enterprise.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: > stdout: > stderr: github.com[0: 207.97.227.239]: errno=Connection timed out > fatal: unable to connect a socket (Connection timed out) > > at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897) > at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:858) > at hudson.plugins.git.GitAPI.fetch(GitAPI.java:200) > at hudson.plugins.git.GitAPI.fetch(GitAPI.java:1105) > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:813) > at hudson.plugins.git.GitSCM.access$100(GitSCM.java:72) > at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1018) > at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2236) > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:326) > at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > ERROR: Could not fetch from any repository > FATAL: Could not fetch from any repository > hudson.plugins.git.GitException: Could not fetch from any repository > at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1025) > at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2236) > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:326) > at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

12 years

[xwiki-devs] [Proposal] XWiki 5.x cycle theme

by Vincent Massol

Hi everyone, We're getting close to the end of the 4.x cycle (only one more release, 4.5, which should be out at the end of January) and thus we need to start thinking about 5.x (see http://dev.xwiki.org/xwiki/bin/view/Community/VersioningAndReleasePractices ) As a reminder here are our past themes: * 3.x: Theme 1: "Building Apps and Distributing them" (This means for example that the Extension Manager in progress is a key element of XE 3.x. It also means making it easier to create applications in XE.), Theme 2: "Polishing" * 4.x: Theme 1 (top priority): Ease of use, Theme 2: Quality Internally at XWiki SAS we've had a brainstorming meeting with everyone to discuss what could be the main themes for XWiki 5.x The result is the following: Theme: Speed and Simplicity ----------------------------------------- Mission: Improve XWiki's usage for new and regular users by improving Usability and Usage Speed in order to make XWiki simpler and faster both from a pure performance point of view and from are user interface point of view. Technical details: - Individual Feature Improvement from a Usability perspective including speed of access (real time updates, commenting in activity stream) - General Usability Improvements on XE and XEM for simplicity - Technical Rewrite of certain features (activity stream) for performance or architecture reasons - General Performance Improvement of XWiki (page loading, rendering time) - Bug Fixing in general WDYT? Thanks -Vincent

12 years

[xwiki-devs] [VOTE] ASM 3.x vs 4.x choice

by Vincent Massol

Hi devs, We have a problem ATM since we bundle both ASM 3.1 and 4.0 at the same time in XWiki. See http://jira.xwiki.org/browse/XE-1269 We have to take some decisions: 1) We say that we don't support indexing .class files in attachments at the moment (we open a jira for it so that we don't forget to fix it later on) and we open an issue on the tika parser tracker to migrate to ASM 4.X. We follow that issue and when they add support for it we upgrade to it. 2) I put back pegdown 1.0.2 (we're on 1.2.1) but that means changing code and removing features since they have implemented new features since 1.0.2 (they have released 3 versions since then). I don't like this. 3) We modify Tika parser sources so that it works with ASM 4.0 and we publish in our maven repo. It's like 1) but we do the work. Personally I think that 3) is too much work for the benefits so I would go for 1). WDYT? Any other idea? I'm voting 1 (i.e. ASM 4.0) Thanks -Vincent

12 years

[xwiki-devs] [VOTE] Merge new Markdown branch from Guillaume Laforge

by Vincent Massol

Hi devs, I've been working with Guillaume Laforge on reimplementing our support of Markdown. The current version we have relies on Pegdown's HTML serializer which we then read with our HTML parser. This causes several issues, amongst which: * http://jira.xwiki.org/browse/XRENDERING-237 * http://jira.xwiki.org/browse/XRENDERING-236 So Guillaume and I have completely rewritten it, this time mapping the AST events generated by Pegdown to XWiki Rendering events. The work can be seen here: https://github.com/glaforge/xwiki-rendering/tree/master/xwiki-rendering-syn… It fully passes our CTS. I'm this proposing to integrate this work in 4.5M1 since it fixes existing bugs. There's a small risk that it's going to cause other bugs elsewhere but I think it's worth it, especially seen that our markdown support is quite new. Here's my +1 Thanks -Vincent

12 years

[xwiki-devs] [ANN] XWiki 4.4 released

by Vincent Massol

12 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs