Most assets call processTemplate to do their template processing. Inside

of processTemplate, there is a call to $self->get which adds all the asset
properties to the list of template variables.  Sometimes they duplicate
entries in the www_ method (like view).  Sometimes they're not interesting,
like templateId, but they're still valid template variables.
I'm going to start a new template variable entry for each asset that
will just contain those variables.  Any www_ method calling processTemplate
can then include them via ISA into their list of template variables.

lib/WebGUI/Help/Asset_Event.pm

@@ -4,6 +4,12 @@ our $HELP = {
 	'event add/edit' => {
 		title => '72',
 		body => '73',
+		isa => [
+			{
+				tag => 'asset fields',
+				namespace => 'Asset'
+			},
+		],
 		fields => [
                         {
                                 title => '512',
@@ -37,19 +43,28 @@ our $HELP = {
                         },
                 ],
 		related => [
-			{
-				tag => 'asset fields',
-				namespace => 'Asset'
-			},
 			{
 				tag => 'event template',
 				namespace => 'Asset_Event'
 			},
 		]
 	},
+
+	##I didn't break out individual asset level variables here
+	##because there are so few of them. --ck
 	'event template' => {
 		title => '96',
 		body => '97',
+		isa => [
+			{
+				tag => 'asset template',
+				namespace => 'Asset'
+			},
+			{
+				tag => 'template language',
+				namespace => 'Asset_Template'
+			},
+		],
 		fields => [
 		],
 		variables => [
@@ -59,12 +74,18 @@ our $HELP = {
 		          {
 		            'name' => 'start.label'
 		          },
+		          {
+		            'name' => 'eventStartDate'
+		          },
 		          {
 		            'name' => 'start.date'
 		          },
 		          {
 		            'name' => 'start.time'
 		          },
+		          {
+		            'name' => 'eventEndDate'
+		          },
 		          {
 		            'name' => 'end.date'
 		          },