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 959
  • Win 644
  • Mac 215
  • Linux 100
Mar 9 Mar 8 Mar 7 Mar 6 Mar 5 Mar 4 Mar 3 Mar 2 Mar 1 Feb 28 Feb 27 Feb 26 Feb 25 Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24
Windows 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 0 0 0 0 0 0 0 0
Mac 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
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