[Trac-dev] How would I add descriptive tips to main navigation bar

[Trac-dev] More than one GroupStatsProvider

Hello!

I'm developing a plugin which implements another progressbar view of a
milestone. But I want to have the normal ticket count progressbar
(DefaultGroupStatsProvider) too. Is it possible to enable too providers in
trac.ini or is it possible to return more than one stat object out of the
"def
get_ticket_group_stats(self, ticket_ids)" function.

I'm grateful for any hints!

Yours' sincerely,

Joachim Langenbach

--

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

[Trac-dev] How to access wiki page content from macro code?

Hi,

beginners question: If I have a fixed named wiki page, e.g. "wiki/MyPage",
how can I read and process the page content from within Python macro code?
I'm sure this is documented somewhere, but where?

TIA!

--

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

Re: [Trac-dev] How to access wiki page content from macro code?

*

> beginners question: If I have a fixed named wiki page, e.g. "wiki/MyPage",
> how can I read and process the page content from within Python macro code?
> I'm sure this is documented somewhere, but where?

I don't know where it's documented, but here's an example:

http://trac.edgewall.org/browser/trunk/trac/wiki/interwiki.py?rev=8899&marks=104-106#L100

Tim

--

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

Re: [Trac-dev] How to access wiki page content from macro code?

Quoting "Tim Hatch" <tim <at> timhatch.com>:
*

> I don't know where it's documented, but here's an example:
>
> http://trac.edgewall.org/browser/trunk/trac/wiki/interwiki.py?rev=8899&marks=104-106#L100

Many thanks, this works perfectly.

--

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

[Trac-dev] Right-to-Left languages & L10N

I use Trac for several projects, in several organizations.
In some of the projects it is required to work in Hebrew (to be more
precise: mix of Hebrew & English),
which is of course right-to-left language.
Does L10N include improved support for RTL layout?
As far as the actual translation, I will be happy to assist with the
Hebrew one (I opened a ticket for it [1]),
but it seems that actually incorporating the RTL support is a bit
beyond simply translating...

[1] http://trac.edgewall.org/ticket/9040

--

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

[Trac-dev] Inconsistent terminology for TracLinks pointing to the repository browser

Hello,

I was going to open a ticket suggesting the following incosistency with
TracLink terminology
 * timeline: points to /timeline
 * log: points to /log
... and so forth

Whereas,
 * source: points to /browser

but would one would probably expect that:
 * browser: points to /browser

I found that browser: was already implemented as a TracLink, which is great!

Is there a reason we would not want to add this to the Trac help page [1],
noting that browser: is an alias for source:, and suggest deprecating the
use of source:?  Or perhaps for 0.12 just mention the browser: prefix for a
TracLink and not mention the source: prefix for a TracLink?

It seems preferable to use the browser: TracLink for the sake of consistent
terminology since it points to the TracBrowser, and a request matching
/browser.

As far as I can tell - repos, source, and browser are aliases for the same
TracLink [2].

[1] http://trac.edgewall.org/wiki/TracLinks
[2]
http://trac.edgewall.org/browser/trunk/trac/versioncontrol/web_ui/browser.py?rev=9156&marks=715,717-718#L703
-- 
View this message in context: http://old.nabble.com/Inconsistent-terminology-for-TracLinks-pointing-to-the-repository-browser-tp27485031p27485031.html
Sent from the Trac Dev mailing list archive at Nabble.com.

--

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

Re: [Trac-dev] Inconsistent terminology for TracLinks pointing to the repository browser

"source" is more descriptive since it is the noun you are linking to,  
a single source file.

--Noah

On Feb 6, 2010, at 5:16 PM, Ryan J Ollos wrote:

*

>
> Hello,
>
> I was going to open a ticket suggesting the following incosistency  
> with
> TracLink terminology
> * timeline: points to /timeline
> * log: points to /log
> ... and so forth
>
> Whereas,
> * source: points to /browser
>
> but would one would probably expect that:
> * browser: points to /browser
>
> I found that browser: was already implemented as a TracLink, which  
> is great!
>
> Is there a reason we would not want to add this to the Trac help  
> page [1],
> noting that browser: is an alias for source:, and suggest  
> deprecating the
> use of source:?  Or perhaps for 0.12 just mention the browser:  
> prefix for a
> TracLink and not mention the source: prefix for a TracLink?
>
> It seems preferable to use the browser: TracLink for the sake of  
> consistent
> terminology since it points to the TracBrowser, and a request matching
> /browser.
>
> As far as I can tell - repos, source, and browser are aliases for  
> the same
> TracLink [2].
>
> [1] http://trac.edgewall.org/wiki/TracLinks
> [2]
> http://trac.edgewall.org/browser/trunk/trac/versioncontrol/web_ui/browser.py?rev=9156&marks=715,717-718#L703
> -- 
> View this message in context: http://old.nabble.com/Inconsistent-terminology-for-TracLinks-pointing-to-the-repository-browser-tp27485031p27485031.html
> Sent from the Trac Dev mailing list archive at Nabble.com.
>
> -- 
> You received this message because you are subscribed to the Google  
> Groups "Trac Development" group.
> To post to this group, send email to trac-dev <at> googlegroups.com.
> To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com 
> .
> For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en 
> .
>

--

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

Re: [Trac-dev] Inconsistent terminology for TracLinks pointing to the repository browser

*

Ryan J Ollos wrote:
> Is there a reason we would not want to add this to the Trac help page [1],
> noting that browser: is an alias for source:, and suggest deprecating the
> use of source:?  Or perhaps for 0.12 just mention the browser: prefix for a
> TracLink and not mention the source: prefix for a TracLink?

I prefer keeping both. I use source: when linking to a file, and
browser: to link to a directory.

-- Remy

Re: [Trac-dev] Inconsistent terminology for TracLinks pointing to the repository browser

Remy Blank-2 wrote:
*

> 
> Ryan J Ollos wrote:
> I prefer keeping both. I use source: when linking to a file, and
> browser: to link to a directory.
> 
> -- Remy
> 

Should we update the TracLinks documentation page then to specify the
aliases for source?  Would you also want to include `repos` in the
documentation?

-- 
View this message in context: http://old.nabble.com/Inconsistent-terminology-for-TracLinks-pointing-to-the-repository-browser-tp27485031p27486628.html
Sent from the Trac Dev mailing list archive at Nabble.com.

--

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

Re: [Trac-dev] Inconsistent terminology for TracLinks pointing to the repository browser

Also, looks like we probably want to update [2], rather than the link I
initially mentioned [1] since Christian has been working on a page update.

[1] http://trac.edgewall.org/wiki/TracLinks
[2] http://trac.edgewall.org/wiki/0.12/TracLinks
-- 
View this message in context: http://old.nabble.com/Inconsistent-terminology-for-TracLinks-pointing-to-the-repository-browser-tp27485031p27486640.html
Sent from the Trac Dev mailing list archive at Nabble.com.

--

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