Displaying 1 to 10 from 10 results

winit - Window handling library in pure Rust

  •    Rust

For features within the scope of winit, see FEATURES.md. For features outside the scope of winit, see Missing features provided by other crates in the wiki.

winit - Window handling library in pure Rust

  •    Rust

Winit is a window creation and management library. It can create windows and lets you handle events (for example: the window being resized, a key being pressed, a mouse movement, etc.) produced by window. Winit is designed to be a low-level brick in a hierarchy of libraries. Consequently, in order to show something on the window you need to use the platform-specific getters provided by winit, or another library.

nodejs-fft-windowing - Applies a windowing function to an array of data, making it ready to be FFT'd

  •    Javascript

nodejs-fft-windowing is a node.js module that applies a windowing function to an array of data, making it ready to be FFT'd. This article by National Instruments gives a good introduction to why windowing functions are useful.

collection-view - UICollectionView for the web

  •    TypeScript

A container for displaying large ordered collections of data items and presenting them using arbitrary layouts (e.g. lists, grids). Large collections can be scrolled smoothly by displaying only a limited number of elements. This is also known as "windowing" or "virtualization". Changes to the data (remove, add, move) and changes to the layout are properly animated by the collection view. The library is inspired by iOS' UICollectionView and Android's RecyclerView. The collection view also handles resizing of the container properly, maintaining the current position in the collection.

toaru-nih - A completely-from-scratch hobby operating system: bootloader, kernel, drivers, C library, and userspace

  •    C

ToaruOS-NIH is a distribution of ToaruOS which contains no third-party components. Its bootloader, kernel, modules, C library, and userspace applications are all written by the ToaruOS development team and direct contributors. This distribution aims to eventually replace the core of the mainline ToaruOS, with the various third-party components building against our own C library. This is a long-term project, and developing the C library to the point where it is useful for this purpose is not expected to be completed for quite some time.

Fizzygum - a new web framework, an entire platform really, designed from the ground up to handle complex things easily

  •    CoffeeScript

Tired of stringing libraries together? Try a new web framework that handles complex things, easily. Fizzygum started (in Oct 2012) from Morphic.js by Jens Mönig.

react-layer-stack - Layering system for React. Useful for popover/modals/tooltip/dnd application

  •    Javascript

The problem is that sometimes the second property isn't what you want in your specific case. Sometimes you want to mount your component into the different physical DOM node and hold the logical parent-child connection at the same time. Canonical example is a Tooltip-like component: at some point, during development process, you could find that you need to add some description for your UI element: it'll be rendered in some fixed layer and it should know its coordinates (which are corresponding UI element coord or mouse coords) and at the same time it needs information whether it should be shown right now or not, its content and some context from parent components.


  •    Javascript

A fast, versatile virtual-render list component for React. This component was originally forked from ReactList, so credit for the core functionality goes to orgsync. I have re-architected it to be more modular, fixed some of the rendering issues, added additional options, and added code coverage.

react-virtual-container - Optimise your React apps by only rendering components when in proximity to the viewport

  •    Javascript

Optimise your React apps by only rendering your components when they are in proximity to the viewport. This library provides you with the ability to create a "virtual container", where it's children will only get rendered if the "virtual container" is within a given proximity of the viewport. This provides you with a nice mechanism by which to lazy load images or "heavy" components.