Search
1000 results for “wyatt_h_knott”
-
@wyatt At least it isn't a Commodore 64, Atari 800, Apple II, or NES, where disabling TSX instructions will make a lot of software not work.
-
@wyatt Put some AY-3-8910 music from X1, MSX, Mockingboard, or Atari ST on your website, and tell them you used a YM2149F SSG.
-
@wyatt Put some AY-3-8910 music from X1, MSX, Mockingboard, or Atari ST on your website, and tell them you used a YM2149F SSG.
-
@wyatt Put some AY-3-8910 music from X1, MSX, Mockingboard, or Atari ST on your website, and tell them you used a YM2149F SSG.
-
@wyatt Put some AY-3-8910 music from X1, MSX, Mockingboard, or Atari ST on your website, and tell them you used a YM2149F SSG.
-
@wyatt Put some AY-3-8910 music from X1, MSX, Mockingboard, or Atari ST on your website, and tell them you used a YM2149F SSG.
-
@wyatt @indigoparadox SDL 1 is LGPL, which is troublesome on modern platforms without a meaningful shared library mechanism. Like it or not, a lot of my prospective audience are using Steam with Steamworks achievements, iOS, modern Xbox, modern PlayStation, or Nintendo Switch. What would be the object files that could be meaningfully relinked with a modified copy of SDL for these platforms?
-
@wyatt @indigoparadox SDL 1 is LGPL, which is troublesome on modern platforms without a meaningful shared library mechanism. Like it or not, a lot of my prospective audience are using Steam with Steamworks achievements, iOS, modern Xbox, modern PlayStation, or Nintendo Switch. What would be the object files that could be meaningfully relinked with a modified copy of SDL for these platforms?
-
@wyatt @indigoparadox SDL 1 is LGPL, which is troublesome on modern platforms without a meaningful shared library mechanism. Like it or not, a lot of my prospective audience are using Steam with Steamworks achievements, iOS, modern Xbox, modern PlayStation, or Nintendo Switch. What would be the object files that could be meaningfully relinked with a modified copy of SDL for these platforms?
-
@wyatt @indigoparadox SDL 1 is LGPL, which is troublesome on modern platforms without a meaningful shared library mechanism. Like it or not, a lot of my prospective audience are using Steam with Steamworks achievements, iOS, modern Xbox, modern PlayStation, or Nintendo Switch. What would be the object files that could be meaningfully relinked with a modified copy of SDL for these platforms?
-
@wyatt @indigoparadox SDL 1 is LGPL, which is troublesome on modern platforms without a meaningful shared library mechanism. Like it or not, a lot of my prospective audience are using Steam with Steamworks achievements, iOS, modern Xbox, modern PlayStation, or Nintendo Switch. What would be the object files that could be meaningfully relinked with a modified copy of SDL for these platforms?
-
@wyatt @hatzka If I had to guess, these fundamental changes have happened since the XFree86 era:
1. Internationalization: Personal computer use has expanded out of the Americas and western Europe. Asia in particular brings a need for large glyph sets, contextual glyph shaping, diacritic stacking, bidirectional writing, top-to-bottom writing, and antialiasing to make small curves easier to distinguish. How well does X11's font paradigm handle these, as opposed to relying on "modern" toolkits to shove bitmaps around?
2. High density: People expect things to appear the same size on more than one display connected to one computer even if one has more pixels per millimeter than the other.
3. Privacy: Computer networks have become much less trusted over the past few decades. There was demand to deter publishers of proprietary applications from surreptitiously activating a keylogger or screen logger to exfiltrate your data in other applications.
-
@wyatt @hatzka If I had to guess, these fundamental changes have happened since the XFree86 era:
1. Internationalization: Personal computer use has expanded out of the Americas and western Europe. Asia in particular brings a need for large glyph sets, contextual glyph shaping, diacritic stacking, bidirectional writing, top-to-bottom writing, and antialiasing to make small curves easier to distinguish. How well does X11's font paradigm handle these, as opposed to relying on "modern" toolkits to shove bitmaps around?
2. High density: People expect things to appear the same size on more than one display connected to one computer even if one has more pixels per millimeter than the other.
3. Privacy: Computer networks have become much less trusted over the past few decades. There was demand to deter publishers of proprietary applications from surreptitiously activating a keylogger or screen logger to exfiltrate your data in other applications.
-
@wyatt @hatzka If I had to guess, these fundamental changes have happened since the XFree86 era:
1. Internationalization: Personal computer use has expanded out of the Americas and western Europe. Asia in particular brings a need for large glyph sets, contextual glyph shaping, diacritic stacking, bidirectional writing, top-to-bottom writing, and antialiasing to make small curves easier to distinguish. How well does X11's font paradigm handle these, as opposed to relying on "modern" toolkits to shove bitmaps around?
2. High density: People expect things to appear the same size on more than one display connected to one computer even if one has more pixels per millimeter than the other.
3. Privacy: Computer networks have become much less trusted over the past few decades. There was demand to deter publishers of proprietary applications from surreptitiously activating a keylogger or screen logger to exfiltrate your data in other applications.
-
@wyatt @hatzka If I had to guess, these fundamental changes have happened since the XFree86 era:
1. Internationalization: Personal computer use has expanded out of the Americas and western Europe. Asia in particular brings a need for large glyph sets, contextual glyph shaping, diacritic stacking, bidirectional writing, top-to-bottom writing, and antialiasing to make small curves easier to distinguish. How well does X11's font paradigm handle these, as opposed to relying on "modern" toolkits to shove bitmaps around?
2. High density: People expect things to appear the same size on more than one display connected to one computer even if one has more pixels per millimeter than the other.
3. Privacy: Computer networks have become much less trusted over the past few decades. There was demand to deter publishers of proprietary applications from surreptitiously activating a keylogger or screen logger to exfiltrate your data in other applications.
-
@wyatt @hatzka If I had to guess, these fundamental changes have happened since the XFree86 era:
1. Internationalization: Personal computer use has expanded out of the Americas and western Europe. Asia in particular brings a need for large glyph sets, contextual glyph shaping, diacritic stacking, bidirectional writing, top-to-bottom writing, and antialiasing to make small curves easier to distinguish. How well does X11's font paradigm handle these, as opposed to relying on "modern" toolkits to shove bitmaps around?
2. High density: People expect things to appear the same size on more than one display connected to one computer even if one has more pixels per millimeter than the other.
3. Privacy: Computer networks have become much less trusted over the past few decades. There was demand to deter publishers of proprietary applications from surreptitiously activating a keylogger or screen logger to exfiltrate your data in other applications.
-
@wyatt See if you live close to a Michaels. That's the craft store where I last bought Perler beads.
-
@wyatt See if you live close to a Michaels. That's the craft store where I last bought Perler beads.
-
@wyatt See if you live close to a Michaels. That's the craft store where I last bought Perler beads.
-
@wyatt See if you live close to a Michaels. That's the craft store where I last bought Perler beads.
-
@wyatt See if you live close to a Michaels. That's the craft store where I last bought Perler beads.
-
@wyatt Firefox 149 adds Split View, which I understand as a multi-document interface (MDI) with a rudimentary tiling window manager. https://support.mozilla.org/en-US/kb/split-view-firefox
-
@wyatt Firefox 149 adds Split View, which I understand as a multi-document interface (MDI) with a rudimentary tiling window manager. https://support.mozilla.org/en-US/kb/split-view-firefox
-
@wyatt Firefox 149 adds Split View, which I understand as a multi-document interface (MDI) with a rudimentary tiling window manager. https://support.mozilla.org/en-US/kb/split-view-firefox
-
@wyatt Firefox 149 adds Split View, which I understand as a multi-document interface (MDI) with a rudimentary tiling window manager. https://support.mozilla.org/en-US/kb/split-view-firefox
-
@wyatt Firefox 149 adds Split View, which I understand as a multi-document interface (MDI) with a rudimentary tiling window manager. https://support.mozilla.org/en-US/kb/split-view-firefox
-
@wyatt I learned about Roland from the synthesizer lab at a college where I took enrichment classes.
-
@wyatt @kawa There have been a few attempts at "lossy PNG". One method, anticipated by the standard, involves reducing colors in a continuous-tone image to store it in indexed mode. The other involves adjusting pixels of 24-bit images to be better predicted by PNG's line filter, giving more zero bytes for DEFLATE to use
Indexed: https://pngquant.org/
Blurizer: https://github.com/kornelski/mediancut-posterizer/tree/blurizer -
@wyatt @kawa There have been a few attempts at "lossy PNG". One method, anticipated by the standard, involves reducing colors in a continuous-tone image to store it in indexed mode. The other involves adjusting pixels of 24-bit images to be better predicted by PNG's line filter, giving more zero bytes for DEFLATE to use
Indexed: https://pngquant.org/
Blurizer: https://github.com/kornelski/mediancut-posterizer/tree/blurizer -
@wyatt @kawa There have been a few attempts at "lossy PNG". One method, anticipated by the standard, involves reducing colors in a continuous-tone image to store it in indexed mode. The other involves adjusting pixels of 24-bit images to be better predicted by PNG's line filter, giving more zero bytes for DEFLATE to use
Indexed: https://pngquant.org/
Blurizer: https://github.com/kornelski/mediancut-posterizer/tree/blurizer