On Sat, 25 Sep 2010, Carsten Klein wrote:

Trac has a serious documentation problem. Normally I have 3 types of help
when developing software:
  * documentation of the API
  * examples
  * help by users or developers

you forgot the first rule: help yourself by learning from the sources.

It seems you did not read my mail really. My problem is that neither documentation nor relevant parts of source can't be found (mainly due to the reason Google is not allowed to scan them which I now know) and that I got no answers. The problem is that all ways fail. I skip all your following statements, which all refer to the same wrong assumption.

(1) what exactly is the code you are referring to, is it a plugin, or is
it some modification to trac, or did you embed the code into the genshi
template you are using?

Actually it is not relevant where the code is to a give a hint how templates must be designed. To answer your question - it is in spamfilter plugin (which BTW a short Google call with the code itself shows also).

In case information is missing then there could have been a mail with a short sentence what information is missing. I got NO reply at all for a week.

And, googling for trac add_link reveals that you might have wanted to
extend upon the INavigationContributor extension point

Don't assume I'm totally dumb. I DID google for trac, add_link and many combinations of this long before even thinking to ask at the mailinglist.

And, by having a good look at the in source documentation on that
interface, would have revealed that any links you contribute to a page
will automatically be rendered by the system. If you want to have more
than that feel free to implement your own link providers...

Your text does not say anything at all. Somehow I must define where I want a link in my template, as software may be intelligent, but it can't know what I want. So we come back to the question: I have 4 links - "What do I need to add in template to get this done?"

(2) where is the java plugin being hosted at? if it is different
locations, i.e. <your trac>/login and <weird>/applet, then the
application, in this case trac, will not allow you to connect as an
authorized user due to the missing session token/id. Something which a
competent developer like yourself should have figured out in the first
place by pure logic.

As said the applet works fine, when page is already authenticated by browser. If not, the plugin sends basic authentication.

I now search a way how I can convert this basic authentication into a trac login. Probably I stated not clear enough, but I want to do that in Trac and not in the applet (otherwise I would not have asked in trac-dev). So my problem is to create a correct session based on the basic authentication information I get. Everything in Trac, as plugin.

(1) searching for 'trac' on google yields trac prominently as the first
result available

Exactly this it does not. For end users there is something to be found, but not for developers. I again tried all your examples and not one of them really leads me to useful information. Always I reach pages which itself are useless. Most prominent are usually old bug report tickets which is a waste of high ranking of Trac website. Probably I find the releveant information after hours of searching or with a lot of previous knowledge of trac structure. But in its current form nearly no request can be fullfilled by Google search.

I don't write such letters when I fail for first or second time. This is the situation for me since I first started to do Trac stuff nearly 1 year ago.

Did you ever try Googling for Java, QT, C, C++ or Python related topics? A big difference to the way of Trac, I don't expect that quality for trac, but e.g. "trac add_link" does not give me any relevant information as search term and this is the same for all topics I had till now.

I did not know how to programm Python when I started, but it was much easier to learn a new language than to fix certain issues in Trac. Usually I need to do trial an error which is very ineffective.

P.S. You did write a lot of text, but you did not provide a single hint how template and generating code work together or how authentication system works. If documentation was good enough, you would have been able to provide at least one or two links to pages or source, which could help me to solve issues. Your whole text make clear that my opinion is valid.

Your whole mail says "We have a problem, but we wont admit it". Actually I'm happy that answers from Christian actually have been much more realistic.

Ciao
--
http://www.dstoecker.eu/ (PGP key available)

--
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to trac-...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en.

Reply via email to