[Cuis-dev] Erudite
Mariano Montone
marianomontone at gmail.com
Sun Oct 16 07:04:06 PDT 2022
A possible idea for the implementation:
Have an EruditeBookFilesSerializer that converts books to and from disk.
On disk, have a main file with the book title and sections descriptions,
in Smalltalk format.
Let's say, book.st:
EruditeBook new
title: 'My book';
sections: {'Section1'.
'Section2' -> {'Subsection1'. 'Subsection2'}}
Sections and subsections point to files on disk.
I thought of using yaml for that file, but Cuis does not have support.
Then, each section and subsection lives on its own file; they have plain
Erudite contents.
Please let me know if you have other ideas for an implementation.
Cheers,
Mariano
El 15/10/22 a las 18:36, Hilaire Fernandes via Cuis-dev escribió:
>
> Hi Mariano,
>
> Ok I got it.
>
> Writing the documentation in Erudite source format is fine as long as
> it is not melted with Smalltalk classes and methods, can be versioned
> independently, translated, etc. I don't think then it will be more
> difficult to edit than Texinfo.
>
> So it only needs to build Erudite book from erudite source format files.
>
>
> Le 15/10/2022 à 15:18, Mariano Montone via Cuis-dev a écrit :
>> My example was with Markdown, but you would use files in Erudite
>> source format, not Markdown, for your usecase. Then you build Erudite
>> books from those files. It is straightforward. There are no
>> conversions. Only matter: there are no good external editing tools
>> for those files, that can give you a preview, etc. But, are there
>> good user-facing editing tools for TexInfo, for example? Not sure
>> Emacs counts. So, I think it would be more or less like what you have
>> now with TexInfo, but you would have Erudite source files instead.
>> Also, I'm thinking a specialized Erudite editor could be provided for
>> files in Erudite format, coded in Cuis + Erudite, if you wanted.
> --
> GNU Dr. Geo
> http://drgeo.eu
> http://blog.drgeo.eu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20221016/1cc3f0ae/attachment-0001.htm>
More information about the Cuis-dev
mailing list