<?xml version="1.0" encoding="utf-8"?><!-- generator="b2evolution/1.9.3" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Image Markup and Presentation</title>
						<link>http://hcmc.uvic.ca/blogs/index.php?blog=20</link>
				<description></description>
				<language>en-CA</language>
				<docs>http://backend.userland.com/rss</docs>
				<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=1.9.3"/>
				<ttl>60</ttl>
								<item>
					<title>Meeting re: Martin Segger project</title>
					<link>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;title=meeting_re_martin_segger_project&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
					<pubDate>Thu, 08 Mar 2007 00:11:01 +0000</pubDate>
					<dc:creator>David</dc:creator>
					<category domain="main">Activity log</category>					<guid isPermaLink="false">1146@http://hcmc.uvic.ca/blogs/</guid>
					<description> (Mins: 30) Had a meeting with Scott and Chris Petter that involved a discussion of Martin Segger's architectural plans project, with reference to possible use of IMaP for presentation. So far we don't know what the project requirements are, so it is not possible to say if IMaP is suitable.</description>
					<content:encoded><![CDATA[<p>Had a meeting with Scott and Chris Petter that involved a discussion of Martin Segger's architectural plans project, with reference to possible use of IMaP for presentation. So far we don't know what the project requirements are, so it is not possible to say if IMaP is suitable.</p>]]></content:encoded>
					<comments>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;p=1146&amp;c=1&amp;tb=1&amp;pb=1#comments</comments>
				</item>
								<item>
					<title>Too many maps!</title>
					<link>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;title=too_many_maps&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
					<pubDate>Wed, 20 Dec 2006 18:40:42 +0000</pubDate>
					<dc:creator>David</dc:creator>
					<category domain="main">Tasks</category>					<guid isPermaLink="false">336@http://hcmc.uvic.ca/blogs/</guid>
					<description> (Mins: 20) The IMaP administration program is showing signs of strain when the number of maps in a project gets large. The viHistory maps are becoming a problem; there are already over 30 maps, and the 1903 Fire Insurance maps will add about 100 more. Managing this many maps with the current methods is awkward. Giving the user access to them in the IMaP Viewer (via the Maps menu) is also problematic; the menu either gets very long or has many submenus. The only way to manage the glut of maps is to break them up into different projects, which makes finding a map to view harder.

Some elements of both the administration program and the viewer will need to change to deal with this:


  In the administration program, selecting maps from a SELECT list is awkward. Also, these lists do not allow for a hierarchical arrangement of maps. The selects and other lists should be replaced with tree strutures.  
  There needs to be a way to create the map definitions for multiple maps all sharing the same basic parameters, but with different names, titles and raster images. The current template feature does not do this effectively.
  The Data directory, used to hold the raster image and shape files, should allow for subfolders to match the hierarchical structure of the project's maps. Right now all files are in one folder, which makes them difficult to manage.
  Something needs to be done with the Maps menu in the viewer. With more than a few maps it gets too complex. Perhaps another level is needed, so that multiple projects each containing a reasonable number of maps can be shown on the menu.



