#csharp#2d#avaloniaui#csharp#dotnet_core#dotnetcore#editor#game_development#graphics#graphics_editor#linux_desktop#painting#pixel_art#pixi#procedural_drawing#procedural_generation#raster_graphics#sprites#tabs#vector_graphics
PixiEditor is a free, easy-to-use 2D graphics editor that combines pixel art, painting, and vector tools all in one program. You can create game sprites, animations, logos, and edit images with a simple interface. It supports mixing vector and raster graphics on the same canvas and lets you export to many formats like PNG, SVG, GIF, and MP4. The powerful Node Graph system allows you to create complex, non-destructive effects and animations. It also has a timeline for frame-by-frame animation and autosaves your work to prevent loss. This makes it a versatile tool for artists and game developers.
https://github.com/PixiEditor/PixiEditor
https://pypi.python.org/pypi/oauthlib
A generic, spec-compliant, thorough implementation of the #OAuth request-signing logic for python
OAuth often seems complicated and difficult-to-implement. There are several prominent libraries for handling OAuth requests, but they all suffer from one or both of the following:
They predate the OAuth 1.0 spec, AKA RFC 5849.
They predate the OAuth 2.0 spec, AKA RFC 6749.
They assume the usage of a specific HTTP request library.
OAuthLib is a generic utility which implements the logic of OAuth without assuming a specific HTTP request object or web framework. Use it to graft OAuth client support onto your favorite HTTP library, or provide support onto your favourite web framework. If you’re a maintainer of such a library, write a thin veneer on top of OAuthLib and get OAuth support for very little effort.
https://aaronparecki.com/2012/07/29/2/oauth2-simplified#others
OAuth 2 Simplified
Sun, Jul 29, 2012 9:30am -07:00
Many services such as #Facebook, #Github, and #Google have already deployed OAuth 2 servers, and deployed implementations win.
The #OAuth 2 spec itself leaves many decisions up to the implementor. Instead of describing all possible decisions that need to be made to successfully implement OAuth 2, this post makes decisions that are appropriate for most implementations.
This post is an attempt to describe OAuth 2 in a simplified format to help developers and service providers implement the protocol.