flr 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: edfe0b5dab4b4dda94c17168b8178f80a0903ccb989f498253dca53041b4d751
+  data.tar.gz: 9e83742e89792aeba9f52a0b68e793afa633c0bc84261a1deb3aff8741ed08c2
+SHA512:
+  metadata.gz: 722245bb8985fe6c2d29116d4cc8b3f8434a21aea05af0acbfcf6e2c62cf9ed1236a2ceea57c389a74f54b39c6f9699bddd631701bb45eff7d6e6a13a186c705
+  data.tar.gz: a8a4136d3e6146eca5f81488ae8adbb3a6307f2bbfa7d952ddebd8ed81f9358ed81d5b87cd652445676bfa47fbfd89305c483b0cccd5c1e6ebb9ee8ee7a079ca

data/.gitignore

@@ -0,0 +1,39 @@
+# General
+*.swp
+*.swo
+*.rbo
+*.gem
+.DS_Store
+.rbenv-version
+.rbx/
+/concatenated.*
+
+# Yardoc
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+
+# Specs
+/spec/reports/
+/tmp/
+
+# RVM files
+/.rvmrc
+/.ruby-version
+/.ruby-gemset
+
+# Bundler files
+/.bundle
+
+# rspec failure tracking
+.rspec_status
+
+# IDEs
+.idea/
+
+# Local Pubspec Tests
+pubspec.yaml
+pubspec.lock
+.packages

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.travis.yml

@@ -0,0 +1,7 @@
+---
+sudo: false
+language: ruby
+cache: bundler
+rvm:
+  - 2.6.3
+before_install: gem install bundler -v 1.17.2

data/CHANGELOG.md

@@ -0,0 +1,40 @@
+## 1.0.0
+- Support for processing font assets ( `.ttf`, `.otf`, `.ttc`) 
+- Improve robustness
+
+## 0.2.2
+
+- improve robustness
+- fix bug
+
+## 0.2.1
+
+- optimize flr help command
+- fix bad info in flr.gemspec
+
+## 0.2.0 - BREAKING CHANGES
+
+- modify the way the Flr configuration is stored: discard the flrfile.yaml file and write the configuration to the pubspec.yaml file
+- `flr generate` and `flr monitor` are combined into `flr run [--auto]`
+- generate `r.g.dart` instead of `R.dart`
+- new `R` class: 
+	- discards `R_X` code struct, and uses `R.x` code  struct
+	- unifies the access way of all types asset resources: using the asset resource ID function, such as `R.image.test()`, `R.svg.test(width: 100, height: 100)`, `R.text.test_json()`
+	- provides `AssetResource` class  to acces the asset metadata, such as `assetName`, `packageName`, `fileBasename`
+- increase the range of legal character sets : `0-9`, `A-Z`, `a-z`, `_`, `+`, `-`, `.`, `·`,  `!`,  `@`,  `&`, `$`, `￥`
+- colored terminal output 
+
+## 0.1.13
+
+- `flr generate` supports checking and outputtting assets with bad filename
+- fix bug
+
+## 0.1.12
+
+- support auto service that automatically specify assets in `pubspec.yaml` and generate  `R.dart` file,  which can be triggered manually or by monitoring asset changes
+- support for processing image assets ( `.png`, `.jpg`, `.jpeg`, `.gif`, `.webp`, `.icon`, `.bmp`, `.wbmp`, `.svg` ) 
+- support for processing text assets ( `.txt`, `.json`, `.yaml`, `.xml` ) 
+- support for processing [image asset variants](https://flutter.dev/docs/development/ui/assets-and-images#asset-variants)
+- support for processing asset which’s filename is bad:
+   - filename has illegal character (such as  `blank`,  `~`, `@`, `#` ) which is outside the range of  valid characters (`0-9`, `A-Z`, `a-z`, `_`,  `$`)
+   - filename begins with a number or character `_`  or character`$`

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at yorkzhang520@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Docs/flr_cli_deployment_check_list.md

@@ -0,0 +1,25 @@
+## Flr Cli Deployment Check List
+
+1. 确定Deployment的版本号：X.Y.Z
+1. 编辑`lib/flr/version.rb`，更新`VERSION`：
+
+	```ruby
+	module Flr
+  		VERSION = "X.Y.Z"
+  		...
+	end
+	```
+1.  更新CHANGELOG.md
+1. 在项目根目录下运行脚本更新Gemfile：`bundle exec ./bin/flr`
+1. 提交当前变更到git
+1. 在项目根目录下运行脚本打包Gem：`gem build flr.gemspec`
+1. 本地安装Flr进行测试：`sudo gem install flr-x.y.z.gem`
+1. 若无问题，则发布Flr到RubyGems市场
+
+## Publish Flr Cli
+
+1. 在项目根目录下运行脚本发布Flr：`gem push flr-x.y.z.gem`
+
+## Other
+ 
+1. 从RubyGems市场下架指定版本的Flr：`gem yank flr -v x.y.z`

data/Docs/flr_usage_example_gif_record_scripts.txt

@@ -0,0 +1,42 @@
+
+注意：录制前，请先还原pubspec.yaml
+---------------------------------------------
+
+Flr Usage Example
+
+---------------------------------------------
+
+1. Run `flr init`
+
+---------------------------------------------
+
+2. Edit pubspec.yaml
+to configure the resource directory paths
+
+---------------------------------------------
+
+3. Run `flr run`
+
+---------------------------------------------
+
+One More Thing:
+
+If you want Flr to auto generate when you change Flutter asssets, 
+
+you can Run `flr run --auto` to launch a monitoring service.
+
+For example:
+
+---------------------------------------------
+
+1. Run `flr run --auto`
+
+---------------------------------------------
+
+2. Add a new asset:
+163.com.yaml
+
+---------------------------------------------
+
+3. Press `Ctrl-C` 
+to terminate the monitoring service if you want

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in flr.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,28 @@
+PATH
+  remote: .
+  specs:
+    flr (1.0.0)
+      bundler (~> 2.0, >= 2.0.2)
+      listen (~> 3.0, >= 3.2.1)
+      thor (~> 1.0, >= 1.0.1)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ffi (1.12.1)
+    listen (3.2.1)
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
+    rb-fsevent (0.10.3)
+    rb-inotify (0.10.1)
+      ffi (~> 1.0)
+    thor (1.0.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  flr!
+
+BUNDLED WITH
+   2.0.2

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2019 York
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/flr

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "flr"
+
+Flr::CLI.start(ARGV)

data/flr.gemspec

@@ -0,0 +1,47 @@
+
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "flr/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "flr"
+  spec.version       = Flr::VERSION
+  spec.authors       = ["York"]
+  spec.email         = ["yorkzhang520@gmail.com"]
+
+  spec.summary       = "Flr(Flutter-R): A Flutter Resource Manager CLI TooL."
+  spec.description   = "Flr(Flutter-R): A Flutter Resource Manager CLI TooL, which can help flutter developer to auto specify assets in pubspec.yaml and generate r.g.dart file after he changes the flutter project assets."
+  spec.homepage      = "https://github.com/Fly-Mix/flr-cli"
+  spec.license       = "MIT"
+
+  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
+  # to allow pushing to a single host or delete this section to allow pushing to any host.
+  if spec.respond_to?(:metadata)
+    # spec.metadata["allowed_push_host"] = "https://rubygems.org"
+
+    spec.metadata["homepage_uri"] = spec.homepage
+    spec.metadata["source_code_uri"] = spec.homepage
+    spec.metadata["changelog_uri"] = "#{spec.homepage}/blob/master/CHANGELOG.md"
+  else
+    raise "RubyGems 2.0 or newer is required to protect against " \
+      "public gem pushes."
+  end
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features|README)}) }
+  end
+
+  spec.bindir        = "bin"
+  spec.executables   = ["flr"]
+  spec.require_paths = ["lib"]
+
+  # spec.add_development_dependency "rake", "~> 10.0"
+  # spec.add_development_dependency "rspec", "~> 3.0"
+
+  spec.add_runtime_dependency "bundler", "~> 2.0", '>= 2.0.2'
+  spec.add_runtime_dependency "thor", "~> 1.0", '>= 1.0.1'
+  spec.add_runtime_dependency "listen", "~> 3.0", '>= 3.2.1'
+
+end

