On Mon, Mar 30, 2009 at 10:20 AM, mr.freeze <[email protected]> wrote:
>
> The rationale was having the ability to manipulate the DOM from a
> controller dynamically based on request variables.
What prevents you from doing this sort of thing in the biew? What makes
this better?
For example - take flash(): It does not say _where_ it will be displayed,
not the color, etc. --- it is only logical.
So my question is, why do you need DOM manipulation at controller level?
Why are you not doing logical manipulation, and a DOM module for use by
view which sets, handles view aspects.
Another way to state this: At controller, it makes sense to me to say
something that looks like:
emphasis('some message');
What empahsis does (color, small, big) - e.g. implementation details of
emphasis - I cannot see what advantage there is to push this into
controller. In fact, I see much coupling, and many reasons to NOT do that.
I still do not see any good motivation for this.
- Yarko
> For example, say
> you had three input fields on a form, City, State and Zip. When the
> user submits the form, each piece of data is validated against it's
> relationship with the other pieces i.e., is the City in the Zip, is
> the City in the State, is the Zip in the State? Once the offending
> piece of data is found, I want to use jQuery's animate function to
> slightly shrink the pieces that are good and turn their backgrounds
> green. For the data that is bad, I want to use the animate function to
> make the field bigger and turn it's background red.
>
> On Mar 30, 9:23 am, Yarko Tymciurak <[email protected]> wrote:
> > On Mon, Mar 30, 2009 at 5:40 AM, notabene <[email protected]> wrote:
> >
> > > On 30 Mar., 09:13, Yarko Tymciurak <[email protected]> wrote:
> > > > On Mon, Mar 30, 2009 at 1:58 AM, notabene <[email protected]>
> wrote:
> >
> > > > > Thumbs up. Very good idea!
> >
> > > > > We have had the discussion around MVC. And the conclusion were,
> that
> > > > > there is no clear-cut border between MVC. No perfect or true
> division.
> >
> > > > I think maybe you missed some point of the discussions on division...
> > > one
> > > > discussion was about where to define forms.
> >
> > > > I do not think it is ever a good idea to include color settings in
> > > > controller / business logic...
> >
> > > As it is right now You can put color-settings in controllers!
> > > I Agree that color-settings hardly never belongs in a controller, but
> > > the example from mr.freeze is just a simple example. I believe you
> > > could as well put business logic into the script.
> >
> > > Regards Niels Bjerre
> >
> > I still don't understand what the motivation for this is... if the
> example
> > is not an example of what makes this more useful than what can be done
> now,
> > then then I'd like to see one...
> >
> >
> >
> > > > Yarko
> >
> > > > > (Java-) scripting functionality in controllers can ease the way for
> > > > > AJAX forms and functionality in views.
> >
> > > > > On 30 Mar., 06:15, mdipierro <[email protected]> wrote:
> > > > > > Some clarifications.
> > > > > > Right now one can already do this in views by inserting
> somewhere:
> >
> > > > > > <script>
> > > > > > $(document).ready(function() { do_something(); });
> > > > > > </script>
> >
> > > > > > Mr. Freeze's suggestions has pros and cons. In my opinion:
> >
> > > > > > Pros:
> > > > > > - it is more compact
> > > > > > Cons:
> > > > > > - moves into the controller something that (usually) belongs
> to
> > > the
> > > > > > view.
> > > > > > - if the script in quotes has a bug it may break web2py_ajax
> > > > > > because everything would go in the same
> $(..).ready(function(){}).
> >
> > > > > > I would like to hear more opinions about this. Perhaps some
> examples
> > > > > > when this would be better than placing the code in the view.
> >
> > > > > > Massimo
> >
> > > > > > On Mar 29, 10:46 pm, Jason Brower <[email protected]> wrote:
> >
> > > > > > > Good question.
> > > > > > > I like the idea as it gives us a nice place to put scripts and
> make
> > > > > them
> > > > > > > apply to the views we want very easily. so +1 on that!
> > > > > > > Regards,
> > > > > > > Jason Brower
> >
> > > > > > > On Sun, 2009-03-29 at 20:23 -0700, mr.freeze wrote:
> > > > > > > > It's basically a new global list, response.scripts, that is
> > > rendered
> > > > > > > > in the jQuery(document).ready function so you can inject
> > > javascript
> > > > > > > > from the controller. Massimo mentioned that it may go
> against
> > > MVC
> > > > > > > > separation standards and wanted me to put it out here to get
> a
> > > few
> > > > > > > > opinions. Sample usage:
> >
> > > > > > > > def index():
> > > > > > > > if not request.vars.name:
> > > > > > > >
> response.scripts.append("$('#messages').text('Messages:
> > > Name
> > > > > > > > Missing').css('color','red');")
> > > > > > > > else:
> > > > > > > >
> response.scripts.append("$('#messages').text('Messages:
> > > Hello
> > > > > > > > " + request.vars.name + "');")
> > > > > > > > return dict()
> >
> > > > > > > > What do you think?
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
