Results for devils

Shared sources used in the dust-devil socks5 server and monitoring clients.

A remote monitoring client for the dust-devil socks5 server.

A socks5 proxy server with advanced remote monitoring capabilities.

Async libudev wrapper

Utilities for working with publicly available raw MSL, Mars2020, and InSight images

Core features for interacting with the game Devil Daggers

A cross-platform NES Emulator written in Rust using wgpu

A simple audio ai conversation system

A correct, full-featured Unix daemon library and CLI for Rust

A fast, modular, no_std-friendly, batteries-included library for Game AI written in Rust.

Multi-AI council TUI - orchestrate conversations between AI advisors

Pure-Rust PCX (ZSoft PC Paintbrush) reader/writer for oxideav — clean-room from the PCX 5.0 spec

Ruby bindings for DevIL cross platform image loading library

Bridge between ImageRuby and Devil image library

A Ruby Gem that provides a simple method to return a randomly selected Devil Fruit name. It's useful for adding fun and flavor to your applications.

An embeddable static pages engine for Rails apps and the devil

<p>Sass or the much better approach of scss is really helpful and a big silver bullet for my css structuring in ruby projects.</p> \ <p>Standard sass command works for whole directories or single files only. In general it gets the jobs we want done, but in practical usage i think the sass command tool is a little bit unconvinient. A common scenario for me is, \ that you have whole bunch of sass files, which you want to compile to a single compressed output file. But if you have splitted your sass files in component based modules and you want to watch the complete folder you have to care for dependency handling in each file, because each file will be compiled for its own.</p> \ <pre># compiling a complete folder with scss ~ $ sass css/scss:css/compiled</pre> \ <p>So converting the whole folder is not what i want, because i don\'t want to import for example my color.sass config file in each module again. Compiling a single file seems to be the better solution, and it works in general, as expected, but the devil is in the detail. </p> <pre># compiling a single file where the other files are imported. ~ $ sass css/scss/main.scss:css/compiled/main.css</pre> \ <p>If we change a file with impact to our main.sass file, the --watch handle will not get it, because it observes only the timestamp of the given main.sass.</p> <p>Here is it, where mindful_sass tries to help out. You use it according to the single file variant of sass, but it tries to observe the whole folder the given sass file is placed. If a timestamp of file in the sass folder or its children changes it will compile the specified main.sass again.</p> \ <p>This gem is not aimed to replace anything in the sass universe. It is only a wrapper to avoid the described unconvinience, and i hope that it gets useless as fast as possible, because the sass development gets this feature done for themselves.</p> \ <p>Thanks anyway to the sass developer team.</p>

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.