Hi,
I'm currently working on the great patch Evelina has made for the new
xwiki administration.
I'd like to take advantage of this to make some modifications to the
default XWiki Preferences.
1) Browse Title Bar Text.
----------------------------------
* Current : XWiki - $doc.space - $doc.name
* Proposal : $doc.displayTitle ($doc.space) - XWiki
2) HTTP Meta Information
-------------------------------------
* Current :
<meta name="description" content="XWiki for sharing information" />
<meta name="keywords" content="wiki" />
<meta name="author" content="" />
<meta name="language" content="en" />
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
* Proposal :
<meta name="description" content="$!doc.displayTitle" />
<meta name="keywords" content="wiki $!doc.tags" />
<meta name="author"
content="$!xwiki.getLocalUserName($doc.getAuthor(), false)" />
<meta name="language" content="$!context.language" />
<meta http-equiv="Content-Type" content="text/html; charset=$xwiki.encoding" />
3) License
----------------
* Current : This wiki is licensed under a <a
href="http://creativecommons.org/licenses/by/1.0/">Creative
Commons</a> license
* Proposal : This wiki is licensed under a <a
href="http://creativecommons.org/licenses/by/3.0/">Creative
Commons</a> license
4) Version
----------------
* Current : empty, actually it's not even taken into account if filled
* Proposal : XWiki $xwiki.getVersion() - <a
onclick="openURL('http://www.xwiki.org/xwiki/bin/view/Main/Documentation',
'_blank'); return false;"
href="http://www.xwiki.org/xwiki/bin/view/Main/Documentation">Documentation</a>
(An administration menu will replace the current Documentation link at
the top right corner, shout if you think it's an error).
I'm +1 with 1) 2) 3) 4) .. indeed.
That's all (at least for the moment).
Thanks,
--
Jean-Vincent Drean
Hi All,
I cannot test xwiki-webdav anymore because XWikiCacheStore throws a null
pointer exception that i cannot figure out. I think this is introduced by a
recent commit, please help me with this. Following is the exception,
<dump>
java.lang.NullPointerException
at
com.xpn.xwiki.store.XWikiCacheStore.initCache(XWikiCacheStore.java:95)
at
com.xpn.xwiki.store.XWikiCacheStore.initCache(XWikiCacheStore.java:80)
at
com.xpn.xwiki.store.XWikiCacheStore.<init>(XWikiCacheStore.java:62)
at com.xpn.xwiki.XWiki.initXWiki(XWiki.java:675)
at com.xpn.xwiki.XWiki.<init>(XWiki.java:652)
at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:312)
at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:383)
at
com.xpn.xwiki.plugin.webdav.XWikiDavResourceImpl.getXWikiContext(XWikiDavResourceImpl.java:350)
at
com.xpn.xwiki.plugin.webdav.XWikiDavResourceImpl.<init>(XWikiDavResourceImpl.java:205)
at
com.xpn.xwiki.plugin.webdav.XWikiResourceFactoryImpl.createResource(XWikiResourceFactoryImpl.java:105)
at
com.xpn.xwiki.plugin.webdav.XWikiResourceFactoryImpl.createResource(XWikiResourceFactoryImpl.java:69)
at
com.xpn.xwiki.plugin.webdav.XWikiDavServlet.service(XWikiDavServlet.java:351)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:219)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:738)
at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:113)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:325)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:859)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:391)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)
</dump>
In XWikiCacheStore.initCache() method,
CacheFactory cacheFactory = context.getWiki().getCacheFactory();
here, cacheFactory has become null.
I've only found this problem and currently looking into it, if anyone can
help me get over this quickly it would be a big help.
Thanks.
- Asiri
I'm building a wiki that has three level of categories. When I add an
article, I want the page to have three dynamic select boxes. Which means if
user select a top category, the subcategory select box will change
accordingly, so as the "sub subcategory".
I can't find anything built in xwiki support this. Could anybody suggest me
something? Like should I use Groovy script? Javascript? HQL?
Thank you!
Fei
--
View this message in context: http://www.nabble.com/how-to-set-up-or-program-to-have-dynamic-select-boxes…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
On Jun 21, 2008, at 5:55 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-06-21 05:55:33 +0200 (Sat, 21 Jun 2008)
> New Revision: 10552
>
> Modified:
> xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> render/DefaultXWikiRenderingEngine.java
> Log:
> XWIKI-942: Customize default document cache duration
> Done. Use the key xwiki.rendering.defaultCacheDuration in xwiki.cfg
> to configure this. By default documents are not cached.
>
>
> Modified: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/
> xwiki/render/DefaultXWikiRenderingEngine.java
> ===================================================================
> --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> render/DefaultXWikiRenderingEngine.java 2008-06-21 03:49:16 UTC (rev
> 10551)
> +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> render/DefaultXWikiRenderingEngine.java 2008-06-21 03:55:33 UTC (rev
> 10552)
> @@ -235,7 +235,8 @@
> MonitorPlugin monitor = Util.getMonitorPlugin(context);
> try {
> // We need to make sure we don't use the cache
> duretion currently in the system
This comment doesn't match the change below anymore. I would have
updated it but I don't know why it was important that we don't use any
cache duration and whether it has side effects now that we do...
>
> - context.setCacheDuration(0);
> + context
> + .setCacheDuration((int)
> context
> .getWiki().ParamAsLong("xwiki.rendering.defaultCacheDuration", 0));
Thanks
-Vincent
I'm +1 for view mode and left panel take too many place so : Layout2
On Tue, Jun 17, 2008 at 3:50 PM, Evelina Slatineanu
<evelina.slatineanu(a)xwiki.com> wrote:
> I am +1 for layout 2 + Jv's proposal to have a hidden div for the big icons
> (which is even faster than ajax and it is exactly like Control Panel in
> Windows - no need to have the menu anymore).
>
> Although layout 3 looks good at first view, I have some comments about it:
>
> 1. the integration of admin pages like Panels (which need view mode) can be
> very difficult (example: for Panel Wizard
> I had to change layoutvars.vm so that it display the panels for the
> requested space instead of the ones in "Panels" space).
>
> 2. why not letting the user to customize the administration layout as he
> wants, meaning to choose what panels he wants to have on the left or on the
> right in the admin page? I mean if the users sees that he needs more room
> to edit application pages inside admin, he can change the layout...I really
> don't see the issue
>
> So I'm really +1 to keep admin in view mode.
>
> Thanks,
> Evelina
>
>
> -----Original Message-----
> From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] On Behalf Of
> Jean-Vincent Drean
> Sent: Tuesday, June 17, 2008 4:32 PM
> To: XWiki Developers
> Subject: Re: [xwiki-devs] [VOTE] Overhaul of the administration, layout
>
> BTW I'm +1 for Layout2.
>
> On Mon, Jun 16, 2008 at 6:17 PM, Jean-Vincent Drean <jv(a)xwiki.com> wrote:
>> Hi XWikiers,
>>
>> Evelina has finished the ground work on the new administration and
>> it's now time to vote for its layout.
>> http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministration
>>
>> Proposals :
>>
>> Admin in view mode, with a left menu :
>>
> http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationLayout1
>> Admin in view mode, without a left menu :
>>
> http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationLayout2
>> Admin in edit mode, with a navigation panel :
>>
> http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationLayout3
>> Admin in edit mode, without a navigation panel :
>>
> http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationLayout4
>>
>> Other question, how do we display the space selector :
>>
>>
> http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationSpaceSel
> ection
>>
>> --
>> Jean-Vincent Drean
>>
>
>
>
> --
> Jean-Vincent Drean
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
--
Thomas Mortagne
Hello developers,
Thank you for responding to my previous query.
Can you please explain the differences between the following two macros,
what advantages does includeInContext provide over the other?
1. includeForm()
2. includeInContext()
Having retrieved an object on a page, how can I update some fields of that
object and save?
Doc.save() saves the document changing its version.... but, doesn't update
the object-parameters. What am I missing?
Regards,
Archana Mettu.
I am trying to build the xwiki-core jar file from sources, But I am
getting the following error when i run the maven install. other projects
under core compile without any issue. Any one has the same experience
building xwiki core jar from source. Please help.
Thanks
Satya
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 38 source files to C:\xwiki new\xwiki
platform\core\xwiki-patc
service\target\classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
C:\xwiki new\xwiki
platform\core\xwiki-patchservice\src\main\java\org\xwiki\pla
form\patchservice\web\PatchServiceAction.java:[14,46] package
org.xwiki.platfor
.patchservice.plugin does not exist
C:\xwiki new\xwiki
platform\core\xwiki-patchservice\src\main\java\org\xwiki\pla
form\patchservice\hook\PatchCreator.java:[25,46] package
org.xwiki.platform.pat
hservice.plugin does not exist
C:\xwiki new\xwiki
platform\core\xwiki-patchservice\src\main\java\org\xwiki\pla
form\patchservice\hook\PatchCreator.java:[39,4] cannot find symbol
symbol : class PatchservicePlugin
location: class org.xwiki.platform.patchservice.hook.PatchCreator
C:\xwiki new\xwiki
platform\core\xwiki-patchservice\src\main\java\org\xwiki\pla
form\patchservice\hook\PatchCreator.java:[45,24] cannot find symbol
symbol : class PatchservicePlugin
location: class org.xwiki.platform.patchservice.hook.PatchCreator
C:\xwiki new\xwiki
platform\core\xwiki-patchservice\src\main\java\org\xwiki\pla
form\patchservice\web\PatchServiceAction.java:[33,8] cannot find symbol
symbol : class PatchservicePlugin
location: class org.xwiki.platform.patchservice.web.PatchServiceAction
C:\xwiki new\xwiki
platform\core\xwiki-patchservice\src\main\java\org\xwiki\pla
form\patchservice\web\PatchServiceAction.java:[34,13] cannot find symbol
symbol : class PatchservicePlugin
location: class org.xwiki.platform.patchservice.web.PatchServiceAction
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
Hi everyone,
Yesterday was our second DocHour day day. The following bugs were
fixed: http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&&customfie…
- Jerome Velociter
XWIKI-1351 Write a tutorial for newcomers on how to create Java selenium tests.
- Artem Melentev
XWIKI-1211 Document the comment on page save feature
- Thomas Mortagne
XAWM-80 Improve wiki descriptor editor documentation
- Vincent Massol
XWIKI-2488 Improve Macro display in the Code Zone by removing the
Bundled With Skin attribute
XWIKI-1483 Document the {pre} macro
So that's a total of 5 distinct tasks around documentation
improvement. This is not much but not everyone had time with the 1.5M2
release very soon and bugfixing day to finish.
You can still do your doc hour and add it to this conversation.
Thanks everyone
--
Thomas Mortagne
The XWiki development team is pleased to announce the release of XWiki
Workspaces 1.1 Milestone 2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
New features have been implemented in this release, amongst them :
* Global roles: the administrator can now delegate responsibilities to
groups of administrators and power users
* Public registration: It is now possible to enable public registration
for visitors that do not own an account
* Invitation management: You can invite via email people who are not
registered yet on the XWiki Workspaces instance to come and work in
existing workspaces.
You can read the full release notes, including screenshots of the
aforementioned features, here :
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesWorkspaces11Milestone2
To get started with XWiki Workspaces, point your browser at
http://workspaces.xwiki.org
Thanks
-The XWiki dev team
Hi everyone,
Yesterday was our second bug fixing day (which we intend to have every
wednesday). The following bugs were fixed: http://tinyurl.com/6xup69
- Vincent
XWIKI-2485 Calling the Flush Cache API prevents Users and Groups from
being deleted properly
- Sergiu
XWIKI-2386 Non-threadsafe manipulation of the document in SaveAction
XWIKI-2385 displayPrettyName does not show the mandatory mark in
certain situations
- Thomas
XWIKI-2468 sql exception during delete virtual wiki in Oracle
XWIKI-2483 Lots of code don't take care of "xwiki.temp.dir" when a
temporary directory is needed
- Artem
XWIKI-2317 Documents created from APIs starts at version 2.1
- Fabio
XECLIPSE-91 Keybinding conflicts may interfere with normal
accelerator operation
XECLIPSE-93 Open page menu item not visible when using XEclipse in
the Eclipse IDE
XECLIPSE-97 Indexer must start indexing all spaces automatically + be
persistent
XECLIPSE-90 Compatibility with Confluence Fabio Mancinelli Eugene
Kuleshov
So that's a total of 10 bugs fixed. Well done everybody and thanks to
all who participated.
Special kudos to Fabio, Sergiu and Thomas.
Thanks
-Vincent
Hi Artem,
On Jun 19, 2008, at 2:44 PM, amelentev (SVN) wrote:
> Author: amelentev
> Date: 2008-06-19 14:44:27 +0200 (Thu, 19 Jun 2008)
> New Revision: 10459
>
> Modified:
> xwiki-platform/web/trunk/standard/src/main/webapp/templates/
> editactions.vm
> Log:
> XWIKI-114: Adding comment for edit changes
>
> fix old typo
You cannot do this since:
* the issue is already closed and has already been released
* this won't appear in the release notes
The best is to create a new jira issue for this explaining what the
problem is from the user's point of view.
Thanks
-Vincent
> Modified: xwiki-platform/web/trunk/standard/src/main/webapp/
> templates/editactions.vm
> ===================================================================
> --- xwiki-platform/web/trunk/standard/src/main/webapp/templates/
> editactions.vm 2008-06-19 12:06:15 UTC (rev 10458)
> +++ xwiki-platform/web/trunk/standard/src/main/webapp/templates/
> editactions.vm 2008-06-19 12:44:27 UTC (rev 10459)
> @@ -75,7 +75,7 @@
>
> #if((!$commentFieldAdded)&&($xwiki.hasEditComment()))
> #set($commentFieldAdded = 1)
> -#if($xwiki.isEditCommentHidden())
> +#if($xwiki.isEditCommentFieldHidden())
> <input type="hidden" name="comment" value="" size="80" />
> #else
> $msg.get("core.comment"): <input type="text" name="comment" value=""
> size="80" />
Hello everyone,
maybe http://markmail.org/ would be interesting for XWiki to. Seems very
useful for me.
Btw. has someone some feedback on my last mail regarding the SSO project?
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