#3506 Allow tracd to serve projects from the URL root

I've added an updated patch for #3506 which changes the option name to
"--single-env" (pacopablo's patch used "--serve-root") for serving a
single project without the project list page.  This was suggested for
postponement to 0.10.1 in order to establish a feature freeze.  So, two
questions:

 * should I go ahead and commit it, or wait until after 0.10?
 * any opinions on the name of the option?

-- Matt Good

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Re: TracPerforce-0.4.1

Re: TracPerforce-0.4.1

Mike.Gee <at> bell.ca wrote:
> I have tried the new TracPerforce 0.4.2 install with the same results as below. I was able to successsfully
build the p4python P4Client.so using the p4api for /r05.2/bin.linux24x86-rhel3 but am unclear on how I
can use these libs for the PyPerforce build.
>  
> From your advice below, it appears I need to build PyPerforce/src/perforce/api.so using the same
version of the api as above?  Can you provide direction on how to do that? 
>  
> Thanks
>  
> Mike

Mike,

Under the PyPerforce source tree there is a third-party/p4api directory.
You simply need to unpack the p4api.tar you downloaded from the Perforce
website into the corresponding platform's subdirectory and rebuild.

There should be some instructions for building for other platforms on:
http://pyperforce.sourceforge.net/doc/installing.html

Hope that helps.

Cheers,
Lewis.

--

-- 
Lewis Baker                                               I-SiTE
Software Engineer                               3D Laser Imaging
Phone  : +61 8 8338 9222
Fax    : +61 8 8338 9229
Email  : lewis <at> isite3d.com.au         http://www.isite3d.com.au/

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Moin-like table colspan syntax (patch)

I've added colspan wiki syntax like this :

||||||3 colimns span||
||||2 cols span||---||
|| -1- || -2- || -3- ||

if it is ok I'd like to add more moin-style syntax. Whatche think?

Patch:

Index: C:/work/workspace/trac/wiki/formatter.py
===================================================================
--- C:/work/workspace/trac/wiki/formatter.py	(revision 3710)
+++ C:/work/workspace/trac/wiki/formatter.py	(working copy)
@@ -221,6 +221,7 @@
         r"(?P<indent>^(?P<idepth>\s+)(?=\S))",
         # || table ||
         r"(?P<last_table_cell>\|\|\s*$)",
+        r"(?P<table_cell_colspan>\|\|\|+)",
         r"(?P<table_cell>\|\|)"]

     _processor_re = re.compile('#\!([\w+-][\w+-/]*)')
@@ -668,6 +669,17 @@
         else:
             self.in_table_cell = 1
             return '<td>'
+
+    def _table_cell_colspan_formatter(self, match, fullmatch):
+        self.open_table()
+        self.open_table_row()
+        tdspan = '<td colspan=%d>' % (len(match)/2)
+        if self.in_table_cell:
+            return '</td>'+tdspan
+        else:
+            self.in_table_cell = 1
+            return tdspan
+        

     def open_table(self):
         if not self.in_table:

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

WikiFormatting: add colspan (patch)

I'm very impressed by this project now begin to use it. To feel more
confortable with it I want to add some moinmoin wiki syntax I'm used
to; for example, this patch I do use adds colspan syntax like

||||colspan-2||
||col1||col2||

I would like to add some more syntax if this one is ok:

trunk/trak/wiki/formatter.py

Index: C:/work/workspace/trac/wiki/formatter.py
===================================================================
--- C:/work/workspace/trac/wiki/formatter.py	(revision 3710)
+++ C:/work/workspace/trac/wiki/formatter.py	(working copy)
@@ -221,6 +221,7 @@
         r"(?P<indent>^(?P<idepth>\s+)(?=\S))",
         # || table ||
         r"(?P<last_table_cell>\|\|\s*$)",
+        r"(?P<table_cell_colspan>\|\|\|+)",
         r"(?P<table_cell>\|\|)"]

     _processor_re = re.compile('#\!([\w+-][\w+-/]*)')
@@ -668,6 +669,17 @@
         else:
             self.in_table_cell = 1
             return '<td>'
+
+    def _table_cell_colspan_formatter(self, match, fullmatch):
+        self.open_table()
+        self.open_table_row()
+        tdspan = '<td colspan=%d>' % (len(match)/2)
+        if self.in_table_cell:
+            return '</td>'+tdspan
+        else:
+            self.in_table_cell = 1
+            return tdspan
+        

     def open_table(self):
         if not self.in_table:

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

#3692 - [PATCH] - Enable Generic use of INavigationContributor

This is a tiny non-destructive patch, which will enable flexible
additions of navigation bars.

http://trac.edgewall.org/ticket/3692

A few tiny css / cs additions would follow, I hope those can be
included into the 0.10 source-code base.

Is it enouth to file a patch ticket, or should I notify the development
list additionally?

.

--
http://lazaridis.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
-~----------~----~----~----~------~----~------~--~---

Re: #3692 - [PATCH] - Enable Generic use of INavigationContributor

-On [20060910 04:00], Ilias Lazaridis (ilias <at> lazaridis.com) wrote:
>Is it enouth to file a patch ticket, or should I notify the development
>list additionally?

Submitting the patch is good enough.

If the ticket tracking software developers cannot bother to check their own
tickets in the system, it would be a waste of effort anyway, methinks. :)

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/
Tomorrow's battle is won during today's practice...

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Re: Moin-like table colspan syntax (patch)

Patches should be attached to a ticket in Trac and please avoid posting
duplicate messages to the list.

There is a ticket for colspan where you can attach this:
http://trac.edgewall.org/ticket/1293

-- Matt Good

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Track and SVN

Hello,

Ive installed track on www.aaaa.com and I have SVN installed on
www.bbbb.net, can any body please let me know how I can give path to
SVN to trac installation on www.aaaa.com.

Thanks in advance

Rigs
Saurabh

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Re: Track and SVN

On 9/12/06, saurabhperiwal <at> gmail.com <saurabhperiwal <at> gmail.com> wrote:
> Ive installed track on www.aaaa.com and I have SVN installed on
> www.bbbb.net, can any body please let me know how I can give path to
> SVN to trac installation on www.aaaa.com.

If these are physically separate servers (as opposed to two domains
running on the same server), this is not currently possible. You need
to run Trac on the same machine as Subversion. See ticket #493 on
trac.edgewall.org.

Regards,

Manuzhai

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---