riverpod
반응형 캐싱 및 데이터 바인딩 프레임워크입니다. Riverpod은 비동기 코드 작업을 쉽게 만듭니다.
이미지의 일부를 투명하게 설정할 수 있는 그래픽 페인트 편집기 애플리케이션입니다.
반응형 캐싱 및 데이터 바인딩 프레임워크입니다. Riverpod은 비동기 코드 작업을 쉽게 만듭니다.
Flutter 애플리케이션용 타입 안전하고 반응형이며 가벼운 SQLite 추상화입니다. 이 라이브러리는 런타임 종속성입니다.
Canvas 경로 생성 및 조작을 도와주는 플러터 라이브러리
v0.3.0Flutter 토스트 플러그인입니다.
사람이 이해하기 쉬운 파일 크기를 얻는 패키지입니다. 원시 파일 크기를 사람이 읽기 쉬운 문자열로 변환합니다.
더 안전한 프로그래밍을 촉진하기 위한 러스트 스타일의 타입인 Option과 Result의 정의.
Flutter Localization는 맵 데이터를 사용한 앱 내 로컬라이제이션을 위한 패키지입니다. flutter_localizations 자체에서 영감을 받아 더 쉽게, 빠르게 구현할 수 있습니다.
{"sdk":"flutter"}{"sdk":"flutter"}^0.3.2^0.20.2^1.0.2^2.3.6^2.1.1^2.0.15^2.4.1^2.0.3^4.8.1^1.17.1^6.1.6^0.3.0^5.2.0^1.1.0^8.3.0^2.0.1^1.0.0+2^3.2.0^11.4.0^9.1.2^1.1.2^2.0.11^8.3.5^1.2.0^2.3.0^1.0.1{"path":"packages/colorpicker"}{"sdk":"flutter"}{"sdk":"flutter"}^5.2.0^0.9.3^5.0.0^1.4.2^2.2.4^2.0.0^2.2.0^2.4.1^2.3.7^6.7.1아래는 영문 원문 스냅샷입니다. 최신 내용은 GitHub에서 확인하세요.
Paintroid, also known as Pocket Paint, is associated to Catroid. It is a graphical paint editor application for the Android platform that, among others, allows setting parts of pictures to transparent.
Since Pocket Paint is now available in Google Play store you can also download Paintroid (Pocket Paint) from here. Alternatively, you can find it on **F-Droid ** here.
For more information oriented towards developers please visit our developers page.
Note This repository is the Flutter version of Paintroid
make getmake runAlternatively make all can be used to:
flutter clean→flutter pub get→build_runner build→ →flutter run
make buildmake testmake unitmake widgetmake integrationFor integration tests:
Run the integration tests without device:
make integration to run all integration testsmake integration target=name_test to run a specific integration test file
example: make integration target=line_toolmake integration target=name_test id=n to run a specific test in a file
example: make integration target=line_tool id=1
(make sure to add the test suffix to the test file name)Run the integration tests with device:
flutter devicesmake integration-drive to run all integration testsmake integration-drive target=name_test to run a specific integration test file
example: make integration-drive target=line_toolmake integration-drive target=name_test id=x to run a specific test in a file
example: make integration-drive target=line_tool id=1
(make sure to add the test suffix to the file name)Please report all bugs on our Jira Bugtracker
If you want to contribute we suggest that you start with forking our repository and browse the code. Then you can look at our Issue-Tracker and start with fixing one ticket. Please make sure to pick a ticket with the status "Ready for development" and comment on the ticket that you are working on it. We strictly use Test-Driven Development and Clean Code, so first read everything you can about these development methods. Code developed in a different style will not be accepted. When you are done, comment again on the ticket and create a pull request on github. After you've created a pull request we will review your code and do a full testrun on your branch.
Let's start to set up the working environment using the instructions in our Wiki!
License of our project (mainly AGPL v3).