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

Quick​Edit

by gamcoh ALL

a Sublime text plugin like brackets quick edit

Labels Html, Css, php, Quick, Edition

Details

Installs

  • Total 948
  • Win 633
  • Mac 215
  • Linux 100
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 Mar 5
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 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