weathermap

Subversion Repositories:

[/] [docs/] [pages/] [editor.html] - Diff between revs 1 and 85

Rev 1 Rev 85

Line 6... Line 6...

<link rel="stylesheet" type="text/css" media="screen" href="weathermap.css" /> <link rel="stylesheet" type="text/css" media="screen" href="weathermap.css" />

<meta name="generator" content= <meta name="generator" content=

"HTML Tidy for Mac OS X (vers 12 April 2006), see www.w3.org" /> "HTML Tidy for Mac OS X (vers 12 April 2006), see www.w3.org" />

<title>PHP Weathermap <title>PHP Weathermap

v0.91 v0.97a

- Editor</title> - Editor</title>

<style type="text/css" media="print"> <style type="text/css" media="print">

/*<![CDATA[*/ /*<![CDATA[*/

body { font-size: 12pt; } body { font-size: 12pt; }

a { color: black; text-decoration: underline; font-weight: normal;} a { color: black; text-decoration: underline; font-weight: normal;}

Line 38... Line 38...

</ul> </ul>

</div> </div>

<div id="header"> <div id="header">

<h1>PHP Weathermap <h1>PHP Weathermap

v0.91 v0.97a

</h1> </h1>

<h4>Copyright © 2005-2007 Howard Jones, <tt><a <h4>Copyright © 2005-2010 Howard Jones, <tt><a

href="mailto:howie@thingy.com">howie@thingy.com</a></tt>. (<a href="mailto:howie@thingy.com">howie@thingy.com</a></tt>. (<a

href="http://www.network-weathermap.com/">Website</a>)</h4> href="http://www.network-weathermap.com/">Website</a>)</h4>

</div> </div>

Line 53... Line 53...

<p class="notebox"><b>Note:</b> <p class="notebox"><b>Note:</b>

This section is basically unaltered from the v0.7 manual. The editor This section is basically unaltered from the v0.7 manual. The editor

hasn't really changed since then, except to fix some bugs, and work hasn't really changed since then, except to fix some bugs, and work

with the new config directives - that is to say, it won't edit them, but with the new config directives - that is to say, it won't edit them, but

nor will it remove/damage them. It's still true to say that the editor is nor will it remove/damage them. It's still true to say that the editor is

the easiest way to initially lay out your map, and pick your TARGETs if you use Cacti, but after that, some hand-editing will help with cosmetics. the easiest way to initially lay out your map, and pick your <a href="config-reference.html#LINK_TARGET">TARGETs</a> if you use Cacti, but after that, some hand-editing will help with cosmetics.

</p> </p>

<p>New in version 0.7, there is a partially-complete interactive editor included. In this release, it allows for visual layout of nodes and links, modification of most parameters, and some integration with Cacti for picking data-sources. <strong>It is not integrated into Cacti's management pages, OR access control.</strong></p> <p>New in version 0.7, there is a partially-complete interactive editor included. In this release, it allows for visual layout of nodes and links, modification of most parameters, and some integration with Cacti for picking data-sources. <strong>It is not integrated into Cacti's management pages, OR access control.</strong> </p>

<p>To use the editor, you need to make a few extra considerations beyond those needed by the command-line weathermap software, as detailed in the <a href="main.html#install_standaloneeditor">Installation Guide</a>. <p>To use the editor, you need to make a few extra considerations beyond those needed by the command-line weathermap software, as detailed in the <a href="main.html#install_standaloneeditor">Installation Guide</a>.

</p> </p>

<p> <p>

Once you have all that taken care of, put a copy of one of your configuration files into the configs directory you just created, and then go to: <tt>http://www.your.web.server/cacti/php-weathermap/editor.php</tt> (or whereever you put it). You should get a menu to either create a map, or open the ones you just put in that directory. Once you have all that taken care of, put a copy of one of your configuration files into the configs directory you just created, and then go to: <tt>http://www.your.web.server/cacti/php-weathermap/editor.php</tt> (or whereever you put it). You should get a menu to either create a map, or open the ones you just put in that directory.

</p> </p>

Line 73... Line 73...

