e.g. C#/XAML, Java/XML, JS/HTML, Objective-C/Storyboard XML.. or Kotlin (Jetpack Compose), Dart (Flutter), JSX (React), Swift (SwiftUI)
I, for one, much more prefer working with a programming language alone. Microsoft tries too hard to push the C#/XAML with Windows GUI programming or cross-platform Xamarin.Forms. I prefer it because I don't have to switch tabs and also I don't need to do weird-finding-the-widget code like in Java (#getViewById). Jetpack Compose is a godsend for Android programming. Dart/Flutter is as well. Everything fits so nicely. Not so with markup language programming.
Happy New Year!
I created a new markup language during the New Year holidays.
https://pub.dev/packages/simple_widget_markup
You can also try it out on the following sites. However, a full HD or higher display is recommended.
https://simple-widget-markup-editor.web.app/
The reason I made this was because I wanted to deliver to my app users new information on Flutter Web, but HTML was difficult to use and markdown was not expressive.
The parsed markup text is replaceable with Flutter's Widget, so most of the static parts of the layout can be written in this language as well.
Also, This language is inherently simple, so even non-programmers should be able to use it immediately after training. (Although the documentation is still inadequate ...)
I don't know how much it will be accepted, but I hope it helps someone who has the same worries as me.
Thank you.
So they've created the ultimate replacement.
Your Only Data Language.
Hi, assuming that I have already come up with the design/rules of my markup language (not XML-based), what would I do next in order to "publish" or "release" it. (like making a parser etc)
For those that want to see it right away: GitHub: https://github.com/touchmarine/to Online Playground: http://touchlabs.io/play
I used markdown to write all kind of docs, mostly for my projects, but it started to become a PITA. Using markdown for online comments/posts or short docs is great but try anything more and it becomes increasingly frustrating.
Markdown is lightweight and that's one of the best things about it and I don't want to change that. But it's missing some very basic features like comments, notes/admonitions, and attributes. To get those features you have to use a markdown flavor that's incompatible with others or abandon markdown altogether and write your docs in an unreadable language.
I designed Touch to come with a default set of semantic elements that are common in writing. This set is not yet final (it might shrink) but in addition to markdown it provides:
- comments
- attributes (note: they're intended to be used very sparingly and serve as an escape hatch)
- numbered headings
- notes (or also known as admonitions or callouts)
- description lists
- subtitles (might be removed from default)
- captions (might be removed from default)
I very much enjoy working with Go so I designed Touch based on similar principles:
- it is explicit and has simpler syntax with fewer rules (e.g. both
-aand- aare list items unlike in markdown; see also 17 principles governing emphasis in markdown) - simpler syntax allows for easier tooling
- it is orthogonal and prefers composability (e.g. a named link element is composed from a group and a link element)
- comes with auto-formatting like gofmt
Touch is the result of my experieces with markdown, John MacFarlane's post beyond markdown, and my "research" of other people's problems with markdown. I would like to add that Touch really tries to stay similar to markdown as to stay familiar but, unlike markdown flavors, it's not constrained by it.
Would love to hear your thoughts! Best, touchmarine
Mau is a lightweight markup language heavily inspired by AsciiDoc that makes it a breeze to write blog posts or books. If you already know Markdown or AsciiDoc you already know which type of software Mau is, and you will quickly learn its syntax.
The main goal of Mau, however, is to provide a customisable markup language. While Mau's syntax is fixed by its implementation, its output is created through user-provided templates. This strategy gives the user great flexibility with no added complexity.
I currently use Mau to write posts for my blog The Digital Cat and to write my book Clean Architectures in Python. The Mau documentation is also written using Mau.
I hope someone else can find it useful!
Source code: https://github.com/Project-Mau/mau
Official documentation: The Mau book at https://www.thedigitalcatbooks.com/
https://cooklang.org/
Is there a project which tries to recreate all / the most important scientific papers with plaintext markup languages (e.g. Markdown, AsciiDoc, or LaTeX). Storing them as PDFs feels like such waste of space if most papers are just text and diagrams anyways. Also, PDFs are not responsive and don't scale pleasantly on different screen sizes.
Apparently, most lightweight markup languages such as Markdown, Asciidoc, etc. use hand-rolled parsers, mostly based on regex and states, and don't have clear ASTs.
CommonMark seems to be closest to a clean parser, as for instance cmark uses re2c to generate a lexer, and has a well-defined AST, and a reasonable parsing strategy is defined here:
https://spec.commonmark.org/0.30/#appendix-a-parsing-strategy
I assume no common lightweight markup language can be parsed by a standard parser? If you could, I'm guessing someone would have already done that?
Could you design a usable lightweight markup language that *can* be parsed by a standard parser? From my run in trying to implement an Asciidoc grammar for Instaparse, I've seen Asciidoc started to require me to complicate the grammar a ton, and stuff such as escapes/markup within code blocks seemed really complex- if not impossible...
https://preview.redd.it/1mqnat26wqk71.png?width=1538&format=png&auto=webp&s=e05f00f7d989352a770aa04e1a7c03c5c9b43dce
The newest release of pytermgui has a completely rewritten Markup language parser, which among other things yields an up to 60% performance gain compared to older versions.
The way this is done is actually quite simple:
- The ANSI and Markup language tokenizers were completely rewritten to decrease the amount of unnecessary branches, locals and statements
- Each
MarkupLanguageinstance keeps a cache of inputs and results from its `parse()` method, and on subsequent calls returns those results instead of re-parsing the strings every time
There is also support for a nicer macro syntax:
- Old:
[!align]30:center Hello world! - New:
[!align(30:center)]Hello world!
The usage of : instead of , is an intentional design choice: macro calls should be visually distinct from native Python method calls.
I am already well into the next version, which will be a rewrite of WindowManager and include some major (and for the moment final) syntactical changes to the library's mouse interface. It will also feature a much better frame-based rendering system.
For those interested in the stable release, the next one currently seems to be the candidate. I currently cannot provide an ETA as university just started, but I'll try to get it out as soon as possible.
For more information, check out the repository link above or the most recent release.
Thank you for reading, have a nice day!
I remember it came out in the 2000s, I think it had a title that began with the letter P, and might've been based on a book
Hello you mad lads. Sorry about ushering forth the end times, but I decided the world needed to be able to write HTML using C and damned be the consequences. I call it the "Fantastic Markup Language" or "FML" for short.
I wrote about it in a blog post: <https://www.timtimestim.com/b/fml.html>
(That post has swear words in it, if you're uncomfortable with that kind of thing)
(Do I flair this as an article or a project? The world may never know. Ima go with article.)
Hi! First, I'm not sure if markup languages are really on topic, so feel free to remove the post otherwise.
Around 2015, after trying many other things, I ended up rolling my own semantic markup language. Its original niche target was book writing. Since then, the language has slowly evolved and stabilized. I now also use it to generate all kinds of HTML documents, and even wrote a PhD thesis exported to LaTeX with it. In spite of this, I've done very little communication about it, nor about why I made it; in part, the reason being that I don't know about any active “semantic markup language design” community like this one for programming languages… and also that at the time I wasn't very good at English :-)
Anyway, now that I made a website for it, I thought it might be of interest here. Even though I'm now quite committed on backwards compatibility, I'm still very curious about feedback concerning the design!
The language itself is best described in its documentation, so I'll share instead a bit about the motivations.
Those are the requirements I had for the language:
- Capable of handling exports to EPUB, multi-file indexed HTML, and PDF (LaTeX) with a fine-grained control (so either rich enough semantically out of the box, or extensible). This leaves out LaTeX as source language, because it is bad at anything other than PDF and the like (I tried LaTex to EPUB translation with a variety of tools, including pandoc for a year or two, and it did not satisfy the principle of least surprise in the least, nor allowed for fine-grained css control).
- Capable of semantic markup: like HTML/CSS, LaTeX or asciidoc. That is, a language semantically extensible enough so that true WYSIWYM can happen, allowing for a better time at maintenance and refactorings in big projects. So no markdown and similarly semantically limited languages, which are a bit like text-based attempts at WYSIWYG, if that is a thing.
- File inclusion, simple textual macros and variables for easy reuse of snippets, concision, and abstraction of output-format or document version specific code (like code common to several books in a series or to several pages in a static website). This excludes most if not all “lightweight” markup languages (including asciidoc, whose “macros” mean a different t
Hey all,
A small (3 man) team of us have developed a real time interpreted cross platform markup language based on xml syntax using flutter. It's quite powerful, giving the user the ability to link into any existing back end api and automatically have front end widgets build from the data. We have built inspections systems for multiple large companies using our language/interpreter already.
I was wondering if there was anyone that I could chat with that could give us some feedback on the application/idea/execution as we are planning to release the interpreter and documentation on how to use the language for free in the next month, and are slightly unclear as to the proper path to take beforehand.
Has anyone had experience doing something similar, or releasing a software for free to users?
A brief list of some of the functionality we have in (there are over 100 widgets as of now).
- Fully customizable UI
- Forms and validation, posting, etc.
- The ability to interact with things such as gps, nfc, MQTT, local databases, web databases, bluetooth beacon, barcode, etc.
- A custom event system.
- UI widgets such as tree views, lists, tabs, drawers etc.
My discord is TheOlajos#6491
Thanks!!
There's a significant number of things you cannot change within the in-application OSD layout editor, for whatever reason, so I'm assuming manually editing the config files is the only way to do it.
Thanks for any advice anyone has!
https://cooklang.org/
