Laeserin @Laeserin - 2mo
Finally got my debugger setup, on my new computer, and I immediately rediscovered why using a debugger is a programming superpower.
xdebug for PHP
There is now only one 30040 book on wss://thcitadel.nostr1.com, but it is correctly formatted, including the tags. More will be published soon, for test data, and then I'll republish the Bible books in the updated format. Had to refactor the whole thing. Took me all day. But it's no long as embarrassingly static. 😅
GitCitadel @GitCitadel - 2mo
#ProjectAlexandria is coming along. Here you see some of Aesop's fables. If you want to better understand how such a an eBook is constructed, you can view the original 30040 event, with the linked 30041 events listed, here: https://njump.me/nevent1qqswqqzfxpmm3fx4dn39dc373mtds2veqv0vzlf2dfw0f3yv75gqu5sprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqgs9wd35keyxxn966y8jg5thvzy75ggfpk2q0ac4aq79w76xzxhxahqxmd5hw nostr:nevent1qvzqqqqqqypzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpr3mhxue69uhhg6r9vd5hgctyv4kzumn0wd68yvfwvdhk6tcqyr8a596mxuk30fyvck8tlzcdfjnautdvhewm7a34d5fdh8uccqz2kgwfqdv
Stella is an entire herd of wild, spergy testers.
Yeah, I refactored everything and it started acting weird and I had no clue what was going on. 😅 🤷♀️
Here the book is, all alone, in the card view. It will soon be getting company, tho! 😊 Had to redo all of the logic, to account for the "d" tag construct and having optional tags, and the removal of "content" in the 30040.
I feel like the card isn't well-defined enough, on the background. Should maybe be a tad lighter, like ToC.
It did, actually, because it showed me the same result that my logging was showing me: nothing. And run it again... nothing. And run it again... nothing. It was an infinite loop. 😅 I had a copy-paste error with a getter that called itself. Looked at it for almost an hour and couldn't see the problem, so I was like, let me ask the debugger, and then the stack blew up.
I'm assuming the cards will be ordered in rows and columns.
You can use the events for anything, just need to include a link to the .mp3 or .mp4. Could also use it for a an art gallery, or something. Include a link to the image for each piece in the respective 30041 section and bind similar artwork-sections into a collect with a 30040, so that you get an index on the left and can page through them. Or a magazine or journal, with the articles each in a 30041, and the 30040 is a volume. Whatever.
Let me go do an audiobook one. That's a fun idea.
Here you can see how you could do something like that. Each audiofile in the collection gets it's own section, where you can add information and images, and then you can page through the sections and click on the mp3 files, to listen to them. Sorry that the Asciidoc formatting doesn't let you see the pictures, yet. It actually looks quite pretty, with the original book covers from Beatrix Potter. I think nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn still has markdown formatting setup, but I made him a ngit issue for it. https://i.nostr.build/Aie20eHR2CNvryOb.png
Here's how each section looks, in my code editor preview. You could also format the sections with a table, so that it looks like on the original webpage. https://librivox.org/the-tale-of-peter-rabbit-and-others-by-beatrix-potter/ Then it's horizontal formatting, rather than vertical.
I just did this real quick, so I didn't color the background or center the text in the columns, or anything, but this gives you an idea of what the table-based orientation looks like in the viewer.
Each section is a separate event, they're just linked together in a row by the index event. You can change which sections are included, or edit the content of the sections, after the fact, as they are parameterized replaceable. Someone who is writing a wiki page about Beatrix Potter, could (theoretically, they haven't implemented it, yet) take the first section only, and place that event in the wiki page, as a quote or reference.
I think this makes it more clear, why we wanted Asciidoc, instead of markdown. People can use these event types for high-quality publishing, with stylesheets and complex tables, side bars, etc. Can't even adjust image size, with markdown.
