Hi devs,
the current templates for xwiki pages include a xhtml standard <DOCTYPE>
for any html page generated which triggers the standard mode CSS
interpretation in browsers (see
http://www.quirksmode.org/css/quirksmode.html for details). This causes
issues in applications that use GWT generated code (like XWatch) since GWT
does not work properly in standards mode yet (see
http://code.google.com/p/google-web-toolkit/issues/detail?id=1305 for
details). I propose to parametrize the document type definition (its
existance and type), thus allowing the developer to take control of the
type of document it generates, for each generated page.
The solutions would be:
- using a request parameter to specify the doctype
- using a $response function, just like $response.setContentType() to set
the doctype at render time (this solution might require post processing to
change the default generated doctype in the page).
WDYT?
Hi,
I've been using Maven 2.1 snapshot built from maven trunk for more
than a week now and didn't get any issue.
I'd like to propose that we remove our old maven zip and replace it
with a recent trunk version.
This will allow:
* fixing lots of maven bugs we have since we're using an old maven
version
* putting us on the maven 2.1 release track. This will allow us to
detect any issue and report it to the maven team so that the final 2.1
release will work for us
Here's my +1
Thanks
-Vincent
Hi,
I've updated our official Maven install zip for building XWiki to a
newer version.
It's available on http://dev.xwiki.org/xwiki/bin/view/Community/Building
It would be good if you could update and start using this new version.
Thanks
-Vincent
The XWiki development team is pleased to announce the release of XWiki
Eclipse 1.1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download#HXWikiEclipse
XEclipse 1.1 introduces several bug fixes and improvements for a nicer
user experience.
Changes from 1.0.1:
* XECLIPSE-70 - Invalid text in delete dialog box
* XECLIPSE-84 - Invalid version displayed when editing a page
* XECLIPSE-87 - Cannot reconnect after disconnecting
* XECLIPSE-89 - Login name with space
* XECLIPSE-23 - Double-clicking on a tree node should open the node
* XECLIPSE-73 - Add edit working set feature
* XECLIPSE-77 - In preview panel, display the current URL and allow
typing any URL
* XECLIPSE-78 - In preview pane, add right click action to open the
current URL in external browser
* XECLIPSE-81 - Let user decide if they want to overwrite the server
version rather than merge it
For more information see the Release notes and instructions at:
http://code.xwiki.org/xwiki/bin/view/Extensions/XEclipseExtension
Thanks
-The XWiki dev team
Hi,
I'm proposing to make toucan the default skin in 1.3M2. Several reasons:
1) It's nicer and cleaner than Albatross
2) If we want to get feedback on it we need it to make it the default.
It's important to do this now so that we can deliver a perfect Toucan
for 1.3 final
3) One of the highlight of the 1.3 release is the new skin
Here's a big +1 from me.
Thanks
-Vincent
Hi devs,
I've just installed Archiva on http://laam.xpertnet.biz:8080/archiva/index.action
under my account there. Raffaello will probably move it somewhere
else in the near future.
http://laam.xpertnet.biz:8080/archiva
Right now I've configured it to:
* Remove snapshots that are older than 30 days
* Keep the last 2 snapshots artifacts
* Delete snapshots when a released version exist
Now let's monitor how it goes...
Thanks
-Vincent
Hi,
As planned I'd like to release 1.3M2. It was planned for today but
since we're still busy I propose to do the release over the week end
and on monday morning.
Is there anything we're still working on that prevents 1.3M2 from
being released? And if so when can you have these finished?
Thanks
-Vincent
Hi,
I'm trying to write a XWiki parser and I'm having some issue writing
an ANTLR grammar for it. More specifically the following grammar
doesn't recognize "{macro/}":
http://dev.xwiki.org/xwiki/bin/view/Drafts/AntlrGrammarXWiki
If some of you have some experience with Antlr, I'd be grateful for
some help. In the meantime I'll keep searching...
Thanks
-Vincent
Hi,
Here's some design details on the new xwiki rendering component I'm
writing, for which I'd like to have feedback from the dev community.
Sources:
http://svn.xwiki.org/svnroot/sandbox/components/xwiki-rendering/xwiki-rende…
In the new design, macros are parsed and generate "MacroBlock"s events
in the Listener.
Here are some refinements I'm proposing:
* MacroBlock has a traverse(Listener) method.
* In order to make Macros independent on the Listener (this is very
important IMO in order to allow for any kind of transformations) we
need to make the MacroBlocks emit Listener events.
* Since the wiki syntax is not enough to generate all possible
rendering options (for example no wiki syntax for XHTML forms) we have
2 options:
1) add as many Listener events as there are XHTML features or
2) add an onHTMLElement(...) event in the Listener
* Option 2) (onHTMLElement) looks much better IMO (simpler, can evolve
with the HTML spec, faster, etc)
This allows for example to have a iText renderer to generate PDFs from
page content which would be way more difficult if the HTML was passed
as standard text (this would need to reparse again the content of
Listener's onText() calls. Same applies for any Listener/Renderer
since they'll need to have some special handling for HTML.
Of course since WikiModel and Doxia don't have HTML events in their
Listener/Sink we'll need to perform some mapping when we want to use
bridge to them. It probably means we'll need to output the HTML
elements as simple text events for them.
WDYT?
Mikhail, I'm curious to know how you're handling this use case in
wikimodel.
Thanks
-Vincent