Adds DRYML markers viewable with FireMarker (a Firefox/Firebug extension)
Dryml FireMarker is a tool composed by 2 components:
- "FireMarker": a Firebug extension that graphically shows special markers embedded in any HTML page.
- "dryml-firemarker": a gem to use with Dryml/Hobo that simply marks (with FireMarker markers), specific parts of HTML with their related metainfo.
1. FireMarker (FF extension)
FireMarker is an extension for Firebug that graphically shows special markers embedded in any HTML page. Its main benefit is that you can easily read the metainfo related to any specific part of the HTML by just hovering the mouse on the page-item. It also adds a few interactive features to Firebug and an inline file viewer/editor.
- Recent Firefox >= 3.6
- Recent Firebug
Download the latest compiled extension from:
Install in Firefox with Tools > Add-ons > Install Add-on From File...
2. Dryml FireMarker (gem)
Dryml FireMarker is a ruby gem, so you can istall it as usual:
$ [sudo] gem install dryml-firemarker
Since Dryml is implemented in 3 different ways in Hobo 1.0.x, Dryml 1.1.x and Dryml >= 1.3, you must setup your app consistently with the dryml version it uses.
2.1 Hobo 1.0.x and Hobo/Dryml 1.1.x Setup
In an initializer file:
DRYML_METAINFO = RAILS_ENV == 'development' require 'dryml<version>-firemarker'
<version> is '10' for Hobo 1.0.x or '11' for Hobo/Dryml 1.1.x
You must set the
DRYML_METAINFO in order to include the metainfo in the page.
2.2. Hobo/Dryml >= 1.3 Setup
Add just one line to the
gem 'dryml-firemarker', :require => 'dryml13-firemarker', :group => :development
There are no bugs to fix in the Hobo/Dryml >= 1.3.0 version, so you don't need to set the
DRYML_METAINFO in order to include the metainfo in the page. You can add or skip the metainfo by just adding or commenting out the previous statement (and restart the app).
With an initializer file you can ignore the file from version control, in order to avoid to impose its use to anybody else in your team.
If your app uses the
rapid taglib, the gem for the 1.0.x and 1.1.x should be loaded in all environments, since it fixes a few consolidated bugs coded in that taglib. Besides, you can safely load it in all environments, because - by default - it will add the matainfo to the page only in development mode, and will keep the fixes consistent in all environments.
There is no clean way to have a local only solution in Rails 3 when you changes the Gemfile, since you have to list all the gems in the Gemfile. If you are working with a team and don't want to impose your Gemfile to the rest of the team and if you are using git, you can use the
git update-index --assume-unchanged Gemfile command after your change to the Gemfile (and eventually the Gemfile.lock, and git will not bother you as long as you will not change the file again.
# wrap the loading in the code if ENV["DRYML_METAINFO"] ... end # rails 2 $ export DRYML_METAINFO=true; script/server -p 3001 # rails 3 $ export DRYML_METAINFO=true; rails s -p 3001
In the very rare case your application needs to override one of
page-scripts helpers/tags, you must take into account that the tags that your application uses are defined in the
dryml-firemarker.dryml taglib included in this gem (and not the same tags defined in the regular rapid taglib). The current implementation does not support that overriding, unless you also manually load the tag
<include plugin="dryml-firemarker"\> right after the rapid tag inclusion in the application.dryml file.
- Install and setup the FF Extension component and the gem
- Start/restart the app
- Render any page in Firefox
- Open Firebug (F12)
- Select the "HTML" tab
- Uncheck "Show Comments" in the HTML tab menu
- Select the "Markers" tab in the Firebug HTML side panel
- Check "dryml" option in the Markers tab menu
Select any node in the HTML panel or click on the Firebug's inspect icon and hover the mouse on any part of the page, then click on it to select the node: the Markers panel will be populated with all the markers that include that specific node. They are listed from close to far. The closest are the most specific markers that wrap the selected node: e.g. an <a> tag that produces a specific link; the farest are the most general: e.g. a <page> tag that wraps the whole page (including the <a> tag listed at the beginning).
Hovering up and down in the Markers list may be useful to understand what specific dryml statement is creating the specific highlighted part in the page and HTML source, and eventually helps to chose what to override. (Notice that invisible page-parts are highlighted only in the source and have a dimmed color.)
You can open any dryml file (at the right line) by clicking on the path listed in the marker's table. You can close it by clicking on it again. If you hold the "Ctrl" or the "Alt" key while you click on a path, you will open the file in a new FF tab instead: that might be useful when you need to explore a large file.
The green paths (with an ending "+") are editable because they are application files, while the blue paths are just viewable because they are libraries or auto-generated files that doesn't make sense to edit. Note: if you installed hobo as a pplugin (version
If you want to save an edited file, just close it and FireMarker will ask if you want to save it.
Add "edit in external editor" feature to allow to open the dryml file in your preferred IDE.
Copyright (c) 2011 by Barquin International
Designed and developed by Domizio Demichelis
See LICENSE for details.