Hi Richard, My first impulse would be to write the document DSL or DSLs as a Scribble dialect. Scribble allows you to freely insert code in text documents and enables PDF rendering. I'm not sure if there is a best practice for writing Scribble languages, but I've found that it's easier to start from an existing, simple Scribble dialect and add/remove some functionality to get a hang of it. It could also handle the "general Documents language": most Scribble dialects inherit functionality from scribble/base, so there's a parallel.
As for the records and reports: if I understand correctly, you don't want separate DSLs for these, but you want to be able to create these from within a "#lang documents/..." file? For instance so that an administrative employee can schedule a meeting directly in the invite, keep contact info in correspondence in sync with records, and so on? I'm pretty sure you can write a Scribble-based language so that you get side effects when you run programs written in it, so executing the document could read/write from/to a database and connect to an email server or web server. I guess you'll still want to review any documents even if the syntax is valid, so posting a preview document to a company-internal web server or sending a preview email, possibly with a link to send out the document definitively and something to roll back/permanently record the changes made to the database are all options. I'm sure others know more how the technical details would work, but it sounds like a fascinating project. I can't commit to anything right now, but it'd be great if you could keep us posted. Regards, Vincent -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
