Features
|
Site Manager extension
|
![]() ![]()
![]()
|
Launchy integration
|
Launchy integration allows to do tasks that Nvu does not implement (or poorly); I personnally use that to:
- edit code (html, xml, php, JavaScript...) with APIs and code folding using ConTEXT, SciTE or Eclipse
- reformat HTML pages in xHTML-strict using htmlTidy
- quickly filter/resize with ImageMagick or XnView
- properly publish my pages and scripts with FileZilla or gFTP
Installation
NsmConText relies on Launchy (both JAR included in the same XPI); so if you already have Launchy on your Nvu, you'll have to uninstall it first (note that you can keep your launchy.xml configuration file).
As far as I know, Nvu doesn't properly support localized extensions; it might be possible with future versions of Nvu, but for now, you have to choose a language-specific version of this extension.
To install on Nvu:
- choose your language above
- save the extension on your hard drive (save link target as...)
- launch Nvu
- Tools > Extensions > install
- close and relaunch Nvu
Do not install this extension on Firefox! If you're looking for such an extension for Firefox, it's called Launchy.
Changelog
- version 0.3.1 (2005-12-05)
- bug fix (the "add an application" button now works)
- version 0.3.0 (2005-11-29)
- all features related to the current page (edit / reformat) and ASP/JSP/PHP support have been moved to HandCoder
- compatible with HandCoder 0.3.0
- version 0.2.5 (2005-09-18)
- Launchy configuration tools
- Tidy support to auto-indent and reformat HTML source
- experimental ASP/JSP/PHP support
- HTTP preview of the current page
- keyboard shortcuts to preview (F5), edit (F6) or reformat (F7) current page
- ability to pass arguments to default editors
- version 0.2.2 (2005-07-25)
- fixed a bug in NsmConText options dialog
- version 0.2.1 (2005-07-12)
- "Editor" button to edit current HTML source with external editors
- Launchy 4.0.0 included
- version 0.2.0 (2005-06-02)
- context menus in the main editor window (for links and images)
- Launchy 3.9.0 included
- version 0.1.1 (2005-03-05)
- first localization (some bugs remain, see above)
- FTP client support for distant site folders
- better action filter according to the file type
- HTTP preview of html pages and php/asp/jsp scripts
- Launchy 3.9.0 included
- version 0.1.0 (2005-02-25)
- very first XUL extension!!!
- option dialog to specify default editors (code / images)
- Launchy 3.9.0 included
Roadmap
This is what needs to be done for the 1.0 version:
- user-defined file filters
- best possible PHP/ASP/JSP support
- update link refs when moving a file in the Site Manager
- DW-style FTP sync
- Launchy configuration utility
FAQ
- Do Launchy & NsmConText work under Linux or MacOS?
-
Yes. On Windows there is a bonus: more than 60 applications are automatically detected (register-based info).
- Does NsmConText work with distant files?
- Not yet. I'd recommand anyway to work on a local site, then publish it on the server with an FTP client like FileZilla.
- I'm used to [MyFavoriteEditor] for PHP (or ASP, JSP, CSS, JS...) but I don't know how to add an editor to Launchy.
-
Best: configure a launchy.xml file in your chrome directory.
Quick and dirty: open NsmConText option box and paste [MyFavoriteEditor]'s path in the "code editor" field.
A double-clic on the PHP file in the site manager will open [MyFavoriteEditor], but [MyFavoriteEditor] will not appear in the context menu.
Launchy configuration
You'll have to create a 'launchy.xml' file in your profile 'chrome' directory; read this for more info.
For instance, to use SciTE as text editor:
<?xml version="1.0" encoding="UTF-8"?>
<configurations xmlns="http://launchy.mozdev.org/configurations">
<application>
<label>Scintilla Text Editor</label>
<type>7</type>
<command>C:\Program Files\SciTE\SciTE.exe</command>
<arguments></arguments>
</application>
</configurations>
File types in launchy.xml :
- Web Browsers
- Mail clients
- Media clients
- FTP clients
- Download Managers
- File Explorers
- Editors
- Image Viewers
In NsmConText, types 2 and 5 are ignored. Note that I think Launchy uses MIME type to show the corresponding application type, whereas NsmConText uses the Site Manager file filter (i.e. the file's extension).
Note also that NsmConText only allows to edit local files (though it is able to show distant files). This should be solved with the upcoming "FTP sync" feature.









last update: