Explore >> Select a destination
|
You are here 
|
dylanpaulus.com | ||
| | | | |
patrickthebold.github.io
|
|
| | | | | ||
| | | | |
mbuffett.com
|
|
| | | | | Recently I migrated my side-project from Redux, which I've used in every React project for the past four years, to pullstate, here is my tale. Problems with Redux Feel free to skip this part if you already know the pain points of Redux, there's nothing in here that hasn't been discussed a million times before. These are the problems as I see them, most important first: The boilerplate. Oh man, the boilerplate. Want to add a counter? First, add the field to your interface (I'm assuming TypeScript), add a default value, create a new action type for the incrementing, write an action creator, add the case to your reducer, add the dispatcher hook to your component, dispatch your action creator. It's exhausting just to list the steps, nevermind actually doing it for every bit of state you need to keep track of. | |
| | | | |
realfiction.net
|
|
| | | | | ||
| | | | |
hackaday.io
|
|
| | | I've posted the scripts used to generate the anti-aliased text used in the User Interface. The first is a Photoshop script,CreateFontData.jsx. This makes a set of PNG files, one for each character. The second isConvertText.py, a Python script that takes the output of CreateFontData and generates C code for display the characters on the Epson LCD used in the project. Note these scripts have some hard-coded pathnames in them (to the development folder) but this is pretty easy to find and modify. | ||
