http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5194
--- Comment #4 from Christopher Brooks <[email protected]> 2012-07-11 17:07:12 PDT --- I updated ptolemy.actor.gui.HTMLViewer so that if the URL cannot be found, then it is passed to ptolemy.util.FileUtilities.nameToURL() that understands things like $CLASSPATH. So, if you put the user's ~/KeplerData/workflows/module/outreach directory in the classpath and refer to the urls like <a href="$CLASSPATH/demos/getting-started/00-StatisticalSummary.xml">Statistical Summary</a> then the link should work. We have the classpath, we should use it. Having the url be able to get a property is a possibility, but using the classpath is cleaner. I don't want to have a URL execute arbitrary Ptolemy expression language code because someone could extend this to support: <a href="ptexpr:exec("rm veryimportantfile")">Model</a> Can the outflow/workflow directory be added to the classpath or do you really want to read the property? If you want to read the property, then maybe <a href="property:outreach.workflow/demos/getting-started/04-HelloWorld.xml">Hello World</a> would be ok. This would just call ptolemy.util.StringUtilities.getProperty(), which does not invoke the expression language, but does understand certain properties and does not return null. Also, property: is more like about: and other protocol syntaxes. Comments? -- Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. _______________________________________________ Kepler-dev mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
