Open Source Ecology
Main Text Channels / other-open-source-groups
They have discords, links expire, so just look them up or ask Eric
1
1
1
### Call the compiler with a glob pattern
osript compile --source='./*in*.+(osr)' --output='./${SRC_NAME}.+(md)' --debug=true --language=osr
Input : https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/tests/test.in.osr
Output : https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/tests/test.in.md
I needed something like this to also decouple data from cloud services as Google Sheets to produce mainly static content, including rendering templates over Jekyll into PDFs (Manuals)
Quite some fun stuff
Internally it's using/abusing Liquid (JS implementation) (used in Jekyll and Github pages) and I extended it for Javascript whilst having scope variables accessible between the both (see https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/examples/js-tests.html).
Next chapters :
2
### Call the compiler with a glob pattern
osript compile --source='./*in*.+(osr)' --output='./${SRC_NAME}.+(md)' --debug=true --language=osr
Input : https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/tests/test.in.osr
Output : https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/tests/test.in.md
I needed something like this to also decouple data from cloud services as Google Sheets to produce mainly static content, including rendering templates over Jekyll into PDFs (Manuals)
Quite some fun stuff
Internally it's using/abusing Liquid (JS implementation) (used in Jekyll and Github pages) and I extended it for Javascript whilst having scope variables accessible between the both (see https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/examples/js-tests.html).
Next chapters :
### Call the compiler with a glob pattern
osript compile --source='./*in*.+(osr)' --output='./${SRC_NAME}.+(md)' --debug=true --language=osr
Input : https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/tests/test.in.osr
Output : https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/tests/test.in.md
I needed something like this to also decouple data from cloud services as Google Sheets to produce mainly static content, including rendering templates over Jekyll into PDFs (Manuals)
Quite some fun stuff
Internally it's using/abusing Liquid (JS implementation) (used in Jekyll and Github pages) and I extended it for Javascript whilst having scope variables accessible between the both (see https://git.osr-plastic.org/plastichub/lib-content/src/branch/master/examples/js-tests.html).
Next chapters :
the purpose of the language is rather intermediate, transforming content from one source to another output format - with zero dependencies I gonna check it out in depth over the weekend - looks like a good replacement for Jekyll ...
@Holger - it handles xlsx, google sheets and CSV files so far (internal query language is still missing...).
To manage BOMs I am also still looking for something more adequate. More likely we have to shift from Spreadsheets to something ERP'ish. Different product configurations and also different sources makes this pretty difficult. Especially now in c19 times, one has to change quickly among different suppliers - not just material is running out everywhere but also prices changed a lot over night - to a degree that we had to refund even orders.
However, til now we're using Spreadsheets but also increasingly PDM/BOM features within Solidworks which come with a bunch of extras as automatic sustainability reports - still trying to extract this data via Solidworks APIs ...
There was a nice editor for BOMs somewhere on Github (Nodejs & VUE based) - I hope I can find it back. Not sure though at which level you want it
BOMs seem also to rely a lot on the internal company's data organization/structure. In the next years, I am continuing with this here :
Turns out that you need the BOM data in different ways across different system. For instance customers want to re-order replacements for consumables - it's really tedious and time consuming to handle this with a small team.
3 3
1
3
2
1
What sucks most is the limited choices of boards with debugger interfaces/pins, close to your production variant, leaving you mostly with exorbitant macros and debug print statements running fast out of memory.
I guess we have some standards for low-tech extruders
References:
1. Lydia-v4.5: http://files.osr-plastic.org/files/machines/extrusion/lydia-v4.5/
2. - clamp (in progress) : http://files.osr-plastic.org/files/machines/extrusion/components/101_lucy/. open tasks : ejection and mold cooling
3. Lydia-Mini (ok for filament): http://files.osr-plastic.org/files/machines/extrusion/lydia-mini/ 
I guess we have some standards for low-tech extruders
References:
1. Lydia-v4.5: http://files.osr-plastic.org/files/machines/extrusion/lydia-v4.5/
2. - clamp (in progress) : http://files.osr-plastic.org/files/machines/extrusion/components/101_lucy/. open tasks : ejection and mold cooling
3. Lydia-Mini (ok for filament): http://files.osr-plastic.org/files/machines/extrusion/lydia-mini/ 
1
2
