xwiki-devs April 2011

xwiki-devs@xwiki.org

39 participants
91 discussions

[xwiki-devs] About Comments: Hasitha Abeykoon's GSOC Proposal

by Hasitha Abeykoon

Hi Marius Dumitru , Sorry for the latency in reply. I had an interview today at Virtusa. What i meant by - mapping a particular word with another word is "Once a word is typed auto complete replaces it with another word which is defined by user " - mapping a particular word with a specific font is "Once a word is typed auto complete format it with a predefined format for that word by user " Is there anything else I should change in my proposal? Any new comments are highly appreciated. Thank you. -- *Hasitha Abeykoon,* *Department of Computer Science & Engineering,* *University of Moratuwa. * * * *Skype: foreverhasitha*

13 years, 8 months

[xwiki-devs] Asking For Comments:

by Hasitha Abeykoon

Hi Marius Dumitru , I have done a proposal for the project idea of "Auto Completion in Content editors" on the melange site. Please provide me with your valuable comments on that proposal. Thank You. -- *Hasitha Abeykoon,* *Department of Computer Science & Engineering,* *University of Moratuwa. * * * *Skype: foreverhasitha*

13 years, 8 months

[xwiki-devs] [VOTE] Group commons-pom, commons-tools and commons-core together

by Vincent Massol

Hi devs, The idea is to have the same version and same release for everything related to commons. Rationale: * Stop the spread of a git repos (see https://github.com/xwiki). * Make it even easier to release. Only one command to release the whole xwiki-commons * No need for git modules (svn externals previously) The proposal is: xwiki-commons/ (git repo) |_ xwiki-commons-pom/ |_ xwiki-commons-tools/ |_ xwiki-commons-core/ |_ pom.xml Details: * xwiki-commons/pom.xml contains everything that's currently in xwiki-commons-pom/pom.xml *except* the parts related to the tools (license and verification) * xwiki-commons/pom.xml has an artifact id of "xwiki-commons" * xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as parent and adds the parts related to the tools (license and verification) * xwiki-commons/xwiki-commons-pom/pom.xml has an artifact id of "xwiki-commons-pom" * xwiki-commons/xwiki-commons-tools/pom.xml uses xwiki-commons/pom.xml as parent * all other git repos uses "xwiki-commons-pom" as their parent Note that for JIRA we would have 3 jira projects to make it easy for users (because jira doesn't allow nested components): * XWiki Commons POM * XWiki Commons Tools * XWiki Commons Core Note that if we agree we would do the same for xwiki-platform (ie move platform tools in xwiki-platform). Here's my +1 Thanks -Vincent

13 years, 8 months

[xwiki-devs] Proposal "Auto Completion in Content Editors" has been refined

by 许凌志(Jamesxu)

Thanks for Sergiu's advices, I have refined my proposal in two aspect: 1. Add "bonding" period in my timeline from April 22th to May 22th 2. Details the technologies of ajax used in front end in both editors, as suggested by Sergiu, in xwiki editor, the ajax for communicating with server side could be implement by prototype, and the code should also be used in WYSIWYG editor by using GWT JSNI to invoke in the GWT code. -- 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, 8 months

[xwiki-devs] GSoC: AJAX Form Editor

by Omar Lopez Orendain

Hi Everyone! I'm a third year student from Mexico, the proyect AJAX form Editor sounds pretty good to me, i have a PHP5, XHTML/CSS, JavaScript, Jquery,Python and some ruby background. i did some stuff working with Drupal (plugin managment, edit views, etc.) this as part of my social service, no big deal and currently developing something call "interactive book" as part of a academic final proyect, here i help to a PhD student to implement some interactive functionalities to his work (using Jquery mostly ). I found excited this AJAX form editor proyect, 'cause this could be a pretty nice oportunity to implement/work with AJAX so, i would like to know what you guys expect regarding this?... I was cheking out the within minutes page, and i wonder if the "form editor" just gone be an extension of the "whitin minutes proyect". Or what is the relation between them. Cheers! :) -- Omar R. López Orendain

13 years, 8 months

[xwiki-devs] Project Proposal XWiki for GSoC 2011

by Kasun Nishshanka

