diff --git a/.travis.yml b/.travis.yml new file mode 100644 index 00000000000..a533aa377b3 --- /dev/null +++ b/.travis.yml @@ -0,0 +1,8 @@ +language: node_js +node_js: + - "node" +notifications: + webhooks: https://www.travisbuddy.com +env: +- MY_VAR=EverythignIsAwesome +- NODE_ENV=TEST \ No newline at end of file diff --git a/404.html b/404.html new file mode 100644 index 00000000000..ef76943d220 --- /dev/null +++ b/404.html @@ -0,0 +1,80 @@ + + + + + + + + + mnmlurl - Minimal URL is a modern URL shortener with support for custom alias + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+

404

+ page not found +
+
+ +
+ + + diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 00000000000..14a434e3166 --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,38 @@ +# Changelog +# Title +### Description by [Liyas Thomas](https://github.com/liyasthomas) + +--- + +# 1.0.0 + +## This is it, Title 1.0.0! +We are finally out of beta, therefore many bugs were fixed and camera received a brand new look. + +* **NEW**: Camera redesign +* **NEW**: Camera redesign +* **NEW**: macOS and iOS support +* **IMPROVEMENT**: Major improvements +* **IMPROVEMENT**: Updated libraries +* **FIX**: Fixed many bugs and crashes +* **FIX**: Graphic glitches +* **FIX**: Statusbar too dark +* **TRANSLATION**: Updated translations +* **REVERT**: Brought back the "Help" button +* **OTHER**: Removed all analytics + +--- + +# 0.9.0 + +## I worked a lot on Web apps, WebAR, WebGL & PWAs +So I think Lvr is now ready to be released :) + +I will keep the usual branch model. + +* Stable release on `master` branch + +--- + +## Thanks +* [Google](https://www.google.com) - for [Polymer](https://polymer-project.org) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000000..a67988e54fc --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,76 @@ +# 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, sex characteristics, gender identity and expression, +level of experience, education, socio-economic status, 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 liyascthomas@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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see +https://www.contributor-covenant.org/faq diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000000..374205a6375 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,180 @@ +# Introduction + +### Write something nice here! + +>First off, thank you for considering contributing to Active Admin. It's people like you that make Active Admin such a great tool. + +[source: [Active Admin](https://github.com/activeadmin/activeadmin/blob/master/CONTRIBUTING.md)] **Need more inspiration?** [1] [Read The Docs](http://read-the-docs.readthedocs.org/en/latest/contribute.html) [2] [Mustache.js](https://github.com/janl/mustache.js/#contributing) + +### Tell them why they should read your guidelines. + +>Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests. + +[source: [Hoodie](https://github.com/hoodiehq/hoodie/blob/master/CONTRIBUTING.md)] + +### Explain what kinds of contributions you are looking for. + +Keep an open mind! Improving documentation, bug triaging, or writing tutorials are all examples of helpful contributions that mean less work for you. + +> Elasticsearch is an open source project and we love to receive contributions from our community — you! There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests or writing code which can be incorporated into Elasticsearch itself. + +[source: [Elasticsearch](https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md)] **Need more inspiration?** [1] [Devise](https://github.com/plataformatec/devise/wiki/Contributing) [2] [Geocoder](https://github.com/alexreisner/geocoder#known-issue) (“known issue”) + +### Explain contributions you are NOT looking for (if any). + +Again, defining this up front means less work for you. If someone ignores your guide and submits something you don’t want, you can simply close it and point to your policy. + +> Please, don't use the issue tracker for [support questions]. Check whether the #pocoo IRC channel on Freenode can help with your issue. If your problem is not strictly Werkzeug or Flask specific, #python is generally more active. Stack Overflow is also worth considering. + +[source: [Flask](https://github.com/pallets/flask/blob/master/CONTRIBUTING.rst)] **Need more inspiration?** [1] [cucumber-ruby](https://github.com/cucumber/cucumber-ruby/blob/master/CONTRIBUTING.md#about-to-create-a-new-github-issue) [2] [Read the Docs](http://read-the-docs.readthedocs.org/en/latest/open-source-philosophy.html#unsupported) + +# Ground Rules +### Set expectations for behavior (yours, and theirs). +This includes not just how to communicate with others (being respectful, considerate, etc) but also technical responsibilities (importance of testing, project dependencies, etc). Mention and link to your code of conduct, if you have one. + +> Responsibilities +> * Ensure cross-platform compatibility for every change that's accepted. Windows, Mac, Debian & Ubuntu Linux. +> * Ensure that code that goes into core meets all requirements in this checklist: https://gist.github.com/audreyr/4feef90445b9680475f2 +> * Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback. +> * Don't add any classes to the codebase unless absolutely needed. Err on the side of using functions. +> * Keep feature versions as small as possible, preferably one new feature per version. +> * Be welcoming to newcomers and encourage diverse new contributors from all backgrounds. See the [Python Community Code of Conduct](https://www.python.org/psf/codeofconduct/). + +[source: [cookiecutter](https://github.com/audreyr/cookiecutter/blob/master/CONTRIBUTING.rst)] **Need more inspiration?** [1] [Celery](https://github.com/celery/celery/blob/master/CONTRIBUTING.rst#community-code-of-conduct) [2] [geocoder](https://github.com/alexreisner/geocoder#contributing) + +# Your First Contribution +Help people who are new to your project understand where they can be most helpful. This is also a good time to let people know if you follow a label convention for flagging beginner issues. + +> Unsure where to begin contributing to Atom? You can start by looking through these beginner and help-wanted issues: +> Beginner issues - issues which should only require a few lines of code, and a test or two. +> Help wanted issues - issues which should be a bit more involved than beginner issues. +> Both issue lists are sorted by total number of comments. While not perfect, number of comments is a reasonable proxy for impact a given change will have. + +[source: [Atom](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#your-first-code-contribution)] **Need more inspiration?** [1] [Read the Docs](http://docs.readthedocs.org/en/latest/contribute.html#contributing-to-development) [2] [Django](https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/#first-steps) (scroll down to "Guidelines" as well) + +### Bonus points: Add a link to a resource for people who have never contributed to open source before. +Here are a couple of friendly tutorials you can include: http://makeapullrequest.com/ and http://www.firsttimersonly.com/ + +> Working on your first Pull Request? You can learn how from this *free* series, [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github). + +[source: [React](https://github.com/facebook/react/blob/master/CONTRIBUTING.md#pull-requests)] + +As a side note, it helps to use newcomer-friendly language throughout the rest of your document. Here are a couple of examples from [Active Admin](https://github.com/activeadmin/activeadmin/blob/master/CONTRIBUTING.md): + +>At this point, you're ready to make your changes! Feel free to ask for help; everyone is a beginner at first :smile_cat: +> +>If a maintainer asks you to "rebase" your PR, they're saying that a lot of code has changed, and that you need to update your branch so it's easier to merge. + +# Getting started +### Give them a quick walkthrough of how to submit a contribution. +How you write this is up to you, but some things you may want to include: + +* Let them know if they need to sign a CLA, agree to a DCO, or get any other legal stuff out of the way +* If tests are required for contributions, let them know, and explain how to run the tests +* If you use anything other than GitHub to manage issues (ex. JIRA or Trac), let them know which tools they’ll need to contribute + +>For something that is bigger than a one or two line fix: + +>1. Create your own fork of the code +>2. Do the changes in your fork +>3. If you like the change and think the project could use it: + * Be sure you have followed the code style for the project. + * Sign the Contributor License Agreement, CLA, with the jQuery Foundation. + * Note the jQuery Foundation Code of Conduct. + * Send a pull request indicating that you have a CLA on file. + +[source: [Requirejs](http://requirejs.org/docs/contributing.html)] **Need more inspiration?** [1] [Active Admin](https://github.com/activeadmin/activeadmin/blob/master/CONTRIBUTING.md#1-where-do-i-go-from-here) [2] [Node.js](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-contributions) [3] [Ember.js](https://github.com/emberjs/ember.js/blob/master/CONTRIBUTING.md#pull-requests) + +### If you have a different process for small or "obvious" fixes, let them know. + +> Small contributions such as fixing spelling errors, where the content is small enough to not be considered intellectual property, can be submitted by a contributor as a patch, without a CLA. +> +>As a rule of thumb, changes are obvious fixes if they do not introduce any new functionality or creative thinking. As long as the change does not affect functionality, some likely examples include the following: +>* Spelling / grammar fixes +>* Typo correction, white space and formatting changes +>* Comment clean up +>* Bug fixes that change default return values or error codes stored in constants +>* Adding logging messages or debugging output +>* Changes to ‘metadata’ files like Gemfile, .gitignore, build scripts, etc. +>* Moving source files from one directory or package to another + +[source: [Chef](https://github.com/chef/chef/blob/master/CONTRIBUTING.md#chef-obvious-fix-policy)] **Need more inspiration?** [1] [Puppet](https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md#making-trivial-changes) + +# How to report a bug +### Explain security disclosures first! +At bare minimum, include this sentence: +> If you find a security vulnerability, do NOT open an issue. Email XXXX instead. + +If you don’t want to use your personal contact information, set up a “security@” email address. Larger projects might have more formal processes for disclosing security, including encrypted communication. (Disclosure: I am not a security expert.) + +> Any security issues should be submitted directly to security@travis-ci.org +> In order to determine whether you are dealing with a security issue, ask yourself these two questions: +> * Can I access something that's not mine, or something I shouldn't have access to? +> * Can I disable something for other people? +> +> If the answer to either of those two questions are "yes", then you're probably dealing with a security issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're unsure, just email us at security@travis-ci.org. + +[source: [Travis CI](https://github.com/travis-ci/travis-ci/blob/master/CONTRIBUTING.md)] **Need more inspiration?** [1] [Celery](https://github.com/celery/celery/blob/master/CONTRIBUTING.rst#security) [2] [Express.js](https://github.com/expressjs/express/blob/master/Security.md) + +### Tell your contributors how to file a bug report. +You can even include a template so people can just copy-paste (again, less work for you). + +> When filing an issue, make sure to answer these five questions: +> +> 1. What version of Go are you using (go version)? +> 2. What operating system and processor architecture are you using? +> 3. What did you do? +> 4. What did you expect to see? +> 5. What did you see instead? +> General questions should go to the golang-nuts mailing list instead of the issue tracker. The gophers there will answer or ask you to file an issue if you've tripped over a bug. + +[source: [Go](https://github.com/golang/go/blob/master/CONTRIBUTING.md#filing-issues)] **Need more inspiration?** [1] [Celery](https://github.com/celery/celery/blob/master/CONTRIBUTING.rst#other-bugs ) [2] [Atom](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#reporting-bugs) (includes template) + +# How to suggest a feature or enhancement +### If you have a particular roadmap, goals, or philosophy for development, share it here. +This information will give contributors context before they make suggestions that may not align with the project’s needs. + +> The Express philosophy is to provide small, robust tooling for HTTP servers, making it a great solution for single page applications, web sites, hybrids, or public HTTP APIs. +> +> Express does not force you to use any specific ORM or template engine. With support for over 14 template engines via Consolidate.js, you can quickly craft your perfect framework. + +[source: [Express](https://github.com/expressjs/express#philosophy)] **Need more inspiration?** [Active Admin](https://github.com/activeadmin/activeadmin#goals) + +### Explain your desired process for suggesting a feature. +If there is back-and-forth or signoff required, say so. Ask them to scope the feature, thinking through why it’s needed and how it might work. + +> If you find yourself wishing for a feature that doesn't exist in Elasticsearch, you are probably not alone. There are bound to be others out there with similar needs. Many of the features that Elasticsearch has today have been added because our users saw the need. Open an issue on our issues list on GitHub which describes the feature you would like to see, why you need it, and how it should work. + +[source: [Elasticsearch](https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#feature-requests)] **Need more inspiration?** [1] [Hoodie](https://github.com/hoodiehq/hoodie/blob/master/CONTRIBUTING.md#feature-requests) [2] [Ember.js](https://github.com/emberjs/ember.js/blob/master/CONTRIBUTING.md#requesting-a-feature) + +# Code review process +### Explain how a contribution gets accepted after it’s been submitted. +Who reviews it? Who needs to sign off before it’s accepted? When should a contributor expect to hear from you? How can contributors get commit access, if at all? + +> The core team looks at Pull Requests on a regular basis in a weekly triage meeting that we hold in a public Google Hangout. The hangout is announced in the weekly status updates that are sent to the puppet-dev list. Notes are posted to the Puppet Community community-triage repo and include a link to a YouTube recording of the hangout. +> After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity. + +[source: [Puppet](https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md#submitting-changes)] **Need more inspiration?** [1] [Meteor](https://meteor.hackpad.com/Responding-to-GitHub-Issues-SKE2u3tkSiH ) [2] [Express.js](https://github.com/expressjs/express/blob/master/Contributing.md#becoming-a-committer) + +# Community +If there are other channels you use besides GitHub to discuss contributions, mention them here. You can also list the author, maintainers, and/or contributors here, or set expectations for response time. + +> You can chat with the core team on https://gitter.im/cucumber/cucumber. We try to have office hours on Fridays. + +[source: [cucumber-ruby](https://github.com/cucumber/cucumber-ruby/blob/master/CONTRIBUTING.md#talking-with-other-devs)] **Need more inspiration?** + [1] [Chef](https://github.com/chef/chef/blob/master/CONTRIBUTING.md#-developer-office-hours) [2] [Cookiecutter](https://github.com/audreyr/cookiecutter#community) + +# BONUS: Code, commit message and labeling conventions +These sections are not necessary, but can help streamline the contributions you receive. + +### Explain your preferred style for code, if you have any. + +**Need inspiration?** [1] [Requirejs](http://requirejs.org/docs/contributing.html#codestyle) [2] [Elasticsearch](https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#contributing-to-the-elasticsearch-codebase) + +### Explain if you use any commit message conventions. + +**Need inspiration?** [1] [Angular](https://github.com/angular/material/blob/master/.github/CONTRIBUTING.md#submit) [2] [Node.js](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#step-3-commit) + +### Explain if you use any labeling conventions for issues. + +**Need inspiration?** [1] [StandardIssueLabels](https://github.com/wagenet/StandardIssueLabels#standardissuelabels) [2] [Atom](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#issue-and-pull-request-labels) diff --git a/LICENSE b/LICENSE new file mode 100644 index 00000000000..acd9d2a947d --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2019 Liyas Thomas + +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. diff --git a/README.md b/README.md new file mode 100644 index 00000000000..f46e6d1fd9a --- /dev/null +++ b/README.md @@ -0,0 +1,118 @@ +``` +When I wrote this, only God and I understood what I was doing. Now, only God knows. +``` +
+ Liyas Thomas +
+

