« first day (1400 days earlier)      last day (375 days later) » 

04:22
I've had an idea for the token moving algorithm for literate mode
That is to say, the algorithm that actually handles moving tokens in something like 3 '+ 4
The current implementation is a little complex and uses 2Tuples
Or whatever scala calls them
That's because it goes from left to right and has to determine position based on lookahead
But what I was thinking is that...it goes in reverse
Mind blowing I know but like instead of going l2r and requiring lookahead and whatnot, going r2l means reaching a move token simply removes the head of a list of seen tokens and inserts it at position number of quotes
That way only a list of tokens should be needed
Instead of 2tuples
Or whatever scala calls them
04:52
Simplifying token moving would be great
@lyxal Tuple2s but I assume people just call them 2-tuples when speaking
 
8 hours later…
12:48
yep
that's good stuff
[that mac] noice
13:06
lyxal pushed a commit to Vyxal/v3-the-good-update in Vyxal/Vyxal: greatly simplify the moving algorithm
used to be 50 lines
now it's 44 lines
@lyxal [user] Deep inside, we're all 3s
@lyxal [user] Nice
PETAH THE HORSE IS HERE
OH YEAH
[user] Huh
[that mac] petah!
[user] ?
@Bridget my ping noise, which just triggered twice in a row :p
13:11
[user] Ah
[bored] ﹫<unknown user> should "join on nothing" automatically convert a list of only numbers to the number formed by concatenating them
[bored] similar to jelly's D and a one byter for “⌊
13:27
Sure
Why not
Sounds like a good idea to me
Anyhow I'm pretty sure the new lexers are finished
So next thing will be to make tests for them
And then change the parser a bit to accommodate some of the minor changes I made to what tokens are returned
[Ginger] h
13:43
[lyxal ♦️] Why the long h?
[Ginger] that's my "layout despair" h
[Ginger] did you read my talking about theseus's layout earlier
[lyxal ♦️] Been there done that :p
[lyxal ♦️] And with Vue + typescript + golden layout of all things
[bored] i have something resembling tips and tricks set up
[lyxal ♦️] Excellent
@Bridget [Ginger] well, history is repeating itself and I would like your advice
[lyxal ♦️] Rulered :p
[Ginger] here's the summary: if we want the editor panels to be resizable, we either break mobile responsiveness...
@Bridget [Ginger] ...or we I spend a bunch of time making the UI completely restructure itself on mobile to not break
[Ginger] super happy I remembered to handle edits on rulered messages :disturb_smile:
[lyxal ♦️] Resizable how?
@Bridget [Ginger] like the editors are in panes and you can drag the borders to resize them
[Ginger] which I think would be cool
[lyxal ♦️] And so how does mobile currently get its layout?
[Ginger] responsive design
[lyxal ♦️] And is it completely vertical or what does it look like?
[bored] mobile has some issues with header and footer
[bored] when typing on the builtin keyboard
[Ginger] have you not seen the mobile layout?
@Bridget [lyxal ♦️] Not for a while
@Bridget [Ginger] it hasn't changed since I made it, pretty much; the terminal and editors just stack on top of each other
[lyxal ♦️] And so if you don't resize anything it'll effectively be the same?
[Ginger] but making that happen with just CSS is not possible with the pane library, so I would have to make the UI completely rebuild itself when it detects a mobile screen size
[lyxal ♦️] As in, no resizing = exact same layout (assuming resizing is an option)
@Bridget probably not; one of the other things I'd be doing is expanding the "island" of UI to take up the whole screen
it'd look a bit more like vscode
[lyxal ♦️] What I was trying to get at to see if it was possible is whether the pane resize can be disabled for mober
@Bridget we're discussing the new mobile editor
[lyxal ♦️] Allow resize on demskpot and disallow it on mober
[lyxal ♦️] Would that work?
@Bridget this is what I mean; it cannot, so the UI would have to detect mober in the JS and rearrange the components internally to remove all the resizing stuff
which is possible, but annoying
13:54
@Ginger [lyxal ♦️] Detecting mober in js isn't hard
my rationale for doing all this is that the editor feels cramped with its current design; the element offcanvas solution is good for mobile (touchscreen) but annoying on desktop (mouse)
[lyxal ♦️] And if done right, it should just be a matter of loading in a different html element
@Bridget yes, but redoing the UI is
I've been working on this for the past three months, trust me when I say it'd be hard :p
[`lyxal` ♦️] Surely you can have a check like

if (mober) {
header Box += responsive version of text box
} else {
header box += resizable version of text box
}
I cannot
13:57
pacmanboss256 opened pull request #2089 (add tips) in Vyxal/Vyxal
the pane library's React components go around the entire UI
[lyxal ♦️] What if...a dedicated mober url
even more annoying, since now we're duplicating the entire page and moving code around to be shared
my inclination is to leave the UI as-is for release
[lyxal ♦️] Probably
[lyxal ♦️] o/
then we can get feedback from people who are actually using it, and prioritize it if necessary
when is release tho :(
lyxaaaaal! answer me!
14:00
[RubenVerg] btw, did you add support for inputting lambdas?
whar
!!/status
@Ginger I am working hard... or am I hardly working?
@Ginger [RubenVerg] last time I checked there was no way to input λ and similar
[RubenVerg] (iirc, might just be remembering wrong)
oh yeah right
I'll do that today
syntax element autocomplete
14:56
Yo, sorry I've been gone for a little while, I've been moving. I bought a house \o/
 
3 hours later…
18:14
[AlanTheBagel] nice
18:37
yall!
I have finally made the element offcanvas UI work like I want
a separate search input for elements and modifiers, that's visible even when scrolling
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Move element offcanvas search input into tab pane
I love CSS I love CSS I love CSS

« first day (1400 days earlier)      last day (375 days later) »