Hello,
I'm currently reading about XWiki and XEclipse and would like to ask if
there is any consensus about XWiki pages templates which might also be
usable from XEclipse probably after some code hacking on its plugins.
I'm currently working on some project for my client (source code will be
contributed/available later in the project stage) where there is a need
to use XEclipse and enhance it to support some predefined
forms/templates for web pages creation. So far I've found just XWiki FAQ
tutorial on
http://platform.xwiki.org/xwiki/bin/view/DevGuide/FAQTutorial which
tries to deals with some kind of templates. However this looks quite
general at least so far to me and so I would like to ask the question
above about consensus where and how to go with templates in xwiki/xeclipse.
My current idea is to stick with the XWiki server as a provider of
templates to preserve ability to use templates from both browser and
xeclipse and to enhance xeclipse new page creation wizard to provide a
list of available templates on the server side...
Thanks for any idea where to start or where to look for more information
with regarding to this project task.
Karel
Hi All,
Is it possible to search(or get) a page in xwiki by its title through
RESTfulAPI?
I read in the forum that through RESTfulAPI we can only retrieve every page
in a space and check whether page with given title exists.
Or is it not the case?
Any help would be really appreciated.
Thanks,
Manish
--
View this message in context: http://xwiki.475771.n2.nabble.com/Searching-page-by-title-in-space-through-…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Salute!
Let me present you one of the largest worldwide enterprises where I work as a manager of HR department.
Our company is dealing with a great number of different fields, such as:
\ real estate
\ logistics
\ supporting in opening of banking accounts
\ etc.
And our company currently has vacant positions of regional managers in Europe:
- payment 2300 � +bonus
- max 3-4 business hours a day
- flexible working schedule
If you�re interested, please provide us your contact information in order we could contact you for further communication. Jordan(a)europ-joblist.com
Attention! We are recruiting only those who have a right to work in Europe!
We will be very happy to have you join our professional team.
Hello,
My question is about personal data management in XWiki.
How and where can I store personal data?
For example a user could have a different skin from the other users when
he logs in, or different documents (with personal content).
I'd like to know how to do it.
Thanks,
Marie
Hi guys (especially Ludovic and Thibaut),
I read [1] and [2] and I have a few questions. I would like to know very
clear what UI/UX platform changes are you proposing independent of the
Application Within Minutes.
(A) Page creation
1. Unique page name
Currently if you specify the name of an existing page in the default
create page form you get an error message saying that the specified page
already exists. Do you propose any change to this? Should we instead
create a page with a similar name based on a specified strategy (e.g.
MyPage1, MyPage2, with a simple counter strategy).
2. Skip page name
Do you propose to remove the page name field from the default create
page form (triggered from the Add > Page menu) and to automatically
generate it from the title (using the default naming strategy)?
3. Implicit location
Do you propose to remove the wiki/space fields from the default create
page form and instead always create the page in the current wiki/space?
i.e. Add > Page menu will add the page to the current wiki/space.
4. Implicit template
Currently template providers can be limited to a list of spaces. Do you
propose to automatically use a template provider if it is the only one
defined for the current/selected space?
5. Create sheet/template
Are you proposing to have a (slightly) different form even for plain
wiki pages? e.g. replace the "Save & Continue" and "Save" buttons with a
"Create" button. What other differences do you propose?
-----
I talked with Caty about this and she is against 3. and 4. She would
improve the current create page form by:
* displaying all the templates independent of the current space
(currently we display only the templates that can be applied to the
current space although we can create the page in a different space)
* when a template is selected, limit the list of spaces from the space
selector so that the user can choose only a space where the selected
template can be applied.
(B) Display Resolution
(1) Remove the "inline" editing mechanism
What do you propose to do with the "Edit > Inline form" menu seen by the
advanced users? Should we keep it and just replace the URL? What about
simple users, will they be noticing any difference (since we already
have just one Edit button that points to the proper edit mode)?
(2) Sheet parameters
Do you mean velocity variables defined in the sheet code? This will work
only if the variables are used after the sheet code is evaluated.
(3) Display Resolution Rules
I could find fields for specifying display sheets (defaultViewSheet and
defaultEditSheet) only in BaseClass (old core). XWikiDocument doesn't
have any. This makes sense because sheets are in fact *class* sheets.
That is, you write a sheet for a specific class, you don't write it for
a specific document. Have I understood correctly that you want to be
able to create a sheet for a document (not a class)? This could be
useful for documents that have multiple objects and you need a sheet
that displays data from all the objects (using the class sheet of one of
the object types is not enough).
Thanks,
Marius
[1]
http://dev.xwiki.org/xwiki/bin/view/Design/ApplicationWithinMinutesPageCrea…
[2]
http://dev.xwiki.org/xwiki/bin/view/Design/ApplicationWithinMinutesCoreChan…
Hi, According to the discussion with Marius, I list the work plan for this
week(6.27-7.3).
Implement the skeleton of the auto-suggestion functions include following
things:
(1). Implement the function that logs a message in the firebug console
whenever the caret is after [[ (but just that, nothing more!)
(2). Implement the function that requests the list of wiki pages matching
some prefix user input. BUT, don't actually query the database, instead
simply return a dummy list from the server.
(3). Implement the function that displays the list of wiki pages where the
caret is, but using just a plain HTML list inside a DIV. *Nothing fancy*. No
CSS!
All these three things covers all the proccesses of the auto-suggestion
functions, it will give an overview of the whole projects, and the rest of
work will refine the skeleton gradually later.
--
Best wishes,
许凌志(Jame Xu)
MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University
Department of Computer Science and Technology, Xi’an Jiaotong University
Hi,
The proposal is to make all click methods be named click*() in UI functional tests.
For example in ViewPage, instead of:
public LoginPage login()
{
this.loginLink.click();
return new LoginPage();
}
We would have:
public LoginPage clickLogin()
{
this.loginLink.click();
return new LoginPage();
}
Right now we have some methods starting with click and other not following this pattern, the idea is to homogeneize it.
WDYT?
Thanks
-Vincent
Hi, These days with the help of Marius, I seperate my codes into
sub-modules, and commit them with their test modules one by one
In last week I have committed two modules:
1. suggestion box for link (
http://farm6.static.flickr.com/5268/5599744930_ff65ddfdc3_z.jpg)
2. suggestion box for image (
http://farm6.static.flickr.com/5063/5600563446_5f15f500d1_z.jpg)
I have also written a readme document in the same dir of the two modules, to
guide developers to run and test the modules seperately.
--
Best wishes,
许凌志(Jame Xu)
MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University
Department of Computer Science and Technology, Xi’an Jiaotong University