Skip to content

Add option in that controls Home and End. Default unchanged. - #222

Open
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end
Open

Add option in that controls Home and End. Default unchanged.#222
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end

Conversation

@soegaard

Copy link
Copy Markdown
Member

This PR adds a new option in "Editing | General Editing".

The conventions on macOS differ from Windows/Linux when it comes
the handling of the Home and End keys. On macOs they are move
to the beginning and end of the document, on the other systems to
the beginning and end of the line.

If the new option is checked, the macOS convention is used.
The option also affects shift+Home/End.

The default value is set of false. Should this default to true on macOS?

image

@soegaard

soegaard commented Mar 27, 2021

Copy link
Copy Markdown
MemberAuthor

Note that this PR relies on

https://github.com/racket/string-constants/pull/51

which add the string constant missing in the test below.

@rfindler

Copy link
Copy Markdown
Member

I think it would be better if it was clear what both states of the checkbox mean. One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Probably it is good to add some test cases for this.

The documentation in DrRacket also needs a tweak for this change.

There should be a bump to the version dependency with this too.

@soegaard

Copy link
Copy Markdown
MemberAuthor

I think it would be better if it was clear what both states of the checkbox mean.
One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Ideally I'd like to add a tooltip to this check box.

Alex Harsanyi has a nice tooltip-mixin, but it would be better to have similar functionality directly in the framework.
https://docs.racket-lang.org/gui-widget-mixins/index.html?q=gui-widget-mixins

In the mean time:
Now: "Home and End go to the beginning or end of the document"
Suggestion: "If checked, Home and End keys go to beginning and end of the document.
If unchecked, they go to the beginning and end of the line."

I think, visually it is better to keep a check box - there are no other radiobuttons in that dialog.
Also, there are only two options. [1]

Probably it is good to add some test cases for this.
Is there an existing test that can be mimicked?

The documentation in DrRacket also needs a tweak for this change.

I looked at https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.html
Now, it doesn't mention Home and End. Is this the page, you had in mind?

There should be a bump to the version dependency with this too.
Ok.

[1] "Consider a checkbox when the user needs to choose between two states."
https://developer.apple.com/design/human-interface-guidelines/macos/buttons/radio-buttons/

@rfindler

Copy link
Copy Markdown
Member

I'll have to ask the release managers about gui-widget-mixins as it would be a new pkg in the distribution but I like the idea of a tooltip.

The page I had in mind is this one, sorry about that.

@rfindler

Copy link
Copy Markdown
Member

Hi @soegaard : let's go ahead and add that dependency to have a tooltip for this checkbox item. But let's hold off until next week to merge this pull request so that it'll happen only in the release after the upcoming one (just to avoid trouble).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@soegaard@rfindler
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Add option in that controls Home and End. Default unchanged. by soegaard · Pull Request #222 · racket/gui · GitHub
Skip to content

Add option in that controls Home and End. Default unchanged. - #222

Open
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end
Open

Add option in that controls Home and End. Default unchanged.#222
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end

Conversation

@soegaard

Copy link
Copy Markdown
Member

This PR adds a new option in "Editing | General Editing".

The conventions on macOS differ from Windows/Linux when it comes
the handling of the Home and End keys. On macOs they are move
to the beginning and end of the document, on the other systems to
the beginning and end of the line.

If the new option is checked, the macOS convention is used.
The option also affects shift+Home/End.

The default value is set of false. Should this default to true on macOS?

image

@soegaard

soegaard commented Mar 27, 2021

Copy link
Copy Markdown
MemberAuthor

Note that this PR relies on

https://github.com/racket/string-constants/pull/51

which add the string constant missing in the test below.

@rfindler

Copy link
Copy Markdown
Member

I think it would be better if it was clear what both states of the checkbox mean. One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Probably it is good to add some test cases for this.

The documentation in DrRacket also needs a tweak for this change.

There should be a bump to the version dependency with this too.

@soegaard

Copy link
Copy Markdown
MemberAuthor

I think it would be better if it was clear what both states of the checkbox mean.
One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Ideally I'd like to add a tooltip to this check box.

Alex Harsanyi has a nice tooltip-mixin, but it would be better to have similar functionality directly in the framework.
https://docs.racket-lang.org/gui-widget-mixins/index.html?q=gui-widget-mixins

In the mean time:
Now: "Home and End go to the beginning or end of the document"
Suggestion: "If checked, Home and End keys go to beginning and end of the document.
If unchecked, they go to the beginning and end of the line."

I think, visually it is better to keep a check box - there are no other radiobuttons in that dialog.
Also, there are only two options. [1]

