davinci-text 1.0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 2f30467eb252d09c694b12f81f2f5e159ffb8b3a
+  data.tar.gz: 6d3a5c029b2383ed11a6acd61d1aba04c67615ab
+SHA512:
+  metadata.gz: b29ffa23610dfc406a8fbcc37044410664d76f36426cd7f2b4f15226704283530b2f41cb8224a64585b2bd2aa0177b32a15041466a2b3b5f0dc527ac53e0eb67
+  data.tar.gz: 22721d4f906a539380943fc6e719364ad5ca61486d89a75e6c9621734037002282127ef73c06f18761b376ee5f9c31cacbfed97bc1984b5ea198c8396b9e3a0d

data/.byebug_history

@@ -0,0 +1,86 @@
+continue
+pp @material_controller.options
+@material_controller.options
+@material_controller.options[:comment_foreground]
+@material_controller.options[:comment_foregroun]
+exit
+continue
+exit
+continue
+setting.xpath('./string[position()=1]/text()').text
+setting.xpath('./dict/key[text()="foreground"]/following-sibling::string[1]/text()').text
+setting[name]
+setting["name"]
+setting.text
+setting[0]
+setting
+@options
+continue
+all_settings
+continue
+pp all_settings
+all_settings
+@input_controller.options
+continue
+@options
+continue
+@options
+continue
+key
+continue
+key = key.split(",")
+key
+continue
+@options
+key.gsub(/\s/, "")
+key.gsub/\s/, "")
+key
+continue
+key
+continue
+key
+continue
+key
+continue
+key
+continue
+key
+continue
+key
+continue
+key
+continue
+settings_keys
+continue
+settings_values
+settings_keys
+continue
+@filepath
+continue
+@base
+continue
+@new_dir
+@newdir
+continue
+root_dir
+continue
+current_dir
+continue
+@directory
+@filepath
+@new_dir
+root_dir
+continue
+new_dir
+current_dir
+continue
+root_dir
+new_dir
+continue
+filepath
+continue
+filepath.split("/")[0..-4]
+filepath[0..-4]
+filepath.split("/")
+filepath
+script_directory

data/.circleci/config.yml

@@ -0,0 +1,57 @@
+# Ruby CircleCI 2.0 configuration file
+#
+# Check https://circleci.com/docs/2.0/language-ruby/ for more details
+#
+version: 2
+jobs:
+  build:
+    docker:
+      # specify the version you desire here
+       - image: circleci/ruby:2.4.1-node-browsers
+      
+      # Specify service dependencies here if necessary
+      # CircleCI maintains a library of pre-built images
+      # documented at https://circleci.com/docs/2.0/circleci-images/
+      # - image: circleci/postgres:9.4
+
+    working_directory: ~/repo
+
+    steps:
+      - checkout
+
+      # Download and cache dependencies
+      - restore_cache:
+          keys:
+          - v1-dependencies-{{ checksum "Gemfile.lock" }}
+          # fallback to using the latest cache if no exact match is found
+          - v1-dependencies-
+
+      - run:
+          name: install dependencies
+          command: |
+            bundle install --jobs=4 --retry=3 --path vendor/bundle
+
+      - save_cache:
+          paths:
+            - ./venv
+          key: v1-dependencies-{{ checksum "Gemfile.lock" }}
+        
+      # Database setup
+    #   - run: bundle exec rake db:create
+    #   - run: bundle exec rake db:schema:load
+
+      # run tests!
+      - run:
+          name: run tests
+          command: |
+            mkdir /tmp/test-results
+            TEST_FILES="$(circleci tests glob "spec/**/*_spec.rb" | circleci tests split --split-by=timings)"
+            
+            bundle exec rspec 
+
+      # collect reports
+      - store_test_results:
+          path: /tmp/test-results
+      - store_artifacts:
+          path: /tmp/test-results
+          destination: test-results

data/.gitignore

