whups

Hello!
I have some problems about whups.
How can I create the querys in Query Builder for period (I mean from one date to another)?

Thanks,
nmark

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org

Re: whups

Quoting Natalia Markova <N.Markova <at> vaz.ru>:

> I have some problems about whups.

This is the list for chora ...

> How can I create the querys in Query Builder for period (I mean from  
> one date to another)?

Date search isn't implemented yet.

-chuck
--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org

large numbers of repos

hi.

I was trying to find a way to view a large number of repos easily, but
(atleast with subversion) it appears that I have to create a different
sourceroot for each repo.   As it is we currently have over 50 repos, so
the text list created for the "Other Repositories" was rather long.  I
would prefer to have it look like cvs.horde.org, but couldn't figure out
how to do that.  Suggestions would be handy.

In the meantime I made a makeshift patch to chora/lib/Chora.php that makes
dealing with a large number of different repo a bit easier.  I realize this
isn't the ideal horde way of doing it (If i had the time I would try and
make it behave more like IMP's folder selection in the top right of the
page) but it is functional and useful in this form.

-greg

(See attached file: libchora.patch)

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org

Re: large numbers of repos

Zitat von Greg_Swift <at> aotx.uscourts.gov:

>
> hi.
>
> I was trying to find a way to view a large number of repos easily, but
> (atleast with subversion) it appears that I have to create a different
> sourceroot for each repo.   As it is we currently have over 50 repos, so
> the text list created for the "Other Repositories" was rather long.  I
> would prefer to have it look like cvs.horde.org, but couldn't figure out
> how to do that.  Suggestions would be handy.

cvs.horde.org has only one repository.

> In the meantime I made a makeshift patch to chora/lib/Chora.php that makes
> dealing with a large number of different repo a bit easier.  I realize this
> isn't the ideal horde way of doing it (If i had the time I would try and
> make it behave more like IMP's folder selection in the top right of the
> page) but it is functional and useful in this form.

The patch is reverse. Beside that, I think it's a good idea to turn  
the source roots list into a drop down list for a large number of  
repos. This could happen at a certain threshold, like more than 3 or 4  
repos. If you are willing to provide such a patch - against the CVS  
HEAD version of Chora - please put it on bugs.horde.org.

Jan.

--

-- 
Do you need professional PHP or Horde consulting?

Re: large numbers of repos

chora-bounces <at> lists.horde.org wrote on 07/29/2007 05:27:57 AM:

> Zitat von Greg_Swift <at> aotx.uscourts.gov:
>
> >
> > hi.
> >
> > I was trying to find a way to view a large number of repos easily, but
> > (atleast with subversion) it appears that I have to create a different
> > sourceroot for each repo.   As it is we currently have over 50 repos,
so
> > the text list created for the "Other Repositories" was rather long.  I
> > would prefer to have it look like cvs.horde.org, but couldn't figure
out
> > how to do that.  Suggestions would be handy.
>
> cvs.horde.org has only one repository.

thats what I was afraid of...

> > In the meantime I made a makeshift patch to chora/lib/Chora.php that
makes
> > dealing with a large number of different repo a bit easier.  I realize
this
> > isn't the ideal horde way of doing it (If i had the time I would try
and
> > make it behave more like IMP's folder selection in the top right of the
> > page) but it is functional and useful in this form.
>
> The patch is reverse. Beside that, I think it's a good idea to turn