Hi, I am a student of University of Moratuwa Sri Lanka, currently following my Chemical and Process Engineering degree. Although I'm not a computer science student I found it is a very interesting subject, especially Java programming. I have experience in developing Java programs and web based application using JSP technologies. Last year got the chance to play with the xWiki and I must say I really enjoyed working with it. So I thought it is better if I can participate in the XWiki project through the GSoC 2011. Recently I had my 3rd semester end exam and was unable to send an application earlier, since my exam is now over and having two months of vacation I'm pretty sure that I can successfully participate in a project for XWIki. I looked at the project ideas in your web site and found some of the ideas are quite interesting. I'm interested in the following two ideas. Add support for parameters types in Wiki Macros Structural Search and Replace I really appreciate your feed back and guidance on this matter. Kind Regards, -- Nishshanka Kamburugamuwa. University of Moratuwa Moratuwa, Sri Lanka.

13 years, 8 months

[xwiki-devs] [Discussion] Template provider action after create

by Luca Anca

Hi devs, since I fail in all the ways to get a dashboard to be editable when editing it after creation from a template, I would like to know what you think of the next idea: We add a field to the TemplateProvider to specify what should be the action on creation from that template: "save & view", "save & edit", or "edit". Let me explain what first option would mean and then you'll figure out the other ones. When you have a template provider with "save and view" action on creation the following will happen: 1. click the add button 2. choose a template & fill in the page & space name 3. click create 4. the document is created and saved, and the user is being shown the document in view mode. The current implementation is "edit", which means that at point 4 in the list above no document is saved, the user is being shown the new document is edit mode, and until he hits save the document is not saved. I think it's a nice to have feature, since for other templates it might make sense that the document is, actually, created (and saved). Since a document created from a template already has content, it has meaning and data. ** The only major drawback** I see with this is that, looking at the create form, the user will not know what will happen when he clicks "Create", since it will vary according to his choice of template. We might fix this by adding this information under the template name in the list of templates in this form. What do you think about this? is it a nice feature to have? Thanks, Anca

13 years, 8 months

[xwiki-devs] [tomcat_home]\work\Catalina\localhost\xwiki

by Iola Hagen [ioh]

Hi I have an installation of xwiki enterprise running on windows 2008 with tomcat 6 and xwiki 2.1.1.25889 and recently I have noticed a [tomcat_home]\work\Catalina\localhost\xwiki folder which contains folders with names such as 0bRde345 which contain attachments. This work folder is growing very large, I understood that the attachments are stored in the database so I wonder if you could let me know what is causing the sudden growth if these files? Cheers Iola

13 years, 8 months

[xwiki-devs] GSOC 2011: Google Android Client

by Robert Kruszewski

Hi I've just submitted my proposal regarding google android client, sorry for such late submission. However, I've been trying to incorporate comments previously mentioned in the discussion. I would be very thankful for any comments. Regards Robert Kruszewski

13 years, 8 months

[xwiki-devs] [Discussion] Customize button for the dashboard

by Luca Anca

Hi all, I've got some suggestions that the current way of editing the dashboard is not really intuitive (Edit -> Inline Form), and mainly because users wouldn't necessarily look under "Edit" for a method to change the dashboard. Also, other users that I've observed, forgot that they need to go in some edit mode before changing things. I also agree that without documentation no user would figure out that editing a dashboard is under Edit -> Inline Form. While editing will still remain "in inline mode", from the technical pov, we need to provide a easier way for users to discover this. Let's look at the following options: 1/ Add a "Customize" menu entry under edit, in the page menu, as proposed in the mockups from Cati, a long time ago: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/GadgetsDashboard . 2/ Add a "Customize this dashboard" button in the dashboard in view mode, in the top right corner, something like http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/oldDashboa… but styled better to integrate with the current dashboard. 3/ Define and implement a mechanism to allow the inline form edit to be triggered for a document without that document having to include a document which has an object in it. E.g. as Vincent proposed at one point, trigger inline mode when an object is present in the current document. I should note that solutions 1 and 3 still assume that the user will go to "Edit" to try to customize the dashboard, which can also be problematic (I cannot figure it out for sure right now, we need fresh users or proper UX expertise which I don't have). WDYT? Thanks, Anca

13 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 April 2011