Probably it is good to add some test cases for this.
Is there an existing test that can be mimicked?

The documentation in DrRacket also needs a tweak for this change.

I looked at https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.html
Now, it doesn't mention Home and End. Is this the page, you had in mind?

There should be a bump to the version dependency with this too.
Ok.

[1] "Consider a checkbox when the user needs to choose between two states."
https://developer.apple.com/design/human-interface-guidelines/macos/buttons/radio-buttons/

@rfindler

Copy link
Copy Markdown
Member

I'll have to ask the release managers about gui-widget-mixins as it would be a new pkg in the distribution but I like the idea of a tooltip.

The page I had in mind is this one, sorry about that.

@rfindler

Copy link
Copy Markdown
Member

Hi @soegaard : let's go ahead and add that dependency to have a tooltip for this checkbox item. But let's hold off until next week to merge this pull request so that it'll happen only in the release after the upcoming one (just to avoid trouble).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@soegaard@rfindler
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add option in that controls Home and End. Default unchanged. by soegaard · Pull Request #222 · racket/gui · GitHub
Skip to content

Add option in that controls Home and End. Default unchanged. - #222

Open
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end
Open

Add option in that controls Home and End. Default unchanged.#222
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end

Conversation

@soegaard

Copy link
Copy Markdown
Member

This PR adds a new option in "Editing | General Editing".

The conventions on macOS differ from Windows/Linux when it comes
the handling of the Home and End keys. On macOs they are move
to the beginning and end of the document, on the other systems to
the beginning and end of the line.

If the new option is checked, the macOS convention is used.
The option also affects shift+Home/End.

The default value is set of false. Should this default to true on macOS?

image

@soegaard

soegaard commented Mar 27, 2021

Copy link
Copy Markdown
MemberAuthor

Note that this PR relies on

https://github.com/racket/string-constants/pull/51

which add the string constant missing in the test below.

@rfindler

Copy link
Copy Markdown
Member

I think it would be better if it was clear what both states of the checkbox mean. One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Probably it is good to add some test cases for this.

The documentation in DrRacket also needs a tweak for this change.

There should be a bump to the version dependency with this too.

@soegaard

Copy link
Copy Markdown
MemberAuthor

I think it would be better if it was clear what both states of the checkbox mean.
One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Ideally I'd like to add a tooltip to this check box.

Alex Harsanyi has a nice tooltip-mixin, but it would be better to have similar functionality directly in the framework.
https://docs.racket-lang.org/gui-widget-mixins/index.html?q=gui-widget-mixins

In the mean time:
Now: "Home and End go to the beginning or end of the document"
Suggestion: "If checked, Home and End keys go to beginning and end of the document.
If unchecked, they go to the beginning and end of the line."

I think, visually it is better to keep a check box - there are no other radiobuttons in that dialog.
Also, there are only two options. [1]

Probably it is good to add some test cases for this.
Is there an existing test that can be mimicked?

The documentation in DrRacket also needs a tweak for this change.

I looked at https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.html
Now, it doesn't mention Home and End. Is this the page, you had in mind?

There should be a bump to the version dependency with this too.
Ok.

[1] "Consider a checkbox when the user needs to choose between two states."
https://developer.apple.com/design/human-interface-guidelines/macos/buttons/radio-buttons/

@rfindler

Copy link
Copy Markdown
Member

I'll have to ask the release managers about gui-widget-mixins as it would be a new pkg in the distribution but I like the idea of a tooltip.

The page I had in mind is this one, sorry about that.

@rfindler

Copy link
Copy Markdown
Member

Hi @soegaard : let's go ahead and add that dependency to have a tooltip for this checkbox item. But let's hold off until next week to merge this pull request so that it'll happen only in the release after the upcoming one (just to avoid trouble).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@soegaard@rfindler
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add option in that controls Home and End. Default unchanged. by soegaard · Pull Request #222 · racket/gui · GitHub
Skip to content

Add option in that controls Home and End. Default unchanged. - #222

Open
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end
Open

Add option in that controls Home and End. Default unchanged.#222
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end

Conversation

@soegaard

Copy link
Copy Markdown
Member

This PR adds a new option in "Editing | General Editing".

The conventions on macOS differ from Windows/Linux when it comes
the handling of the Home and End keys. On macOs they are move
to the beginning and end of the document, on the other systems to
the beginning and end of the line.

If the new option is checked, the macOS convention is used.
The option also affects shift+Home/End.

The default value is set of false. Should this default to true on macOS?

image

@soegaard

