#varvara — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #varvara, aggregated by home.social.
-
-
-
-
-
-
I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.
Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.
It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.
"Let's try to go slow, and fix things."
Priceless.
-
I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.
Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.
It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.
"Let's try to go slow, and fix things."
Priceless.
-
I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.
Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.
It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.
"Let's try to go slow, and fix things."
Priceless.
-
I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.
Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.
It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.
"Let's try to go slow, and fix things."
Priceless.
-
I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.
Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.
It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.
"Let's try to go slow, and fix things."
Priceless.
-
@neauoire may I propose: varvara touch input, as an extension of the mouse device
additions:
- one byte for touch id (0 means no touch i.e. mouse input)
- one byte for touch pressure (>0 is down, 0 is up)
xy coordinates will reuse that of mouse device
as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)
so if I use noodle with a touchscreen, it'll treat my touch input as the mouse
but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!
wdyt ^^
#uxn #varvara -
@neauoire may I propose: varvara touch input, as an extension of the mouse device
additions:
- one byte for touch id (0 means no touch i.e. mouse input)
- one byte for touch pressure (>0 is down, 0 is up) EDIT: upsize to short for better fidelity
xy coordinates will reuse that of mouse device
as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)
so if I use noodle with a touchscreen, it'll treat my touch input as the mouse
but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!
wdyt ^^
#uxn #varvara -
@neauoire may I propose: varvara touch input, as an extension of the mouse device
additions:
- one byte for touch id (0 means no touch i.e. mouse input)
- one byte for touch pressure (>0 is down, 0 is up) EDIT: upsize to short for better fidelity
xy coordinates will reuse that of mouse device
as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)
so if I use noodle with a touchscreen, it'll treat my touch input as the mouse
but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!
wdyt ^^
#uxn #varvara -
@neauoire may I propose: varvara touch input, as an extension of the mouse device
additions:
- one byte for touch id (0 means no touch i.e. mouse input)
- one byte for touch pressure (>0 is down, 0 is up) EDIT: upsize to short for better fidelity
xy coordinates will reuse that of mouse device
as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)
so if I use noodle with a touchscreen, it'll treat my touch input as the mouse
but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!
wdyt ^^
#uxn #varvara -
@neauoire may I propose: varvara touch input, as an extension of the mouse device
additions:
- one byte for touch id (0 means no touch i.e. mouse input)
- one byte for touch pressure (>0 is down, 0 is up) EDIT: upsize to short for better fidelity
xy coordinates will reuse that of mouse device
as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)
so if I use noodle with a touchscreen, it'll treat my touch input as the mouse
but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!
wdyt ^^
#uxn #varvara -
heyo @neauoire, what's your opinion on stateful ports?
e.g. I want to connect to an address, I set the
actionport to connect mode by writingaction/Connect, then I write in the address string until the null byteI understand that this is opposed to the file device which does this by writing a pointer* to the filename in memory and then an operation on another port, is that the preferred way? (if so, why?)
#uxn #varvara -
„Textvorschläge sind immer willkommen“
Ihre Leseleidenschaft hat Varvara schon viel beim Deutschlernen geholfen. Deshalb hat sie bei Little World den „Buchclub“ gegründet, wo sie sich mit anderen über Prosa und Poesie austauscht. -
-
-
I made a #gapbuffer in #uxntal in about 500 bytes of #uxn bytecode!
https://paste.sr.ht/~ismael-vc/4e90f62e9149f8b7a0dc91175abcb4a367e8f35b
It outputs:
https://paste.sr.ht/~ismael-vc/bc25e5df6cbe5f3d01fc4c8d8f4477253d67b2b2
(Gap size 4 bytes for debuging purposes, I still need to do proper bounds checking but I think that's about it.)
Used this as reference:
-
I made a #gapbuffer in #uxntal in about 500 bytes of #uxn bytecode!
https://paste.sr.ht/~ismael-vc/4e90f62e9149f8b7a0dc91175abcb4a367e8f35b
It outputs:
https://paste.sr.ht/~ismael-vc/bc25e5df6cbe5f3d01fc4c8d8f4477253d67b2b2
(Gap size 4 bytes for debuging purposes, I still need to do proper bounds checking but I think that's about it.)
Used this as reference:
-
-
-
-
-
-
-
I have simplified how to use my hexdump routine, inspired by `hexdump -C`:
https://paste.sr.ht/~ismael-vc/6bb65882c10e69ef5eedd3353d0be3432e9b77d1
No need 2 have symbols or macros defined to use it, just copy paste and you are ready to go!
Example: `#0100 mem/log`
It has proven to B extremely useful 4 me, when developing TalOS & now with D Kibi editor project.
The version in the XXIIVV Oscean wiki is shorter but it doesn't show D absolute padding nor D ASCII contents.
The `-C` in `hexdump` means: "canonical mode".
-
Got the cursor to move using the WASD keys (Dvorak) in Kibi!
⬅️ ⬆️ ⬇️ ➡️
-
Today I worked a bit in kibi, made a little refactor and implemented padding to the hello message.
Not much but I'm pleased. 😄
-
I finally got some time to work in kibi today, I have impremented and debugged kibi/get-win-size, kibi/get-cur-pos (used to get the window size) and updated kibi/draw-rows to draw the correct number of purple tildes on the first column. 😊
I also made the makefile a lot nicer. 🧘♂️
That means I'm almost at the middle of chapter 3 "Raw input and output", at step 35 of the original tutorial (special case the last row)! 🚀
https://git.sr.ht/~ismael-vc/kibi/tree/main/item/src/kibi.tal
https://viewsourcecode.org/snaptoken/kilo/03.rawInputAndOutput.html
-
@garvalf yes that happens because D terminal uses cooked or sane mode (check "man stty"), it process input line by line by default (waiting for enter) & echoes what U type back so U can see it. We want to process each byte as it comes instead (we'll need to echo back "manually" when we reach D actual editing part). Check D second link of my tutorial and D "about" of femto.
If U have any #uxn #varvara or #uxntal questions, feel free to reach me out anytime.
And welcome to the uxn community! :)
-
Hello everyone!
I'm making a port of the Kilo editor by antirez (originally in C) to #uxntal AKA kibi (I'm not sure it will be around 1 "kibi"lines of code lol!
But I'm also porting the awesome tutorial by snaptoken teaching how kilo works.
I'd greatly appreciate if someone could take a look (maybe even follow along the tutorial) in order to get feedback.
https://git.sr.ht/~ismael-vc/kibi/tree/main/item/doc/index.md
I'm aiming for no previous Uxntal experience required!
Best regards.
-
Do you think this formated #uxntal table using ASCII control codes and markdown inspired macros to delimit data is readable?
https://paste.sr.ht/~ismael-vc/399f6b0a0487b2c775b057ecdec347abf3501c64
-
I made a string interpolation routine in #uxntal in 28 bytes.
00: do interpolation.
0000: do termination.@ istr/log ( istr* -- )
••••LDAk ?{
••••••••INC2 LDAk ?{
••••••••••••POP2 JMP2r }
••••••••LDA2k /log
••••••••INC2 INC2 !/log }
••••LDAk :putc
••••INC2 !/logInterpolated strings look like
%\s { 20 }
%\n { 0a }
%\$ { 00 }
%\0 { 0000 }
@ foo "foo, \s \0
@ bar "bar \s \0
@ text "These \s "are: \s [ \$ =foo ] [ \$ =bar ] "and \s "baz. \n \0https://paste.sr.ht/~ismael-vc/11e9df8c74c602e81d45e3e6d28bc620676faa3b
#uxn #varvara -
Hello everyone! I'd like to humbly request feedback regarding this testing library I've been using and plan to release soon after some of your valuable feedback.
This is how the API looks like: https://paste.sr.ht/~ismael-vc/9c33e9c6127c3e469b94020a1fb1b52c651265d3
And this is the same without comments so you can see it without noise: https://paste.sr.ht/~ismael-vc/2ddd593348f76043d40d0aa1d310967c07f6eb69
Anything from name bikeshedding to new assertion routines or whatever you would like to suggest will be greatly appreciated.
Best regards :)
-
Having fun with a little programming book of old:
https://uxnomicon.miraheze.org/wiki/Fun_to_Program_your_Varvara
-
Today I started reading an interesting book!
Software Tools in #Pascal by Kernighan Plauger.
I hope I can finish chapter 1 tomorrow. I'm doing the exercises in Uxntal for the Uxnomicon wiki.
So far I'm really liking the Pascal examples and the book in general.
https://uxnomicon.miraheze.org/wiki/Software_Tools_in_Uxntal
-
Starting december adventure late, I'm going to spend improving the uxnomicon
https://uxnomicon.miraheze.org/wiki/Uxnomicon
I'll keep a log here: https://uxnomicon.miraheze.org/wiki/Snufkin%27s_December_Adventure_2005
Yesterday I started organizing how to lay out an standard library.
-
NotLauren at Discord came up with this beautiful tal sugared snippet:
-
@rl_dane @mdc I wonder how #uxn opcodes compare to what F18 chips from #GreenArrays have.
Only 32 opcodes, 8 of them special (can be used in th last 3 bits of a kind of 18-bit #VLIW word) versus 256 opcodes of #uxn
#varvara offers much more high level i/o, F18A has 4 interchip ports, GPIO, A/D interface and SERDES, which can be used to build things like Ethernet for example.
varvara-fpga does not implement most varvara I/O features at all.https://www.greenarraychips.com/home/documents/greg/DB001-221113-F18A.pdf
https://www.greenarraychips.com/home/documents/greg/PB004-110412-F18A-IO.pdf
-
@rl_dane @mdc I wonder how #uxn opcodes compare to what F18 chips from #GreenArrays have.
Only 32 opcodes, 8 of them special (can be used in th last 3 bits of a kind of 18-bit #VLIW word) versus 256 opcodes of #uxn
#varvara offers much more high level i/o, F18A has 4 interchip ports, GPIO, A/D interface and SERDES, which can be used to build things like Ethernet for example.
varvara-fpga does not implement most varvara I/O features at all.https://www.greenarraychips.com/home/documents/greg/DB001-221113-F18A.pdf
https://www.greenarraychips.com/home/documents/greg/PB004-110412-F18A-IO.pdf
-
@rl_dane @mdc I wonder how #uxn opcodes compare to what F18 chips from #GreenArrays have.
Only 32 opcodes, 8 of them special (can be used in th last 3 bits of a kind of 18-bit #VLIW word) versus 256 opcodes of #uxn
#varvara offers much more high level i/o, F18A has 4 interchip ports, GPIO, A/D interface and SERDES, which can be used to build things like Ethernet for example.
varvara-fpga does not implement most varvara I/O features at all.https://www.greenarraychips.com/home/documents/greg/DB001-221113-F18A.pdf
https://www.greenarraychips.com/home/documents/greg/PB004-110412-F18A-IO.pdf