Gist 69a9d27f495ef695f39947559d3ead66

100%

Gist 69a9d27f495ef695f39947559d3ead66

✓ Published0🌍 Public

Last edited May 24, 2022

Created on May 24, 2022

This example demonstrates a Kotlin-based reactive flow pipeline that emits a sequence of eight "Hello" messages at 700-millisecond intervals. The visualization pairs two components: an `Activity_Flow.kt` file that subscribes to a lifecycle-scoped `Flow` collector, and a `ViewModel_Flow.kt` file that defines the `triggerFlow()` function using the `flow` builder with `repeat` and `delay` operators. The code highlights the use of Kotlin coroutines and the Flow API for asynchronous, time-based data streaming, though it does not render any graphical output.

AI-generated description

Similar vizzes

Loading thumbnail…

Game of Life functional in Kotlin

This example demonstrates Conway’s Game of Life as a purely functional Kotlin implementation, rendering 100 generations of a small initial board pattern as console text output. The code defines a `step` function that computes the next generation using `mapIndexed` and a `neighboursAlive` helper, checking alive neighbor counts against the standard 2–3 survival and 3 birth rules. It uses `Stream.iterate` from the Java Streams API to generate the infinite sequence of boards, limiting it to 100 steps. The rendering approach prints each board via `toMultiLineString`, encoding live cells as “Ö” and dead cells as “†”.

BBastiTee

57% match

Loading thumbnail…

Gist fed523040b43046b27a52290d26c4ceb

This example visualizes the structure of a small React component hierarchy through a static code excerpt, showing how typed props and event handlers are passed between parent and child components. The code uses the Flow type checker to define an `onSubmit` prop as a `Function`, with class `A` passing its `handleSomeEvent` method to component `B` via a prop. The rendering approach is purely textual, relying on the explicit Flow annotations and JSX syntax to illustrate data flow rather than any graphical output. It demonstrates type-safe callback propagation in a React/Flow environment, though no runtime visualization or data processing library appears in the snippet.

CCaged

56% match

Loading thumbnail…

Aggregated Event Sequences with Flow Histograms

This example visualizes aggregated event sequences from network connection logs, displaying each sequence as a row of colored blocks in a middle panel alongside attribute histograms on the left and detailed sequence information on the right. Users can filter sequences and events using regular expressions, with matching elements highlighted in green. Clicking events in the detail view builds rules that update the filter. The visualization uses d3.v5 with SVG rendering, employing d3.scaleBand, d3.scaleLinear, d3.axisBottom, d3.axisLeft for histograms, and d3.event handlers for interactivity.

Ffloresh

50% match

Loading thumbnail…

Gist a3686a8f89494538dbfcf1144718885c

This example shows a personal reference collection for building an Android and web app with machine learning and conversational interfaces, compiled from Google I/O Extended Lima 2019. The visualization is a text-based list that links to codelabs, documentation, and developer consoles for ML Kit Firebase, Dialogflow, Flutter UI, and Firebase Hosting. It uses no charting libraries, instead presenting raw text and URLs as the primary graphic. The code highlights Flutter’s declarative UI and notes web-specific caveats like non-clickable buttons and broken animations, with references to SharedPreferences and Fuchsia.

MMistyBlunch

49% match

Loading thumbnail…

To-do list

This example shows a simple interactive to-do list titled “To get the Flow going,” presenting three checkbox items that ask about daily habits and ending with a self-affirmation. Built with React, it renders the list as JSX components, using the `useState`-less controlled inputs directly in the markup. The code imports a custom `todoItem` component that returns a list item with a checkbox and label, while the main `App` component composes three instances with hardcoded phrases. Styling is applied via plain CSS, setting a steelblue background and font size on the list container.

JJunyanL

49% match

Loading thumbnail…

Data Flow Diagram

This visualization renders a reactive data flow diagram for a ModelJS application, using a force-directed graph layout to display the dependencies between reactive properties and lambda functions. The graph is constructed from runtime-generated JSON describing the flow, with SVG rendering driven by D3's force layout. Nodes are positioned by the layout, with `property` nodes colored coral and `lambda` nodes white, while links trace the flow of data between them. The diagram includes zoom and pan interactions, and visually encodes the structure of reactive dependencies in a dynamic, graph-based form.

CCurran Kelleher

49% match

Loading thumbnail…

Playing with Azure Functions

This example visualizes how three Azure Functions HTTP triggers enqueue messages to a shared storage queue, showing the sequential flow from request to queue insertion. The code uses the `ICollector<string>` interface to add messages named "Larry", "Moe", and "Curly" to an Azure Storage queue, with each function call triggering the enqueue operation. The visualization highlights the request–response cycle via the `HttpRequestMessage` and `HttpResponseMessage` objects, while `TraceWriter` logs the incoming URI. It demonstrates the serverless event-driven pattern where HTTP calls produce queue entries, though the rendering itself is not shown in the provided code.

HHugoberry

48% match

Loading thumbnail…

Hello Reactor

This example demonstrates a minimal event-driven communication system built with JavaScript. It shows how two listeners attached to the same `'big bang'` event respond to a dispatched payload, with one listener logging a fixed message and the other printing the passed arguments. The code defines a custom `Reactor` class and an `Event` class, showcasing manual event registration, callback storage, and dispatch logic. The implementation relies on JavaScript's array `forEach` method to invoke all registered callbacks with the spread `...eventArgs` syntax. The data originates from a hardcoded dispatch call passing the values `135`, `'test'`, and `[1, 2, 3]`.

MMAKIO135

48% match