Mail Archives: geda-user/2015/03/12/17:35:00
Hi, Kai-Martin.
On Tue, Mar 10, 2015 at 12:29:55PM +0100, Kai-Martin Knaak wrote:
...
> >> > Please look at 'info geda-scheme' for more info on this.
> >>
> >> Err, well ... this is well hidden.
> >> How should I know that "geda-scheme" is the term to look for in info?
> > You already know the answer, right? ;)
>
> Actually no. I knew that info existed. But the few times I looked at an
> info page it got me less information than the corresponding man page. So
> info never registered in my internal list of information sources.
>
> Since about the turn of the century www+google have firmly established
> themselves as the one stop to retrieve howto information. So the most
> efficient way to get info pages to the reader might be a mirror on a web
> page which is indexed by the crawlers of google and company.
We could ask DJ to place the geda-scheme document converted into HTML
somewhere on the geda-project.org server. The conversion process can be
automated in order to always have an up-to-date version since it is as
easy as just 'make html' in the docs/ directory of the geda-gaf
repository.
...
> >> Somebody with write access to the wiki might remove the attribute "on-
> >> line" to make the heading compatible for offline use, too)
> > I believed you do have write access, do you?
>
> Not anymore.
> My login got removed three times for no reason -- just like everybody else
> on the wiki. No details were given, no warning in advance. It just
> happened. Apparently, this was the wiki operators idea of how to handle a
> migration to a different server. I reapplied and got access again. During
> this time geda devs indicated on this list, they did not appreciate the
> work done in the wiki. In my case, this was mainly
I, for one, appreciate your work as well as the work of other
developers / wiki authors very much.
...
> > My gschem has 'Gschem User Guide' as the first entry in the 'Help' menu
>
> Fair enough.
> There is also a link to a local copy of faq-gschem.html, to a local copy
> of the geda wiki and to the internet version of the wiki. All of them have
> a dedicated accel key combo. Unfortunately, the local copies come with no
> navigation at all. No index, no site map, no context. As a seasoned user I
> sort of know how these pages relate and what to expect. But how does this
> catalog work for a newbie?
> Maybe less would be more: Provide just one entry for documentation and
> redirect users from there.
Don't know about one entry, but the main wiki page now contains
hand-made site map (thanks to Roland Lutz). We just have to wait till
the next release and it'll be available in the offline documentation.
As for index, if I correctly understand what you mean, the already
available glossary could serve for it. In my translation, I tried to add
as many relevant terms in there and links to them as possible. Don't know
what do you mean by 'context', either.
> > (<H><G>). Does yours has one? (However, all the 'Help' menu entries
> > don't work for me for some reason :) Wine seems to have broke them,
>
> This is probably a MIME issue. The mime type of the documentation files is
> "text/html". To show the applications your desktop uses to open them do:
> gvfs-mime --query text/html
> Most likely, it says the default application is wine. It also presents a
> list of desktop files registered for file with the mime type text/html. A
> sub set of these desktop files is presented as "recommended applications".
>
> To change the default to the www browser iceweasel you could do:
> gvfs-mime --set text/html iceweasel.desktop
>
> An alternative would be
> mimeopen -d LOCAL/PATH/TO/doc/geda-gaf/wiki/index.html
> This presents a list of applications. Actually, this list is compiled from
> the list of desktop files returned by gvfs-open. Choose one and it will be
> the default for the current user from now on. The place, where this
> information is stored is: $HOME/.local/share/applications/defaults.list
>
> ---<)kaimartin(>---
Thank you for the tips, but I have neither gvfs-mime nor mimeopen
installed in my system :) The issue has been fixed by adding one line in
~/.mailcap, though.
Regards,
Vladimir
- Raw text -