panzoom
linux_kernel_map
panzoom | linux_kernel_map | |
---|---|---|
2 | 3 | |
2,042 | 810 | |
- | - | |
0.0 | 0.0 | |
6 months ago | over 1 year ago | |
TypeScript | Python | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
panzoom
-
Interactive Map of Linux Kernel
And the controls seem to be made with https://github.com/timmywil/panzoom:
-
BlazorPanzoom - Enable panning and zooming of your components and elements
Hello everyone. I have released BlazorPanzoom, a wrapper library for timmywil's JavaScript panzoom library found here: panzoom.
linux_kernel_map
- Interactive Map of Linux Kernel
-
Starting A Long-Term Project?
My understanding of documentation * First and foremost, code should be readable and understandable after all comments are stripped out. * After code is understandable without comments, I add in comments anyway explaining the flow of the program and generally why something is being done. Perfect example of critically important commenting is that I note to self where sdl auto frees stream memory because this is not the way that C should work (I understand sdl did it to make code shorter and cleaner but it is still nonetheless wrongful to implicitly free any memory in c no matter the reason). * Anything I have to look up online I make comments about * If I must include garbage code, it always goes under the namespace MaybeBreakDontKnowHowToFix as a warning to myself and others. * Although I rarely use unmodified code from stackoverflow, I always comment the original inspiration the code came from. * I try to achieve 100% code coverage for projects. Combined with fsanitize=address, I’m able to fish out the vast majority of possible problems. * I make documentation about everything and don’t skimp on the opinions (which, sadly, most documentation does). I always comment on how things work together, possible issues you might have, errors you would encounter, and my opinions on how your code should be using my library optimally. * I try to make visual maps of my code. A particularly beautiful map by someone else: https://github.com/makelinux/linux_kernel_map * I always contain step-by-step build instructions of what commands to run to do what things (even though it’s usually just ./build --release or something simple) and openly disregard Windows because it’s not worth my time to port the development system to trashy useless operating systems. When I need to compile exes, I just use mingw and test in wine without ever touching Windows.
What are some alternatives?
vue-panzoom - Vue plugin to zoom/pan dom elements
fsv - fsv is a file system visualizer in cyberspace. It lays out files and directories in three dimensions, geometrically representing the file system hierarchy to allow visual overview and analysis.
BlazorPanzoom - Blazor wrapper for timmywil's panzoom library that helps make zooming and panning of Blazor components and elements easier
makelinux
react-zoom-pan-pinch - 🖼 React library to support easy zoom, pan, pinch on various html dom elements like <img> and <div>
unpkg - The CDN for everything on npm
panzoom - Universal pan and zoom library (DOM, SVG, Custom)
react-diagrams - a super simple, no-nonsense diagramming library written in react that just works
react-medium-image-zoom - 🔎 🏞 The original medium.com-inspired image zooming library for React (since 2016)
amcharts4 - The most advanced amCharts charting library for JavaScript and TypeScript apps.
panzoom - A library for panning and zooming elements using CSS transforms :mag:
pts - A library for visualization and creative-coding