data/lib/flr.rb

@@ -0,0 +1,71 @@
+require 'thor'
+require 'flr/version'
+require 'flr/command'
+require 'flr/string_extensions'
+
+module Flr
+
+  class CLI < Thor
+
+    def self.help(shell, subcommand = false, display_introduction = true)
+      introduction = <<-MESSAGE
+A Flutter Resource Manager CLI TooL, which can help flutter developer to auto specify assets in pubspec.yaml and generate r.g.dart file after he changes the flutter project assets.
+More details see https://github.com/Fly-Mix/flr-cli
+
+      MESSAGE
+      if display_introduction
+        puts(introduction)
+      end
+      super(shell,subcommand)
+    end
+
+    def self.exit_on_failure?
+      puts("")
+      help(CLI::Base.shell.new, false, false)
+      true
+    end
+
+    desc "version", "Display version"
+    long_desc <<-LONGDESC
+      Display the version of Flr.
+
+    LONGDESC
+    def version
+      Command.version
+    end
+    map %w[-v --version] => :version
+
+    desc "init", "Add flr configuration and dependency \"r_dart_library\" into pubspec.yaml"
+    long_desc <<-LONGDESC
+      Add flr configuration 
+      and dependency \"r_dart_library\"(https://github.com/YK-Unit/r_dart_library) into pubspec.yaml.
+
+    LONGDESC
+    def init
+      Command.init
+    end
+
+    desc "run [--auto]", "Scan assets, specify scanned assets in pubspec.yaml, generate \"r.g.dart\""
+    long_desc <<-LONGDESC
+      
+      #{"With no option".bold}, #{"Flr".bold} will scan the asset directories configured in `pubspec.yaml`,
+      then specify scanned assets in pubspec.yaml,
+      and generate "r.g.dart" file.
+
+      #{"With".bold} #{"--auto".red.bold} #{"option".bold}, #{"Flr".bold} will launch a monitoring service that continuously monitors asset directories configured in pubspec.yaml.
+      If the service detects any asset changes, #{"Flr".bold} will automatically scan the asset directories,
+      then specify scanned assets in pubspec.yaml,
+      and generate "r.g.dart" file.
+
+      You can terminate the monitoring service by manually pressing #{"\"Ctrl-C\"".bold} if it exists.
+
+    LONGDESC
+    option :auto, :type => :boolean
+    def run_command
+      options[:auto] ? Command.start_monitor : Command.generate
+    end
+
+    map 'run' => :run_command
+
+  end
+end