Hi all,
Here I have attached some mock GUIs and a very intuitive requirements spec
that illustrate the
basic workings of XWiki-Eclipse plug-in. It's better if we can finalize
these drafts soon because I
need to go on with the development :). I have few doubts on the java package
structure as well as
about the icon graphics for the plug-in (i thought of re-using eclipse's
ones where suitable).
I went through XWiki XML RPC APIs and am comfortable with thw way they work
(had to
sharpen my SWT skills too). I'm looking forward to hear from you..
- Tharindu
Hi
In Albatross skin, by default, the edit window is quite small. A big part of
the screen real estate is taken up by the XWiki Document information panel
on the right, the header and footer.
Some wiki's have a feature by which the editor can be popped into a seperate
window which can be maximised. Some others let you increase the editor area
as much as you want.
This would make edits of larger pages much easier, and you can focus on
editing the document rather than scroll continuosly up and down.
I had posted a screen shot of this problem sometime back.
How easy is it to make this change? And is the popup editor feasible with
XWiki architecture?
Thanks
Shiva
--
View this message in context: http://www.nabble.com/Feature-Request%3A-Maximize-edit-window-tf3913467.htm…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
I'm writing a treeview (using the yahoo treeview javascript api) to
display the list of all pages of a wiki and in order to have good
performances I need to call a server-side method for getting all
children pages of a given page (so that the nodes or the treeview are
loaded dynamically). In order to implement this I thus need a new
XWiki Action.
Now I think it would be good to generalize this common need. As we
add more Ajax to our UIs we'll need more and more calls from JS to
the server side.
I'm thus proposing a generic ExecuteXMLAction (or AjaxAction or
another name) that would do the following:
* Get the class, method and parameter to execute from the HTTP request
* Verify that the class is in the api package (to prevent security
issues)
* Call the method using introspection
* Return the result as XML using XStream (it generates automatically
XML from any java object)
Note: I'd need to define the format for sending the information in
the request. Not sure about which format to use.
WDYT?
Thanks
-Vincent
Hi,
When I use the new page panel in XWiki 1.0 final to create a blog post,
I found that the new blog post has been created in the Blog space not
Current space (noted at bottom of the panel).
I did some look in the calling, and I found that equalvalent is adding,
e.g., following line after a page link:
?xpage=create&tocreate=post&title=testblogcreation
also I did a test on the xwiki.org page:
http://www.xwiki.org/xwiki/bin/view/Main/WebHome?xpage=create&tocreate=post…
which should result in create a new page at Main space but I got
directed here:
http://www.xwiki.http://www.xwiki.org/xwiki/bin/inline/Blog/testblogcreatio…
see, it's not Main.
test for "tocreate=page" result in right place.
thus I doubt that the code for "tocreate=post" has some where miss the
space parameter.
as we need use the "new page" panel tool for creating blog posts in the
calling space, anywhere I can get into solving this?
Thanks in advance!
Muzi
Hi friends,
I'm planning to use XWiki on a lab as a Documentation Tool. The Access to
the Wiki would be restricted... so, people could only be added by an
Administrator.
By default, anyone who clicks on Register link on XWiki main page can
Register itself. I tryed to change the Acess Rights of the Register Page
(I`ve added XWikiAdminGroup with full acess to Register Page and XWikiGuess
Denyed), but nothing changed... anyone can still register anyperson. I've
already tried many things on AcessRights but I'm not able to see what's the
problem. The rights on Register Page seems to never change.
I really need to restrict the rights on Register Pages.
May anyone, please, help me?
cheers
Jonas.
--
JONAS FURTADO DIAS
>> jonasdias(a)gmail.com
Hello again, and here's my progress report:
I need the Google gdata api integrated into xwiki to help me with my task of
developing Google Docs capabilities for XWiki.
The gdata api can be downloaded from:
http://code.google.com/p/gdata-java-client/ (other programming languages
available, but I believe we need java, right? :) )
Upon build, said api exports about a dozen jars into it's lib folder, of
which (I believe) I only need 3: gdata-base, gdata-spreadsheets and
gdata-client (might need others too, not sure, since I can't attempt to
build right now - the gdata api requires JDK 1.5 to build). Those jars need
be added to the xwiki lib folder and updating of build.xml and pom.xml as
necessary.
>From my observation, Google updates this api frequently (2 weeks?) so it
would be really nice if we could actually include the gdata download and
build process into svn / building xwiki (not sure if it can <or should> be
done, since I am not up to speed with how the whole svn building is done).
If there are any other details required, do ask, and I'll do my best to
answer ASAP.
Have a nice day,
Radu
Cheers guys!
I need help with something: I need to add a couple of fields to the
registration form (google user and password for Google Docs), but I can't
find the darn sources responsible for generating that page or any user
management tools (tried spotlight-ing them, searching with eclipse, and
still nothing), please hint me at them.
Thanks for your time,
Radu Danciu
Hello,
How can I get in java the value of an input build with apache.ecs.xhtml? I searched an hour or so on google and haven't found anything related to that.
E.g:
input hidden_input = new input();
input.setID(prefix + name);
...
and at a certain moment its value changes (with javascript). Then I need its value in java. Maybe there is a way to get it using xwiki api somehow...
I would be very thankful for an answer. Thank you very much.
Evelina
Hi,
XWiki Watch is a GWT based Feed Aggregator with collaborative features.
It has the following features:
- Feeds, Groups and Keywords configuration using an AJAX interface.
Configuration are managed by spaces.
- Storing of articles themselves in XWiki pages using the FeedPlugin's
capabilities
- AJAX UI to navigate articles, open the content
- Collaborative tagging, commenting and flagging of articles, store a
'read' status
- Filtering UI to see only articles from a group, a feed, only flagged
articles, matching a keyword, etc..
- TagCloud of tags applied to articles
- Text analysis feature on the content of articles matching a filter
- Press Review feature allowing to generate an HTML or PDF page listing
articles and comments matching a filter
- Look and Feel adapted to the Albatross skin by Laurent Lunati !
- Packageable as an XWiki Application (xar) that can run on XWiki 1.1M2
(currently the trunk) with correct plugins activated (FeedPlugin,
AutoTag, ZipExplorer)
XWiki Watch is based on the new GWT App framework included in the XWiki
Core GWT API (XWIKI-1334)
Some code I will propose to move to the core GWT API (A choice dialog
and a Wizard manager)
I'd like to propose a vote for:
1/ Create a new project XWiki Watch
2/ Opening the developement of XWiki Watch (build documentation, provide
a RoadMap, etc..)
3/ Decide where to commit it
4/ Decide weather or not to provide a different dev and users lists
Ludovic
--
Ludovic Dubost
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
AIM: nvludo Yahoo: ludovic
