Tow more cents. This is what I normally do:
Place {{=form}} in the html. Save the generated html from the
browser.
Customize the form using a tool. replace the hidden fields with
{{=form.hidden_fields()}}.
Replace the value="...." with value="{{=form.impval.field}}"
Save it back into the view.
In this way I only need to manipulate the html.
On Jun 29, 12:48 pm, "Hans Donner" <[email protected]> wrote:
> hi guys,
>
> the temperature outside is high enough, so lets try to stay cool here. :-)
>
> for the moment i'm fine with what i can do with web2py, how the framework is
> worked on (frequent updates etc). The latter is why i'm using it.
>
> I've seen various frameworks, with parts i do not like and stuff that i
> liked, as with the tapestry templating. That does not mean that it must also
> be present in web2py, but looking into
> these kind of differences gives me better insights.
>
> Questions like he ones Yarko raises are important, and should be raised and
> answered before development.
>
> For now I consider this as an exhange of ideas and experiences that perhaps
> may become a request for some change, or not.
>
> So to continue on trying to define the problem, I think there is
> a second part as well: does the app (logic) follows from the screens, vice
> versa, or...
> In some cases I start with a rough mockup in html to get some feeling for
> what I need, frequently using html snippets I found somewhere.
>
> ------- Original Message -------
> From: Yarko Tymciurak <[email protected]>
> To: [email protected]
> Sent: 29/06/2009, 18:02:51
> Subject: [web2py:25241] Re: Web2py is not too designer friendly?
>
> I agree w/ Massimo here -
>
> It "feels" like all are jumping into solutions and tools and
> implementations...
>
> What I want to "nail" is the problem, and what (WHAT) we are talking about,
> would like to do,
> and what makes sense and is web2py-ish, pythonic...
>
> So - Hans makes this very good point:
> - to use professional graphic artists, we need a clean way to interface with
> them.
> -- Hans makes suggestions on how things should look, before identifying
> the problem, and how to approach it.
> -- I think the problem (as stated) is "how to give a graphic artist an
> application template which he can work with and see results as he works....
>
> This is where the "no installation" of web2py is really great, but now:
> how do you best prepare a VIEW template of YOUR CURRENT APP for that
> professional graphic designer, and how do you tell him to work with it so
> that you can use the results.
>
> That (I think) is the problem statement.
> I'm not clear what the specific requirements are.
>
> I do NOT think html into the views is necessarily the "correct" or
> desireable solution.
>
> On Mon, Jun 29, 2009 at 10:17 AM, mdipierro <[email protected]> wrote:
>
> > It is a different philosophy. This seems more in line with the Kid/
> > Genshi template language than the web2py template language.
>
> > Massimo
>
> > On Jun 29, 10:08 am, Hans Donner <[email protected]> wrote:
> > > Web2py must stay a python programming framework, and I love the ease
> > > it porvides for a programmer. However, when I want to have great
> > > looking pages re layout etc my design skills are a bit less. So I want
> > > help from somebody who can do great stuff with html, css and jquery
> > > stuff and they prefer tags and javescripts etc, and are less skilled
> > > with python, the part we are great in (and web2py helps us too look
> > > great). And the {{=<insert your favourite pythone code here>}} looks a
> > > bit funny to them, and they cannot use it to generate mockups that we
> > > can easily feed into our web2py app - esp if you have to do some
> > > conversions back and forth.
>
> > > Hence the reference to Tapestry, I'm not quite aware how things are
> > > now, but when I worked with it they had both a good framework for the
> > > programming part and allowed the html guys to work with tags that
> > > their tools understand. So they could produce something like the very
> > > simple:
>
> > > <html>
> > > <head>
> > > <title>Tutorial: HelloWorld</title>
> > > </head>
> > > <body>
> > > <p>The current data and time is: <strong><span jwcid="@Insert"
> > > value="ognl:new java.util.Date()">June 26 2005</span></strong></p>
> > > <p><a href="#" jwcid="@PageLink" page="Home">refresh</a></p>
> > > </body>
> > > </html>
>
> > > The jwcid attributes makes the magic happens, where the html tags
> > > become components that can have certain behaviour. In the example the
> > > @insert will replace the mock value of "june 26 2005" with a realdate.
> > > And yes, the @insert could perhaps be done by some javascript stuff
> > > but that is some other discussion.
>
> > > When they render the file, it looks good in their tool and gives a
> > > sence of how the page will look like. When rendered with the framework
> > > it looks even better, cause of all the dynamic stuff that happens and
> > > data from the db is stuffed into that template.
>
> > > The current custum forms are rendered with
>
> > > {{=form.custom.begin}}
> > > {{=form.custom.widget.somefield}}
> > > {{=form.custom.end}}
>
> > > rendering is nice when run in web2py, but doesn't look like html
> > > anywhere else. This might be more html-friendlier for the source:
>
> > > <form web2py="form.custom.begin">
> > > <input type="text" web2py="form.custom.widget.somefield">
> > > </form>
>
> > > (the form.custom.end is implied by the closing form tag linked to
> > > form.custom.begin, and if the widget for somefiled is say a radiobox,
> > > it will replace the current used text input tag)
>
> > > This way also tables with specific rendering can be made, making use
> > > of the power of the framework to make it into the live site and by
> > > allowing mock data in the html files so the designer will have some
> > > feeling how it looks like.
>
> > > This is not a must, more something I saw somewhere else and what i
> > > liked. For me this does not make web2py into something different what
> > > it is and/or what it should be. It may even be a plugin or so for
> > > web2py.
>
> > > On Mon, Jun 29, 2009 at 3:47 PM, ceej<[email protected]> wrote:
>
> > > > Hi there,
>
> > > > I would just like to say that, web2py is a python programming
> > > > framework not a designing one and it's a lot easier to use than most.
> > > > I can implement the greatest of design that any designer could dream
> > > > up with ease. I do not understand when you say "the html views could
> > > > perhaps bit more html and less python" because they are pure html/css
> > > > when rendered and using the html helpers you can add any ids/classes
> > > > you want which is what you need to integrate a design. (You can also
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
