Broke - a Django porting to Javascript
Hi everyone, this is David and I'd like to show you my last project. Since I needed an MVC framework for my JS projects and all the solutions out there didn't really fit me, I tried to port Django to Javascript. You can have a look at the project here: http://github.com/brokenseal/broke So far I port: - a simple request/response system - models (not yet fields) - managers - two query systems: local and remote (the latter does not work yet) - url resolving system - middlewares - context processors - a simple template system, very similar to the one Django uses - views - pre_save and post_save signals (events) It's still very early to use it anywhere in production but I'm working on it pretty much every day and I'd like to know what you think about it. You can have a look at a simple demo I've put online, using Django on the server side: http://demo.brokenseal.it/ I realize that the documentation should be rewritten completely, since for now it's a rip-off of the actual Django documentation, if you have any complaint about it please feel free to contact me. There is still a lot to do, anyone whom would like to help is welcome. Cheers, David -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: dict object is not callable (newforms/forms.py full_clean)
I got the same problem in a different context:
Exception Type: TypeError
Exception Value:'dict' object is not callable
Exception Location: /usr/lib/python2.4/site-packages/Django-0.95.1-
py2.4.egg/django/newforms/forms.py in full_clean, line 180
Can someone help?
On 5 Feb, 11:29, Antonio <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm trying to use a ManyToManyField between two tables ... the models are
> this:
>
> class Rim(models.Model):
> nome = models.CharField(maxlength=30)
>
> def __str__(self):
> return self.nome
>
> class Previsione(models.Model):
> nave = models.CharField(maxlength=50)
> data = models.DateField()
> grt = models.PositiveSmallIntegerField()
> naz = models.CharField(maxlength=10)
> h_inizio = models.TimeField()
> rims = models.ManyToManyField(Rim)
>
> into te views.py:
>
> def previsione(req, varid=None):
> if req.method == 'POST':
> myform = nf.models.form_for_model(Previsione)(req.POST)
>
> if myform.is_valid():
> dati = Previsione(**myform.clean_data)
> dati.save()
>
> return HttpResponseRedirect('.')
> else:
> if varid is None:
> myform = nf.models.form_for_model(Previsione)()
> else:
> instance = get_object_or_404(Previsione, pk=varid)
> myform = nf.models.form_for_instance(instance)
>
> return render_to_response('create_form.html', \
> { 'titolo': 'Archivio Previsioni',
> 'form': myform.as_table() })
>
> when I'm trying to save the form (with one or many rims selected) I've this
> error:
>
> Exception Type: TypeError
> Exception Value: 'dict' object is not callable
> Exception Location:
> /usr/local/python2.5/site-packages/django/newforms/forms.py
> infull_clean, line 167
>
> [EMAIL PROTECTED]: django_src# svn update
> At revision 4459.
>
> can someone help me ?
>
> tanks in advance ... and sorry for my english
>
> --
> #include
> int main(void){char
> c[]={10,65,110,116,111,110,105,111,32,98,97,114,98,111,110,
> 101,32,60,104,105,110,100,101,109,105,116,64,116,105,115,99,97,108,105,110,101,
> 116,46,105,116,62,10,10,0};printf("%s",c);return 0;}
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
FlatPage and Internationalization
Hi everyone, lately i was trying to internationalize a wesite which had flatpages, but i also needed to translate those pages so i came up with this idea to get site specific AND language specific flatpages. I put on the FlatPage class this attribute: language= models.CharField(maxlength= 7, choices= settings.LANGUAGES) and in the view i modified this line f = get_object_or_404(MyFlatPage, url__exact=url, sites__id__exact=settings.SITE_ID) to look like this if = get_object_or_404(MyFlatPage, url__exact=url, sites__id__exact=settings.SITE_ID, language= request.LANGUAGE_CODE) What do you think? With this changes, you'll be able to retrieve site specific and language specific flatpages. While i was thinking about, it 've been wondering why no one else ever thought about it and I thought it'd been a good idea to share this code. What do you think? Could it be an upgrade for django flatpages module? Did I miss something or someone else already thought about it? Let me know. Cheers, David --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: FlatPage and Internationalization
Sorry, that shouldn't be MyFlatPage but just FlatPage... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: FlatPage and Internationalization
That's what i am about to do, but if guys from the development team agree we could implement it in the official django code On Nov 9, 3:34 pm, Eugene Morozov <[EMAIL PROTECTED]> wrote: > I've implemented similar system. Only I have used MyFlatPage and > MyFlatPageTranslation models, because it makes easier to locate and > translate pages in the admin interface. > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Problems with extra_context in generic date base views
Hello to everyone,
I'm quite new so please go easy on me.
I already searched on the mailing list but couldn't find a good answer for
my problem.
I am writing a project for a website where i retrieve events from a
database, together with them I need, on the same page, to show a list of
banners, taken from an other model other than the one regarding the events.
Here is the code:
-
class CampagnaPubblicitaria(models.Model):
...
sponsor= models.ForeignKey(Sponsor)
def in_campagna(self):
#determina il periodo della campagna pubblicitaria
oggi= datetime.toordinal(TODAY)
data_inizio_campagna_ord=
datetime.toordinal(self.data_inizio_campagna)
if data_inizio_campagna_ord<= oggi <=
(data_inizio_campagna_ord+ self.durata_campagna):
return True
else:
return False
...
class Sponsor(models.Model):
banner= models.ForeignKey(Banner)
...
-
Now, I am using django own generic date based views and i am trying to
pass as an extra_context value this:
banner_list=
Banner.objects.filter(sponsor__campagnapubblicitaria__in_campagna=
True).order_by('?')[:6]
evento_index_info_dict= {
'queryset': Evento.objects.all(),
'date_field': 'data_di_inserimento',
'extra_context': {'banner_list': banner_list}
}
But when i try to have a look at the page, i get this error:
---
TypeError at /
Cannot resolve keyword 'in_campagna' into field
---
Is that because the QuerySet doesn't actually evaluate the value of
in_campagna for every record of the database? Is there any other way to do
the same job, other than writing a huge filter? ^^'
And, am I wrong i pass the extra_context in a "urls" context rather than a
"view" context? Is there any other way to write extra_context for the
template other than write it directly on the urls.py code?
Thanks in advance if anyone will have the patience to understand what i
wrote and the patience to reply me.
Regards,
David
--
Brokenseal di Callegari Davide
Le informazioni contenute in questo messaggio di posta elettronica sono
riservate e confidenziali e ne e' vietata la diffusione in qualunque modo
eseguita. Qualora Lei non fosse la persona a cui il presente messaggio e'
destinato, La invitiamo ad eliminarlo e a non utilizzare in alcun caso il
suo contenuto, dandone gentilmente comunicazione al mittente.
The information contained in this e-mail and any attachments is
confidential and may well also be legally privileged. If you are not among
the named recipients, please notify the sender immediately by reply e-mail
and then delete this message from your system, do not use the contents for
any purpose whatsoever nor disclose them to anyone else.
Rif. D.L. 196/2003.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
404 on date based archives
Hi everyone, I keep on getting a weird problem on my project.
I use date based generic views to retrieve events for a web site, when I
use archive_index and archive month no problems, but when i use
archive_day or detail_object I keep on getting a 404.
I searched over the mailing list to find someone else who has got the same
problem as mine, Jare Zgoda, but he used to use SQLite and I am using
MySQL with a correct time zone setting.
Here is the code:
---
detail_info_dict= {
'queryset': Evento.objects.all(),
'date_field': 'pub_date',
'extra_context': general_extra_context,
'allow_future': True,
'month_format': '%m',
}
general_info_dict= {
'queryset': Evento.objects.all(),
'date_field': 'pub_date',
'extra_context': general_extra_context,
'allow_future': True,
'allow_empty': True,
'month_format': '%m',
}
index_info_dict= {
'queryset': Evento.objects.all(),
'date_field': 'ins_date',
'extra_context': index_extra_context,
'allow_empty': True,
}
urlpatterns= patterns('django.views.generic.date_based',
(r'^(?P\d{4})/(?P\d{1,2})/(?P\d{1,2})/(?P\d{1,10})/$',
'object_detail', detail_info_dict),
(r'^(?P\d{4})/(?P\d{1,2})/(?P\d{1,2})/$',
'archive_day', general_info_dict),
(r'^(?P\d{4})/(?P\d{1,2})/$', 'archive_month',
general_info_dict),
(r'^/?$', 'archive_index', index_info_dict),
)
---
On the "Evento" class I use this code to retrieve the absolute_url of the
events:
---
def get_absolute_url(self):
return "/%s/%s" % (self.pub_date.strftime("%Y/%m/%d"), self.id)
---
Hope anyone can help me...
Thanks in advance,
David
--
Brokenseal di Callegari Davide
Le informazioni contenute in questo messaggio di posta elettronica sono
riservate e confidenziali e ne e' vietata la diffusione in qualunque modo
eseguita. Qualora Lei non fosse la persona a cui il presente messaggio e'
destinato, La invitiamo ad eliminarlo e a non utilizzare in alcun caso il
suo contenuto, dandone gentilmente comunicazione al mittente.
The information contained in this e-mail and any attachments is
confidential and may well also be legally privileged. If you are not among
the named recipients, please notify the sender immediately by reply e-mail
and then delete this message from your system, do not use the contents for
any purpose whatsoever nor disclose them to anyone else.
Rif. D.L. 196/2003.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: MySQLdb problems
Thank you very much Geert, it worked well. Cheers, David On Thu, 13 Jul 2006 19:27:56 +0200, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > > Hi David, > > birrafondaio wrote: > .. >> raise ImproperlyConfigured, "Error loading MySQLdb module: %s" % e >> django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb >> module: cannot import name ImmutableSet >> --- >> >> I already searched for people with similar problems as mine but can`t >> find any solution. >> I`ve already installed mysql and mysql-python but nothing seems to >> work, can someone help me please? I`m getting desperate, any help will >> be much appreciated. > .. > > This has been discussed here before. You probably upgraded MySQLdb over > an > older version. You need to remove set.py from the MySQLdb 1.2.1 > installation. > > I reported it here: > http://sourceforge.net/tracker/index.php?func=detail&aid=1445105&group_id=22307&atid=374932 > > Hope this works. > > Cheers, > > Geert > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Port Django to Javascript
Hi folks,
I created a project not long ago and I'm currently maintaining it called
Broke which wants to be a porting to Javascript of
Django https://github.com/brokenseal/broke-client
You can find it featured inside the todomvc project from addy osmani
https://github.com/addyosmani/todomvc (
https://github.com/brokenseal/todomvc for the latest updates from broke )
I think the project itself has a lot of potential but lacks two very
important things: a real documentation and a community.
I'm writing to you all to see if anyone could be interested in taking part
to this project.
Broke currently features a lot of cool stuff such as:
- pythonic classes and models: write stuff like
models.Model.create({
__name__: "todo.models.Task"
,title: models.CharField({ max_length: 200 })
,is_complete: models.BooleanField({ 'default': false })
,update: function(kwargs){
if('is_complete' in kwargs && kwargs['is_complete']) {
this.elements().addClass('done');
} else if('is_complete' in kwargs && !kwargs['is_complete']) {
this.elements().removeClass('done');
}
return this._super(kwargs);
}
});
- django templating: you can basically reuse the same templates you are
currently using server side, with some limitations ( the only supported
tags are if-else, for cycles, ifequal, comment )
- database routing: you can choose to save your object on any data source
you want ( local storage, remote server, a local json object )
Have a look at the code base and let me know what you think.
Anyone? :)
Cheers,
Davide
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/nXspKySFAhQJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
Re: Port Django to Javascript
Thanks for asking, Marcin.
This project started back in 2009 because at that time there was not even a
single js mvc framework around that I liked ( at that time the only ones
around were JavascriptMVC, Jamal and another one, can't remember the name ).
That's the main reason behind this project but there are plenty more than
that.
What I essentially ported to js is the philosophy that we all love and care
for, from Django and a feeling that this is missing on the js communities.
It's like when Django started: why didn't they use Rails? Same reasons here.
Cheers!
Davide
Il giorno giovedì 5 aprile 2012 08:36:03 UTC+2, Marcin ha scritto:
>
> What's the motivation for this project? Who (especially already being
> familiar with python and django) would want to use this, and for what?
>
> On Thu, Apr 5, 2012 at 07:22, DvD wrote:
>
>> Hi folks,
>> I created a project not long ago and I'm currently maintaining it called
>> Broke which wants to be a porting to Javascript of Django
>> https://github.com/brokenseal/broke-client
>> You can find it featured inside the todomvc project from addy osmani
>> https://github.com/addyosmani/todomvc (
>> https://github.com/brokenseal/todomvc for the latest updates from broke )
>>
>> I think the project itself has a lot of potential but lacks two very
>> important things: a real documentation and a community.
>> I'm writing to you all to see if anyone could be interested in taking
>> part to this project.
>> Broke currently features a lot of cool stuff such as:
>> - pythonic classes and models: write stuff like
>>
>> models.Model.create({
>> __name__: "todo.models.Task"
>> ,title: models.CharField({ max_length: 200 })
>> ,is_complete: models.BooleanField({ 'default': false })
>> ,update: function(kwargs){
>> if('is_complete' in kwargs && kwargs['is_complete']) {
>> this.elements().addClass('done');
>> } else if('is_complete' in kwargs && !kwargs['is_complete']) {
>> this.elements().removeClass('done');
>> }
>>
>> return this._super(kwargs);
>> }
>> });
>>
>> - django templating: you can basically reuse the same templates you are
>> currently using server side, with some limitations ( the only supported
>> tags are if-else, for cycles, ifequal, comment )
>> - database routing: you can choose to save your object on any data
>> source you want ( local storage, remote server, a local json object )
>>
>> Have a look at the code base and let me know what you think.
>> Anyone? :)
>>
>> Cheers,
>> Davide
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/django-users/-/nXspKySFAhQJ.
>> To post to this group, send email to django-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-users?hl=en.
>>
>
>
>
> --
> Marcin Tustin
> Tel: 07773 787 105
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/X3MyD7pFJhAJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
Re: Port Django to Javascript
Hey, is no one is really interested in helping in this project? -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/kQ_GesNzV7wJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Port Django to Javascript
Actually, I already put together some code that works on node.js inspired by Django, have a look https://github.com/brokenseal/broke My original intention was to create a framework that would work seamlessly on the server and on the client side but it was just too much for me that I left that project aside to concentrate on the client side only with https://github.com/brokenseal/broke-client I'm not asking help to start the project, I'm asking for help to make an already existing project a kick ass open source project with a community around it and I think that this is the right place since we all share Django love :) Il giorno mercoledì 2 maggio 2012 16:11:45 UTC+2, yati sagade ha scritto: > > I am a Django user, but I don't see anything wrong in a JS framework > inspired by Django. Afterall, only great things can inspire. But I fail to > understand why JavaScript has to be only client side - It is a perfectly > valid choice as a server side language for not all, but certainly some use > cases. Besides, the server-side portion and the client-side portions can > share code. I recently wrapped up a project that involved using > Node.js<http://nodejs.org>in the backend, and man how I missed Django there. > The current sane choice > for a web framework on top of Node is Express.js <http://expressjs.com/>(Node > is itself very low level) - which is inspired by > Sinatra <http://www.sinatrarb.com/>, a web development framework(they > call it a DSL) for Ruby. My point is when something inspired by a Ruby > server-side framework can become the de-facto standard choice for the > Node.js community, why not let them taste Django? I personally find the > idea compelling, but *only* if the server-side capabilities of the language > are respected. If we look solely at the client side, no-one would want to > ditch jQuery/Prototype ;) > > Now for the motivation, I would always love to hack together a quick app > using the same language(and importantly, the same mindset) both on the > server and client sides ;) And yes, with the WebWorkers API ported to > work with Node.js > <http://blog.std.in/2010/07/08/nodejs-webworker-design/>(never tried) we are > going to see some serious advancements. > > I understand people's minds have been brutally injured by JavaScript in > the past(I'm one of them), but then it *is* a capable language, and it > doesn't harm if someone is willing enough to bring reusability and > structure to apps written in it by means of a framework. > > Cheers! > > On Wed, May 2, 2012 at 3:02 PM, N.Aleksandrenko > wrote: > >> Why do you want to port django to javascript, there are great js libs >> and frameworks. It will be better to make a js bundle for django >> making in ajax ready. >> Js Tools working out of the box. Such as: >> + ajax upload >> + ajax registration with error handeling >> + ajax pages >> + binding django and a js framework (as backbone) >> + bind django with ad ui library (as jquery ui) >> >> and much more basic stuff >> >> Building the apps with django is still not DRY. If you are a frontend >> developer you can make a bundle to make django better and many people >> may find it helpfull and use it. >> If you decide to start such project ... call :) me i can i will help >> with ideas and code. >> >> >> >> On Wed, May 2, 2012 at 11:51 AM, Gerald Klein wrote: >> > Maybe I missed an earlier post but I am always looking for new projects >> > please explain your requirements. >> > >> > --jerry >> > >> > >> > On Wed, May 2, 2012 at 2:15 AM, DvD wrote: >> >> >> >> Hey, >> >> is no one is really interested in helping in this project? >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups >> >> "Django users" group. >> >> To view this discussion on the web visit >> >> https://groups.google.com/d/msg/django-users/-/kQ_GesNzV7wJ. >> >> To post to this group, send email to django-users@googlegroups.com. >> >> To unsubscribe from this group, send email to >> >> django-users+unsubscr...@googlegroups.com. >> >> For more options, visit this group at >> >> http://groups.google.com/group/django-users?hl=en. >> > >> > >> > >> > >> > -- >> > >> > Gerald Klein DBA >> > >> > contac...@geraldklein.com >> > >> > www.geraldklein.com >> > >> > j...@zognet.com >> > >> > 70
multiple filters on the same (reversed) foreignkey leads to multiple join
A clean project/app in django 1.3 with just two models
from django.db import models
class Base(models.Model):
pass
class Child(models.Model):
base = models.ForeignKey(Base)
flag1 = models.BooleanField()
flag2 = models.BooleanField()
A Queryset with a single use of `.filter` works as expected:
>>> qs = Base.objects.filter(child__flag1=True)
>>> print qs.query
SELECT "t0_base"."id"
FROM "t0_base" INNER JOIN "t0_child"
ON ("t0_base"."id" = "t0_child"."base_id")
WHERE "t0_child"."flag1" = True
but if I start to add additional filters...
>>> qs = qs.filter(child__flag2=True)
>>> print qs.query
SELECT "t0_base"."id"
FROM "t0_base" INNER JOIN "t0_child"
ON ("t0_base"."id" = "t0_child"."base_id")
INNER JOIN "t0_child" T3
ON ("t0_base"."id" = T3."base_id")
WHERE ("t0_child"."flag1" = True AND T3."flag2" = True )
>>> qs = qs.filter(child__flag1=False)
>>> print qs.query
SELECT "t0_base"."id"
FROM "t0_base" INNER JOIN "t0_child"
ON ("t0_base"."id" = "t0_child"."base_id")
INNER JOIN "t0_child" T3
ON ("t0_base"."id" = T3."base_id")
INNER JOIN "t0_child" T4
ON ("t0_base"."id" = T4."base_id")
WHERE ("t0_child"."flag1" = True AND T3."flag2" = True AND
T4."flag1" = False )
I don't think that this is the expected behavior, should I open a new
bug?
david
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
