ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Phalcon​PHP Completions

by james2doyle ST2/ST3

A set of completions for the Phalcon PHP Framework made for Sublime Text 3

Labels phalcon, php

Details

Installs

  • Total 12K
  • Win 8K
  • OS X 2K
  • Linux 3K
Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30 Mar 29 Mar 28 Mar 27 Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8 Mar 7 Mar 6
Windows 4 1 7 1 4 5 2 3 4 6 4 8 5 2 5 4 7 5 3 2 9 3 9 5 8 9 5 4 4 10 5 7 3 5 3 5 4 5 8 5 3 5 9 7 2 4
OS X 0 1 0 0 1 0 0 0 3 1 0 0 1 0 0 0 0 1 0 0 1 0 0 1 1 1 0 0 2 1 1 0 0 1 1 0 0 2 4 0 1 0 1 0 2 1
Linux 3 0 1 1 0 0 1 0 1 1 1 2 0 0 2 0 3 0 2 0 0 2 1 1 0 2 0 1 3 2 2 1 1 2 3 1 3 0 3 4 1 3 1 2 2 5

Readme

Source
raw.​githubusercontent.​com

phalconphp-completions

A ton of completions for Phalcon PHP 1.3.*. There are 414 total right now. This is pretty much a copy-paste from my sublime-node-snippets repo.

testing example

Installing

Drop this folder in your Sublime Text packages directory.

Package Control

Just look for phalconphp-completions on Package Control. It is called “Node Completions” on the site, but comes up as “phalconphp-completions”.

Manual

  • Open the Commands Palette (command+shift+p)
  • Package Control: Add Repository
  • Past in this repos URL
  • Press Enter
  • Open the palette again
  • press enter on “phalconphp-completions”
  • watch it install

Using

Pressing \ (backslash) or : will end the snippet lookup.

You will have better results if you pretend the slashes and colons aren't needed. So if you are looking for Phalcon\Text::increment, you would type phalcontextincrement and you would see the results coming up.

See the GIF above!

Building

I went to each page of the node docs, and copied the functions. Then I wrote a converter to take each function and convert it to a snippet.

For Example, this line:

Phalcon\Text::endsWith($str, $end, $ignoreCase)

Is going to get converted to:

Phalcon\\Text::endsWith(\\$${1:str}, \\$${2:end}, \\$${3:ignoreCase});${0}

sources.txt

This file is cool. It is just a line-by-line output of the Phalcon docs functions. This is the file that is raked over to generate the snippets.

Running The Build

Just run node build.js and it will rake the sources.txt file and then write the new snippet in the snippets folder.

Everything before the first ( will be used as the filename.

Adding New Snippets

Here is how I quickly got all these snippets. First I went to the docs for the class, and I looked to see what the code examples were wrapped in.

For the all the docs pages, the methods and properties are show in a p.method-signature element. So to quickly get the list, I ran the following code:

Array.prototype.slice.call(document.querySelectorAll(".method-signature"), 0).map(function(item){
  return item.textContent.trim();
}).join("\n");

Then copied the output, added the class in front (replacing the type info), and pasted it in the sources.txt file. Done!

Contributing

Just add (or edit) a line in the source file. Then run node build.js to generate the new snippets.

License

The MIT License

Copyright © 2015 James Doyle james2doyle@gmail.com

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.