> It relies on Markdown (and LaTeX through extensions). We export to Md, but will be adding more import/export options in the future. We hope to create a publication standard for it.
Do we need a new standard for structured documents? Would a <section> not be sufficient?
Re:Show HN: Gingko, a tree-document editor
by adriano_f on Friday August 30, 2013 @04:24PM
(#6304003)
For three levels deep, no we don't need a new standard. Larger trees, linked together will probably need something new.
Re:Show HN: Gingko, a tree-document editor
by IanCal on Saturday August 31, 2013 @05:28AM
(#6306328)
Larger trees are fine with <section>, and linking together is already defined with <a>.
Re:Show HN: Gingko, a tree-document editor
by zachrose on Friday August 30, 2013 @06:24PM
(#6304597)
Why does it matter how many levels there are?
He's probably talking about many-to-many relationships that he has planned.
Hi Adrioano,
I've been working on a relatively similar, but much larger and very complex project (AI/Maths) for some years now. It makes me really happy to see people coming up with the vision of a "hypertext" perspective shift.
Do you mind explaining why your surname is Ferrari?
Re:Show HN: Gingko, a tree-document editor
by adriano_f on Sunday September 01, 2013 @10:23AM
(#6310470)
"Hypertext" perspective shift... I like that.
What's your project called? Can I see it?
PS: My ancestry goes: Italian > Argentinian > born in Kuwait > living in Canada. "Ferrari" means iron-worker in Italian, so it's not a rare surname in Italy.
Check your mail (I'll probably land in your spam folder).
PS: Very interesting ancestry, wish I had more knowledge into my own. It led me to think that you might be related to the Ferrari Company somehow.
1. It's both a viewer and a word processor. It relies on Markdown (and LaTeX through extensions). We export to Md, but will be adding more import/export options in the future. We hope to create a publication standard for it.
2. The structure of the document is an "outline of index cards". Each card can have one or more children. Source content (in markdown) is edited by toggling edit mode on that card.
3. Yes, we are extracting parts of this as open-source. The rest remains proprietary (for now, at least).
> I apologize if any of the above seems harsh
No need to apologize. Thoughtful criticism is what we need.
Thanks!