xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] How to build and run wysiwyg editor

by 许凌志(Jamesxu)

I need to build and run wysiwyg editor seperately, I have tried downloaded all the source file from svn: http://svn.xwiki.org/svnroot/xwiki/platform/web/trunk/ and builded it using "mvn install", then I got a war file with complied GWT javascript and related files and two jars: xwiki-web-gwt-wysiwyg-server-3.1-SNAPSHOT.jar, xwiki-web-gwt-wysiwyg-client-3.1-SNAPSHOT-shared.jar, but I didn't find the entry to run wysiwyg editor, so that I can run it on my browser seperately in order to test my own code further. However I found a document http://dev.xwiki.org/xwiki/bin/view/Community/Building#HBuildingtheWYSIWYGe…, it tells to run test on browser using the maven profile -Pmanual, I tried it, but still can not run it on the browser. Anyone can tell me how to run the wysiwyg editor so that I can work on the codes, and test it in my own browser? -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

13 years, 10 months

[xwiki-devs] [Proposal] Default edit mode for a page

by Luca Anca

Hi all, starting from the need of the dashboards, to specify the default edit mode for a page, here's how I would like to implement it, in the following days. Context: There is already a mechanism for this, which works like this: if, document A includes sheet B and sheet B has an object of type "XWiki.SheetClass", then clicking the edit button of document A will automatically open the edit mode specified in the XWiki.SheetClass object of the sheet B. Proposal: 1/ I propose an enhancement of the existing mechanism, to allow such an XWiki.SheetClass object to be attached to the document A directly. Namely the edit mode for the document A will be read first from the objects of type XWiki.SheetClass in document A, then if none found, from the objects in the included sheet. 2/ XWiki.SheetClass should be renamed to XWiki.EditModeClass, or XWiki.DefaultEditModeClass, or something alike, that suggests its purpose. Current class name will be deprecated but still preserved for a good while. What would be your name proposals for this? 3/ optionally, we could deprecate the current mechanism, and say that objects should never be attached to sheets anymore, only to pages. This way, the usecase of a sheet should be implemented by adding the EditModeClass object in the template from which docs are created, so that it can be easily propagated to a set of documents. I am not against the current mechanism, I think it's a nice helper, and the replacing implementation has the drawback of making it mandatory to create documents through templates, or manually adding this object in the doc creation code. Therefore, I would be -0.5 on this. WDYT? 4/ optionally, add an edit mode panel (or whatever we want to replace them with) to change this from a nice UI. This can turn out useful in cases when such an edit object is added automatically (e.g. dashboards) and when it's no longer needed (dashboard macro call is deleted from the page), the default edit mode still stays the one set automatically. This is very optional, as I see little cases when users would delete just the macro call, and not the page as a whole. Thanks, Anca

13 years, 10 months

[xwiki-devs] XWikiContext#getUser and not logged in users

by Thomas Mortagne

Hi devs, I'm currently working on http://jira.xwiki.org/jira/browse/XWIKI-6103 which has two aspects: 1) stored the user as a DocumentReference in the context so that we stop loosing the user all the time when switching databases 2) provide a DocumentReference oriented API to deal with the current user For 2 I would like to propose some change in the way to see not logged in user: I would like to make getUserReference return null when there is no user logged in instead of some DocumentReference containing <currentwiki>:XWiki.XWikiGuest. I understand that when dealing with string "XWikiGuest" hack appear but null when there is actually no context user makes much more sense at Java level IMO. Make safer to distinguish between no logged in user and logged in user and you don't really care what has been chosen as virtual name for not logged in users at this level. That will not impact anything which already exist and is just for code that will use the new API of course but I think it deserve some debate first since that's another way to see things and well it's an API. WDYT ? -- Thomas Mortagne

13 years, 10 months

[xwiki-devs] GSoc 2011: idea "Auto Completion in Content Editors" (updated)

by 许凌志(Jamesxu)

