Hello,
On 9/13/2010 5:20 PM, Olemis Lang wrote:
On Sat, Sep 11, 2010 at 5:34 AM, Christian Boos<[email protected]> wrote:
On 8/21/2010 2:18 PM, Itamar O wrote:
I have users that are used to writing long specification& design
documents as Word documents, and have expressed interest in starting to work
in Trac-wiki instead.
As far as document management& versioning is concerned, I would like to
allow them to manage their wiki documents at-least as easily and intuitively
as file-based documents allow.
The main use-cases include:
First, 0.13 will hopefully feature a rewrite of the wiki parser that will
make authoring content more "robust" (less quirks, more expressive power).
Some advanced operations like (batch) copy are also on my list. I have also
laid out a plan for supporting transclusion and other powerful mechanisms
inspired from MediaWiki (see
http://trac.edgewall.org/wiki/TracDev/Proposals/AdvancedWikiFormatting#Transclusion)
I've read this page and all that's awesome !!!
About compatibility with other wiki markups ...
Q:
- What's the idea ? Are you planning to release support
for multiple markups or just incorporate useful and
advanced features missing in Trac ?
The second, incorporate useful and advanced features missing in Trac.
The idea is to have a non-conflicting set of markup that "just works"
according to the expectations you could have from using other similar
tools (bitbucket, github, google code, ...). The most visible step in
this direction is the support of WikiCreole, which started in 0.12 and
should become complete in 0.13 or 0.14 (see
http://trac.edgewall.org/wiki/WikiCreole for coverage details).
Of course it's not possible nor desirable to support *all* possible
markups, if only because of the incompatibilities, but when there's an
unambiguous and useful piece of syntax that "fits" in the rest of the
puzzle, it can be an useful addition.
However, as the new wiki parser for 0.13 will hopefully make it possible
to support more complex bits of syntax through the plugin system than
what is currently possible, I expect that we should be able to move some
of the advanced stuff in optional components. That way, the base syntax
will remain simple, on the level of Trac 0.11 even i.e. the creole
compatibility could become optional, I'm sure those who are from the
"there should be one and only way to do it" camp will be happy ;-)
- What's the really advanced stuff ? wanna know ...
ñam , ñam ...
Well, for now that was the link you cited above. Is this transclusion
thing not enough advanced for your taste? ;-)
Besides, Itamar proposed a detailed list of other advanced enhancements
in the first mail of this discussion, and I'll integrate those ideas one
of these days in the TracDev pages (though as I already said, this is
more for the longer term, 0.15 even).
which I believe will also provide some of the infrastructure support for
composing complex documents from individual pages. Finally, progress on the
GenericTrac model will bring the addition of wiki properties,
Q:
- what are wiki properties are exactly ?
The equivalent of the ticket custom properties, but for wiki pages.
as well as the
possibility for plugins to define new resources easily (e.g. "documents").
Q:
- How would it look like ?
No idea yet ;-)
A document would be a structured aggregate of wiki pages. While this
could be done by building yet another wiki page, using a dedicated kind
of resource would make it possible to have a distinctive view and edit
mode. For example, we could even have two main viewing modes, single
page mode and multi-page mode, the second could look like a two panes
TOC + content. The edit mode could feature some convenient ways to
organize the pages, etc.
In the same vein, a generalization of ticket workflow to e.g. wiki workflow
should also be possible, longer term.
coooool !!!! ... however firstly tickets, next wiki pages, ... why not
to think on resource workflows (i.e. if somebody creates a custom
resource in plugin, then provide components or mechanisms to attach a
workflow for them ...) ???
Well yes, the idea has been floating around for some time, especially
for milestone (planning, freezing, retiring, etc.) but currently the
workflow is quite closely tied to the inner working of the ticket
module, so this will likely be not trivial to generalize.
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
