From: Jonathan Phillips <jon@...15...> I have not done much looking into adding the keyboard shortcuts and man page to the help menu for the next release. I really want to do this task, but could you use any help pointing me how to do this.
I wonder what the best way to accomplish this task would be? I guess we could add a link to the keyboard shortcuts page to the webpage where the shortcut keys are located, or we could set up a file where the keyboard keys are located in the source and you could edit that file so that on CVS build, all keys are updated accordingly.
I think Inkscape should ship with its own copy of help files in HTML, corresponding to the release. I think I will move the shortcuts from Wiki to XML and set up generating HTML in makefile. So, you can assume that the distribution includes an HTML file; your task is to run browser on it.
As to the best way to run browser, I'm not sure. I doubt there is a cross-platform reliable way to detect the default browser and run it, but I may be wrong - anyone?
If we cannot access default browser, perhaps we should store a browser executable path in preferences. But that's ugly.
Another idea is to start to use YELP from GNOME world.
Never seen it. Anyone has an opinion on Yelp?
Another thing, did you realize that Inkscape can open files from URLs. I opened a few svg examples from croczilla.com/svg/ from the commandline.
Sounds like this could be added to Tips-and-tricks page.
I think we should add an open file from url menu item.
Why not, try to do it - it should not be difficult.
_________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
On Wed, 21 Jan 2004, bulia byak wrote:
From: Jonathan Phillips <jon@...15...> I have not done much looking into adding the keyboard shortcuts and man page to the help menu for the next release. I really want to do this task, but could you use any help pointing me how to do this.
I wonder what the best way to accomplish this task would be? I guess we could add a link to the keyboard shortcuts page to the webpage where the shortcut keys are located, or we could set up a file where the keyboard keys are located in the source and you could edit that file so that on CVS build, all keys are updated accordingly.
I think Inkscape should ship with its own copy of help files in HTML, corresponding to the release. I think I will move the shortcuts from Wiki to XML and set up generating HTML in makefile. So, you can assume that the distribution includes an HTML file; your task is to run browser on it.
As to the best way to run browser, I'm not sure. I doubt there is a cross-platform reliable way to detect the default browser and run it, but I may be wrong - anyone?
If we cannot access default browser, perhaps we should store a browser executable path in preferences. But that's ugly.
Take a look at 'ScrollKeeper': http://scrollkeeper.sourceforge.net/
ScrollKeeper is a standard way of doing documentation that both GNOME and KDE use. When you navigate to the 'Help' area in your start menu, on most distros, that's the scrollkeeper system.
There are a number of different browsers that can understand Scrollkeeper documentation, including the KDE Help Center, Nautilus, and Yelp, the standard GNOME help browser.
Documents for ScrollKeeper are written in DocBook, so the source files can also be used to produce HTML, PDF, etc. versions. This is why we used DocBook for the manual; once Scrollkeeper support is in Inkscape, then the manual could be shipped with the app directly, as a help system.
Anyway, take a look -- from what I can tell it seems to be the accepted standard solution for handling help file browsing.
Bryce
participants (2)
-
Bryce Harrington -
bulia byak