Dear Marius Florea and Anca Luca: I am James Xu and I want to contribute to xwiki community through GSoc project. I am interested in working on the idea "Auto Completion in Content Editors". I choose this idea for two reasons: First, I knew Xwiki since 2009, and that is the first time to use xwiki as wiki system in our lab, and I think it's time to give something back to xwiki. Second, the idea "Auto Completion in Content Editors" attracts me a lot. I have done some projects related to autocompletion before. the first project is to implement an autocompletion feature for search input form for a Web search system of our lab; the second is to research how to aggregate widgets for a mashup system, and wired all them up through an autocompletion algorithm. Though they are different from this idea, they give me some general ideas for autocompletion, and I want to extend autocompletion function to the content editors based on the kowledge gained from the previous projects and research. Here are my understanding of the requirements of this idea, and I hope you can give me more tips and feedbacks: For xwiki editor: - Implements autocompletion function for content editor, for example, when user want add link to their wiki page, they first type"[[", and then the autocompletion function will run to give him the suggestion of some documents begin with the charactor he types in, the list will narrowed when he types more. another example can be autosuggest to the attachment link. - Auto completion for some syntax like eclipse HTML editor. for example,if user type"{{" which is the syntax for xwiki macros, then it should suggest him a list of macros name like "box, code..." when user select one, if say "box", it will insert to xwiki the following: "{{box cssClass="" title="" width=""}} {{/box}}" , user should not remember what the attributes for the macros, and would not to close the tag after a long input. what should I do is to find out which syntax can be improved by such kind of autocompletion, and what is the interaction between the editor and the user. For xwiki WYSIWYG editor: - Supply the same function as what we have done in xwiki editor, and then translate automatically into what should it look like for end users. For example,when user finnish the box macro, it should be transalted to visualized box module for user, as well as when user type //word//, it will shows up '*word*'. I have almost 4 years web development experiences, php for 3 years, and java for 2 years. I have some knowledge in using SSH(Strust2+spring+hibernate) as java web framework. I am also practiced in javascript/css/html,and have more than 3 year development experiences. I use dojo for almost 4 years since version 0.9, and jquery for 2 years, I am starting to use GWT this year, but I think I would be a quick learner based on the knowledge I gained from the other two js toolkits. Look forward to your feedbacks. -- Best wishes, 许凌志(James Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

13 years, 10 months

Re: [xwiki-devs] CAS Integration + new User creation

by Marco Antonio González