There are a number of things <i>not</i> editable in the editor currently: There are a number of things <i>not</i> editable in the editor currently:

<ul> <ul>

<li>background images and icons - it's intended that the editor will allow you to upload image files to the server, which will then appear in a list where appropriate.</li> <li>background images and icons - it's intended that the editor will allow you to upload image files to the server, which will then appear in a list where appropriate.</li>

<li>colours - there's no way to pick colours currently, either for the map elements or for the scale.</li> <li>colours - there's no way to pick colours currently, either for the map elements or for the scale.</li>

<li>defaults - the editor lags behind the current command-line software here. It generates 'old-style' global options for some features where the correct thing to do is make changes to the DEFAULT link and node definitions. Similarly, there is no per-node or per-link adjustment of things like font, label style or label offset.</li> <li>defaults - the editor lags behind the current command-line software here. It generates 'old-style' global options for some features where the correct thing to do is make changes to the DEFAULT link and node definitions. Similarly, there is no per-node or per-link adjustment of things like font, label style or label offset.</li>

<li>NODE TARGETs</li> <li><a href="config-reference.html#NODE_NODE">NODE</a> TARGETs</li>

<li>Multiple SCALEs</li> <li>Multiple SCALEs</li>

<li>Curves</li> <li>Curves</li>

<li>Link offsets or Label offsets</li> <li>Link offsets or Label offsets</li>

</ul> </ul>

Luckily, the editor shouldn't damage any of these things that you put into the configuration file by hand, so it's safe to do some work in the editor where it's quicker or more intuitive, and then fine-tune the file by hand. Luckily, the editor shouldn't damage any of these things that you put into the configuration file by hand, so it's safe to do some work in the editor where it's quicker or more intuitive, and then fine-tune the file by hand.

</p> </p>

</div> </div>

</div> </div>

</body> </body>

</html> </html>

Rev 1		Rev 85
Line 6...		Line 6...
`<link rel="stylesheet" type="text/css" media="screen" href="weathermap.css" />`		`<link rel="stylesheet" type="text/css" media="screen" href="weathermap.css" />`
`<meta name="generator" content=`		`<meta name="generator" content=`
`"HTML Tidy for Mac OS X (vers 12 April 2006), see www.w3.org" />`		`"HTML Tidy for Mac OS X (vers 12 April 2006), see www.w3.org" />`

`<title>PHP Weathermap`		`<title>PHP Weathermap`
`v0.91`		`v0.97a`
`- Editor</title>`		`- Editor</title>`
`<style type="text/css" media="print">`		`<style type="text/css" media="print">`
`/<![CDATA[/`		`/<![CDATA[/`
`body { font-size: 12pt; }`		`body { font-size: 12pt; }`
`a { color: black; text-decoration: underline; font-weight: normal;}`		`a { color: black; text-decoration: underline; font-weight: normal;}`
Line 38...		Line 38...
`</ul>`		`</ul>`
`</div>`		`</div>`

`<div id="header">`		`<div id="header">`
`<h1>PHP Weathermap`		`<h1>PHP Weathermap`
`v0.91`		`v0.97a`
`</h1>`		`</h1>`
`<h4>Copyright © 2005-2007 Howard Jones, <tt><a`		`<h4>Copyright © 2005-2010 Howard Jones, <tt><a`
`href="mailto:howie@thingy.com">howie@thingy.com</a></tt>. (<a`		`href="mailto:howie@thingy.com">howie@thingy.com</a></tt>. (<a`
`href="http://www.network-weathermap.com/">Website</a>)</h4>`		`href="http://www.network-weathermap.com/">Website</a>)</h4>`
`</div>`		`</div>`


