Hi,
Here is the second email promised about the creation process.
The main issue is to allow to create without already having a page name
and to have automated page naming based on the user provided data and
rules associated to the creation.
http://dev.xwiki.org/xwiki/bin/view/Design/ApplicationWithinMinutesPageCrea…
This is an important part of the user experience and something we have
found to be not natural when developping applications.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
+1 (If my vote counts)
Martin
Marius Dumitru Florea <mariusdumitru.florea(a)xwiki.com> wrote:
>Hi devs,
>
>Do we have a specification for what a tag is inside XWiki? On
>http://extensions.xwiki.org/xwiki/bin/view/Extension/Tag+Application
>tags are defined as keywords but no constraints are specified.
>
>I'd like to enforce this two constraints on tags:
>* tags can't have leading and trailing white space characters
>* tags' case is saved but case is ignored when comparing two tags (once
>you defined a tag "news" you can't define a new tag "News"; the existing
>tag is reused; tag's case is used only for display)
>
>Optionally, we could enforce that tags can't contain white spaces.
>
>WDYT?
>
>If no one is against it then I'd like to change the UI to apply these
>constraints.
>
>Thanks,
>Marius
>_______________________________________________
>devs mailing list
>devs(a)xwiki.org
>http://lists.xwiki.org/mailman/listinfo/devs
Dear all,
I have submitted the proposal (XEclipse “RESTification”) before student
application deadline (April 8th),
However, until today, I do not get any comments on this proposal.
Clearly it will not be the case that the proposal is so well written
that no comments are needed.
In fact, I am worrying about the opposite side: the proposal has
fundamental issues and mentors do not want to comment about it.
If that is the case, I would like some one may point out the problems
and I will try to refine the proposal as soon as possible.
Best regards
Jun Han
Hi,
I want to know if there are any thoughts about the current Homepage of a
standard XWiki Enterprise Manager.
- What do you think of the current functionality?
- What do you think worths keeping or should be removed?
- What other functionality would you think would help the experience?
Thanks,
Caty
P.S. A similar thread exists also for XE Homepage
Hi,
I want to know if there are any thoughts about the current Homepage of a
standard XWiki Enterprise.
- What do you think of the current functionality: Welcome message, Spaces,
Tags, Activity Stream?
- What do you think worths keeping or should be removed?
- What other functionality would you think would help the experience?
Thanks,
Caty
P.S. A similar thread exists also for XEM Homepage
HI,
I have worked out an application for GSoC 2011. I need an idea whether it is
good enough for the submit?
Please point out anything you may think to be revised.
Regards,
-Kasun.
--
Kasun Nishshanka.
University of Moratuwa.
Moratuwa-Sri Lanka.
Hello all,
I've been working (and almost finished) a patch to fix the issue:Missing
default input focus and Enter key handling
<http://jira.xwiki.org/jira/browse/XWIKI-4383>
I have a question regarding point 1) Popups.
As far as I've seen in the custom lightbox that xwiki has, no global
event is fired when a lightbox "window" has finished loading, other than
only a onComplete function parameter which, is useful, but for this
specific issue, when talking about opening a popup, I see no reason why
to not have the first input element in that box selected by default. The
way I tackled the whole point 2) is by automatically selecting the first
input for the #admin-page-content object, solving all panels focus at
once. I wanted to implement the same functions for the popups, but can't
do that without a global event. Therefore I wanted to ask your
input/suggestions for this approach
Cheers,
Stefan
--
---------------------------------------------------------------
Stefan Mirea,
Webmaster @ Mercator College <http://mercator-college.org>
---------- Forwarded message ----------
From: Ecaterina Moraru (Valica) <valicac(a)gmail.com>
Date: Tue, Apr 12, 2011 at 15:32
Subject: Re: [xwiki-users] [Gsoc-2011] Project Proposal for Mobile Skin
XWiki
To: Avinash Parida <avinash3006(a)gmail.com>
Hi Avinash,
Unfortunately if you didn't enter your participation in melange, there is
nothing we can do to get you accepted in GSOC.
But you are very welcomed to participate as a member of this community in
the process: with feedback, patches, etc.
Thanks,
Caty
On Tue, Apr 12, 2011 at 14:49, Avinash Parida <avinash3006(a)gmail.com> wrote:
> Hi Caty,
>
> Sorry, I got late so couldnt submit the proposal in time on melange :'( .
> If possibly anything could be done then I would be glad to do or perhaps
> help in the project as an outsider. I will try next year perhaps as I think
> it wouldnt be possible to participate as I didnt sent it on melange.
>
> Regards,
> Avinash
>
>
> On Tue, Apr 12, 2011 at 1:42 PM, Ecaterina Moraru (Valica) <
> valicac(a)gmail.com> wrote:
>
>> Hi Avinash,
>>
>> The proposal was supposed to be sent by using melange
>> http://www.google-melange.com/
>>
>> and the email was more like a tool to receive feedback.
>>
>> Thanks,
>> Caty
>>
>> On Mon, Mar 28, 2011 at 12:52, Avinash Parida <avinash3006(a)gmail.com>wrote:
>>
>>> Hi,
>>>
>>> I am Avinash Parida , undergraduate final year from India . I am
>>> really interested to work with XWiki organization , and propose my
>>> project for GSoC 2011. I have attached an overview of the
>>> Project Proposal for Mobil Skin XWiki and my resume outlining relevant
>>> work experience and education . I feel my skills and knowledge in web
>>> technologies and design are of best utilization for this project.
>>> www.globaldelight.com/XWiki/Gsoc-XwikiProposal.pdf
>>> <http://www.globaldelight.com/XWiki/Gsoc-XwikiProposal.pdf%20>[Gsoc
>>> Project Proposal]
>>>
>>> I have also attached detailed mobile views for the project.These are
>>> initial
>>> layouts and am willing to make further iterations on remarks.
>>>
>>> www.globaldelight.com/XWiki/XWiki-Mobile-layouts.zip [Mobile Skin
>>> Layouts ]
>>>
>>> Please have a look at the proposal and i am ready for comments and
>>> fine-tuning it.
>>> Hoping for a positive response.
>>>
>>>
>>> Regards,
>>> Avinash Parida
>>> BTech 2011
>>> DA-IICT
>>>
>>> User Interface Intern
>>> Robosoft Technologies
>>> _______________________________________________
>>> users mailing list
>>> users(a)xwiki.org
>>> http://lists.xwiki.org/mailman/listinfo/users
>>>
>>
>>
>
>
> --
> Avinash Parida
> BTech 2007
> DA-IICT
>
> User Interface Intern
> Robosoft Technologies
>
>
Hi,
I was working on the XWiki Mobile skins initial iterations of layouts and themes and would like to discuss further on this topic.These are some of the UI views:
http://www.globaldelight.com/XWiki/xwiki-layouts.jpg [Overall feel and look]
http://www.globaldelight.com/XWiki/activity-page.jpg [Activity Page]
http://www.globaldelight.com/XWiki/edit-page.jpg [Edit Page]
http://www.globaldelight.com/XWiki/profile-page.jpg [Profile Page]
I am working further on creating more detailed versions and also flowcharts for the views.
On reading the previous threads I wanted to dig in on Development point of view. I thought of 2 options for the scope of this project and its purpose.
1. Making a browser based mobile skin only by using HTML5 + CSS + JS , velocity templates and fetching the data from REST or XML-RPC. The data can be also displayed by using Ajax making it a good web-app. But this does not allow the use of native capabilities like camera or notification as it resides on the browser.
2. The use of web-technologies for making cross-platform application with JS touch framework and porting framework.
The application needs to use the phones native features such as Camera API, Notification(Vibrate) , Geolocation, File Storage and much more which are not possible via simply an web-application so requires a porting framework.
Either PhoneGap or Appcelerator Titanium will be good but i have been following both and I want to point out a few things.
Advantages of PhoneGap
-MIT licence
-Easier testing in browser /simulator
-Support for iOS , Android, Symbiam, PalmOS
Advantages of Titanium
-Easy to get native looking app , native UI component
-Better performance
-can be extended to add native feature
Developing on PhoneGap or Titanium is not an ideal form considering XWiki is written in Java but solves the purpose of making it mobile compatible.
These allows the app to be natively packaged for different platforms like iOS , Android or Symbian. This way the app resides on the phone and only minimum data transfer is required. This would really enable to access XWiki on mobile devices in an appropriate way. The main focus is to access the main XWiki features. I am still working on fetching data using REST on the above porting framework , would be great if i could get more help on this.
Hope my ideas and opinions would be helpful. I would really appreciate comments and remarks towards this.
Regards,
Avinash
Hi,
I am looking for "xwiki" update features for example all xwiki user can do some update changes and this update can not update the existing application until admin is not approved the changes once admen approve the changes then its affect the application. Can you guise please help me how to achieve this features in xwiki applications.
Thanks & Regards
_______________________________________
Jitendra Kumar | Capgemini | Bangalore
Consultant | EFH-Luminant | Portfolio Management
jitendra.kumar(a)capgemini.com
Direct: +91-80-6656- 7000 extn: 805 8011
Voip: 312-799-7777 Extn:8027726
_______________________________________
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to
read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message
in error, please notify the sender immediately and delete all copies of this message.