Liyas Thomas

+ Built with ❤︎ by + liyasthomas and + contributors + +
+ +--- + +[![Build Status](https://travis-ci.org/liyasthomas/banner.svg?branch=master)](https://travis-ci.org/liyasthomas/banner) [![GitHub release](https://img.shields.io/github/release/liyasthomas/banner/all.svg)](https://github.com/liyasthomas/banner/releases/latest) [![repo size](https://img.shields.io/github/repo-size/liyasthomas/banner.svg)](https://github.com/liyasthomas/banner/archive/master.zip) [![license](https://img.shields.io/github/license/liyasthomas/banner.svg)](https://github.com/liyasthomas/banner/blob/master/LICENSE) [![contributions welcome](https://img.shields.io/badge/contributions-welcome-brightgreen.svg?style=flat)](https://github.com/liyasthomas/banner/issues) [![Website](https://img.shields.io/website-up-down-green-red/https/shields.io.svg?label=website)](https://liyas-thomas.firebaseapp.com) [![Donate](https://img.shields.io/badge/$-donate-ff69b4.svg)](https://www.paypal.me/liyascthomas) + +# banner Banner + +### 🚩 A simple and clean banner generator by [Liyas Thomas](https://github.com/liyasthomas) + +
+
+ banner + banner +
+
+ +### Features :sparkles: + +:heart: **Lightweight and minimal**: Crafted with minimalistic UI design + +:electric_plug: **Real-time demo**: WYSIWYG (what you see is what you get) banner editor + +:zap: **Make it your own**: Customize everything! + +:robot: **AI**: Generate combination colors for background and foreground + +:sparkles: **Choose custom colors**: Randomize or choose your own colors + +:rocket: **Save**: Download generated banner to disk + +--- + +## Demo + +[https://liyasthomas.github.io/banner](https://liyasthomas.github.io/banner) + +1. Give a heading +2. Customize everything! +3. Download banner + +You're done! + +--- + +## Built with + +* **[Chromium](https://github.com/chromium/chromium)** - Thanks for being so fast! +* HTML - For the web framework +* CSS - For styling components +* JavaScript - For magic! + +--- + +## Contributing + +Please read [CONTRIBUTING](CONTRIBUTING.md) for details on our [CODE OF CONDUCT](CODE_OF_CONDUCT.md), and the process for submitting pull requests to us. + +--- + +## Continuous Integration + +We use [Travis CI](https://travis-ci.com) for continuous integration. Check out our [Travis CI Status](https://travis-ci.org/liyasthomas/banner). + +--- + +## Versioning + +This project is developed by [Liyas Thomas](https://github.com/liyasthomas) using the [Semantic Versioning specification](https://semver.org). For the versions available, see the [releases on this repository](https://github.com/liyasthomas/banner/releases). + +--- + +## Change log + +See the [CHANGELOG](CHANGELOG.md) file for details. + +--- + +## Authors + +### Lead Developers +* [**Liyas Thomas**](https://github.com/liyasthomas) - *Author* + +### Testing and Debugging +* [Liyas Thomas](https://github.com/liyasthomas) + +### Contributors +* [Liyas Thomas](https://github.com/liyasthomas) + +### Thanks +* [Dribbble](https://dribbble.com) + +See the list of [contributors](https://github.com/liyasthomas/banner/graphs/contributors) who participated in this project. + +--- + +## License + +This project is licensed under the [MIT License](https://opensource.org/licenses/MIT) - see the [LICENSE](LICENSE) file for details. + +--- + +## Acknowledgments + +* Hat tip to anyone who's code was used +* Inspirations: + * [Dribbble](https://dribbble.com) \ No newline at end of file diff --git a/favicon.ico b/favicon.ico new file mode 100644 index 00000000000..b089a45a253 Binary files /dev/null and b/favicon.ico differ diff --git a/icons/github.svg b/icons/github.svg new file mode 100644 index 00000000000..33cb29171ab --- /dev/null +++ b/icons/github.svg @@ -0,0 +1,62 @@ + + + +image/svg+xml + + + + \ No newline at end of file diff --git a/icons/icon-144x144.png b/icons/icon-144x144.png new file mode 100644 index 00000000000..452a0a9e689 Binary files /dev/null and b/icons/icon-144x144.png differ diff --git a/icons/icon-192x192.png b/icons/icon-192x192.png new file mode 100644 index 00000000000..b6d4e22dad8 Binary files /dev/null and b/icons/icon-192x192.png differ diff --git a/icons/icon-48x48.png b/icons/icon-48x48.png new file mode 100644 index 00000000000..d90705f891d Binary files /dev/null and b/icons/icon-48x48.png differ diff --git a/icons/icon-512x512.png b/icons/icon-512x512.png new file mode 100644 index 00000000000..65181484db8 Binary files /dev/null and b/icons/icon-512x512.png differ diff --git a/icons/icon-72x72.png b/icons/icon-72x72.png new file mode 100644 index 00000000000..45d75562473 Binary files /dev/null and b/icons/icon-72x72.png differ diff --git a/icons/icon-96x96.png b/icons/icon-96x96.png new file mode 100644 index 00000000000..caf7e48f162 Binary files /dev/null and b/icons/icon-96x96.png differ diff --git a/icons/logo.svg b/icons/logo.svg new file mode 100644 index 00000000000..08db68a5a77 --- /dev/null +++ b/icons/logo.svg @@ -0,0 +1,54 @@ + +image/svg+xml + + \ No newline at end of file diff --git a/icons/pwalogo.svg b/icons/pwalogo.svg new file mode 100644 index 00000000000..1ab6a2d5b61 --- /dev/null +++ b/icons/pwalogo.svg @@ -0,0 +1,9 @@ + + + + + + + + + diff --git a/icons/screely.png b/icons/screely.png new file mode 100644 index 00000000000..4b124fc7d6c Binary files /dev/null and b/icons/screely.png differ diff --git a/icons/screely2.png b/icons/screely2.png new file mode 100644 index 00000000000..d1bbe578c34 Binary files /dev/null and b/icons/screely2.png differ diff --git a/index.html b/index.html new file mode 100644 index 00000000000..96a1e75fbf0 --- /dev/null +++ b/index.html @@ -0,0 +1,259 @@ + + + + + + + + Postwoman - API request builder + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+ +

Postwoman

+ +

API request builder

+
+
+
+ Request + +
+
+ Authentication + + +
+
+ Parameters +
    +
  1. + + +
    2. +
  2. + + +
    3. +
  3. + + +
    4. +
+ + +
+
+ Request Body +
    +
  1. + + +
    2. +
  2. + + +
    3. +
  3. + + +
    4. +
+ + +
+
+ Response + + + +
+ +
+ + + + + diff --git a/manifest.json b/manifest.json new file mode 100644 index 00000000000..5ca4fb0bfb8 --- /dev/null +++ b/manifest.json @@ -0,0 +1,41 @@ +{ + "name": "Postwoman", + "short_name": "Postwoman", + "description": "API request builder", + "icons": [ + { + "src": "icons/icon-48x48.png", + "sizes": "48x48", + "type": "image/png" + }, + { + "src": "icons/icon-72x72.png", + "sizes": "72x72", + "type": "image/png" + }, + { + "src": "icons/icon-96x96.png", + "sizes": "96x96", + "type": "image/png" + }, + { + "src": "icons/icon-144x144.png", + "sizes": "144x144", + "type": "image/png" + }, + { + "src": "icons/icon-192x192.png", + "sizes": "192x192", + "type": "image/png" + }, + { + "src": "icons/icon-512x512.png", + "sizes": "512x512", + "type": "image/png" + } + ], + "start_url": "/", + "display": "standalone", + "theme_color": "#121212", + "background_color": "#121212" +} diff --git a/package.json b/package.json new file mode 100644 index 00000000000..ccaff35ea2d --- /dev/null +++ b/package.json @@ -0,0 +1,16 @@ +{ + "name": "Banner", + "repository": { + "type": "git", + "url": "https://github.com/liyasthomas/banner.git" + }, + "description": "A simple and clean banner generator", + "author": "liyasthomas", + "version": "0.1.9", + "devDependencies": { + "jshint": "^2.10.2" + }, + "scripts": { + "test": "jshint travis.js" + } +} diff --git a/script.js b/script.js new file mode 100644 index 00000000000..059dff780dc --- /dev/null +++ b/script.js @@ -0,0 +1,116 @@ +const parseHeaders = xhr => { + const headers = xhr.getAllResponseHeaders().trim().split(/[\r\n]+/) + const headerMap = {} + headers.forEach(line => { + const parts = line.split(': ') + const header = parts.shift().toLowerCase() + const value = parts.join(': ') + headerMap[header] = value + }) + return headerMap +} +const app = new Vue({ + el: '#app', + data: { + method: 'GET', + url: 'https://yesno.wtf', + auth: 'None', + path: '/api', + httpUser: '', + httpPassword: '', + params: [], + bodyParams: [], + contentType: 'application/json', + response: { + status: '', + headers: '', + body: '' + } + }, + computed: { + rawRequestBody() { + const { + bodyParams + } = this + if (this.contentType === 'application/json') { + try { + const obj = JSON.parse(`{${bodyParams.filter(({ key }) => !!key).map(({ key, value }) => ` + "${key}": "${value}" + `).join()}}`) + return JSON.stringify(obj) + } catch (ex) { + return 'invalid' + } + } else { + return bodyParams + .filter(({ + key + }) => !!key) + .map(({ + key, + value + }) => `${key}=${encodeURIComponent(value)}`).join('&') + } + }, + queryString() { + const result = this.params + .filter(({ + key + }) => !!key) + .map(({ + key, + value + }) => `${key}=${encodeURIComponent(value)}`).join('&') + return result == '' ? '' : `?${result}` + } + }, + methods: { + sendRequest() { + this.$refs.response.scrollIntoView({ + behavior: 'smooth' + }) + this.response.status = 'Loading...' + const xhr = new XMLHttpRequest() + const user = this.auth === 'Basic' ? this.httpUser : null + const pswd = this.auth === 'Basic' ? this.httpPassword : null + xhr.open(this.method, this.url + this.path + this.queryString, true, user, pswd) + if (this.method === 'POST' || this.method === 'PUT') { + const requestBody = this.rawRequestBody + xhr.setRequestHeader('Content-Length', requestBody.length) + xhr.setRequestHeader('Content-Type', `${this.contentType}; charset=utf-8`) + xhr.send(requestBody) + } else { + xhr.send() + } + xhr.onload = e => { + this.response.status = xhr.status + const headers = this.response.headers = parseHeaders(xhr) + if ((headers['content-type'] || '').startsWith('application/json')) { + this.response.body = JSON.stringify(JSON.parse(xhr.responseText), null, 2) + } else { + this.response.body = xhr.responseText + } + } + }, + addRequestParam() { + this.params.push({ + key: '', + value: '' + }) + return false + }, + removeRequestParam(index) { + this.params.splice(index, 1) + }, + addRequestBodyParam() { + this.bodyParams.push({ + key: '', + value: '' + }) + return false + }, + removeRequestBodyParam(index) { + this.bodyParams.splice(index, 1) + } + } +}) diff --git a/style.css b/style.css new file mode 100644 index 00000000000..0c37149eaa5 --- /dev/null +++ b/style.css @@ -0,0 +1,185 @@ +:root { + --bg-color: #121212; + --fg-color: #fff; + --ac-color: #F8E81C; +} + +* { + box-sizing: border-box; + outline: 0; + border: 0; + font-family: 'Poppins', 'Roboto', 'Noto', sans-serif; +} + +::selection { + background-color: var(--ac-color); + color: var(--bg-color); +} + +@keyframes fadein { + from { + opacity: 0; + } + + to { + opacity: 1; + } +} + +a { + display: inline-flex; + color: inherit; + text-decoration: none; + font-weight: 700; +} + +body { + padding: 0; + background-color: var(--bg-color); + color: var(--fg-color); + font-weight: 500; + font-size: 16px; + line-height: 1.5; + animation: fadein .2s; + -webkit-tap-highlight-color: transparent; + -webkit-touch-callout: none; + -webkit-user-select: none; + user-select: none; +} + +h1, +h2, +h3 { + margin: 0; + font-weight: 700; +} + +header, +footer { + display: flex; + padding: 16px; + width: 100%; + align-items: center; + justify-content: space-between; +} + +.logo { + color: var(--ac-color); +} + +main { + margin: 0 auto; + max-width: 1200px; +} + +button { + margin: 4px; + padding: 8px 16px; + border-radius: 4px; + background-color: var(--ac-color); + color: var(--bg-color); + font-weight: 700; + font-size: 16px; + cursor: pointer; +} + +fieldset { + margin: 16px 0; + border: 1px solid var(--fg-color); + border-radius: 4px; +} + +legend { + color: #57b5f9; + font-weight: 700; +} + +fieldset textarea { + resize: vertical; +} + +fieldset > section, +fieldset > table { + margin: .6em 0; +} + +fieldset > table { + width: 100%; + border: 1px solid #ddd; + border-style: collaped; +} + +fieldset table td input { + box-sizing: border-box; + width: 100%; +} + +fieldset.request { + border-color: #57b5f9; +} + +fieldset.request legend { + color: #57b5f9; +} + +fieldset.authentication { + border-color: #57b5f9; +} + +fieldset.authentication legend { + color: #57b5f9; +} + +fieldset.response { + border-color: #C198FB; +} + +fieldset.response legend { + color: #C198FB; +} + +select, +input, +option, +textarea { + background-color: #000; + border-radius: 4px; + font-size: 18px; + padding: 8px 16px; + color: var(--fg-color); + margin: 4px; + font-family: monospace; + font-weight: 700; + width: calc(100% - 8px); +} + +label { + padding: 4px; +} + +ul, +ol { + margin: 8px 0 0; + padding: 0; + list-style-type: none; + display: flex; +} + +ul li, +ol li { + display: inline-flex; + flex-direction: column; + flex-grow: 1; +} + +@media (max-width: 720px) { + + ul, + ol { + flex-direction: column; + } + + ul li, + ol li { + display: flex; + } diff --git a/sw.js b/sw.js new file mode 100644 index 00000000000..d788f9e48eb --- /dev/null +++ b/sw.js @@ -0,0 +1,150 @@ +importScripts('https://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-sw.js'); +if (workbox) { + console.log(`Yay! Workbox is loaded 🎉`); +} else { + console.log(`Boo! Workbox didn't load 😬`); +} +workbox.routing.registerRoute( + new RegExp('.*\.js'), + new workbox.strategies.NetworkFirst() +); +workbox.routing.registerRoute( + // Cache CSS files. + /\.css$/, + // Use cache but update in the background. + new workbox.strategies.StaleWhileRevalidate({ + // Use a custom cache name. + cacheName: 'css-cache', + }) +); +workbox.routing.registerRoute( + // Cache image files. + /\.(?:png|jpg|jpeg|svg|gif)$/, + // Use the cache if it's available. + new workbox.strategies.CacheFirst({ + // Use a custom cache name. + cacheName: 'image-cache', + plugins: [ + new workbox.expiration.Plugin({ + // Cache only 20 images. + maxEntries: 20, + // Cache for a maximum of a week. + maxAgeSeconds: 7 * 24 * 60 * 60, + }) + ], + }) +); +workbox.precaching.precacheAndRoute([ + '/index.css', + '/index.js', + '/manage.js', + { + url: '/index.html', + revision: '383676' + }, +]); +var CACHE_VERSION = 1; +var CURRENT_CACHES = { + prefetch: 'prefetch-cache-v' + CACHE_VERSION +}; +self.addEventListener('install', function (event) { + var now = Date.now(); + var urlsToPrefetch = [ + 'index.html', + 'manage.html' + ]; + // All of these logging statements should be visible via the "Inspect" interface + // for the relevant SW accessed via chrome://serviceworker-internals + console.log('Handling install event. Resources to prefetch:', urlsToPrefetch); + event.waitUntil( + caches.open(CURRENT_CACHES.prefetch).then(function (cache) { + var cachePromises = urlsToPrefetch.map(function (urlToPrefetch) { + // This constructs a new URL object using the service worker's script location as the base + // for relative URLs. + var url = new URL(urlToPrefetch, location.href); + // Append a cache-bust=TIMESTAMP URL parameter to each URL's query string. + // This is particularly important when precaching resources that are later used in the + // fetch handler as responses directly, without consulting the network (i.e. cache-first). + // If we were to get back a response from the HTTP browser cache for this precaching request + // then that stale response would be used indefinitely, or at least until the next time + // the service worker script changes triggering the install flow. + url.search += (url.search ? '&' : '?') + 'cache-bust=' + now; + // It's very important to use {mode: 'no-cors'} if there is any chance that + // the resources being fetched are served off of a server that doesn't support + // CORS (http://en.wikipedia.org/wiki/Cross-origin_resource_sharing). + // In this example, www.chromium.org doesn't support CORS, and the fetch() + // would fail if the default mode of 'cors' was used for the fetch() request. + // The drawback of hardcoding {mode: 'no-cors'} is that the response from all + // cross-origin hosts will always be opaque + // (https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#cross-origin-resources) + // and it is not possible to determine whether an opaque response represents a success or failure + // (https://github.com/whatwg/fetch/issues/14). + var request = new Request(url, { + mode: 'no-cors' + }); + return fetch(request).then(function (response) { + if (response.status >= 400) { + throw new Error('request for ' + urlToPrefetch + + ' failed with status ' + response.statusText); + } + // Use the original URL without the cache-busting parameter as the key for cache.put(). + return cache.put(urlToPrefetch, response); + }).catch(function (error) { + console.error('Not caching ' + urlToPrefetch + ' due to ' + error); + }); + }); + return Promise.all(cachePromises).then(function () { + console.log('Pre-fetching complete.'); + }); + }).catch(function (error) { + console.error('Pre-fetching failed:', error); + }) + ); +}); +self.addEventListener('activate', function (event) { + // Delete all caches that aren't named in CURRENT_CACHES. + // While there is only one cache in this example, the same logic will handle the case where + // there are multiple versioned caches. + var expectedCacheNames = Object.keys(CURRENT_CACHES).map(function (key) { + return CURRENT_CACHES[key]; + }); + event.waitUntil( + caches.keys().then(function (cacheNames) { + return Promise.all( + cacheNames.map(function (cacheName) { + if (expectedCacheNames.indexOf(cacheName) === -1) { + // If this cache name isn't present in the array of "expected" cache names, then delete it. + console.log('Deleting out of date cache:', cacheName); + return caches.delete(cacheName); + } + }) + ); + }) + ); +}); +self.addEventListener('fetch', function (event) { + console.log('Handling fetch event for', event.request.url); + event.respondWith( + // caches.match() will look for a cache entry in all of the caches available to the service worker. + // It's an alternative to first opening a specific named cache and then matching on that. + caches.match(event.request).then(function (response) { + if (response) { + console.log('Found response in cache:', response); + return response; + } + console.log('No response found in cache. About to fetch from network...'); + // event.request will always have the proper mode set ('cors, 'no-cors', etc.) so we don't + // have to hardcode 'no-cors' like we do when fetch()ing in the install handler. + return fetch(event.request).then(function (response) { + console.log('Response from network is:', response); + return response; + }).catch(function (error) { + // This catch() will handle exceptions thrown from the fetch() operation. + // Note that a HTTP error response (e.g. 404) will NOT trigger an exception. + // It will return a normal response object that has the appropriate error code set. + console.error('Fetching failed:', error); + throw error; + }); + }) + ); +}); diff --git a/travis.js b/travis.js new file mode 100644 index 00000000000..4b886b3dd9c --- /dev/null +++ b/travis.js @@ -0,0 +1,8 @@ +var http = require('http'); +http.createServer(function (req, res) { + res.writeHead(200, { + 'Content-Type': 'text/plain' + }); + res.end('Travis!\n'); // build should pass now! +}).listen(1337, '127.0.0.1'); +console.log('Server running at http://127.0.0.1:1337/');