Hi All, I finally got it. I was trying to create a user without the "XWiki." prefix but when I discovered that if I creates it using the createUser method from the XWiki class, the username must NOT have that prefix, but the new XWikiUser that checkAuth returns must have it. I followed the XWikiSunSSOAuthenticator code and found the solution. Again, many thanks you for your help Marco A. Gonzalez Date: Fri, 25 Mar 2011 12:46:27 +0100 From: Thomas Mortagne <thomas.mortagne(a)xwiki.com> Subject: Re: [xwiki-devs] CAS Integration + new User creation To: XWiki Developers <devs(a)xwiki.org> Message-ID: <AANLkTimN8OT5Nr+=5dLJ6WdQ-M3V9tpwGr3KFk9zeB0E(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Fri, Mar 25, 2011 at 12:46, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: > Hi, > > As Kevin suggested it's a good idea to follow existing authenticators > on http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/authenticators/ > > Note that you get reuse some generic abstract classes in > http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/authenticators/xwiki-aut… > to make it easier for you? Remove the "?" here :) > > 2011/3/25 Marco Antonio Gonz?lez <magonzalez(a)grupointermark.com>: >> Hi, >> >>>> Are you sure wikiname (not a very good variable name ;) ) includes the >>>> "XWiki." prefix? >> >> When I try to use createEmptyUser(xwikiname, userRights, context) from an XWiki object (context.getWiki()) if I manually add "XWiki." in the "xwikiname" it creates an "XWiki.mynewuser", but on the Admin Users page it doesn't looks like a normal user, it lacks many of the the user properties and doesn't have the XWiki.XWikiUserSheet in it's content, also when I try to get it's XWikiDocument it appears as XWiki.XWiki.mynewuser. >> >> I'm working with XWiki version 2.4 (xwiki-core-2.4.jar >> >> Currently, I'm checking how XWikiSunSSOAuthenticator does it, checking what I do wrong. >> >> Thank you, >> Marco A. Gonzalez >> >> Date: Fri, 25 Mar 2011 11:44:30 +0200 >> From: Marius Dumitru Florea <mariusdumitru.florea(a)xwiki.com> >> Subject: Re: [xwiki-devs] CAS Integration + new User creation >> >> Hi Marco, >> >> On 03/25/2011 10:40 AM, Marco Antonio Gonz?lez wrote: >>> Hi all, >>> >>> I'm new developing with XWiki, and I'm not sure this list is the correct to post this, so sorry in advance for any inconvenience and my bad english. >>> >>> I'm trying to get an integration with CAS Auth instead of own XWiki Auth, but when I try to create a user on my own implementation of XWikiAuthServiceImpl, the user is created on XWiki space, but when i log into XWiki and Main is my default Space, the Profile link on top points to /xwiki/bin/view/Main/mynewuser instead of /xwiki/bin/view/XWiki/mynewuser where I can edit his first name, surname, etc. Is this the default behaviour? If not, any suggestions of what I do wrong? >>> >>> The autentication code is, in my CASAuthServiceImpl class: >>> >>> public XWikiUser checkAuth(XWikiContext context) throws XWikiException { >>> ? ? String remoteUser = context.getRequest().getRemoteUser(); >>> ? ? String wikiname = ""; >>> ? ? if ((remoteUser == null) || remoteUser.equals("")) { >>> ? ? ? ?getLogger().warn("checkAuth: User cannot be authenticated (REMOTE_USER is null)"); >>> ? ? ? ?try { >>> ? ? ? ? ? context.getResponse().sendRedirect("/cas/login"); >>> ? ? ? ?} catch (IOException ioe) { >>> ? ? ? ? ? getLogger().warn("checkAuth: CAS Error. Let XWiki handle it. "); >>> ? ? ? ? ? return super.checkAuth(context); >>> ? ? ? ?} >>> ? ? } else if (remoteUser.equalsIgnoreCase("xwiki")) { >>> ? ? ? ?getLogger().warn("checkAuth: User is XWIKI (superadmin)"); >>> ? ? ? ?wikiname = "XWiki.superadmin"; >>> ? ? } else { >>> ? ? ? ?XWiki wiki = context.getWiki(); >> >>> ? ? ? ?wikiname = wiki.clearName(remoteUser, true, true, context); >> >> Are you sure wikiname (not a very good variable name ;) ) includes the >> "XWiki." prefix? >> >>> ? ? ? ?this.context.getWiki().createEmptyUser(wikiname, "edit", context); >>> ? ? } >> >>> ? ? context.setUser(wikiname); >> >> References are resolved relative to the current context: >> >> Foo ? ? ? ? ?-> currentWiki:currentSpace.Foo >> Bar.Foo ? ? ?-> currentWiki:Bar.Foo >> wiki:Bar.Foo -> wiki:Bar.Foo >> >> Hope this helps, >> Marius >> >>> ? ? return new XWikiUser(wikiname); >>> } catch (XWikiException e) { >>> ? ? getLogger().error("checkAuth: Cannot validate user. " + e.getMessage()); >>> ? ? throw e; >>> } >>> >>> Thank you, >>> Marco A. Gonzalez >>> _______________________________________________ >>> devs mailing list >>> devs(a)xwiki.org >>> http://lists.xwiki.org/mailman/listinfo/devs >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> > > > > -- > Thomas Mortagne > -- Thomas Mortagne

13 years, 10 months

[xwiki-devs] Integrating multiple Bonita webapps within a single Xwiki instance

by Eric Mousset

Hi everyone, I am new to Xwiki, although fairly used to the J2EE environment. I have searched Xwiki/Bontia/eXo sites and 3rd parties for answers to the following questions, without limited success so far. The context is that of a single Xwiki instance and multiple Bonita webapps. 1- Can Xwiki and Bonita integrate without using the eXo platform? I guess the answer is Yes; and one of obvious method is to simply integrate multiple Bonita webapps within the webapps directory of the Xwiki. Which leads me to question 2. 2- Assuming that Bonita webapps all contain a common set of libs (starting with the Bonita engine itself), is there a way to "factor in" these libs in the Xwiki libs (as opposed to have them embedded in every single Bonita webapp)? Many thanks, Eric

13 years, 10 months

[xwiki-devs] [GSoC 2011] Mobile Skin for XWiki Enterprise

by Mihai Paun

Hi! My name is Mihai Paun, a final year, soon-to-be Bachelor of Science student at the Faculty of Computer Science – Iasi and I would like to apply to GSoC 2011. I am interested in the proposed project, “Mobile Skin for XWiki Enterprise”. I am also a web developer with ~3 years experience working with a wide variety of technologies, both server-side and frontend”-side”. My weapons of choice have been PHP, Ruby on Rails, Velocity & Groovy (recently, since working on top of XWiki), writing cross-browser compliant code with HTML & CSS and enhancing the user experience with jQuery and prototype JS libraries. Mobile design & development has been the focus of my spare time research during the last year so I believe I have enough knowledge about the particularities and pitfalls of mobile web-apps, design constraints, platform variations and even device fragmentation. I am both an iOS and Android user, a fanboy of none, but a follower of good design principles and good usability, interaction and user experience guidelines. In few simple words, I have what it takes to build the best possible mobile web application for the XWiki platform. Thank you, Mihai Paun

13 years, 10 months

[xwiki-devs] Problem building XE

by K Konro

Hi guys, I have a problem running XE and can't solve it by myself. I have checked out the source, and did mvn install, and if I understand the Building documentation correctly this should be enough to run XE (I'm new to maven). But after the building ends (with status BUILD SUCCESSFUL), I have no jetty running. Also, near the end of build process such message shows up 4 times: [WARNING] Cannot include project artifact: org.xwiki.enterprise:xwiki-enterprise-jetty-hsqldb:pom:3.0-SNAPSHOT; it doesn't have an associated file or directory. I also tried to deploy the generated WAR but after opening up the webroot in browser a hibernate exception shows up about error in configuration file (I believe it can be related to the above). Also, when I tried to build XWiki Platform, it also succeeded, but when trying to quickly deploy app as in instructions (mvn install -Pjettyrun), I got a message about missing archetype, with name looking like not-processed or something: ${xwiki.db.jdbc.groupId}:${xwiki.db.jdbc.artifactId}:jar:${xwiki.db.jdbc.version} I followed the wiki instructions exactly, what am I doing wrong?

