@ngn I thought about that. You could have a minimise button AND a close button. Minimise keeps the listeners but hides the bar (you restore it by re-running the script from your bookmark) , while close switches everything off (re-openable with bookmark). However, the bar's colour also serves to indicate backtick mode (and reminds you why your Tab key is "broken"), so maybe you shouldn't be able to have input-methods without bar.
@ngn btw, feature request: briefly turn backtick styling of the bar on and then off when user presses Tab, to remind him why the Tab key is "broken".
@ngn Why not have it completely hidden, and reappear in full size during backtick mode? This way, after the user presses backtick, he can then click on (or hover over) the bar if he has forgotten the bindings.
@ngn I would assume that he finds it annoying because it occupies (and shadows) an entire line all the time. If it is just while in backtick mode, he can go about browsing as usual, with no visual effect of the (collapsed) bar.
@ngn I know, but I much prefer simultaneous key-combos over dead-keys, which is why I use my custom keyboard layout. The lb breaks my flow. That being said, it isn't intended for me, so don't worry about that.
@Adám also I'd suggest adding some sort of means to view the full list of ` and tab combinations, not just the ones present on the visible strip of chars
@Adám for example `h == ∆, but ∆ isn't visible on the language bar
having to read bqk and bqv isn't very convenient :p
@EriktheOutgolfer That is discouraged as they are not considered identifier chars by Unicode or in other languages, but I've been complaining about it, since I have to maintain code which already uses them.
@ngn APL's ⍺, ⍵, ∆ and ⍙ predate ASCII, and the underscored letters where due to technical reasons so that you could overstrike normal uppercase with _ and use the other golf ball positions for APL symbols. Leaving golfballs, people wanted actual lowercase and the underscored letters could not be mapped back again, because people had started to use naming schemes with e.g. underscored last letter, and namE looks wrong. So the underscored letters were kept alongside the lowercase. TBC…
… Then IBM western Latin codepages came and did not add underscored letters, so the underscored letters were remapped to accented Latin letters (depending on font/cp). Then Unicode came, and we could have them all.
@ngn Because APL is backwards compatible, for good and for bad.
Adám is hosting another informal APL learning session tonight at 18:30 UTC in https://chat.stackexchange.com/rooms/52405/apl, continuing last week's "APL primitive functions' marathon". See https://chat.stackexchange.com/transcript/message/41299896#41299896 if you don't have 20 Stack Exchange rep points.
@ngn Why not? The yet-to-be-launched Space Launch System's solid rocket boosters have their specific dimensions due to backwards compatibility all the way back to Roman chariots.
@Adám when working in a team, people are under pressure to deliver, they make compromises to get work done sooner at the cost of complexity
@Adám there is no incentive to do the unglorious work of tidying things up and eliminating unnecessary code, it's even risky - something might break; if it ain't broke, don't touch it
@Adám this is the case with any company beyond a certain size and profit
@ngn No, not in Dyalog's case, (remember APL#?) but in Dyalog's (potential) customer's cases. The APL world expects old code to keep running. I recently increased support for importing underscored names from mainframe APL2.
@ngn IBM (at least here in Brazil) spends a lot of money to teach their workers COBOL. Friend of mine got hired and she had to spend 3 months learning it before they let her anywhere near their code.
My point was, it's good to throw everything away and start from scratch every once in a while. You don't have to support backwards compatibility for more than 1 version and you can do it with a migration tool. Customers who don't move forward should be left behind because they become a burden to developers.
@ngn That view is unsustainable. Yes, K does that, but has a niche target audience. Generally programming languages stay backwards compatible. If they really want a breaking change, then they make a new language. E.g. Python 2 vs 3. and C vs C++.
To participate in tonight's learning session without 20 Stack Exchange rep points, click lower-left giant avatar, then click "user profile" and there will be a number in the URL; that's your chat ID. Email your chat ID to adam@ with the domain being dyalog.com.
@LucaH Sorry, I confused your rep with your badge count.
@ngn I thought and asked her the same thing, actually. She told me that there were thousands of mainframes still in use, coded in COBOL, and it would cost a lot of money to convert them to another language.
@ngn Merged. Thanks. One funny thing is that clicking the bookmarklet multiple times will add multiple bars, each of which will need to be closed by an additional click on [x]
@Adám if uppercase/lowercase are very different, as is often the case, it doesn't make much sense anymore, e.g. A| is ⍋ but a| is not similar
@Adám I have a few exceptions from visual resemblance: rr ⍴ for example
I imagine a fresh APL recruit would go through the following stages of typing: * clicking on the language bar * tab completion because it's easy to guess visually without prior knowledge about APL * bq completion because it's fewer keystrokes (and also works in RIDE and Vim) * Geoff's keymaps because the are even more convenient and free your ` key
@Adám I'd like to not have to switch layouts too, but with APL, latvian and russian all used sometimes + that windows is stupid and some apps use the 2nd layouts language I need 4 total layouts..
@ngn as Adám said, I don't see a reason not to open a lot of language bars if somebody wants to :p there's no reason I can think of that would require clicking on the bookmark twice
..and now after adding and removing the language (I added the first language shown - afrikaans) I by some reason have a english UK layout that's not shown anywhere. Windows sucks
for example it changed between XP and Vista, 7 and 8, 8 and 8.1, 8.1 and 10, 10 one build and 10 another build (anniversary/creators' updates and such stuff etc.) you can see that's just hell
@EriktheOutgolfer Every other version of Windows was good, and every other bad. I had my high hopes for 9 after the 8 fiasco. And then they skipped to 10!