Line 53...		Line 53...
`<p class="notebox"><b>Note:</b>`		`<p class="notebox"><b>Note:</b>`
`This section is basically unaltered from the v0.7 manual. The editor`		`This section is basically unaltered from the v0.7 manual. The editor`
`hasn't really changed since then, except to fix some bugs, and work`		`hasn't really changed since then, except to fix some bugs, and work`
`with the new config directives - that is to say, it won't edit them, but`		`with the new config directives - that is to say, it won't edit them, but`
`nor will it remove/damage them. It's still true to say that the editor is`		`nor will it remove/damage them. It's still true to say that the editor is`
`the easiest way to initially lay out your map, and pick your TARGETs if you use Cacti, but after that, some hand-editing will help with cosmetics.`		`the easiest way to initially lay out your map, and pick your <a href="config-reference.html#LINK_TARGET">TARGETs</a> if you use Cacti, but after that, some hand-editing will help with cosmetics.`
`</p>`		`</p>`

`<p>New in version 0.7, there is a partially-complete interactive editor included. In this release, it allows for visual layout of nodes and links, modification of most parameters, and some integration with Cacti for picking data-sources. <strong>It is not integrated into Cacti's management pages, OR access control.</strong></p>`		`<p>New in version 0.7, there is a partially-complete interactive editor included. In this release, it allows for visual layout of nodes and links, modification of most parameters, and some integration with Cacti for picking data-sources. <strong>It is not integrated into Cacti's management pages, OR access control.</strong> </p>`
`<p>To use the editor, you need to make a few extra considerations beyond those needed by the command-line weathermap software, as detailed in the <a href="main.html#install_standaloneeditor">Installation Guide</a>.`		`<p>To use the editor, you need to make a few extra considerations beyond those needed by the command-line weathermap software, as detailed in the <a href="main.html#install_standaloneeditor">Installation Guide</a>.`
`</p>`		`</p>`
`<p>`		`<p>`
`Once you have all that taken care of, put a copy of one of your configuration files into the configs directory you just created, and then go to: <tt>http://www.your.web.server/cacti/php-weathermap/editor.php</tt> (or whereever you put it). You should get a menu to either create a map, or open the ones you just put in that directory.`		`Once you have all that taken care of, put a copy of one of your configuration files into the configs directory you just created, and then go to: <tt>http://www.your.web.server/cacti/php-weathermap/editor.php</tt> (or whereever you put it). You should get a menu to either create a map, or open the ones you just put in that directory.`
`</p>`		`</p>`
Line 73...		Line 73...
`There are a number of things <i>not</i> editable in the editor currently:`		`There are a number of things <i>not</i> editable in the editor currently:`
`<ul>`		`<ul>`
`<li>background images and icons - it's intended that the editor will allow you to upload image files to the server, which will then appear in a list where appropriate.</li>`		`<li>background images and icons - it's intended that the editor will allow you to upload image files to the server, which will then appear in a list where appropriate.</li>`
`<li>colours - there's no way to pick colours currently, either for the map elements or for the scale.</li>`		`<li>colours - there's no way to pick colours currently, either for the map elements or for the scale.</li>`
`<li>defaults - the editor lags behind the current command-line software here. It generates 'old-style' global options for some features where the correct thing to do is make changes to the DEFAULT link and node definitions. Similarly, there is no per-node or per-link adjustment of things like font, label style or label offset.</li>`		`<li>defaults - the editor lags behind the current command-line software here. It generates 'old-style' global options for some features where the correct thing to do is make changes to the DEFAULT link and node definitions. Similarly, there is no per-node or per-link adjustment of things like font, label style or label offset.</li>`
`<li>NODE TARGETs</li>`		`<li><a href="config-reference.html#NODE_NODE">NODE</a> TARGETs</li>`
`<li>Multiple SCALEs</li>`		`<li>Multiple SCALEs</li>`
`<li>Curves</li>`		`<li>Curves</li>`
`<li>Link offsets or Label offsets</li>`		`<li>Link offsets or Label offsets</li>`
`</ul>`		`</ul>`
`Luckily, the editor shouldn't damage any of these things that you put into the configuration file by hand, so it's safe to do some work in the editor where it's quicker or more intuitive, and then fine-tune the file by hand.`		`Luckily, the editor shouldn't damage any of these things that you put into the configuration file by hand, so it's safe to do some work in the editor where it's quicker or more intuitive, and then fine-tune the file by hand.`
`</p>`		`</p>`

`</div>`		`</div>`
`</div>`		`</div>`
`</body>`		`</body>`
`</html>`		`</html>`