Hi community !
The second XWiki DocHour is planned on Thursday 19th of June.
So what is this DocHour thing ?
Here is the rules:
* 1 hour
* You choose at what time you want to work on the documentation.
* On xwiki.org
* You choose to document what you want. Ideas of missing documentation:
- In JIRA: http://tinyurl.com/3xtn8t
- Improve existing documentation
- XWiki Watch documentation on http://watch.xwiki.org
- XEM Documentation on http://manager.xwiki.org
- XWiki Workspaces Documentation http://workspaces.xwiki.org
* Make sure you create a jira issue for the work you're doing and
assign to yourself. The issue should be created in the XWiki Core
project, with a "documentation" component. Don't forget to tag it as
"dochour20080619" to be listed in the result of this event.
* If you can't do it on the the planned date, then you can still do it
on another day, as close as possible to the the 19th of June ;)
* The idea is to repeat this event every month or every 2 months.
You can look at the result of previous DocHour at
http://markmail.org/message/dm3kclit4g4s472v
Thanks everyones and hope we will soon have to allocate more space to
xwiki.org database ;)
--
Thomas Mortagne
On Jun 18, 2008, at 6:32 PM, tmortagne (SVN) wrote:
> Author: tmortagne
> Date: 2008-06-18 18:32:27 +0200 (Wed, 18 Jun 2008)
> New Revision: 10412
>
> Modified:
> xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/
> java/com/xpn/xwiki/export/html/HtmlPackager.java
> xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/
> java/com/xpn/xwiki/pdf/impl/PdfExportImpl.java
> xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/
> java/com/xpn/xwiki/plugin/charts/ChartingPlugin.java
> xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/
> java/com/xpn/xwiki/plugin/graphviz/GraphVizPlugin.java
> xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/
> java/com/xpn/xwiki/plugin/image/ImagePlugin.java
> xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/
> java/com/xpn/xwiki/plugin/svg/SVGPlugin.java
> Log:
> Revert XWIKI-2483 (Lots of code don't take care of "xwiki.temp.dir"
> when a temporary directory is needed)
Explanation: I've asked Thomas to revert since I think this could be
dangerous for our stable 1.4 branch and it's not an important bug
anyway so it's better not to take the risk.
Thanks
-Vincent
Hello Devs,
We have already slipped by one more week :( I underestimated the work
needed for invitation management.
Now we are about to be ready, thus I call a vote for releasing XWiki
Workspaces 1.1 Milestone 2 tomorrow, with the following release notes :
http://tinyurl.com/4dnbzf
My +1
Regards,
Jérôme.
Hi everyone,
This is our second bug fix day. Let the fun begin and let's try to
break our previous record of last time (see http://tinyurl.com/6j6rvj
for details) :)
Here are the rules:
* Every Wednesday all XWiki devs should work on fixing bugs only.
* If they're not free on Wednesday they should do it on another day in
the same week
* The bugs should be taken in this order:
a) bugs with patches available
b) bugs planned for the current release. For example for 1.5M2 it's: http://tinyurl.com/5s2fjv
c) bugs with the most votes: http://tinyurl.com/28yqvv d) bugs with
higher severities
Note that the URL i've given are for XWiki Core but the same applies
for all JIRA projects and products.
Right now we're planning to do this for Core, XE and XEM. I hope that
this can be extended to other products such as Watch/Workspaces.
Everyone is invited to help out and not just committers:
* contributors can send patches
* users can vote for their most important issues
* bug reporters should be ready to verify that the fix does solve
their problem
Thanks
-Vincent
hi vincent/fabio
I have completed the first version of the sample plugin for xwiki syntax
colouring.But when i try to commit it to the sandbox I'm getting the
following error
First I checkout the plugin folder by svn co https://malaka@svn.xwiki.org/svnroot/sandbox/plugins/ xwiki-sandbox-plugins
then add my folder to the xwiki-sandbox-plugins folder and add it to the
svn.when I try to commit my work by "svn co" it asked for the password
.After entering the password it gives the following error
svn: Commit failed (details follow):
svn: MKACTIVITY of
'/svnroot/sandbox/!svn/act/38ca4be0-0b6d-48c2-a151-04a2374fb9e3':
500 Internal Server Error (https://svn.xwiki.org)
svn: Your commit message was left in a temporary file:
svn: '/home/malaka/xwiki-repo/xwiki-sandbox-plugins/svn-commit.tmp'
--
Malaka Ekanayake
CSE UOM
On 17 juin 08, at 21:13, Venkatesh Nandakumar wrote:
>
> Hi,
>
> Since my last mail to you and the list, this is what I've implemented.
I am replying to the list.
>
> 1. Double Click Strategies :- double click selects appropriately
> according to wiki syntaxes....
> 2. Advanced Indentation strategies, like for <dl> tags, enumerated
> lists, new paragraph assist, etc.
> 3. Word wrap functionality, goes in hand with new paragraph assist.
> (minor)
> 4. Code completion Assists, for egrecognises different enumerated
> lists,
> and automatically inserts it.
> 5. Minor font change functionalities added to go in hand with syntax
> highlighting
> And the code, still has been implemented as a eclipse plugin.. Though
> I'd soon be integrating it with xeclipse. If possible, could you set
> me
> up an account in the svn repository, and set up a separate branch
> where
> i would have commiting rights, so that I could upload my present work
> and show them to you?
>
That's cool!
Malaka who is working on this has also implemented an editor with
initial syntax highlighting and he'll commit it soon.
I cannot open accounts on the SVN repository so you must ask Vincent
or someone else who has administrative rights for doing so.
> Again Sir, What other functionalities are intended, like groovy/
> velocity
> support, and where do I get information about its syntax etc?
> Is there any other functionality that I have missed out?
>
Here we have to decide how to split the work because there is too much
overlap.
Starting from what Malaka and you have achieved until now I propose
the following:
1) Malaka could concentrate on XWiki parser integration in the Eclipse
text framework as previously discussed with Vincent here on the list.
2) You might discuss with Stephane to concentrate more on your
project's objective that, if I am not wrong, are more semantic-web-
related.
3) Both of you, since you are now expert on this field, could work
together with us in order to integrate advanced feature, such as
support for advanced sub-languages (this has also to be investigated
with respect to how to well modularize the components).
It is important, though, to have a code base where to start for, so
the priority is to commit code in the sandbox so everybody will be in
synch.
WDYT?
Cheers,
Fabio
Hi,
I have build a web app which can provide documents conversion service, both
through web page or RESTful web service. All the documents are converted to
html format.
Now, I want to clean the result html. As discussed before, I go to JTidy[1].
Hense, I find that the last release of JTidy is published at August 1, 2001.
I wonder if there is some more active project for html code cleaning, or
JTidy is just sufficient?
After clean the html, I will write some parser to convert html to xwiki
syntax.
All I have done is a web app which can run standalone. It accept input file,
convert it to format file or purge xwiki syntax code, and output the
result. I'm confused about how to develop it as a xwiki plugin. I know how
to develop a xwiki plugin. As office import need upload file, output the
result, I just don't know how to integrate it in to xwiki. Any suggestion
will be very appreciated.
Thanks.
[1]http://jtidy.sourceforge.net/index.html
--
Sincerely,
Wang Ning
Hi everyone,
Just to let you know that I've taken the liberty of adding a new
custom field in JIRA for Core called "Development Priority" with 3
values: low, medium and high. The idea is to categorize all our jira
issues with this field in order to prioritize our efforts. Note that
we're not using the existing Priority field since that field
represents the priority from the user's point of view.
Thus you're going to see lots of issue notifications coming in...
sorry about that.
If you don't agree about a given priority let us know as a comment in
the issue. Note that the priorities are global, i.e. compared with
other existing jira issues and not absolute.
Thanks
-Vincent