aseprite / aseprite/laf

Migrate code from aseprite to laf

Open
#2 21 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C++
Stars
349
Forks
97
Avg merge
4d 7h
Merged PRs (30d)
2

Description

My plans for the UI part of the laf library are:

- [x] Move the [she library from aseprite](https://github.com/aseprite/aseprite/tree/master/src/she) to `laf::os` namespace.
- [ ] Move the [ui library from aseprite](https://github.com/aseprite/aseprite/tree/master/src/ui) to `laf::ui` namespace.
- [ ] Refactor events (mainly keyboard events) to be more DOM spec-like [[1](https://www.w3.org/TR/DOM-Level-3-Events/)], [[2](https://www.w3.org/TR/DOM-Level-3-Events/#interface-keyboardevent)], [[3](https://www.w3.org/TR/DOM-Level-3-Events/#keys)], [[4](https://cs.chromium.org/chromium/src/ui/events/keycodes/?dr=C)], [[5](https://github.com/WebKit/webkit/blob/dad605136c7145401cdf3917d51894ea5fa7cbdd/Source/WebCore/platform/mac/PlatformEventFactoryMac.mm#L557)].

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing move of the she library into the laf::os namespace, then compare aseprite/src/ui with the target laf::ui namespace. Track the remaining UI migration and the DOM-like keyboard event references; done means the UI library is moved and the planned event refactor is complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.