-
Notifications
You must be signed in to change notification settings - Fork 37
Home
Pillar and MicroDown
The tests in Pillar-Test-Core mix several concerns. They test that a text in some syntax is parsed and equals to some AST. They test that a tree can be exported to some syntax and equals to the original syntax. They test that a tree can be exported to plain text and equals to the original plain text.
testParseOnlyAnnotation
| wiki text tree |
wiki := '@@foo'.
text := ''.
tree := PRDocument new
add: (PRAnnotatedParagraph new
annotation: 'foo';
yourself);
yourself.
self assertWiki: wiki equalsTree: tree.
self assertTree: tree equalsWiki: wiki.
self assertTree: tree equalsText: text
All these tests should be cut in many tests, each with a separate assertion. And each of these assertions should come with only the setup they need.
0 Loading + Travis P8 PillarApp + Microdown = BaselineOfPillarApp
P8 PillarRichText + Microdown = MicrodownForPharo = BaselineOfMicroDev - Ok - Travis
-
Introduire MD dans la boucle de books pillar
-
Splitting baselines to make Pillar for Pharo independent of Pillar Book
-
Faire tourner sur Pharo9 P9 PillarBook + Microdown = BaselineOfPillarMicro P9 PillarBasicDocumentModel (with rich text renderer) + Microdown = MicrodownForPharo = BaselineOfMicrodown
- PillarApp + Microdown
- Pillar-Microdown has only a test?
- Pillar-PillarTextRichTextExporter
- Check why MicrodownCommentRenderer test is not taken into account
- Pillar-ExporterMicrodown has strange dependencies
- Clean old baseline remove baselineOfPear
PillarApp-Microdown (Microdown integration to pillar app) repo: Microdown dependencies: PillarApp, MD-to-Pillar
- extending extension points pillar book to call the microdown parser
[DONE] MicrodownCommentRenderer repo: Microdown dependencies: MicroDown Calypso integration (but this is "pillar" generic)
[DONE] MicroDown repo: Microdown dependencies: PillarDocumentModel Microdown parser microdown model Transform Microdown AST to PillarDocumentModel
[DONE] PillarApp repo: Pillar future: To be split in PillarPipeline and Foundation dependencies: PillarDocumentModel, Mustache (externe), Chrysal (externe) - config files (Chrysal)
- pipeline
- command line, clap
- booktester
Pillar Parser Exporters Pillar Full Model
- extensions
- columns, citations, footnote, slide, tocs App et packaging
DONE] PillarDocumentModel (basic elements + basic visitor) repo: Pillar Pillar-Core PillarRichTextRenderer "for now I thought it was PillarCore but this is not the case" + tests
Currently checking in 8.0.12 + new sba https://travis-ci.com/github/SquareBracketAssociates/booklet-Commander
https://travis-ci.com/github/SquareBracketAssociates/Booklet-LLVMCompilationWithPharo https://travis-ci.com/github/SquareBracketAssociates/Booklet-ManagingCode https://travis-ci.com/github/SquareBracketAssociates/Booklet-OPAL
-
https://github.com/SquareBracketAssociates/Booklet-BuildingMemoryGameWithBloc ! LaTeX Error: File `_support/latex/sbabook/sbabook.cls' not found.
-
Smacc https://travis-ci.org/github/SquareBracketAssociates/Booklet-Smacc ! LaTeX Error: File `_support/latex/sbabook/sbabook.cls' not found.
-
https://github.com/SquareBracketAssociates/Booklet-ClapCommandLine
-
https://github.com/SquareBracketAssociates/Booklet-AMiniSchemeInPharo
-
Chosen https://github.com/SquareBracketAssociates/Booklet-PharoChosenPieces https://travis-ci.com/github/SquareBracketAssociates/Booklet-PharoChosenPieces
To be continued
-
Successfully Migrated to 8.0.12 but should check latest dependency and version of sba
-
OPAL https://github.com/SquareBracketAssociates/Booklet-OPAL
-
Zinc https://github.com/SquareBracketAssociates/booklet-ZincHTTP
-
Managing code https://github.com/SquareBracketAssociates/Booklet-ManagingCode
-
LLVM https://github.com/SquareBracketAssociates/Booklet-LLVMCompilationWithPharo
-
Commander 20
-
STON https://github.com/SquareBracketAssociates/Booklet-STON
-
Booklet-PharoChosenPieces
-
https://travis-ci.org/github/SquareBracketAssociates/Booklet-Scraping
-
https://travis-ci.org/github/SquareBracketAssociates/Booklet-uFFI
-
https://github.com/SquareBracketAssociates/Booklet-DataFrame
-
https://github.com/SquareBracketAssociates/Booklet-ConcurrentProgramming
-
https://github.com/SquareBracketAssociates/Booklet-PharoVirtualMachine
-
https://github.com/SquareBracketAssociates/Booklet-FunWithInterpreters
-
https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle
-
https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle - ObjVlisp https://travis-ci.org/github/SquareBracketAssociates/Booklet-AReflectiveKernel https://travis-ci.org/github/SquareBracketAssociates/Booklet-AReflectiveKernel
-
Broken
-
Spec2 https://github.com/SquareBracketAssociates/BuildingApplicationWithSpec2 ===========Latexmk: Missing input file: '/home/travis/build/SquareBracketAssociates/BuildingApplicationWithSpec2/_result/pdf/Chapters/CaseStudyOne/figures/MissingFIle.png' from line 4946 'LaTeX Warning: File
/home/travis/build/SquareBracketAssociates/BuildingApplicationWithSpec2/_result/pdf/Chapters/CaseStudyOne/figures/MissingFIle.png' not found on input line 799.' 4947Latexmk: Missing input file: '/home/travis/build/SquareBracketAssociates/BuildingApplicationWithSpec2/_result/pdf/Chapters/CaseStudyOne/figures/MissingFIle.png' from line 4948 'LaTeX Warning: File
/home/travis/build/SquareBracketAssociates/BuildingApplicationWithSpec2/_result/pdf/Chapters/CaseStudyOne/figures/MissingFIle.png' not found on input line 799.' 4949Latexmk: Non-existent bbl file 'index.bbl' -
TinyBlog (does not find figures) https://travis-ci.org/github/SquareBracketAssociates/TinyBlogTutorial
-
Testing raises a PP2Failure not found ? https://github.com/SquareBracketAssociates/Booklet-TestingInPharo Not sure that it has been correctly migrated.
-
AI Technics is failing on latexmk?
-
Loop I can latex the expression chapter in standalone pillar build pdf Chapters/Expressions/Expressions.pillar produces a pdf.
-
Loop https://github.com/SquareBracketAssociates/LearningOOPWithPharo
ollected error summary (may duplicate other messages):
pdflatex: Command for 'pdflatex' gave return code 1
Refer to '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks2/LearningOOPWithPharo/_result/pdf/Chapters/Expressions.log' for details
Error: command latexmk failed
PRPDFDocument(Object)>>error:
PRPDFDocument>>executeOnUnixCommand:arguments:workingDirectory:
PRPDFDocument>>executeCommand:arguments:workingDirectory:
PRPDFDocument>>postWriteTransform:
-
https://github.com/SquareBracketAssociates/DynamicWebDevelopmentWithSeaside '/home/travis/build/SquareBracketAssociates/DynamicWebDevelopmentWithSeaside/_result/pdf/Chapters/11-Sudoko/figures/rowOfNumbers.png' from line 7945 'LaTeX Warning: File
/home/travis/build/SquareBracketAssociates/DynamicWebDevelopmentWithSeaside/_result/pdf/Chapters/11-Sudoko/figures/rowOfNumbers.png' not found on input line 4828.' 7946Latexmk: Missing input file: '/home/travis/build/SquareBracketAssociates/DynamicWebDevelopmentWithSeaside/_result/pdf/Chapters/11-Sudoko/figures/rowOfNumbers.png' from line 7947 'LaTeX Warning: File
/home/travis/build/SquareBracketAssociates/DynamicWebDevelopmentWithSeaside/_result/pdf/Chapters/11-Sudoko/figures/rowOfNumbers.png' not found on input line 4828.' -
TODO for Stef in the future
- Migrate FAMIXNG
- still on 7.7.1 https://github.com/SquareBracketAssociates/Booklet-XML
#PROCESS Normally this process should be in Microdown repo.
-
Harvest changes done to MD in Pharo
-
this is for the case somebody touched MD directly. We need to push those changes to the MD repo.
-
Image Pharo Latest
-
Checkout microdown/release avec option "Do not load code" in the dropdown => this will leave the image as is, with the Pharo version of MD => if pharo and MD are clean, there are no changes, we are done
-
Create a new MD branch e.g., "harvestFromPharoXXX"
-
Commit all Pharo changes
-
checkout development
-
merge "harvestFromPharoXXX" into development
-
Freeze for release MD "Precondition: Fixes from pharo have been harvested"
-
Image Pharo Latest
-
Checkout branch release
-
Merge dev dans release
-
Verify that the baseline of pillar in baselineOfMicrodown points on the good tag. (mais attention c'est pour le repo microdown et pas celui de Pharo).
-
Create un tag microdown (- Normalement on n'a pas besoin de toucher BaselineOfIDE)
- Push sur le repository Microdown sur Release Branch
"Precondition: Fixes from pharo have been harvested and release is done" - Take latest Pharo - Load tagged microdown from microdown repo - Commit + PR Pharo
- Check process to develop MD
- Harvest step
- Checkout branch development of MD
- load baselineOfMicrodownDev!