</description>
					<content:encoded><![CDATA[The IMaP administration program is showing signs of strain when the number of maps in a project gets large. The viHistory maps are becoming a problem; there are already over 30 maps, and the 1903 Fire Insurance maps will add about 100 more. Managing this many maps with the current methods is awkward. Giving the user access to them in the IMaP Viewer (via the Maps menu) is also problematic; the menu either gets very long or has many submenus. The only way to manage the glut of maps is to break them up into different projects, which makes finding a map to view harder.

Some elements of both the administration program and the viewer will need to change to deal with this:

<ul>
  <li>In the administration program, selecting maps from a SELECT list is awkward. Also, these lists do not allow for a hierarchical arrangement of maps. The selects and other lists should be replaced with tree strutures.</li>  
  <li>There needs to be a way to create the map definitions for multiple maps all sharing the same basic parameters, but with different names, titles and raster images. The current template feature does not do this effectively.</li>
  <li>The Data directory, used to hold the raster image and shape files, should allow for subfolders to match the hierarchical structure of the project's maps. Right now all files are in one folder, which makes them difficult to manage.</li>
  <li>Something needs to be done with the Maps menu in the viewer. With more than a few maps it gets too complex. Perhaps another level is needed, so that multiple projects each containing a reasonable number of maps can be shown on the menu.</li>
</ul>


]]></content:encoded>
					<comments>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;p=336&amp;c=1&amp;tb=1&amp;pb=1#comments</comments>
				</item>
								<item>
					<title>Updates to IMaP (v1.39)</title>
					<link>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;title=updates_to_imap_v1_39&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
					<pubDate>Wed, 06 Dec 2006 19:45:17 +0000</pubDate>
					<dc:creator>David</dc:creator>
					<category domain="main">Activity log</category>					<guid isPermaLink="false">202@http://hcmc.uvic.ca/blogs/</guid>
					<description> (Mins: 120) The administration utility Project page displayed the names of all of the maps in the project. The viHistory map project has over 30 maps, which made the map name display unworkably large. The display has been replaced with a simple count of the maps and templates in the project.

There was a bug on the administration utility Project | Map Control page that would have allowed the user to select a template as the default map. This is a Bad Thing. Templates will no longer be displayed in the default map selector.

The IMaP demonstration site has been updated. It now has a link to a page where the source code and documentation can be downloaded (as a ZIP file). The page also lists the system requirements. A link to the viHistory maps section has also been added to the examples.

