'Re: STL docs in Gideon? (was: Re: playing with gideon)'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: STL docs in Gideon? (was: Re: playing with gideon)
From:       Max <listposter () machsim ! com>
Date:       2002-11-13 13:25:22
[Download RAW message or body]

Sebastian Kratzert wrote:

>Am Monday 11 November 2002 18:23 schrieb Caleb Tennis:
>  
>
>>>You must be kidding :-)
>>>2 MB is nothing, literally nothing, compared to the inconvenience to
>>>maintain two seperate packages. The inconveninience to read, and answer
>>>the same question "Where is the documentation" over and over and over
>>>again in the mailing list. Worse, if you split gideon into core and
>>>parts you are in "package hell".
>>>
>>>I say "Make it easy, include everything".
>>>      
>>>
>>Why don't we put the documentation online, and use gideon to point to its
>>location?  If a user wants to install the documentation locally, perhaps a
>>simple tar xzf is all they need to do to have local docs.
>>    
>>
>
>I agree with that. 
>I think most people use Kdevelop shipped with a distribution. The 
>distributions can make ducumentation packages for their customers. The other 
>people who don't use Linux distributions will know how to download and 
>install a tarball.
>
Long long time ago, when there was no VC++ from MS, Borland used to 
provide a special to browse, read and search the several help documents 
they ship. Then MS came with MSDN.

The moral of this super summarized story is that it is really convenient 
to be able to browse all documentation at a central location. Therefore 
I propose that Gideon shall have at least a central page ( like the ones 
you can find in VC++.Net and Komodo ) where you can browse, search and 
read HTML pages, man pages etc.

Currently technologies available in KDE, HtDig and in doxygen are very 
good and well tested. What needs to be done is a good integration work 
and at the end an easy to use and easy to configure & install help 
system shall be in Gideon. A believe Qt's assistant is a nice start point.

I am aware that this is more work then simply adding links to web sites. 
But if Gideon is the NEXT KDevelop version, it should at least be 
powerful as VC++.Net, Eclipse and Komodo.

Max.

[Attachment #3 (text/html)]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
Sebastian Kratzert wrote:<br>
<blockquote type="cite" cite="mid200211121552.59197.skratzert@gmx.de">
  <pre wrap="">Am Monday 11 November 2002 18:23 schrieb Caleb Tennis:
  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">You must be kidding :-)
2 MB is nothing, literally nothing, compared to the inconvenience to
maintain two seperate packages. The inconveninience to read, and answer
the same question "Where is the documentation" over and over and over
again in the mailing list. Worse, if you split gideon into core and
parts you are in "package hell".

I say "Make it easy, include everything".
      </pre>
    </blockquote>
    <pre wrap="">Why don't we put the documentation online, and use gideon to point to its
location?  If a user wants to install the documentation locally, perhaps a
simple tar xzf is all they need to do to have local docs.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I agree with that. 
I think most people use Kdevelop shipped with a distribution. The 
distributions can make ducumentation packages for their customers. The other 
people who don't use Linux distributions will know how to download and 
install a tarball.</pre>
</blockquote>
Long long time ago, when there was no VC++ from MS, Borland used to provide
a special to browse, read and search the several help documents they ship.
Then MS came with MSDN.<br>
<br>
The moral of this super summarized story is that it is really convenient
to be able to browse all documentation at a central location. Therefore I
propose that Gideon shall have at least a central page ( like the ones you
can find in VC++.Net and Komodo ) where you can browse, search and read HTML
pages, man pages etc.<br>
<br>
Currently technologies available in KDE, HtDig and in doxygen are very good
and well tested. What needs to be done is a good integration work and at
the end an easy to use and easy to configure &amp; install help system shall
be in Gideon. A believe Qt's assistant is a nice start point.<br>
<br>
I am aware that this is more work then simply adding links to web sites.
But if Gideon is the NEXT KDevelop version, it should at least be powerful
as VC++.Net, Eclipse and Komodo.<br>
<br>
Max.<br>
</body>
</html>

_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

[prev in list] [next in list] [prev in thread] [next in thread] 