13 years, 10 months

[xwiki-devs] [proposal] Standardize a security specification.

by Caleb James DeLisle

Sometimes there is a grey area between a security vulnerability and a really nice feature. I think it is important that everyone understand what a user should be able to do and what a user should not be able to do since "that's not a bug, that's a feature" is cold comfort to a user who just discovered that his security requirements were not met. Also, having a standard laid down will allow us to better classify security issues if they are discovered (I can proudly say that we have improved here by leaps and bounds) I have a draft document which attempts to detail that line between bug and feature and I think it is time to move it into main space. http://dev.xwiki.org/xwiki/bin/view/Drafts/Security+Specifications WDYT? Caleb

13 years, 10 months

[xwiki-devs] XWiki Enterprise 3.0 Release Candidate 1 Available

by Marius Dumitru Florea

The XWiki development team is pleased to announce the release of XWiki Enterprise 3.0 RC 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is the first and hopefully the last release candidate for the 3.0 version. It brings several improvements to the features introduced in the previous milestones. The final release is planned for the beginning of the next week. The highlights of this release are: * Administration section for the WYSIWYG content editor * Attachment Selector Macro * Improvements to the message stream, dashboard, gallery macro, search suggest, extension manager and the administration application For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise30RC1 Thanks -The XWiki dev team

13 years, 10 months

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