soegaard commented Mar 27, 2021

Copy link
Copy Markdown
MemberAuthor

Note that this PR relies on

https://github.com/racket/string-constants/pull/51

which add the string constant missing in the test below.

@rfindler

Copy link
Copy Markdown
Member

I think it would be better if it was clear what both states of the checkbox mean. One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Probably it is good to add some test cases for this.

The documentation in DrRacket also needs a tweak for this change.

There should be a bump to the version dependency with this too.

@soegaard

Copy link
Copy Markdown
MemberAuthor

I think it would be better if it was clear what both states of the checkbox mean.
One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Ideally I'd like to add a tooltip to this check box.

Alex Harsanyi has a nice tooltip-mixin, but it would be better to have similar functionality directly in the framework.
https://docs.racket-lang.org/gui-widget-mixins/index.html?q=gui-widget-mixins

In the mean time:
Now: "Home and End go to the beginning or end of the document"
Suggestion: "If checked, Home and End keys go to beginning and end of the document.
If unchecked, they go to the beginning and end of the line."

I think, visually it is better to keep a check box - there are no other radiobuttons in that dialog.
Also, there are only two options. [1]

Probably it is good to add some test cases for this.
Is there an existing test that can be mimicked?

The documentation in DrRacket also needs a tweak for this change.

I looked at https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.html
Now, it doesn't mention Home and End. Is this the page, you had in mind?

There should be a bump to the version dependency with this too.
Ok.

[1] "Consider a checkbox when the user needs to choose between two states."
https://developer.apple.com/design/human-interface-guidelines/macos/buttons/radio-buttons/

@rfindler

Copy link
Copy Markdown
Member

I'll have to ask the release managers about gui-widget-mixins as it would be a new pkg in the distribution but I like the idea of a tooltip.

The page I had in mind is this one, sorry about that.

@rfindler

Copy link
Copy Markdown
Member

Hi @soegaard : let's go ahead and add that dependency to have a tooltip for this checkbox item. But let's hold off until next week to merge this pull request so that it'll happen only in the release after the upcoming one (just to avoid trouble).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@soegaard@rfindler
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' Add option in that controls Home and End. Default unchanged. by soegaard · Pull Request #222 · racket/gui · GitHub
Skip to content

Add option in that controls Home and End. Default unchanged. - #222

Open
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end
Open

Add option in that controls Home and End. Default unchanged.#222
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end

Conversation

@soegaard

Copy link
Copy Markdown
Member

This PR adds a new option in "Editing | General Editing".

The conventions on macOS differ from Windows/Linux when it comes
the handling of the Home and End keys. On macOs they are move
to the beginning and end of the document, on the other systems to
the beginning and end of the line.

If the new option is checked, the macOS convention is used.
The option also affects shift+Home/End.

The default value is set of false. Should this default to true on macOS?

image

@soegaard

soegaard commented Mar 27, 2021

Copy link
Copy Markdown
MemberAuthor

Note that this PR relies on

https://github.com/racket/string-constants/pull/51

which add the string constant missing in the test below.

@rfindler

Copy link
Copy Markdown
Member

I think it would be better if it was clear what both states of the checkbox mean. One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Probably it is good to add some test cases for this.

The documentation in DrRacket also needs a tweak for this change.

There should be a bump to the version dependency with this too.

@soegaard

Copy link
Copy Markdown
MemberAuthor

I think it would be better if it was clear what both states of the checkbox mean.
One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Ideally I'd like to add a tooltip to this check box.

Alex Harsanyi has a nice tooltip-mixin, but it would be better to have similar functionality directly in the framework.
https://docs.racket-lang.org/gui-widget-mixins/index.html?q=gui-widget-mixins

In the mean time:
Now: "Home and End go to the beginning or end of the document"
Suggestion: "If checked, Home and End keys go to beginning and end of the document.
If unchecked, they go to the beginning and end of the line."

I think, visually it is better to keep a check box - there are no other radiobuttons in that dialog.
Also, there are only two options. [1]

Probably it is good to add some test cases for this.
Is there an existing test that can be mimicked?

The documentation in DrRacket also needs a tweak for this change.

I looked at https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.html
Now, it doesn't mention Home and End. Is this the page, you had in mind?

There should be a bump to the version dependency with this too.
Ok.

[1] "Consider a checkbox when the user needs to choose between two states."
https://developer.apple.com/design/human-interface-guidelines/macos/buttons/radio-buttons/

@rfindler

Copy link
Copy Markdown
Member

I'll have to ask the release managers about gui-widget-mixins as it would be a new pkg in the distribution but I like the idea of a tooltip.

