Re: [asciidoc-discuss] Bullets in the table
On 11/18/06, Stuart Rackham srackham-at-methods.co.nz |asciidoc| <...> wrote: > > Yang wrote: > > Hey Anmar, > > > > Stuart may have something more to say, but there isn't (and probably > > won't be in the near future) any resource for introducing developers > > to the code base (which to be fair is not that large, but I'd say is > > not exactly the best Python code I've seen - no offense to Stuart, who > > I'm sure whipped it up in a hurry and has much better things to work > > on). The question I asked and his reply: > > I'm not suggesting my code is the best on the planet, but hey it's out > there, it's free and it gets the job done. So rather than just sniping > with unsupported assertions why don't you share your expertise with us > and give some examples (or better still write some documentation > yourself). That way we all get to learn something. Wow. Calm down, buddy. Again, no need to be offended. I was just trying to help answer a familiar question. Yes, I threw in a critique (barely), but there are better ways to win over contributors than to snap at your users. But to answer your question: I don't because at the moment I'm still assessing whether another project (Pandoc) would be a wiser investment of effort. Yang > > > > > >>> - Developers' documentation, to make it easier for others to > >>> understand (from a big-picture perspective) how the code is > >>> organized, such that we might be able to contribute more efficiently > >>> to the project. > >> AsciiDoc is a small fairly straight-forward program (just a 4000 line > >> Python script), and while I agree that a nice overview will, well, give > >> you nice overview and maybe a leg up the learning curve, if you want to > >> modify the source code there's no substitute for a working knowledge of > >> the application and just reading the source code. While I've found that > >> it's always a psychological hurdle to open up someone else source, you > >> very quickly get a much better understanding of how things are put > >> together. > > > > But perhaps for a specific question (e.g. table-related code) he can > > offer a pointer. > > > > Yang > > > > > > On 11/17/06, Anmar Oueja anmar-at-canada.com |asciidoc| > > <...> wrote: > >> Hello Stuart: > >> > >> I have been giving this a lot of thought. I went through many Wiki's > >> implementations of Tables (not code, just markup) and found a few good > >> ones. > >> > >> - Mediawiki has the most flexible and most suitable for multiple lines > >> within a table > >> - Dokuwiki has a simple but effective formatting > >> > >> I am willing to look into the code my self, although I am not a > >> developer. Do you know where can I get started? > >> > >> Cheers! > >> > >> Anmar > >> > >> Stuart Rackham wrote: > >>> Hi Anmar > >>> > >>> Anmar Oueja wrote: > Hello Stuart: > > Thanks for the quick response. Any chance this will be rectified in > the near future? > >>> No this is not a priority for me at this stage -- but I'm happy to look > >>> at any workable patches user come up with. > >>> > >>> From the AsciiDoc User Guide: "The current table syntax is overly > >>> complicated and unwieldy to edit, hopefully a more usable syntax will > >>> appear in future versions of AsciiDoc." > >>> > >>> > >>> > >>> > Anmar > > Stuart Rackham wrote: > > Hi Anmar > > > > The current version only allows a paragraph of text in each cell. > > > > Cheers, Stuart > ___ > Asciidoc-discuss mailing list > Asciidoc-discuss@metaperl.com > http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss > > >>> Cheers, Stuart > >> > >> ___ > >> Asciidoc-discuss mailing list > >> Asciidoc-discuss@metaperl.com > >> http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss > >> > > > > ___ > > Asciidoc-discuss mailing list > > Asciidoc-discuss@metaperl.com > > http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss > > > > Cheers, Stuart > -- > Stuart Rackham > > ___ > Asciidoc-discuss mailing list > Asciidoc-discuss@metaperl.com > http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss > ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss
Re: [asciidoc-discuss] Bullets in the table
Yang wrote: > Hey Anmar, > > Stuart may have something more to say, but there isn't (and probably > won't be in the near future) any resource for introducing developers > to the code base (which to be fair is not that large, but I'd say is > not exactly the best Python code I've seen - no offense to Stuart, who > I'm sure whipped it up in a hurry and has much better things to work > on). The question I asked and his reply: I'm not suggesting my code is the best on the planet, but hey it's out there, it's free and it gets the job done. So rather than just sniping with unsupported assertions why don't you share your expertise with us and give some examples (or better still write some documentation yourself). That way we all get to learn something. > >>> - Developers' documentation, to make it easier for others to >>> understand (from a big-picture perspective) how the code is >>> organized, such that we might be able to contribute more efficiently >>> to the project. >> AsciiDoc is a small fairly straight-forward program (just a 4000 line >> Python script), and while I agree that a nice overview will, well, give >> you nice overview and maybe a leg up the learning curve, if you want to >> modify the source code there's no substitute for a working knowledge of >> the application and just reading the source code. While I've found that >> it's always a psychological hurdle to open up someone else source, you >> very quickly get a much better understanding of how things are put together. > > But perhaps for a specific question (e.g. table-related code) he can > offer a pointer. > > Yang > > > On 11/17/06, Anmar Oueja anmar-at-canada.com |asciidoc| > <...> wrote: >> Hello Stuart: >> >> I have been giving this a lot of thought. I went through many Wiki's >> implementations of Tables (not code, just markup) and found a few good ones. >> >> - Mediawiki has the most flexible and most suitable for multiple lines >> within a table >> - Dokuwiki has a simple but effective formatting >> >> I am willing to look into the code my self, although I am not a >> developer. Do you know where can I get started? >> >> Cheers! >> >> Anmar >> >> Stuart Rackham wrote: >>> Hi Anmar >>> >>> Anmar Oueja wrote: Hello Stuart: Thanks for the quick response. Any chance this will be rectified in the near future? >>> No this is not a priority for me at this stage -- but I'm happy to look >>> at any workable patches user come up with. >>> >>> From the AsciiDoc User Guide: "The current table syntax is overly >>> complicated and unwieldy to edit, hopefully a more usable syntax will >>> appear in future versions of AsciiDoc." >>> >>> >>> >>> Anmar Stuart Rackham wrote: > Hi Anmar > > The current version only allows a paragraph of text in each cell. > > Cheers, Stuart ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss >>> Cheers, Stuart >> >> ___ >> Asciidoc-discuss mailing list >> Asciidoc-discuss@metaperl.com >> http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss >> > > ___ > Asciidoc-discuss mailing list > Asciidoc-discuss@metaperl.com > http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss > Cheers, Stuart -- Stuart Rackham ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss
Re: [asciidoc-discuss] Bullets in the table
Hello Yang: Thanks a lot for the introduction. Diving in the best approach. I guess I have to learn Python after all :) Anmar Yang wrote: > Hey Anmar, > > Stuart may have something more to say, but there isn't (and probably > won't be in the near future) any resource for introducing developers > to the code base (which to be fair is not that large, but I'd say is > not exactly the best Python code I've seen - no offense to Stuart, who > I'm sure whipped it up in a hurry and has much better things to work > on). The question I asked and his reply: > >>> - Developers' documentation, to make it easier for others to >>> understand (from a big-picture perspective) how the code is >>> organized, such that we might be able to contribute more efficiently >>> to the project. >> AsciiDoc is a small fairly straight-forward program (just a 4000 line >> Python script), and while I agree that a nice overview will, well, give >> you nice overview and maybe a leg up the learning curve, if you want to >> modify the source code there's no substitute for a working knowledge of >> the application and just reading the source code. While I've found that >> it's always a psychological hurdle to open up someone else source, you >> very quickly get a much better understanding of how things are put together. > > But perhaps for a specific question (e.g. table-related code) he can > offer a pointer. > > Yang > > > On 11/17/06, Anmar Oueja anmar-at-canada.com |asciidoc| > <...> wrote: >> Hello Stuart: >> >> I have been giving this a lot of thought. I went through many Wiki's >> implementations of Tables (not code, just markup) and found a few good ones. >> >> - Mediawiki has the most flexible and most suitable for multiple lines >> within a table >> - Dokuwiki has a simple but effective formatting >> >> I am willing to look into the code my self, although I am not a >> developer. Do you know where can I get started? >> >> Cheers! >> >> Anmar >> >> Stuart Rackham wrote: >>> Hi Anmar >>> >>> Anmar Oueja wrote: Hello Stuart: Thanks for the quick response. Any chance this will be rectified in the near future? >>> No this is not a priority for me at this stage -- but I'm happy to look >>> at any workable patches user come up with. >>> >>> From the AsciiDoc User Guide: "The current table syntax is overly >>> complicated and unwieldy to edit, hopefully a more usable syntax will >>> appear in future versions of AsciiDoc." >>> >>> >>> >>> Anmar Stuart Rackham wrote: > Hi Anmar > > The current version only allows a paragraph of text in each cell. > > Cheers, Stuart ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss >>> Cheers, Stuart >> >> ___ >> Asciidoc-discuss mailing list >> Asciidoc-discuss@metaperl.com >> http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss >> > > ___ > Asciidoc-discuss mailing list > Asciidoc-discuss@metaperl.com > http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss
Re: [asciidoc-discuss] Bullets in the table
Hey Anmar, Stuart may have something more to say, but there isn't (and probably won't be in the near future) any resource for introducing developers to the code base (which to be fair is not that large, but I'd say is not exactly the best Python code I've seen - no offense to Stuart, who I'm sure whipped it up in a hurry and has much better things to work on). The question I asked and his reply: > > - Developers' documentation, to make it easier for others to > > understand (from a big-picture perspective) how the code is > > organized, such that we might be able to contribute more efficiently > > to the project. > > AsciiDoc is a small fairly straight-forward program (just a 4000 line > Python script), and while I agree that a nice overview will, well, give > you nice overview and maybe a leg up the learning curve, if you want to > modify the source code there's no substitute for a working knowledge of > the application and just reading the source code. While I've found that > it's always a psychological hurdle to open up someone else source, you > very quickly get a much better understanding of how things are put together. But perhaps for a specific question (e.g. table-related code) he can offer a pointer. Yang On 11/17/06, Anmar Oueja anmar-at-canada.com |asciidoc| <...> wrote: > Hello Stuart: > > I have been giving this a lot of thought. I went through many Wiki's > implementations of Tables (not code, just markup) and found a few good ones. > > - Mediawiki has the most flexible and most suitable for multiple lines > within a table > - Dokuwiki has a simple but effective formatting > > I am willing to look into the code my self, although I am not a > developer. Do you know where can I get started? > > Cheers! > > Anmar > > Stuart Rackham wrote: > > Hi Anmar > > > > Anmar Oueja wrote: > >> Hello Stuart: > >> > >> Thanks for the quick response. Any chance this will be rectified in > >> the near future? > > > > No this is not a priority for me at this stage -- but I'm happy to look > > at any workable patches user come up with. > > > > From the AsciiDoc User Guide: "The current table syntax is overly > > complicated and unwieldy to edit, hopefully a more usable syntax will > > appear in future versions of AsciiDoc." > > > > > > > > > >> > >> Anmar > >> > >> Stuart Rackham wrote: > >>> Hi Anmar > >>> > >>> The current version only allows a paragraph of text in each cell. > >>> > >>> Cheers, Stuart > >> > >> ___ > >> Asciidoc-discuss mailing list > >> Asciidoc-discuss@metaperl.com > >> http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss > >> > > > > Cheers, Stuart > > > ___ > Asciidoc-discuss mailing list > Asciidoc-discuss@metaperl.com > http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss > ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss
Re: [asciidoc-discuss] Bullets in the table
Hello Stuart: I have been giving this a lot of thought. I went through many Wiki's implementations of Tables (not code, just markup) and found a few good ones. - Mediawiki has the most flexible and most suitable for multiple lines within a table - Dokuwiki has a simple but effective formatting I am willing to look into the code my self, although I am not a developer. Do you know where can I get started? Cheers! Anmar Stuart Rackham wrote: > Hi Anmar > > Anmar Oueja wrote: >> Hello Stuart: >> >> Thanks for the quick response. Any chance this will be rectified in >> the near future? > > No this is not a priority for me at this stage -- but I'm happy to look > at any workable patches user come up with. > > From the AsciiDoc User Guide: "The current table syntax is overly > complicated and unwieldy to edit, hopefully a more usable syntax will > appear in future versions of AsciiDoc." > > > > >> >> Anmar >> >> Stuart Rackham wrote: >>> Hi Anmar >>> >>> The current version only allows a paragraph of text in each cell. >>> >>> Cheers, Stuart >> >> ___ >> Asciidoc-discuss mailing list >> Asciidoc-discuss@metaperl.com >> http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss >> > > Cheers, Stuart ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss
Re: [asciidoc-discuss] Bullets in the table
Hello Stuart: Thanks for the quick response. Any chance this will be rectified in the near future? Anmar Stuart Rackham wrote: > Hi Anmar > > The current version only allows a paragraph of text in each cell. > > Cheers, Stuart ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss
Re: [asciidoc-discuss] Bullets in the table
Hi Anmar The current version only allows a paragraph of text in each cell. Cheers, Stuart -- Stuart Rackham Anmar Oueja wrote: > Hello Asciidoc dudes and dudettes: > > I need to put some bullets in my tables. Here is a fatal attempt at > some ASCIIArt to explain my point: > > ++--+ > | Blah Blah | * Blah Blah | > || ** Blah | > ++--+ > > How can I do that assuming i can? > > This is one thing that is stopping me from seriously considering > Asciidoc for my documentation needs. > > Anmar > > ___ > Asciidoc-discuss mailing list > Asciidoc-discuss@metaperl.com > http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss > ___ Asciidoc-discuss mailing list Asciidoc-discuss@metaperl.com http://metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss
