Menu

Productivity boosting requests and questions.

2008-05-04
2012-11-13
  • Nobody/Anonymous

    Hi Don,

    First I'd like to point out that Scintilla has been updated to 1.76 with "minor bug fixes"...might be a drop-in replacement.

    Second, what flavor of RegEx does NP++ use in the find/replace? I tried a lot of simple expressions that didn't work at all. (eg. ^.*$ acts lazy by only matching the first EOL assertion, and the lazy version (^.*?$) doesn't work at all) is there a switch for enabling multiline RegEx?

    Finally, I'd like to see if some features can or will be implemented:

    1. HTML Tag autoclose for self-closed tags like <input />, <br />, <img />
      - it should insert " />" when "/" or ">" is typed outside of attribute/value entry for a configurable taglist
      - an option to automatically close the last unclosed tag when "</" is typed in HTML mode (like dreamweaver)
        this is sometimes actually more useful than tag autoclose.
      - i have asked the authors of TextFX and XML Tools if this would be possible to implement also

    2. Dynamic highlight/style matching HTML tag - this is too useful not to have and i miss it a lot when moving from SynWeb based editors (http://flatdev.ovh.org/) to Scnitilla editors.
      - when cursor is placed inside a tag, it should highlight/style the matching tagname (without braces)
        ..without physically going to the match...which i think XML Tools does now, and it is not dynamic,
        but requires a keyboard shortcut....and has some quirkiness.

    3. Dynamic (as you type) API code hinting (mostly for HTML/CSS tags/properties/values)
    4. Optional color picker and file selection pop-ups for CSS's url() and HTML's href, src...maybe other attributes.
    5. Color values styled with a background/foreground of the hex color they represent?
       (this is a dream more than an actual request)

    NP++ is very impressive, and i wish i could use it for everything. But the need for keyboard shortcuts to access some useful features is probably the main reason i dont use something like VI in the first place. If #1, #2, and #3 could be implemented it would go a long way to making this a perfect markup editor, for now i have to resort to dev-PHP or Scriptly, neither of which cuts it for non-markup, nor has the breadth of features of NP++, so i have to switch back and forth :(.

    please explain if each request is attainable (if not, why?), and if it may be slated for future versions, i would love to see these make it in (sooner rather than later or never :)

    keep up the great work,
    Leon

     
    • Nobody/Anonymous

      it seems someone also has a requested my #3 quite accurately here:
      http://sourceforge.net/forum/forum.php?thread_id=2021132&forum_id=331753

      in HTML mode:
      1. show taglist after <,
      2. after a tag is selected from list:
        - 1. insert tagname, add a space, and place cursor after space, and display applicable attribute list
        - 2. or complete the tag with ">", add a closing tag, and place the cursor after opening tag
        - 3. or if self-closed tag, autoclose but keep cursor inside and display attribute list
        - 4. or in case of other like <br />, just close it, place cursor after.
      3. after an attribute is selected, place attribute name, and add =", then display applicable value list (if exists).
      4. when value is selected, insert value name, adding a closing "
      5. if user then types a space pop-up attribute list again. this repeats till user enters / or > instead of a space, which closes tag and places cursor after opening tag.

      ..all hint lists should autofilter as you type and autocomplete on tab or enter.

      ...something to that effect maybe with ability to configure behavior priority for specific tags (depeding on user coding style)

      would be awesome to see this.
      Leon