Re: Announcement: django-quickview 0.3 - putting the nitro in rapid web development

On Thu, Feb 28, 2013 at 4:10 PM, Tom Evans <tevans.uk@googlemail.com> wrote:
> On Wed, Feb 27, 2013 at 7:39 PM, Thomas Weholt <thomas.weholt@gmail.com> wrote:
>> pypi : https://pypi.python.org/pypi/django-quickview/
>> Source at https://bitbucket.org/weholt/django-quickview
>>
>> Documentation and tutorial at
>> https://bitbucket.org/weholt/django-quickview/src/fde97a0a0befaeda0ab2317035f8e7cd9c311511/docs/basic.md?at=default
>> for details.
>>
>> Bring on the flames ;-)
>>
>
> Not a flame :)
>
> It would be cooler if you did not have to pollute model classes by
> decorating them with view information. I'd prefer to denote that
> FooModel has fast views *not* in models.py :)

There's an option NOT to use the decorator and keep the ModelViews in
views.py allready as shown in the documentation. I'm going to improve
the decorating options a little bit, but I agree it's nicer to
seperate code related to model and view.

>
> For updating instances, you could make it compulsory to list the
> changed attributes. Then, only the listed attributes are updated.

I've updated the api today so that you can provide just the params you
want to update. It requires a call to the server to get the existing
values, but that can also be avoided by providing the update-call with
a dictionary with the existing values.

>
> Apart from that, looks great. Will probably use this as scaffolding in
> my next HTML5 app.

That's great news. It's still bit of a proof-of-concept thing, but it
has allready saved me lots of time and the coming improvements planned
for version 0.4 will make it even nicer, especially for HTML5 apps
focusing heavy on javascript and dynamic web pages.

My two main concerns are speed and if there are any part of the
implementation that's dangerous in regards to threads, concurrency
etc.

>
> Cheers
>
> Tom



--
Mvh/Best regards,
Thomas Weholt
http://www.weholt.org

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.