@@ -0,0 +1,53 @@
+*.gem
+*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/spec/examples.txt
+/test/tmp/
+/test/version_tmp/
+/tmp/
+
+output/*
+!output/.gitkeep
+
+# Used by dotenv library to load environment variables.
+# .env
+
+## Specific to RubyMotion:
+.dat*
+.repl_history
+build/
+*.bridgesupport
+build-iPhoneOS/
+build-iPhoneSimulator/
+
+## Specific to RubyMotion (use of CocoaPods):
+#
+# We recommend against adding the Pods directory to your .gitignore. However
+# you should judge for yourself, the pros and cons are mentioned at:
+# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
+#
+# vendor/Pods/
+
+## Documentation cache and generated files:
+/.yardoc/
+/_yardoc/
+/doc/
+/rdoc/
+
+## Environment normalization:
+/.bundle/
+/vendor/bundle
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+# Gemfile.lock
+# .ruby-version
+# .ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc

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 matt.cheah@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/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+gemspec
+

data/Gemfile.lock

@@ -0,0 +1,50 @@
+PATH
+  remote: .
+  specs:
+    davinci-text (1.0.0)
+      coyote (~> 1.2)
+      nokogiri (~> 1.8)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    byebug (9.0.6)
+    colored (1.2)
+    coyote (1.2.0)
+      colored (>= 1.2)
+      rb-fsevent (>= 0.4.0)
+    diff-lcs (1.3)
+    mini_portile2 (2.2.0)
+    nokogiri (1.8.0)
+      mini_portile2 (~> 2.2.0)
+    rake (10.4.2)
+    rb-fsevent (0.10.2)
+    rspec (3.6.0)
+      rspec-core (~> 3.6.0)
+      rspec-expectations (~> 3.6.0)
+      rspec-mocks (~> 3.6.0)
+    rspec-core (3.6.0)
+      rspec-support (~> 3.6.0)
+    rspec-expectations (3.6.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.6.0)
+    rspec-mocks (3.6.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.6.0)
+    rspec-support (3.6.0)
+    rspec_junit_formatter (0.3.0)
+      rspec-core (>= 2, < 4, != 2.12.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.15)
+  byebug (~> 9.0)
+  davinci-text!
+  rake (~> 10.0)
+  rspec (~> 3.2)
+  rspec_junit_formatter (~> 0.3)
+
+BUNDLED WITH
+   1.15.4

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 Matt Cheah
+
+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/README.md

@@ -0,0 +1,91 @@
+# DaVinci-Text
+
+![alt text](https://circleci.com/gh/mattcheah/davinci.svg?style=shield&circle-token=5a1e0343c196170c3abe3387d7014657fef4b700 "")
+
+Ruby command-line script to transfer your text-editor color scheme between the Sublime and Atom text editors. 
+
+Support for Dreamweaver and Brackets to come.
+
+## Installation / Setup
+
+Install the gem the normal way:
+
+    $ gem install davinci
+    
+You are now ready to use Davinci.
+
+## Usage
+
+### Command Line Interface
+
+After instaling davinci, run it by simply typing `davinci` in the command line and follow the instructions.
+A command line prompt will show, asking you to choose the text editor you want to transfer your theme from. 
+
+    What Text Editor are you currently using?
+    (1) Sublime
+    (2) Atom
+    > 1
+
+Enter 1 or 2 to select your text editor. The system will then ask for the theme file or theme folder. 
+To figure out where this is, see the [Reference section](https://github.com/mattcheah/davinci/blob/master/REFERENCE.md).
+You may also use the example_files directory, which contains the default Atom theme "Atom-Dark-Syntax", and the default Sublime theme "Monokai".  
+
+    Enter the full filepath of your Sublime tmTheme syntax color file.
+    If you do not know where this can be found, please read the documentation.
+    > /example_files/sublime/monokai.tmTheme
+    
+Enter the path to your theme file or directory. Then give the output text editor to finish things up. 
+
+    What editor would you like to move your color scheme to?
+    (1) Sublime
+    (2) Atom
+    > 2
+
+The system will output the parsed options into a theme template for your output text editor and place the file(s) into a folder nested in the original filepath. 
+To add this newly created theme to your text editor, read the [Reference section](https://github.com/mattcheah/davinci/blob/master/REFERENCE.md). 
+
+To exit the program any time, press ctrl+c
+    
+### One Line Execution
+
+If you don't want to go through the command line interface, simply provide arguments for your filepath (sublime) or directory path (atom), and the name of your output editor ("sublime" or "atom").
+
+`davinci example_files/sublime/monokai.tmTheme atom`
+
+or
+
+`davinci example_files/atom/atom-dark-syntax sublime`
+
+## Warnings
+
+Theme files are parsed by an XML Parser or by Regex. Both of these parsing methods can be potentially unreliable depending on the scopes assigned to the colors in the Sublime XML file, or the combination of Less selectors in the Atom combined file. 
+
+This is further complicated by the fact that editors do not always categorize the same code in the same way. As an example, the `System` in the following Java code
+
+    System.out.println("Hello World!");
+
+is categorized in Sublime as a "Storage Type" keyword, usually reserved for keywords that affect the storage of an item (eg. `void` in Java). However, in Atom, `System` is given the classes `"syntax--variable syntax--other syntax--object syntax--java"`. The most common of these classes would be `syntax--variable`, meaning that even if colors from other classes are parsed (they're not), the color would not necessarily show up the same when transferring between Atom and Sublime.  
+
+All this to say that the process is unstable and you may have to do a little bit of clean-up work on your resulting theme-files. I have found, however, that the overall look and feel of the theme is preserved.
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/mattcheah/davinci. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+### Support for new editors
+
+Contributors who would like to add support for a new editor should make sure their pull requests contain the following: 
+* An Excel or CSV file adding a selector column for their new editor to the [reference sheet](https://docs.google.com/spreadsheets/d/1DqhOP7L2ApQSOU6tKnh1Bx-92pzY7-BJK2Yccf6wr-c/edit?usp=sharing). 
+* A controller for inputting and/or outputting hex codes to/from the options hash.
+* Rspec tests
+    * Input Controllers: Tests should confirm that an options hash contains the correct colors for the primary theme styles (:foreground, :background, :comment_foreground, :string_foreground, etc)
+    * Output Controllers: Tests should confirm that the colors from a given options hash show up correctly in the outputted file(s). If an input controller is provided, it can be used to confirm this. If not, the outputted file must be parsed manually. 
+* Updates to MenuController and cl_args_controller to include functionality.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the davinci project’s codebases is expected to follow the [code of conduct](https://github.com/mattcheah/davinci/blob/master/CODE_OF_CONDUCT.md).