Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Mylyn » Mylyn Wiki Help
Mylyn Wiki Help [message #489208] Thu, 01 October 2009 16:17 Go to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Hi guys,

I really like the approach you've taken with auto-updating
( http://greensopinion.blogspot.com/2008/11/mylyn-converts-wik i-based-user-guide-to.html)
from community maintainable wiki. I want to adopt it for AMP

I note that you have the User Guide all on one page. This works great
for User Guide as the .toc geenration allows users to look at just one
sub-section. But I'm wondering if on Wiki side for AMP it wouldn't be
better to have this organized by section as well -- if the user guide
get's really long it could present loading issues and make it harder
for users to reference and find relevant sections. Do you think it
would be difficult to set up the ant cripts so that they built from a
hierachy instead?

Anything you would have done differently if you were starting over?
Re: Mylyn Wiki Help [message #489422 is a reply to message #489208] Fri, 02 October 2009 18:27 Go to previous messageGo to next message
David Green is currently offline David Green
Messages: 135
Registered: July 2009
Senior Member
Miles Parker wrote:
> Hi guys,
>
> I really like the approach you've taken with auto-updating
> ( http://greensopinion.blogspot.com/2008/11/mylyn-converts-wik i-based-user-guide-to.html)
> from community maintainable wiki. I want to adopt it for AMP
>
> I note that you have the User Guide all on one page. This works great
> for User Guide as the .toc geenration allows users to look at just one
> sub-section. But I'm wondering if on Wiki side for AMP it wouldn't be
> better to have this organized by section as well -- if the user guide
> get's really long it could present loading issues and make it harder for
> users to reference and find relevant sections. Do you think it would be
> difficult to set up the ant cripts so that they built from a hierachy
> instead?
>
> Anything you would have done differently if you were starting over?
>

Miles,

You'll find that Eclipse help has some really neat facilities with anchors and links: you can compose almost any
structure in the Eclipse help table of contents with multiple documents. This means that you should be able to break
your user guide into multiple documents with some tweaking of help toc.xml files.

That said, there is a lot of room for improvement in this area. I recommend watching this issue:

283734: Documentation Best Practices
https://bugs.eclipse.org/bugs/show_bug.cgi?id=283734

As far as starting over, there's no need. We have a great basis from which we can improve. Feel free to submit bugs,
request enhancements, and contribute your ideas and patches. https://bugs.eclipse.org under Tools/Mylyn/WikiText

Chris and David Carver have both done a fair amount of work in this area. You may want to get in touch with them.

You may also want to take a look at these articles by Peter Friese:

http://www.peterfriese.de/getting-started-with-wikitext/
http://www.peterfriese.de/advanced-wikitext/

As far as I know XText is using WikiText to produce their documentation from wiki format, using DocBook as an
intermediary form.

Regards,

David
Re: Mylyn Wiki Help [message #489430 is a reply to message #489422] Fri, 02 October 2009 19:16 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Thanks for all the links -- extremely helpful.

On 2009-10-02 15:27:16 -0700, David Green <dgreen99@gmail.com> said:
> You'll find that Eclipse help has some really neat facilities with
> anchors and links: you can compose almost any structure in the Eclipse
> help table of contents with multiple documents. This means that you
> should be able to break your user guide into multiple documents with
> some tweaking of help toc.xml files.

Yeah, makes sense. It would be nice to not have to maintain the toc
though. The really great thing about the current Mylyn approch is that
you don't have to do *anything* whereas if you are using document
hierarchy you've got to maintain that linkage manually. Which means
that if a user adds a new page, that's not going to show up. But it
seems that it wouldn't be too hard to setup a script to say grab every
document under wiki.eclipse.org/myproject/UserGuide, convert it, and
then generate a toc for it. You could avoid all of the doc book
assembly by simply organizing the documentation hierachrchiaclly, e.g.

UserGuide/Overview/..
UserGuide/Getting_Started/..

With the assumption that everything at a given level is within same
document (sub)section. Then you would simply have say one Contents Page
at each level that would define the ordering within that section. but
it seems that it would at least handle the cannonical case. I'm
thinking that anything that can be done to give Wiki users full control
over the end state of the documentation is to the good. Perhaps someone
has already thought of all that..


>
> As far as I know XText is using WikiText to produce their documentation
> from wiki format, using DocBook as an intermediary form.

I was thinking that must be the case.

BTW, have you thought about any possiblity of providing editing for
online content from WikiText? I didn't see anything on this anywhere
and I don't know if it is even a reasonable thing to do WRT to the Wiki
side of things.
Re: Mylyn Wiki Help [message #489433 is a reply to message #489430] Fri, 02 October 2009 19:23 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Following up on my own post, an even simpler approach would be to
specify one "official" UserGuide/Contents page. Then the ant script
could very easily parse that and generate any document format from it.
Plus it would be a nice resource for Wiki readers.

On 2009-10-02 16:16:01 -0700, Miles Parker <milesparker@gmail.com> said:

>
> Thanks for all the links -- extremely helpful.
>
> On 2009-10-02 15:27:16 -0700, David Green <dgreen99@gmail.com> said:
>> You'll find that Eclipse help has some really neat facilities with
>> anchors and links: you can compose almost any structure in the Eclipse
>> help table of contents with multiple documents. This means that you
>> should be able to break your user guide into multiple documents with
>> some tweaking of help toc.xml files.
>
> Yeah, makes sense. It would be nice to not have to maintain the toc
> though. The really great thing about the current Mylyn approch is that
> you don't have to do *anything* whereas if you are using document
> hierarchy you've got to maintain that linkage manually. Which means
> that if a user adds a new page, that's not going to show up. But it
> seems that it wouldn't be too hard to setup a script to say grab every
> document under wiki.eclipse.org/myproject/UserGuide, convert it, and
> then generate a toc for it. You could avoid all of the doc book
> assembly by simply organizing the documentation hierachrchiaclly, e.g.
>
> UserGuide/Overview/..
> UserGuide/Getting_Started/..
>
> With the assumption that everything at a given level is within same
> document (sub)section. Then you would simply have say one Contents Page
> at each level that would define the ordering within that section. but
> it seems that it would at least handle the cannonical case. I'm
> thinking that anything that can be done to give Wiki users full control
> over the end state of the documentation is to the good. Perhaps someone
> has already thought of all that..
>
>
>>
>> As far as I know XText is using WikiText to produce their documentation
>> from wiki format, using DocBook as an intermediary form.
>
> I was thinking that must be the case.
>
> BTW, have you thought about any possiblity of providing editing for
> online content from WikiText? I didn't see anything on this anywhere
> and I don't know if it is even a reasonable thing to do WRT to the Wiki
> side of things.
Re: Mylyn Wiki Help [message #489722 is a reply to message #489430] Mon, 05 October 2009 12:40 Go to previous messageGo to next message
David Green is currently offline David Green
Messages: 135
Registered: July 2009
Senior Member
Miles,

Comments below:

Miles Parker wrote:
> It would be nice to not have to maintain the toc
> though. The really great thing about the current Mylyn approch is that
> you don't have to do *anything* whereas if you are using document
> hierarchy you've got to maintain that linkage manually.

Agreed, anything that can lower the barrier to writing/maintaining documentation is a good thing.

> You could avoid all of the doc book assembly
> by simply organizing the documentation hierachrchiaclly, e.g.
>
> UserGuide/Overview/..
> UserGuide/Getting_Started/..
>
> With the assumption that everything at a given level is within same
> document (sub)section. Then you would simply have say one Contents Page
> at each level that would define the ordering within that section. but it
> seems that it would at least handle the cannonical case. I'm thinking
> that anything that can be done to give Wiki users full control over the
> end state of the documentation is to the good. Perhaps someone has
> already thought of all that..
>

Yes, having some kind of convention could offload some of this effort. As you mentioned in your follow-up post, having
a TOC page is a good alternative. The key is to come up with something easy and intuitive that can work for your
project and hopefully others as well. Of course, some tooling would be needed to make all of this work.

>
> BTW, have you thought about any possiblity of providing editing for
> online content from WikiText? I didn't see anything on this anywhere and
> I don't know if it is even a reasonable thing to do WRT to the Wiki side
> of things.
>

It's out of scope of the Mylyn WikiText project to provide offline wiki editing. It would make sense to me that
mediawiki would have an option to use CVS or SVN as a backing data store, which would make all of this a lot easier.
Re: Mylyn Wiki Help [message #491852 is a reply to message #489422] Fri, 16 October 2009 04:18 Go to previous messageGo to next message
Peter Friese is currently offline Peter Friese
Messages: 30
Registered: July 2009
Member
David Green wrote on Fri, 02 October 2009 18:27

As far as I know XText is using WikiText to produce their documentation from wiki format, using DocBook as an
intermediary form.



That's right, the Xtext team uses WikiText do write their documentation and we're *very* satisfied with it. If you're intersted, here is the link to our build script: http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tmf/org .eclipse.xtext/plugins/org.eclipse.xtext.doc/customBuild.xml ?root=Modeling_Project&view=markup. The WikiText files can be found here: http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tmf/org .eclipse.xtext/plugins/org.eclipse.xtext.doc/doc/?root=Model ing_Project.

Although it would be great to use the Eclipse wiki to crowdsource the documentaiton, we decided against that. Mainly due to the somehow cumbersome syntax of MediWiki. Or, to express it in a more positive way: we like Textile syntax Smile

Feel free to contact me if you've got any questions regarding how we used WikiText / Textile / DocBook.
Re: Mylyn Wiki Help [message #502868 is a reply to message #491852] Thu, 10 December 2009 00:38 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Peter Friese wrote on Fri, 16 October 2009 04:18


That's right, the Xtext team uses WikiText do write their documentation and we're *very* satisfied with it. If you're intersted, here is the link to our build script: ...
Although it would be great to use the Eclipse wiki to crowdsource the documentaiton, we decided against that. Mainly due to the somehow cumbersome syntax of MediWiki. Or, to express it in a more positive way: we like Textile syntax Smile



Cool, thanks a lot for the links Peter, very helpful. Just a quick question for this thread. So you're actually doing something like:

textile -> wiki
textile -> Eclipse docs

as opposed to

wiki -> Eclipse Docs

??

And as a genral addendum, I've got doc sections seperated now, but I'm thinking of re-integrating them as even on Wiki it's surprisingly difficult to navigate between sections and I'm finding I'm having to spend a fair amount of time maintaining the references between TOC, overview and sections. Sure seems like it might be sipler to have one big page for each of the major components as Mylyn and XText seem to be doing.
Re: Mylyn Wiki Help [message #502870 is a reply to message #502868] Thu, 10 December 2009 01:50 Go to previous messageGo to next message
Peter Friese is currently offline Peter Friese
Messages: 30
Registered: July 2009
Member
Miles Parker wrote on Thu, 10 December 2009 00:38
Peter Friese wrote on Fri, 16 October 2009 04:18


That's right, the Xtext team uses WikiText do write their documentation and we're *very* satisfied with it. If you're intersted, here is the link to our build script: ...
Although it would be great to use the Eclipse wiki to crowdsource the documentaiton, we decided against that. Mainly due to the somehow cumbersome syntax of MediWiki. Or, to express it in a more positive way: we like Textile syntax Smile



Cool, thanks a lot for the links Peter, very helpful. Just a quick question for this thread. So you're actually doing something like:

textile -> wiki
textile -> Eclipse docs

as opposed to

wiki -> Eclipse Docs

??



Not quite. We do
textile (files stored on workspace, resp. CVS) -> docbook -> PDF
textile (files stored on workspace, resp. CVS) -> docbook -> Eclipse Help
textile (files stored on workspace, resp. CVS) -> docbook -> HTML

We were considering writing our documentation on the Eclipse wiki and the transform (wiki -> docbook -> [PDF|HTML|Eclipse Help], but decided against this approach for the following reasons:


  1. Textile syntax is much more concise than any other Wiki markup, including the dialect being used on the Eclipse wiki
  2. We needed to introduce special syntax for linking to files in Eclipse CVS, this was easier with WikiText / Textile.


Quote:

And as a genral addendum, I've got doc sections seperated now, but I'm thinking of re-integrating them as even on Wiki it's surprisingly difficult to navigate between sections and I'm finding I'm having to spend a fair amount of time maintaining the references between TOC, overview and sections. Sure seems like it might be sipler to have one big page for each of the major components as Mylyn and Xtext seem to be doing.


We use a text file to configure the structure of the entire document. This works very well.
Re: Mylyn Wiki Help [message #599354 is a reply to message #489208] Fri, 02 October 2009 18:27 Go to previous messageGo to next message
David Green is currently offline David Green
Messages: 96
Registered: July 2009
Member
Miles Parker wrote:
> Hi guys,
>
> I really like the approach you've taken with auto-updating
> ( http://greensopinion.blogspot.com/2008/11/mylyn-converts-wik i-based-user-guide-to.html)
> from community maintainable wiki. I want to adopt it for AMP
>
> I note that you have the User Guide all on one page. This works great
> for User Guide as the .toc geenration allows users to look at just one
> sub-section. But I'm wondering if on Wiki side for AMP it wouldn't be
> better to have this organized by section as well -- if the user guide
> get's really long it could present loading issues and make it harder for
> users to reference and find relevant sections. Do you think it would be
> difficult to set up the ant cripts so that they built from a hierachy
> instead?
>
> Anything you would have done differently if you were starting over?
>

Miles,

You'll find that Eclipse help has some really neat facilities with anchors and links: you can compose almost any
structure in the Eclipse help table of contents with multiple documents. This means that you should be able to break
your user guide into multiple documents with some tweaking of help toc.xml files.

That said, there is a lot of room for improvement in this area. I recommend watching this issue:

283734: Documentation Best Practices
https://bugs.eclipse.org/bugs/show_bug.cgi?id=283734

As far as starting over, there's no need. We have a great basis from which we can improve. Feel free to submit bugs,
request enhancements, and contribute your ideas and patches. https://bugs.eclipse.org under Tools/Mylyn/WikiText

Chris and David Carver have both done a fair amount of work in this area. You may want to get in touch with them.

You may also want to take a look at these articles by Peter Friese:

http://www.peterfriese.de/getting-started-with-wikitext/
http://www.peterfriese.de/advanced-wikitext/

As far as I know XText is using WikiText to produce their documentation from wiki format, using DocBook as an
intermediary form.

Regards,

David
Re: Mylyn Wiki Help [message #599373 is a reply to message #489422] Fri, 02 October 2009 19:16 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Thanks for all the links -- extremely helpful.

On 2009-10-02 15:27:16 -0700, David Green <dgreen99@gmail.com> said:
> You'll find that Eclipse help has some really neat facilities with
> anchors and links: you can compose almost any structure in the Eclipse
> help table of contents with multiple documents. This means that you
> should be able to break your user guide into multiple documents with
> some tweaking of help toc.xml files.

Yeah, makes sense. It would be nice to not have to maintain the toc
though. The really great thing about the current Mylyn approch is that
you don't have to do *anything* whereas if you are using document
hierarchy you've got to maintain that linkage manually. Which means
that if a user adds a new page, that's not going to show up. But it
seems that it wouldn't be too hard to setup a script to say grab every
document under wiki.eclipse.org/myproject/UserGuide, convert it, and
then generate a toc for it. You could avoid all of the doc book
assembly by simply organizing the documentation hierachrchiaclly, e.g.

UserGuide/Overview/..
UserGuide/Getting_Started/..

With the assumption that everything at a given level is within same
document (sub)section. Then you would simply have say one Contents Page
at each level that would define the ordering within that section. but
it seems that it would at least handle the cannonical case. I'm
thinking that anything that can be done to give Wiki users full control
over the end state of the documentation is to the good. Perhaps someone
has already thought of all that..


>
> As far as I know XText is using WikiText to produce their documentation
> from wiki format, using DocBook as an intermediary form.

I was thinking that must be the case.

BTW, have you thought about any possiblity of providing editing for
online content from WikiText? I didn't see anything on this anywhere
and I don't know if it is even a reasonable thing to do WRT to the Wiki
side of things.
Re: Mylyn Wiki Help [message #599381 is a reply to message #489430] Fri, 02 October 2009 19:23 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Following up on my own post, an even simpler approach would be to
specify one "official" UserGuide/Contents page. Then the ant script
could very easily parse that and generate any document format from it.
Plus it would be a nice resource for Wiki readers.

On 2009-10-02 16:16:01 -0700, Miles Parker <milesparker@gmail.com> said:

>
> Thanks for all the links -- extremely helpful.
>
> On 2009-10-02 15:27:16 -0700, David Green <dgreen99@gmail.com> said:
>> You'll find that Eclipse help has some really neat facilities with
>> anchors and links: you can compose almost any structure in the Eclipse
>> help table of contents with multiple documents. This means that you
>> should be able to break your user guide into multiple documents with
>> some tweaking of help toc.xml files.
>
> Yeah, makes sense. It would be nice to not have to maintain the toc
> though. The really great thing about the current Mylyn approch is that
> you don't have to do *anything* whereas if you are using document
> hierarchy you've got to maintain that linkage manually. Which means
> that if a user adds a new page, that's not going to show up. But it
> seems that it wouldn't be too hard to setup a script to say grab every
> document under wiki.eclipse.org/myproject/UserGuide, convert it, and
> then generate a toc for it. You could avoid all of the doc book
> assembly by simply organizing the documentation hierachrchiaclly, e.g.
>
> UserGuide/Overview/..
> UserGuide/Getting_Started/..
>
> With the assumption that everything at a given level is within same
> document (sub)section. Then you would simply have say one Contents Page
> at each level that would define the ordering within that section. but
> it seems that it would at least handle the cannonical case. I'm
> thinking that anything that can be done to give Wiki users full control
> over the end state of the documentation is to the good. Perhaps someone
> has already thought of all that..
>
>
>>
>> As far as I know XText is using WikiText to produce their documentation
>> from wiki format, using DocBook as an intermediary form.
>
> I was thinking that must be the case.
>
> BTW, have you thought about any possiblity of providing editing for
> online content from WikiText? I didn't see anything on this anywhere
> and I don't know if it is even a reasonable thing to do WRT to the Wiki
> side of things.
Re: Mylyn Wiki Help [message #599414 is a reply to message #489430] Mon, 05 October 2009 12:40 Go to previous messageGo to next message
David Green is currently offline David Green
Messages: 96
Registered: July 2009
Member
Miles,

Comments below:

Miles Parker wrote:
> It would be nice to not have to maintain the toc
> though. The really great thing about the current Mylyn approch is that
> you don't have to do *anything* whereas if you are using document
> hierarchy you've got to maintain that linkage manually.

Agreed, anything that can lower the barrier to writing/maintaining documentation is a good thing.

> You could avoid all of the doc book assembly
> by simply organizing the documentation hierachrchiaclly, e.g.
>
> UserGuide/Overview/..
> UserGuide/Getting_Started/..
>
> With the assumption that everything at a given level is within same
> document (sub)section. Then you would simply have say one Contents Page
> at each level that would define the ordering within that section. but it
> seems that it would at least handle the cannonical case. I'm thinking
> that anything that can be done to give Wiki users full control over the
> end state of the documentation is to the good. Perhaps someone has
> already thought of all that..
>

Yes, having some kind of convention could offload some of this effort. As you mentioned in your follow-up post, having
a TOC page is a good alternative. The key is to come up with something easy and intuitive that can work for your
project and hopefully others as well. Of course, some tooling would be needed to make all of this work.

>
> BTW, have you thought about any possiblity of providing editing for
> online content from WikiText? I didn't see anything on this anywhere and
> I don't know if it is even a reasonable thing to do WRT to the Wiki side
> of things.
>

It's out of scope of the Mylyn WikiText project to provide offline wiki editing. It would make sense to me that
mediawiki would have an option to use CVS or SVN as a backing data store, which would make all of this a lot easier.
Re: Mylyn Wiki Help [message #599718 is a reply to message #489422] Fri, 16 October 2009 04:18 Go to previous messageGo to next message
Peter Friese is currently offline Peter Friese
Messages: 30
Registered: July 2009
Member
David Green wrote on Fri, 02 October 2009 18:27
> As far as I know XText is using WikiText to produce their documentation from wiki format, using DocBook as an
> intermediary form.


That's right, the Xtext team uses WikiText do write their documentation and we're *very* satisfied with it. If you're intersted, here is the link to our build script: http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tmf/org .eclipse.xtext/plugins/org.eclipse.xtext.doc/customBuild.xml ?root=Modeling_Project&view=markup The WikiText files can be found here: http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tmf/org .eclipse.xtext/plugins/org.eclipse.xtext.doc/doc/?root=Model ing_Project

Although it would be great to use the Eclipse wiki to crowdsource the documentaiton, we decided against that. Mainly due to the somehow cumbersome syntax of MediWiki. Or, to express it in a more positive way: we like Textile syntax :)

Feel free to contact me if you've got any questions regarding how we used WikiText / Textile / DocBook.
Re: Mylyn Wiki Help [message #600163 is a reply to message #599718] Thu, 10 December 2009 00:38 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
Peter Friese wrote on Fri, 16 October 2009 04:18
> That's right, the Xtext team uses WikiText do write their documentation and we're *very* satisfied with it. If you're intersted, here is the link to our build script: ...
> Although it would be great to use the Eclipse wiki to crowdsource the documentaiton, we decided against that. Mainly due to the somehow cumbersome syntax of MediWiki. Or, to express it in a more positive way: we like Textile syntax :)


Cool, thanks a lot for the links Peter, very helpful. Just a quick question for this thread. So you're actually doing something like:

textile -> wiki
textile -> Eclipse docs

as opposed to

wiki -> Eclipse Docs

??

And as a genral addendum, I've got doc sections seperated now, but I'm thinking of re-integrating them as even on Wiki it's surprisingly difficult to navigate between sections and I'm finding I'm having to spend a fair amount of time maintaining the references between TOC, overview and sections. Sure seems like it might be sipler to have one big page for each of the major components as Mylyn and XText seem to be doing.
Re: Mylyn Wiki Help [message #600168 is a reply to message #600163] Thu, 10 December 2009 01:50 Go to previous message
Peter Friese is currently offline Peter Friese
Messages: 30
Registered: July 2009
Member
Miles Parker wrote on Thu, 10 December 2009 00:38
> Peter Friese wrote on Fri, 16 October 2009 04:18
> > That's right, the Xtext team uses WikiText do write their documentation and we're *very* satisfied with it. If you're intersted, here is the link to our build script: ...
> > Although it would be great to use the Eclipse wiki to crowdsource the documentaiton, we decided against that. Mainly due to the somehow cumbersome syntax of MediWiki. Or, to express it in a more positive way: we like Textile syntax :)
>
>
> Cool, thanks a lot for the links Peter, very helpful. Just a quick question for this thread. So you're actually doing something like:
>
> textile -> wiki
> textile -> Eclipse docs
>
> as opposed to
>
> wiki -> Eclipse Docs
>
> ??


Not quite. We do
textile (files stored on workspace, resp. CVS) -> docbook -> PDF
textile (files stored on workspace, resp. CVS) -> docbook -> Eclipse Help
textile (files stored on workspace, resp. CVS) -> docbook -> HTML

We were considering writing our documentation on the Eclipse wiki and the transform (wiki -> docbook -> [PDF|HTML|Eclipse Help], but decided against this approach for the following reasons:


Textile syntax is much more concise than any other Wiki markup, including the dialect being used on the Eclipse wiki
We needed to introduce special syntax for linking to files in Eclipse CVS, this was easier with WikiText / Textile.


Quote:
> And as a genral addendum, I've got doc sections seperated now, but I'm thinking of re-integrating them as even on Wiki it's surprisingly difficult to navigate between sections and I'm finding I'm having to spend a fair amount of time maintaining the references between TOC, overview and sections. Sure seems like it might be sipler to have one big page for each of the major components as Mylyn and Xtext seem to be doing.


We use a text file to configure the structure of the entire document. This works very well.
Previous Topic:Sort by due date?
Next Topic:removal of Sanbox highlighters
Goto Forum:
  


Current Time: Sat Aug 23 11:34:11 EDT 2014

Powered by FUDForum. Page generated in 0.09463 seconds