The IMaP demo site and viHistory site have been updated. The Map of London site is not affected.</description>
					<content:encoded><![CDATA[<p>The administration utility Project page displayed the names of all of the maps in the project. The viHistory map project has over 30 maps, which made the map name display unworkably large. The display has been replaced with a simple count of the maps and templates in the project.</p>

<p>There was a bug on the administration utility Project | Map Control page that would have allowed the user to select a template as the default map. This is a Bad Thing. Templates will no longer be displayed in the default map selector.</p>

<p>The IMaP demonstration site has been updated. It now has a link to a page where the source code and documentation can be downloaded (as a ZIP file). The page also lists the system requirements. A link to the viHistory maps section has also been added to the examples.</p>

<p>The IMaP demo site and viHistory site have been updated. The Map of London site is not affected.</p>]]></content:encoded>
					<comments>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;p=202&amp;c=1&amp;tb=1&amp;pb=1#comments</comments>
				</item>
								<item>
					<title>IMaP demonstration site</title>
					<link>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;title=imap_demonstration_site&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
					<pubDate>Wed, 06 Dec 2006 19:38:22 +0000</pubDate>
					<dc:creator>David</dc:creator>
					<category domain="main">Announcements</category>					<guid isPermaLink="false">201@http://hcmc.uvic.ca/blogs/</guid>
					<description> (Mins: 0) A demonstration of IMaP, including the administration utility, is available at http://lettuce.tapor.uvic.ca/~taprimap. All of the IMaP documentation is available from the menu in the administration utility.</description>
					<content:encoded><![CDATA[<p>A demonstration of IMaP, including the administration utility, is available at <a href="http://lettuce.tapor.uvic.ca/~taprimap/imapdemo/demo/">http://lettuce.tapor.uvic.ca/~taprimap</a>. All of the IMaP documentation is available from the menu in the administration utility.</p>]]></content:encoded>
					<comments>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;p=201&amp;c=1&amp;tb=1&amp;pb=1#comments</comments>
				</item>
								<item>
					<title>Updating IMaP installations from Subversion</title>
					<link>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;title=updating_imap_installations_from_subvers&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1</link>
					<pubDate>Wed, 06 Dec 2006 19:12:13 +0000</pubDate>
					<dc:creator>David</dc:creator>
					<category domain="main">Announcements</category>					<guid isPermaLink="false">199@http://hcmc.uvic.ca/blogs/</guid>
					<description> (Mins: 0) IMaP is controlled by the version control system Subversion. All sites using IMaP must be updated through Subversion.

These web sites currently use IMaP:

IMaP demo site (http://lettuce.tapor.uvic.ca/~taprimap/imapdemo/demo/, local folder /home1t/taprimap)

For the IMaP demo web site: shell to server lettuce, then cd /home1t/tapriamp, then run ./svnupdate.sh [pw] where [pw] is a password for the user ID you logged on with (must have Subversion permissions). If you leave off the password you will be asked for it several times, so best to include it. The entire site will be updated (four steps).

viHistory (http://vihistory.uvic.ca/content/maps/imaps.php, http://vihistory.uvic.ca/content/maps/htdocs/admin/admin.php, local folder /home1t/taprhist)

For the viHistory web site: shell to server lettuce, then cd /home1t/taprhist, then run ./svnupdate.sh [pw] where [pw] is a password for the user ID you logged on with. The entire site will be updated – both the viHistory main site and the IMaP instance embedded in the main site (the IMaP instance is embedded at /home1t/taprhist/www/content/maps).

Map of London (http://mapoflondon.uvic.ca/experimental_map.php, local folder /home1t/london)

For the Map of London web site: shell to server lettuce, cd /home1t/london, run ./london_update.sh.  The shell script (written by Mike) has the user name and password right in it, a dubious practice from a security standpoint, but it isn't David's project so he didn't mess with it. The IMaP instance is embedded at /home1t/london/www/imap.
</description>
					<content:encoded><![CDATA[<p>IMaP is controlled by the version control system Subversion. All sites using IMaP must be updated through Subversion.</p>

<p>These web sites currently use IMaP:</p>

<p><strong>IMaP demo site</strong> (<a href="http://lettuce.tapor.uvic.ca/~taprimap/imapdemo/demo/">http://lettuce.tapor.uvic.ca/~taprimap/imapdemo/demo/</a>, local folder /home1t/taprimap)</p>

<p>For the <strong>IMaP demo</strong> web site: shell to server lettuce, then cd /home1t/tapriamp, then run ./svnupdate.sh [pw] where [pw] is a password for the user ID you logged on with (must have Subversion permissions). If you leave off the password you will be asked for it several times, so best to include it. The entire site will be updated (four steps).</p>

<p><strong>viHistory</strong> (<a href="http://vihistory.uvic.ca/content/maps/imaps.php">http://vihistory.uvic.ca/content/maps/imaps.php</a>, <a href="http://vihistory.uvic.ca/content/maps/htdocs/admin/admin.php">http://vihistory.uvic.ca/content/maps/htdocs/admin/admin.php</a>, local folder /home1t/taprhist)</p>

<p>For the <strong>viHistory</strong> web site: shell to server lettuce, then cd /home1t/taprhist, then run ./svnupdate.sh [pw] where [pw] is a password for the user ID you logged on with. The entire site will be updated – both the viHistory main site and the IMaP instance embedded in the main site (the IMaP instance is embedded at /home1t/taprhist/www/content/maps).</p>

<p><strong>Map of London</strong> (<a href="http://mapoflondon.uvic.ca/experimental_map.php">http://mapoflondon.uvic.ca/experimental_map.php</a>, local folder /home1t/london)</p>

<p>For the <strong>Map of London</strong> web site: shell to server lettuce, cd /home1t/london, run ./london_update.sh.  The shell script (written by Mike) has the user name and password right in it, a dubious practice from a security standpoint, but it isn't David's project so he didn't mess with it. The IMaP instance is embedded at /home1t/london/www/imap.</p>
]]></content:encoded>
					<comments>http://hcmc.uvic.ca/blogs/index.php?blog=20&amp;p=199&amp;c=1&amp;tb=1&amp;pb=1#comments</comments>
				</item>
					</channel>
</rss>