The page I had in mind is this one, sorry about that.

@rfindler

Copy link
Copy Markdown
Member

Hi @soegaard : let's go ahead and add that dependency to have a tooltip for this checkbox item. But let's hold off until next week to merge this pull request so that it'll happen only in the release after the upcoming one (just to avoid trouble).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@soegaard@rfindler
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add option in that controls Home and End. Default unchanged. by soegaard · Pull Request #222 · racket/gui · GitHub
Skip to content

Add option in that controls Home and End. Default unchanged. - #222

Open
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end
Open

Add option in that controls Home and End. Default unchanged.#222
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end

Conversation

@soegaard

Copy link
Copy Markdown
Member

This PR adds a new option in "Editing | General Editing".

The conventions on macOS differ from Windows/Linux when it comes
the handling of the Home and End keys. On macOs they are move
to the beginning and end of the document, on the other systems to
the beginning and end of the line.

If the new option is checked, the macOS convention is used.
The option also affects shift+Home/End.

The default value is set of false. Should this default to true on macOS?

image

@soegaard

soegaard commented Mar 27, 2021

Copy link
Copy Markdown
MemberAuthor

Note that this PR relies on

https://github.com/racket/string-constants/pull/51

which add the string constant missing in the test below.

@rfindler

Copy link
Copy Markdown
Member

I think it would be better if it was clear what both states of the checkbox mean. One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Probably it is good to add some test cases for this.

The documentation in DrRacket also needs a tweak for this change.

There should be a bump to the version dependency with this too.

@soegaard

Copy link
Copy Markdown
MemberAuthor

I think it would be better if it was clear what both states of the checkbox mean.
One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Ideally I'd like to add a tooltip to this check box.

Alex Harsanyi has a nice tooltip-mixin, but it would be better to have similar functionality directly in the framework.
https://docs.racket-lang.org/gui-widget-mixins/index.html?q=gui-widget-mixins

In the mean time:
Now: "Home and End go to the beginning or end of the document"
Suggestion: "If checked, Home and End keys go to beginning and end of the document.
If unchecked, they go to the beginning and end of the line."

I think, visually it is better to keep a check box - there are no other radiobuttons in that dialog.
Also, there are only two options. [1]

Probably it is good to add some test cases for this.
Is there an existing test that can be mimicked?

The documentation in DrRacket also needs a tweak for this change.

I looked at https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.html
Now, it doesn't mention Home and End. Is this the page, you had in mind?

There should be a bump to the version dependency with this too.
Ok.

[1] "Consider a checkbox when the user needs to choose between two states."
https://developer.apple.com/design/human-interface-guidelines/macos/buttons/radio-buttons/

@rfindler

Copy link
Copy Markdown
Member

I'll have to ask the release managers about gui-widget-mixins as it would be a new pkg in the distribution but I like the idea of a tooltip.

The page I had in mind is this one, sorry about that.

@rfindler

Copy link
Copy Markdown
Member

Hi @soegaard : let's go ahead and add that dependency to have a tooltip for this checkbox item. But let's hold off until next week to merge this pull request so that it'll happen only in the release after the upcoming one (just to avoid trouble).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@soegaard@rfindler
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add option in that controls Home and End. Default unchanged. by soegaard · Pull Request #222 · racket/gui · GitHub
Skip to content

Add option in that controls Home and End. Default unchanged. - #222

Open
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end
Open

Add option in that controls Home and End. Default unchanged.#222
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end

Conversation

@soegaard

Copy link
Copy Markdown
Member

This PR adds a new option in "Editing | General Editing".

The conventions on macOS differ from Windows/Linux when it comes
the handling of the Home and End keys. On macOs they are move
to the beginning and end of the document, on the other systems to
the beginning and end of the line.

If the new option is checked, the macOS convention is used.
The option also affects shift+Home/End.

The default value is set of false. Should this default to true on macOS?

image

@soegaard

soegaard commented Mar 27, 2021

Copy link
Copy Markdown
MemberAuthor

Note that this PR relies on

https://github.com/racket/string-constants/pull/51

which add the string constant missing in the test below.

@rfindler

Copy link
Copy Markdown
Member

I think it would be better if it was clear what both states of the checkbox mean. One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Probably it is good to add some test cases for this.

The documentation in DrRacket also needs a tweak for this change.

There should be a bump to the version dependency with this too.

@soegaard

Copy link
Copy Markdown
MemberAuthor

I think it would be better if it was clear what both states of the checkbox mean.
One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Ideally I'd like to add a tooltip to this check box.

