Search Results for "timelines"

Plaso (Plaso Langar Að Safna Öllu), or "super timeline all the things," is a Python-based engine designed for automatic creation of timelines in digital forensic investigations. It processes various log files and artifacts to generate a chronological sequence of events, aiding analysts in understanding system activities.​

Perfetto is a production-grade tracing platform for Android, Linux, and Chrome that captures extremely detailed information about what a system is doing over time. It’s designed around a low-overhead producer/consumer model: instrumented components (“producers”) write binary events into shared memory buffers and a collector (“service”) reliably streams them to storage. The data model spans kernel and userspace, so you can stitch together CPU scheduling, app lifecycles, binder/IPC hops, GPU...

emiT is a language all about parallel timelines. At any given point you can send a variable back in time, and make it change things about the past, starting a new timeline where the result is different. You can kill variables, which destroys them permanantly- at least until you send another variable back in time to kill the variable doing the killing. This very quickly leads to a lot of confusion, with a constantly changing source code and the very easy possibility of creating a paradox or a time loop. ...

...Its architecture is built around the concept of a media controller and modular control components, enabling developers to easily add, remove, or customize features such as playback controls, volume sliders, timelines, and fullscreen buttons.

...It is designed to make the often dense and verbose outputs from AI coding sessions easier to read, share, and archive by breaking conversations into paginated, annotated pages with navigable timelines of prompts and responses. Users can run this tool locally or fetch sessions from the Claude API, giving flexibility for individual workflows or team documentation practices. The generated HTML includes interactive navigation and can optionally be published to GitHub Gists for sharing with collaborators or embedding in other documentation. ...

...Its templates are derived from established sources including Google's Site Reliability Engineering material, Azure reports, Elastic Cloud incidents, and reliability engineering books. Each format provides a structured starting point for documenting outages, impact, timelines, causes, and follow-up work. The repository also links to real incident reports that demonstrate how postmortems are written in practice. Vim and Emacs users can configure templates to load automatically when creating appropriately named postmortem files. Additional resources cover blameless culture, incident reviews, action items, failure analysis, and effective postmortem practices.

SWFWire is a set of open-source ActionScript 3 libraries and tools for parsing, editing, and generating SWF files. It’s designed to help developers analyze Flash content, extract embedded assets, or build SWFs programmatically. This project is especially useful for reverse engineering Flash files or building custom Flash pipelines, and includes a visual decompiler/editor.

CHAP Links Library is a web based visualization library for displaying graphs, networks, and timelines. The tools are developed as Google Visualization Charts for Javascript and GWT. Links Library is part of CHAP, the Common Hybrid Agent Platform. This project has been moved to Github. Please visit http://almende.github.com/chap-links-library/

Clint can display data containing in a QAbstractItemModel as charts, trees or timelines. A chart can be linear ( data are displayed as curves, bars or points), radial ( data are displayed like a bar chart but in circle) or a piechart (2D or 3D). A tree displays data from a model like QTreeItemModel in a classic tree (horizontal or vertical) or radial (in circle). A timeline displays data from a model like a QListItemModel following a path.