xwiki-devs December 2009

xwiki-devs@xwiki.org

32 participants
100 discussions

[xwiki-devs] [UX][Proposal] Action Menu in Edit Mode

by Ecaterina Valica

Hi, We should replace the "Choose Editor" panel by using the Action Menu also in Edit Mode. Please comment on this and select your favorite variant: A, B, C, D, E http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ActionMenuEditImpr… Thanks, Caty

14 years, 7 months

[xwiki-devs] [VOTE] Where to put the new Recycle Bin UI

by Sergiu Dumitriu

Hi devs, I committed a friendly UI for viewing the contents of the recycle bin (just for documents, for the attachments there are some API changes needed), and I was wondering where to put it. Right now it adds another tab in the AllDocs wiki index, called "Deleted Documents", and I'm not sure if it's the best thing to do. + it's one place where all the things in the wiki can be seen + it's easy to find - the AllDocs page is getting crowded (another tab won't fit on small displays) - the recycle bin is not exactly a place with valid wiki documents A possible improvement would be to rename the new tab to Trash and also add the deleted attachments in there, as another table. An alternative would be to add a new page similar to AllDocs, called Trash, and which would have tabs for all the recycle bins. This could be linked from the QuickLinks panel only for admins, and from the "This document does not exist, there are versions in the [recycle bin]" message. -- Sergiu Dumitriu http://purl.org/net/sergiu/

14 years, 7 months

[xwiki-devs] [Proposal] [GSOC] Wiki Importer Enhancement

by Arun Reddy

Hi Devs, As the existing Wiki Importer ( GSOC PROJECT - SANDBOX <http://svn.xwiki.org/svnroot/xwiki/sandbox/gsoc/importexport/>) have few set backs in architecture, i would like to make a proposal to modify and enhance to make it better. Here is my proposal : http://gsoc.myxwiki.org/xwiki/bin/view/Import+Export+other+wikis/Wiki+Impor… - A new Wiki model api ( Wiki, Wiki Page, Wiki Page Revision, Wiki Attachment ) which adheres to XWiki Standards. - Separation of Import process, Parsing the import data into a abstract wiki model will be a component. Clients can use it to make their own custom implementation. This abstract model is used by the other XWiki component / client code (Groovy & velocity ) to load the data into XWiki with standard features and little customization (like Preserving history, default names, attachments etc.. ). - Using the existing XWiki model api or xwiki-bridge rather than coming up with a new one. But the issues here is, i dont have all the things which are needed and it has lot more methods which are of no use in import process. Can i proceed with a custom wiki model like this. ? - As wiki importer process large streams of data, would it be wise to design the API more stream oriented and include few stream oriented methods.? I would like to have your suggestions on this. Thanks -Arun Reddy

14 years, 8 months

[xwiki-devs] Smart GWT 2.0 released

by Vincent Massol

fyi, mostly for our wysiwyg developers: http://www.ongwt.com/post/2009/12/15/Smart-GWT-2.0-has-just-been-released Thanks -Vincent

14 years, 8 months

[xwiki-devs] [Proposal][Model] Entity References - Absolute vs Relative

by Vincent Massol

Hi devs, I'm almost done with my entity reference refactoring and I've just realized I have missed something I think. So far the implementation only supports Absolute references (i.e the entity reference factory always return a reference with all parts filled - you choose to use a default factory or a current entity depending on how you wish to resolve the names when they have not been provided in the passed reference string). I now think we must also support relative references (i.e. when some parts can be null) and that it's up to the user of the api to decide if they want to convert a relative reference to an absolute one or not. Here's a use case: renaming of documents. For exemple documents have links specified as a string representing the target doc name. If we don't have relative references then we need to decide if we want to use the default serializer (all parts printed including wiki name) or the compact serializer (only parts different from context reference printed). This doesn't support printing only what the user had decided to fill. For ex a user might have specified voluntarily the space and page name and right now with my implementation he'll get only the page name specified if the new space is the same as the space for the current doc. So here's my proposal: * Entity Reference Factory leaves parts to null when not specified in the string representation. * We add a EntityReference.getAbsoluteReference(EntityReference base) method to return an absolute reference. It's resolved against the passed base reference (i.e. parts not specified are taken from it) WDYT? I'm going to start refactoring my code to do this later today so please let me know if you see any pb with it. Thanks -Vincent

14 years, 8 months

[xwiki-devs] XML Encoding for Application Development

by Andreas Schaefer

Hi For the development of the Groovy based Blog I just developed the code in IntelliJ, copied inside a browser and eventually exported the content into a XAR file. Slowly but surely this is getting way to much work especially when doing sweeping changes. Because I don't use Eclipse I am not able to use the XEclipse tool but I was wondering if anybody knows a way to XML encode text (within Maven2) so that it later could use Ant's copy and filter tool to incorporate the developed code / content inside the XML file that will build up the XAR file. Thanks - Andy

14 years, 8 months

[xwiki-devs] [VOTE] Strategy for handling translations

by Vincent Massol

Hi devs, We need to define a strategy for better handling translations. I've had a call with Guillaume and Jean-Vincent and here's the process we'd like to propose: * One person is in charge of http://l10n.xwiki.org/. This means monitoring the work there, coordinating validation of key values and ensuring validated translations are incorporated in the source tree. Guillaume is willing to take that role for now. * The XE release manager has the responsibility of taking the validated keys on l10n.xwiki.org and committing them during the Milestone 2 dev (before the RC1). * The l10n manager should ping the release manager whenever there are translated and validated keys ready to be incorporated or if there have been important changes to be included in the release after M2 has been released. * The l10n manager should test XE and the applications after the keys have been applied to ensure quality. Basically the l10n manager is responsible for the quality of translations in general. Here's my +1 Thanks -Vincent

14 years, 8 months

[xwiki-devs] XText

by Vincent Massol

This looks nice: http://www.eclipse.org/Xtext/ What is it: http://www.eclipse.org/Xtext/documentation/latest/xtext.html#Overview Not sure it's powerful enough as a grammar for our wiki syntax needs though but maybe interesting to check out. The Eclipse integration looks very nice. Thanks -Vincent

14 years, 8 months

Re: [xwiki-devs] [xwiki-notifications] r25984 - in contrib/sandbox/xwiki-officepreview: . src/main/java/org/xwiki/officepreview src/main/java/org/xwiki/officepreview/internal

by Sergiu Dumitriu

On 12/31/2009 08:39 AM, asiri (SVN) wrote: > Author: asiri > Date: 2009-12-31 08:39:16 +0100 (Thu, 31 Dec 2009) > New Revision: 25984 > > Modified: > contrib/sandbox/xwiki-officepreview/pom.xml > contrib/sandbox/xwiki-officepreview/src/main/java/org/xwiki/officepreview/OfficePreviewVelocityBridge.java > contrib/sandbox/xwiki-officepreview/src/main/java/org/xwiki/officepreview/internal/OfficePreviewVelocityContextInitializer.java > Log: > [misc] Changing all platform dependencies to 2.1-SNAPSHOT version. > > * This will make it possible to use xwiki-officepreview with XE 2.1.x versions. > > * Downside is that xwiki-officepreview will not be able to preview Office 2007 documents (support for which was added in xwiki-officeimporter 2.2M1). Why make it compatible with 2.1.x, when it comes with the price of reduced functionality? From what I see in the commit, you switched to older APIs that are deprecated in 2.2, which means that a new module will be released with deprecated code already, and at some later time it will be harder to migrate, once more code is written. -- Sergiu Dumitriu http://purl.org/net/sergiu/

14 years, 8 months

[xwiki-devs] Paul-Iosif Guralivu wants to stay in touch on LinkedIn

by Paul-Iosif Guralivu

LinkedIn ------------ Paul-Iosif Guralivu requested to add you as a connection on LinkedIn: ------------------------------------------ Guillaume, I'd like to add you to my professional network on LinkedIn. - Paul-Iosif Guralivu Accept invitation from Paul-Iosif Guralivu http://www.linkedin.com/e/9s_c-0fN05p6qjQq9meQgfVB/blk/I1690300468_2/pmpxnS… View invitation from Paul-Iosif Guralivu http://www.linkedin.com/e/9s_c-0fN05p6qjQq9meQgfVB/blk/I1690300468_2/39ve3o… ------------------------------------------ DID YOU KNOW LinkedIn can help you find the right service providers using recommendations from your trusted network? Using LinkedIn Services, you can take the risky guesswork out of selecting service providers by reading the recommendations of credible, trustworthy members of your network. http://www.linkedin.com/e/svp/inv-25/ ------ (c) 2009, LinkedIn Corporation

14 years, 8 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs December 2009