Alex Harsanyi has a nice tooltip-mixin, but it would be better to have similar functionality directly in the framework.
https://docs.racket-lang.org/gui-widget-mixins/index.html?q=gui-widget-mixins

In the mean time:
Now: "Home and End go to the beginning or end of the document"
Suggestion: "If checked, Home and End keys go to beginning and end of the document.
If unchecked, they go to the beginning and end of the line."

I think, visually it is better to keep a check box - there are no other radiobuttons in that dialog.
Also, there are only two options. [1]

Probably it is good to add some test cases for this.
Is there an existing test that can be mimicked?

The documentation in DrRacket also needs a tweak for this change.

I looked at https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.html
Now, it doesn't mention Home and End. Is this the page, you had in mind?

There should be a bump to the version dependency with this too.
Ok.

[1] "Consider a checkbox when the user needs to choose between two states."
https://developer.apple.com/design/human-interface-guidelines/macos/buttons/radio-buttons/

@rfindler

Copy link
Copy Markdown
Member

I'll have to ask the release managers about gui-widget-mixins as it would be a new pkg in the distribution but I like the idea of a tooltip.

The page I had in mind is this one, sorry about that.

@rfindler

Copy link
Copy Markdown
Member

Hi @soegaard : let's go ahead and add that dependency to have a tooltip for this checkbox item. But let's hold off until next week to merge this pull request so that it'll happen only in the release after the upcoming one (just to avoid trouble).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@soegaard@rfindler
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); Add option in that controls Home and End. Default unchanged. by soegaard · Pull Request #222 · racket/gui · GitHub
Skip to content

Add option in that controls Home and End. Default unchanged. - #222

Open
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end
Open

Add option in that controls Home and End. Default unchanged.#222
soegaard wants to merge 1 commit into
racket:masterfrom
soegaard:home-end

Conversation

@soegaard

Copy link
Copy Markdown
Member

This PR adds a new option in "Editing | General Editing".

The conventions on macOS differ from Windows/Linux when it comes
the handling of the Home and End keys. On macOs they are move
to the beginning and end of the document, on the other systems to
the beginning and end of the line.

If the new option is checked, the macOS convention is used.
The option also affects shift+Home/End.

The default value is set of false. Should this default to true on macOS?

image

@soegaard

soegaard commented Mar 27, 2021

Copy link
Copy Markdown
MemberAuthor

Note that this PR relies on

https://github.com/racket/string-constants/pull/51

which add the string constant missing in the test below.

@rfindler

Copy link
Copy Markdown
Member

I think it would be better if it was clear what both states of the checkbox mean. One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Probably it is good to add some test cases for this.

The documentation in DrRacket also needs a tweak for this change.

There should be a bump to the version dependency with this too.

@soegaard

Copy link
Copy Markdown
MemberAuthor

I think it would be better if it was clear what both states of the checkbox mean.
One option would be to have a more verbose checkbox; another would be to use radio buttons with two strings.

Ideally I'd like to add a tooltip to this check box.

Alex Harsanyi has a nice tooltip-mixin, but it would be better to have similar functionality directly in the framework.
https://docs.racket-lang.org/gui-widget-mixins/index.html?q=gui-widget-mixins

In the mean time:
Now: "Home and End go to the beginning or end of the document"
Suggestion: "If checked, Home and End keys go to beginning and end of the document.
If unchecked, they go to the beginning and end of the line."

I think, visually it is better to keep a check box - there are no other radiobuttons in that dialog.
Also, there are only two options. [1]

Probably it is good to add some test cases for this.
Is there an existing test that can be mimicked?

The documentation in DrRacket also needs a tweak for this change.

I looked at https://docs.racket-lang.org/drracket/Keyboard_Shortcuts.html
Now, it doesn't mention Home and End. Is this the page, you had in mind?

There should be a bump to the version dependency with this too.
Ok.

[1] "Consider a checkbox when the user needs to choose between two states."
https://developer.apple.com/design/human-interface-guidelines/macos/buttons/radio-buttons/

@rfindler

Copy link
Copy Markdown
Member

I'll have to ask the release managers about gui-widget-mixins as it would be a new pkg in the distribution but I like the idea of a tooltip.

The page I had in mind is this one, sorry about that.

@rfindler

Copy link
Copy Markdown
Member

Hi @soegaard : let's go ahead and add that dependency to have a tooltip for this checkbox item. But let's hold off until next week to merge this pull request so that it'll happen only in the release after the upcoming one (just to avoid trouble).

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@soegaard@rfindler