I'd be interested in seeing that :-)
On Jun 30, 2011 9:02 PM, Eric Rasmussen ericrasmus...@gmail.com wrote:
Hi Kristian,
For UI-intensive applications I like to go the ajax route. It works well
because Pyramid can focus on tasks like security, validation and
processing
of data, and updating
yeah pyramid works fine for rich ui's. my day job uses gwt for the front end
and pyramid for the back.
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To view this discussion on the web visit
On Thu, Jun 30, 2011 at 11:02 PM, Eric Rasmussen ericrasmus...@gmail.comwrote:
I've been stalling for months on writing a tutorial to demonstrate how you
can structure a UI-rich application with Pyramid, partly because it'd rely
heavily on YUI for the client-side features, and that's not
for RIA i strongly recommend looking at qooxdoo. it is awesome and
supporting mobile platforms.
On Jul 1, 12:43 am, Kristian Benoit kristian.ben...@gmail.com wrote:
I'm not so familiar with web development and am currently writting a social
network like app using pyramid.
It seems to me that
I'd be very interested in seeing that.
As a Pyramid first-timer, I find the documentation itself to be very solid.
What I miss are the cookbook-style blog posts which spring up when projects
have been around for a long time (How to do X with Pyramid). So, any such
tutorials would be very much
On Sat, 2011-07-02 at 00:57 +0100, Benjamin Sims wrote:
I'd be very interested in seeing that.
As a Pyramid first-timer, I find the documentation itself to be very
solid. What I miss are the cookbook-style blog posts which spring up
when projects have been around for a long time (How to do
Thanks Chris, I should have said that I have used the cookbook ('Making A
“User Object” Available as a Request Attribute' was very useful). I just
wanted to encourage further work along those lines.
As an example, I have just been adding database-based authentication. I have
worked it out I
On Sat, 2011-07-02 at 01:14 +0100, Benjamin Sims wrote:
Thanks Chris, I should have said that I have used the cookbook
('Making A “User Object” Available as a Request Attribute' was very
useful). I just wanted to encourage further work along those lines.
As an example, I have just been
On Jul 1, 5:36 pm, Chris McDonough chr...@plope.com wrote:
On Sat, 2011-07-02 at 01:14 +0100, Benjamin Sims wrote:
I understand that Pyramid deliberately doesn't specify these things
and I don't expect hand holding - just adding my encouragement from a
relative newbie perspective.
Sure.
I'm not so familiar with web development and am currently writting a social
network like app using pyramid.
It seems to me that setting a renderer (inheriting a global layout) to a
view and passing a few variables to modify the content of that renderer, is
a little limited. I was inspired by the
Hi Kristian,
For UI-intensive applications I like to go the ajax route. It works well
because Pyramid can focus on tasks like security, validation and processing
of data, and updating the database, while only returning the minimal amount
of information the client-side application needs to
11 matches
Mail list logo
