Bytefield-svg plugin

marc0l92 · 2022-01-17T17:46:43.544Z

Are you an electronic engineering that design microcontroller memory?
Are you a network expert that design communication protocols?
...probably not.

With this plugin you can draw diagrams of your memory map and byte structures using the syntax described here: https://bytefield-svg.deepsymmetry.org/.

Examples

Network protocol message

Memory map

GitHub

GitHub - marc0l92/joplin-plugin-bytefield-svg: Joplin plugin to add support...

Joplin plugin to add support for bytefield-svg diagrams used to describe network protocols, memory layouts and any other binary structure. - GitHub - marc0l92/joplin-plugin-bytefield-svg: Joplin pl...

It will not be useful for most of the Joplin users but it was simple to implement and I need it .

tessus · 2022-01-17T18:10:09.377Z

Additional info: this plugin does not require an outgoing connection. The bytecode-svg code is bundled.

Now it would be great to have a few templates for bit operations: AND, OR, XOR, bitshifts, ....

Nice plugin. Love it.

leoxama · 2022-01-17T18:19:09.389Z

Well done. Great plugin

antoniopaolini · 2022-01-25T08:38:59.072Z

Nice Plugin! Really useful!
The syntax scares me a little, it reminds me of that brief period when I tried to configure Emacs to read Usenet with Gnus...

tessus · 2022-01-25T18:14:15.880Z

Ha, have you ever hacked a sendmail config? I am not talking about the .mc template, but the .cf file?

Before I have to write and/or extend the cf file manually, I'd rather flogg myself using a whip with barbed wire as tails while hanging upside down from my testicles.

laurent · 2022-01-25T18:22:12.531Z

I had to check what that was and ok, I believe you:

# You have two choices here.  If you want the gateway machine to identify
# itself as the DOMAIN, use this line:
Dj$m

# major relay mailer - typical choice is "ddn" if you are on the
# Defense Data Network (e.g. Arpanet or Milnet)
DMsmartuucp

# checkpoint the queue after this many recipients
OC10

# refuse to send tiny messages to more than these recipients
Ob10

# handle "from:<>" special case
R$*<>$*                 $@@                    turn into magic token

# basic textual canonicalization
R<$*<@$+>>              $@$1<@$2>
R$*<$+>$*               $2                     basic RFC822 parsing

# make sure <@a,@b,@c:user@d> syntax is easy to parse -- undone later
R@$+,$+:$+              @$1:$2:$3              change all "," to ":"
R@$+:$+                 $@$>6<@$1>:$2          src route canonical

R$+:$*;@$+              $@$1:$2;@$3            list syntax
R$+@$+                  $:$1<@$2>              focus on domain
R$+<$+@$+>              $1$2<@$3>              move gaze right
R$+<@$+>                $@$>6$1<@$2>           already canonical

# convert old-style names to domain-based names
# All old-style names parse from left to right, without precedence.
R$-!$+                  $@$>6$2<@$1.uucp>      uucphost!user
R$-.$+!$+               $@$>6$3<@$1.$2>        host.domain!user
R$+%$+                  $@$>3$1@$2             user%host

#  Final Output Post-rewriting 
S4
R$+<@$+.uucp>           $2!$1                  u@h.uucp => h!u
R$+                     $: $>9 $1              Clean up addr
R$*<$+>$*               $1$2$3                 defocus


#  Clean up a name for passing to a mailer
#  (but leave it focused)
S9
R$=w!@                  $@$w!$n
R@                      $@$n                   handle <> error addr
R$*<$*LOCAL>$*          $1<$2$m>$3             change local info
R<@$+>$*:$+:$+          <@$1>$2,$3:$4          <route-addr> canonical

antoniopaolini · 2022-01-26T19:05:10.484Z

Oh, no, I was more a "postfix guy".