You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is best description of CLUS collaboration plans about CCLDoc add-ons that I can write. By no mean they is canonical list, I just collected and organized things about I talk and heard from wiser than me in CLUS matters folks. Also I don't know how realistic some points are or how much work to do it will be needed trying to realized it. I still try to fully understand my thread of work.
If someone need more information try contact community of CLUS on freenode #lisp, or Discord #clus-general. You can also read paper staying CLUS reason to be and aims. Unfortunately this paper is much outdated https://github.com/phoe/clus-data/blob/master/paper.pdf.
IMPORTANT
Statement of CLUS community now is: Content is a king! So now we are interested with creating web pages that have good CL content, giving it good look is not issue now. Because I have little idea how make web page look good, I decide do disregard this issue totally.
What we need to do with CCLDoc.
Create new tags for things like variable references, glossary entries, code blocks, diffrent kinds of result values, etc.
EXAMPLE
We want write something like "Function {:cl:functions:some-function}"
which will expand to proper hyperlink to page with some-function.
We want create functions (load-graph *SOMETHING*) (output-graph *SOMETHING* "somewhere")
which creates not single HTML, but bunch of HTML pages hyper-linked with each others. This is connected with previous point, we want that all new defined tags expand in proper hyperlinks in this step.
To make former works, we need to define new class, call it GRAPH-DOCUMENT for now, that is related to class DOCUMENT in some not precised now way.
What we are doing now. There are two threads.
Create some proof of concept CCLDoc file (probably "Function GENSYM") that will used desired tags, which after we need to create.
a) Dig up into CCLDoc code enough to make creation of all add-ons possible.
b) Create documentation of code that we understand as side effect of point a).
Unfortunately I now only person that works on second thread. Time will show what I can do in current situation.
If English of this post is bad, give me a sign, I try to correct it.
The text was updated successfully, but these errors were encountered:
This is best description of CLUS collaboration plans about CCLDoc add-ons that I can write. By no mean they is canonical list, I just collected and organized things about I talk and heard from wiser than me in CLUS matters folks. Also I don't know how realistic some points are or how much work to do it will be needed trying to realized it. I still try to fully understand my thread of work.
If someone need more information try contact community of CLUS on freenode #lisp, or Discord #clus-general. You can also read paper staying CLUS reason to be and aims. Unfortunately this paper is much outdated https://github.com/phoe/clus-data/blob/master/paper.pdf.
IMPORTANT
Statement of CLUS community now is: Content is a king! So now we are interested with creating web pages that have good CL content, giving it good look is not issue now. Because I have little idea how make web page look good, I decide do disregard this issue totally.
What we need to do with CCLDoc.
Create new tags for things like variable references, glossary entries, code blocks, diffrent kinds of result values, etc.
EXAMPLE
We want write something like
"Function {:cl:functions:some-function}"
which will expand to proper hyperlink to page with some-function.
We want create functions
(load-graph *SOMETHING*)
(output-graph *SOMETHING* "somewhere")
which creates not single HTML, but bunch of HTML pages hyper-linked with each others. This is connected with previous point, we want that all new defined tags expand in proper hyperlinks in this step.
To make former works, we need to define new class, call it GRAPH-DOCUMENT for now, that is related to class DOCUMENT in some not precised now way.
What we are doing now. There are two threads.
Create some proof of concept CCLDoc file (probably "Function GENSYM") that will used desired tags, which after we need to create.
a) Dig up into CCLDoc code enough to make creation of all add-ons possible.
b) Create documentation of code that we understand as side effect of point a).
Unfortunately I now only person that works on second thread. Time will show what I can do in current situation.
If English of this post is bad, give me a sign, I try to correct it.
The text was updated successfully, but these errors were encountered: