Mercurial@Turbogears, second stage

[Alexandru Marinescu]

Hi,

I managed to create an alpha of the registration extension which can
be found at:
http://gsoc.turbogears.org/hg/tgext.registration or on BitBucket @
http://bitbucket.org/alexandru_marinescu/tgextregistration

I will have to perform some live tests(when I developed it I had some
problems with the access to an SMTP server and now I'm waiting for an
account on a server were I will have access to a mail server) to be
sure that it works as it should. I will also like to add tw.captcha to
the registration form and if I find some time probably OpenID.


Now I've started working on the second stage of the project, which
will have provide hgweb like functionalities inside a turbogears
extension. For this I have to following two alternatives:
1. Use some of hgweb code, inherit class, modify behaviours(but this
will be quite hard since hgweb wasn't design with true MVC in mind)
2. Proxy hgweb and provide it with an integration with genshi or mako
(Jorge's codemill proxies hgweb and I've seen some projects in the
Django community which do the same think. If I'm not wrong BitBucket
works in a similar way).

Which of the two options would fit better the project?


Regards,
Alexandru Marinescu

[Jorge Vargas]

On Sat, Jul 4, 2009 at 6:30 PM, Alexandru
Marinescu<almar...@gmail.com> wrote:
>
> Hi,
>
> I managed to create an alpha of the registration extension which can
> be found at:
> http://gsoc.turbogears.org/hg/tgext.registration or on BitBucket @
> http://bitbucket.org/alexandru_marinescu/tgextregistration
>
> I will have to perform some live tests(when I developed it I had some
> problems with the access to an SMTP server and now I'm waiting for an
> account on a server were I will have access to a mail server) to be
> sure that it works as it should. I will also like to add tw.captcha to
> the registration form and if I find some time probably OpenID.
>
>
> Now I've started working on the second stage of the project, which
> will have provide hgweb like functionalities inside a turbogears
> extension. For this I have to following two alternatives:
> 1. Use some of hgweb code, inherit class, modify behaviours(but this
> will be quite hard since hgweb wasn't design with true MVC in mind)

correct.

> 2. Proxy hgweb and provide it with an integration with genshi or mako
> (Jorge's codemill proxies hgweb and I've seen some projects in the
> Django community which do the same think. If I'm not wrong BitBucket
> works in a similar way).

That is correct, it's the approach everyone has taken, even BB.

there is a 3. which is to start from scratch calling the hg (not
hgweb) code using the same core functions the CLI client uses.

[Alexandru Marinescu]

I will use the codemill code base and create a genshi templater so that user can easily define their own templates. I will also try to find a way to provide easy access to hg related variables, so that user can have easy access to the information they need about repositories and other mercurial related things.

--
Alexandru Marinescu