<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dsign</id>
	<title>Inkscape Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dsign"/>
	<link rel="alternate" type="text/html" href="https://wiki.inkscape.org/wiki/Special:Contributions/Dsign"/>
	<updated>2026-04-30T04:31:52Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.36.1</generator>
	<entry>
		<id>https://wiki.inkscape.org/wiki/index.php?title=Embedded_Help&amp;diff=7218</id>
		<title>Embedded Help</title>
		<link rel="alternate" type="text/html" href="https://wiki.inkscape.org/wiki/index.php?title=Embedded_Help&amp;diff=7218"/>
		<updated>2006-06-21T22:57:48Z</updated>

		<summary type="html">&lt;p&gt;Dsign: /* Ideas */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rationale ==&lt;br /&gt;
Inkscape 0.44 has some great tutorials, but they alone can not replace an embedded help system like other applications have. The deficiencies are:&lt;br /&gt;
* one cannot find help for a specific tool&lt;br /&gt;
* tutorials don't have hyperlinks nor an index&lt;br /&gt;
* tutorials cannot really be searched - search is limited to the current document and doesn't jump from hit to hit, but just highlights all hits, and the user has to comb though these&lt;br /&gt;
&lt;br /&gt;
Therefore, we should have a &amp;quot;regular&amp;quot;, embedded help system in Inkscape, in conjunction to the tutorials.&lt;br /&gt;
&lt;br /&gt;
== Ideas ==&lt;br /&gt;
* Cedric and Kevin's [[UserManual]] would be a nice base&lt;br /&gt;
*  kind of 3 levels of needs: instant help (already existing, but not for effects/extensions :( ); then a kind of embedded glossary, and finally a big user manual&lt;br /&gt;
** short explanation text should be integrated in the inx file or the extension code and then displayed (in a tab for a dialog ?) with the effect... I don't know what would be the best display place for it (status bar at least)&lt;br /&gt;
* The glossary could be section and subsections of the big manual, with its own menu item.&lt;br /&gt;
* Context-sensitive help is one thing where I think they are spot-on.  How hard would it be for us to provide &amp;quot;F1 Help&amp;quot;? If only to pop up a browser on a given html page and #anchor. (Bob Jamison in http://permalink.gmane.org/gmane.comp.graphics.inkscape.devel/16826)&lt;br /&gt;
* dsign is already working on a SVG rendering help system. It' in an early stage, but it works. And yes, it can be made context sensitive, provided that a way to get the current Inkscape state (in terms of user interface) be implemented.&lt;br /&gt;
&lt;br /&gt;
== Help Systems on Different Operating Systems ==&lt;br /&gt;
=== Linux, *BSD, Other Unices ===&lt;br /&gt;
* Do we want to use something like [http://live.gnome.org/Yelp Yelp]?&lt;br /&gt;
* [http://developer.gnome.org/projects/gdp/handbook/gdp-handbook/ The GNOME Handbook of Writing Software Documentation] - [http://developer.gnome.org/projects/gdp/handbook/gdp-handbook/ar01s08.html &amp;quot;Writing Context Sensitive Help (coming in GNOME-3.0)&amp;quot;]&lt;br /&gt;
&lt;br /&gt;
=== Windows ===&lt;br /&gt;
* Can we produce [http://en.wikipedia.org/wiki/Microsoft_Compressed_HTML_Help CHM files]?&lt;br /&gt;
** [http://www.kosek.cz/xml/dboscon/dbhelp/frames.html From DocBook to integrated help systems]&lt;br /&gt;
** [http://www.herdsoft.com/linux/themen/hlp_to_chm.html  Converting .hlp files to .chm]&lt;br /&gt;
** [http://xchm.sourceforge.net/ xchm], a CHM viewer&lt;br /&gt;
** [http://gnochm.sourceforge.net/ GnoCHM], another CHM viewer (for Gnome)&lt;br /&gt;
** [http://www.nongnu.org/chmspec/latest/ unofficial CHM spec]&lt;br /&gt;
** [http://www.speakeasy.org/%7Erussotto/chm/ CHM doc]&lt;br /&gt;
** http://beeblex.com/lists/index.php/php.pear.doc/7216?s=l:php.pear.doc&lt;br /&gt;
&lt;br /&gt;
=== MacOS X ===&lt;br /&gt;
The [http://www.devworld.apple.com/documentation/Carbon/Conceptual/ProvidingUserAssitAppleHelp/user_help_intro/chapter_1_section_1.html  &amp;quot;User Assistance&amp;quot;] technology or environment has [http://www.stepwise.com/SpecialCoverage/WWDC2001/501.html evolved] through several major stages, but has always been based upon a restricted HTML 3.2 [http://cocoadevcentral.com/articles/000072.php markup] and a lightweight &amp;quot;Help Viewer&amp;quot;. See [http://www.andymatuschak.org/articles/2005/12/18/help-with-apple-help Help on Apple Help] for a near illegible page that describes the making of the excellent help system for the pixel editor [http://www.andymatuschak.org/pages/pixen/ Pixen] (not that many Inkscapers use pixel editors). Apple provides a [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGUsingTechnologies/chapter_8_section_13.html comprehensive account] of the Human Interface factors relating to its technology, but this may be just outside what we need to be thinking about for Inkscape right now.&lt;br /&gt;
&lt;br /&gt;
* [http://chmox.sourceforge.net/ &amp;quot;Read your CHM documents on your Mac.&amp;quot;] - maybe an option too&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [http://www.g2meyer.com/usablehelp/items.html Usable Help], a list of just under 250 links to articles on documentation and help systems for software and consumer products.&lt;br /&gt;
* [http://wiki.inkscape.org/wiki/index.php/Report_on_c%27t_article_12/2006 Review from German c't magazine] pointing out the need of some embedded documentation/help&lt;br /&gt;
* ScislaC has a plan to re-arrange and extend our existing tutorial system (FIXME: is there anything written down yet?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Developer Documentation]]&lt;/div&gt;</summary>
		<author><name>Dsign</name></author>
	</entry>
</feed>