I was focusing on different features though. For me the biggest pain was that all the recipes were always listing ingredients and quantities first and then just referencing them by name. You either have to weight and measure everything first (which I don't do) or scroll back and forth all the time. So I came up with a JSON format that does what cooklang does: create ingredient+quantity object and reference it in the recipe body. This way we get automated scaling but the quantities can still be mentioned in the recipe body. The second issue was that no recipes use this format so I integrated with some LLMs to automatically translate any recipe custom JSON.
6 Comments
NikkiDimes@lemmy.world · 3 pts · 143d
Interesting. Do you have anything to do with the development of this language?
Beep@lemmus.org · -8 pts · 143d
Nope.
NikkiDimes@lemmy.world · 8 pts · 143d
Oh awesome, I'll check it out then!
WreckingBANG@programming.dev · 1 pts · 143d
Sadly the mobile-apps are not foss
mapleseedfall@lemmy.world · 1 pts · 143d
Wow this is almost exactly what im lookingfor this week
ExLisper@lemmy.curiana.net · 1 pts · 143d
Interesting. I was thinking about something like that years ago and eventually I made an app: https://f-droid.org/en/packages/net.curiana.recipes/
I was focusing on different features though. For me the biggest pain was that all the recipes were always listing ingredients and quantities first and then just referencing them by name. You either have to weight and measure everything first (which I don't do) or scroll back and forth all the time. So I came up with a JSON format that does what cooklang does: create ingredient+quantity object and reference it in the recipe body. This way we get automated scaling but the quantities can still be mentioned in the recipe body. The second issue was that no recipes use this format so I integrated with some LLMs to automatically translate any recipe custom JSON.