bootstrap 2

[Nando Florestan]

Hello, I am starting a new project and using Ptah on it. I really like
it.

I am using Ptah because:

- it gives me user management (ptah_crowd) for free
- it gives me nice flash messages
- the layout module is template-language-agnostic, so I can use
Chameleon which is nice but I can also use Genshi which still has
better i18n features
- it uses alembic for sqlalchemy migrations
- the CMS features seem to be really nice, though I won't be requiring
them in this project
- it certainly offers much more stuff of which I am not yet aware.

Concerns:

- Documentation is too shallow and spread over different projects. I
have had to read the code most of the time. By the way, there aren't
enough docstrings.
- Some strings in ptah_crowd are grammatically wrong or simply
inappropriate for my application.
- It is not translated yet (I intend to provide the Brazilian
Portuguese translation, if you will have it).
- In my opinion, Ptah might as well simply have customized Deform; but
at least, I am not forced to use Ptah forms.
- Ptah forces me to use bootstrap. I have discovered that bootstrap is
very good and I am OK with this, but if I weren't, it might have been
a problem because bootstrap is very invasive.

Right now I am really amazed with the features of bootstrap 2.0 which
has just been released this month, and of course I am going to be
using it. I shall customize Deform to output HTML that will be
friendly to bootstrap2. Ptah is still at bootstrap 1.4. Shall we
upgrade it, too?

http://twitter.github.com/bootstrap/upgrading.html

[Nikolay Kim]

> - Documentation is too shallow and spread over different projects. I
> have had to read the code most of the time. By the way, there aren't
> enough docstrings.

yes, thats the problem. we are trying to fix that, but documentation
requires much more work than coding :)

> - Some strings in ptah_crowd are grammatically wrong or simply
> inappropriate for my application.

just send pull requests

> - It is not translated yet (I intend to provide the Brazilian
> Portuguese translation, if you will have it).

we just need help :)
pull requests are welcome.

> - In my opinion, Ptah might as well simply have customized Deform; but
> at least, I am not forced to use Ptah forms.

deform uses colander, we used colander in early days, but in my opinion
colander is too generic. also i think splitting schema definition and
widgets into 2 two decoupled subsystem is wrong.

another reason for ptah.form, we want reuse it. for example
we use ptah.form for ptah setting subsystem, in rest.
and right now i'm working on experimental websocket base content
management ui

> - Ptah forces me to use bootstrap. I have discovered that bootstrap is
> very good and I am OK with this, but if I weren't, it might have been
> a problem because bootstrap is very invasive.

well, thats only for management interface (ptah-manage)
your application ui can use anything.

> Right now I am really amazed with the features of bootstrap 2.0 which
> has just been released this month, and of course I am going to be
> using it. I shall customize Deform to output HTML that will be
> friendly to bootstrap2. Ptah is still at bootstrap 1.4. Shall we
> upgrade it, too?
>
> http://twitter.github.com/bootstrap/upgrading.html

ptah master branch is upgraded to bootstrap2.0 already.
i'm planing to release ptah during week or two, but master is stable.