update! closing in on 0.2 release; please give it a drive

5 views
Skip to first unread message

Alan Runyan

unread,
Dec 16, 2011, 12:59:24 PM12/16/11
to ptahp...@googlegroups.com
The code has stabilized.  And we should have a 0.2 release next week.
We depend on pyramid 1.3a1 or greater.  It works with Python 3.

There is now only 1 scaffolding, ptah_starter which can be used:
$ bin/pcreate -t ptah_starter myapp

We are starting to concentrate on documentation.  I have gutted the documentation.

api autodoc is now working.

Please give it 10 minutes of your time.

You should be able to get Ptah + Model Example + User Management in < 120 seconds.

Install ptah
----------------
- run setup.py develop

Install ptah_crowd
--------------------------
- run setup.py develop

Install ptah_models from examples
--------------------------------------------------
- cd examples/ptah_models
- run setup.py develop

in ptah_models edit settings.ini add `ptah_crowd` to pyramid.includes

$bin/pserve settings.ini 

voila. a simple models app + user management.

there are 3 examples (previously were scaffolds) which you can use.

--
Alan Runyan
Office +17135305244 | Skype/Twitter @runyaga
President of Enfold Systems | http://www.enfoldsystems.com/
Co-founder of the Plone CMS | Free Plone site in less than 10 seconds - http://ploud.com/

Carlos de la Guardia

unread,
Dec 19, 2011, 5:21:09 PM12/19/11
to ptahp...@googlegroups.com
Hi,

tried this during the weekend. In general I got it running OK. There's
a traceback that comes when you want to use the layout preview
feature. This is because on this file:

ptah/ptah/manage/layout.py

Line 5 is currently commented out and that defines PyramidView, which
is expected to be there on line 32.

Carlos de la Guardia

Nikolay Kim

unread,
Dec 19, 2011, 5:33:05 PM12/19/11
to ptahp...@googlegroups.com
On Mon, 2011-12-19 at 16:21 -0600, Carlos de la Guardia wrote:
> Hi,
>
> tried this during the weekend. In general I got it running OK. There's
> a traceback that comes when you want to use the layout preview
> feature. This is because on this file:
>
> ptah/ptah/manage/layout.py
>
> Line 5 is currently commented out and that defines PyramidView, which
> is expected to be there on line 32.
>

we removed pview, so layout preview doesnt work yet.


Wouter Vanden Hove

unread,
Dec 20, 2011, 5:46:55 AM12/20/11
to ptahp...@googlegroups.com
On 19-12-11 23:33, Nikolay Kim wrote:
> we removed pview, so layout preview doesnt work yet.

The reason for me to look at Ptah, is to have some kind of framework
to create a decent UI on top of pyramid (think main_template, reusable
code-snippets, macro's, layouts)

Yesterday I noticed bottle_cap
https://github.com/pauleveritt/pyramid_bottlecap

So now we have two layout-implementations?
Is there any duplicated effort here regarding the layout-system?
Are there synergies possible?
Just asking.


Greets
WouterVH

Paul Everitt

unread,
Dec 20, 2011, 7:53:23 AM12/20/11
to ptahp...@googlegroups.com

There probably are. Up to now it has been premature for us to try. Both KARL and Ptah have been iterating through changes in what they're trying to do on layouts and how they are trying to do it.

Yesterday we got the +1 from OSF (the customer) to put a bunch of resources into Bottlecap-ifying KARL. At the same time, Chris Rossi is finishing a big refactoring this week. We can then write up Bottlecap's layout approach and let Ptah see if it overlaps.

I know Alan had some ideas for layouts (e.g. placeful overrides) that we didn't have. We likely have some things that don't fit his ideas as well.

--Paul

Alan Runyan

unread,
Dec 20, 2011, 9:40:59 AM12/20/11
to ptahp...@googlegroups.com, ptahp...@googlegroups.com

I agree with Wouter. I want Ptah to share a UI layer so programmers can make something reasonably nice looking without much thought. This has not been accomplished.

I will document Ptah layouts before Xmas. The main features of Ptah layouts:
Ptah.layout does not depend on zpt, mako, jinja
The resulting value of a layout call is (HTML) which is included by the next outer layout.
The inner-most layout is computed and it's HTML passed to next outer layout
The inner to outer passing HTML string from layout/view to the next is simple and fast.
A nice side effect is by the time you compute HEAD you know all requirements to satisfy (js, CSS, etc) which need inclusion to make page work (reason ptah.library works naturally using this approach)

Also need to give credit to Nikolay. This layout system was done in previous project he worked on.

Wouter it is useful to get feedback. What fits your brain? ptah.layout? Bottlecap?

Cheers
Alan

Reply all
Reply to author
Forward
0 new messages