Hi Damien,
Thanks for your answer. Comments below.
On 07/21/2014 11:09 AM, Damien Cassou wrote:
On Sat, Jul 19, 2014 at 2:47 AM, Offray Vladimir Luna Cárdenas
<[email protected]> wrote:
The first idea that comes to mind is using STON for storage nodes and tree
information, so I can interchange it with the flatland files world and keep
it readable. Sounds that reasonable?
without more information, it is hard to stay. Try with STON and change
if that does not work :-). We have XML and JSON generators as well.
This is a kind of raw preview of I'm talking about:
http://www.enlightenment.org/ss/e-53cd4f36f021e9.68569046.jpg
Of course in this case, it is just a Help browser with a Playground
window over it, but I would like to have something like Playgrounds
inside the help browser. I was trying to build a custom browser with
Glamour, but seems that Help Browser already has the machinery I'm
looking for.
So my first question is how to use the Help Browser class as a template
for my outliner class? And can I put a Playground where the plain text
is located right now?
The second thing I would like to do is to add pandoc's markdown inside
comments, but I don't like the syntax of comments in Smalltalk because
single quotes are fairly easy to find in light markup language like
markdown. Is difficult to change it to create something more like python
(with """) or Lua (with -[]- )?
There is only one syntax for comments in Pharo. Instead of Markdown,
you might want to have a look at Pillar which is implemented in Pharo
and can generate Markdown (and html, and pdf) :
https://github.com/pillar-markup/pillar-documentation/
I have seen Pillar. Seems really interesting, but Pandocs markdown
support academic citation in several formats and I have already long
docs wrote on that format integrated in my workflow from Zotero and even
there is a growing community working on Scholarly Markdown[1][2] so I
would like to stick with it as much as I can for my own writing.
That being said. I would like also a better integration between
Smalltalk outliners and all the academic publication work flow,
including working better with pandoc as a external library.
[1] https://github.com/scholmd/scholmd/wiki
[2] http://blog.martinfenner.org/2013/06/29/metadata-in-scholarly-markdown/
[3]
http://programminghistorian.org/lessons/sustainable-authorship-in-plain-text-using-pandoc-and-markdown
Thanks again, this conversation with people in the community is very
valuable to me,
Offray
