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

Quick​Edit

by gamcoh ST2/ST3

a Sublime text plugin like brackets quick edit

Labels Html, Css, php, Quick, Edition

Details

Installs

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

Readme

Source
raw.​githubusercontent.​com

QuickEdit

This is a Sublime Text package that allows you to edit css code directly into html code using the tag class names, like QuickEdit on the Brackets IDE.

Since the 2nd version, the plugin also allows you to use it with php variables and functions

Installation

To install this plugin, you have two options:

  1. If you have Package Control installed, simply search for QuickEdit to install.

  2. Clone source code to Sublime Text packages folder. (not recommended)

Usage

super + alt + h near a class name in order to open a frame with the corresponding css styles into it

QuickEdit

Settings

  • You can disable the errors report by changing to false the show_errors entry in the QuickEdit settings
  • You can change the font of the report by changing the font_face attribut in your user settings

Challenges

  • Make it work for IDs too
  • Show errors in the phantom (Could not load the file, Could not find the file, Could not find any css style for this class, id, or other)
  • Many files are included implicitly, we need to find some kind of autoload function that check those files too, maybe by including all the css files that are in the project, or checking if there is a header file somewhere in the project
  • Know the line where we found the css styles even in another file
  • Do not include the comment css styles