On 31.08.2011, at 18:15, Stephen Burrows wrote:
>> I found some use cases that are not yet possible with the form rendering
>> template tags. The biggest issue is that it's not possible to exchange field
>> labels with translated text. Currently there is no way of storing a
>> translated
>> strin
> I found some use cases that are not yet possible with the form rendering
> template tags. The biggest issue is that it's not possible to exchange field
> labels with translated text. Currently there is no way of storing a translated
> string in the templates as variable, like {% trans "foo" as va
On 20.08.2011, at 15:59, Gregor Müllegger wrote:
> I found some use cases that are not yet possible with the form rendering
> template tags. The biggest issue is that it's not possible to exchange field
> labels with translated text. Currently there is no way of storing a translated
> string in th
W00t, poking through the source.
On Saturday, August 20, 2011 at 4:59 PM, Gregor Müllegger wrote:
> So after the exams, vacation and a short illness have I completed a week of
> productive work.
>
> All the parts that were discussed in detail on the mailing list a while back
> are implemented.
So after the exams, vacation and a short illness have I completed a week of
productive work.
All the parts that were discussed in detail on the mailing list a while back
are implemented. The new rendering API is completely in place and well tested.
I've manly added more documentation in the last w
Short summary of last week:
The first challenge was to make auxiliary field creation work with
ForeignKey targets. The first attempt was to move parts of the model
preparation mechanics to AppCache.
This turned out to be a dead end because when AppCache is being
populated, while importing models o
My first attempt at auxiliary field creation ended up worse than
expected, it turned out I had to iron out a few other issues, like
concrete model inheritance.
Anyway, I also encountered a problem with ForeignKeys whose target
field is also a ForeignKey. The latter has to be set up first in this
c
Unfortunately I was not very productive in the last week. The reason are the
three exams for this term that kept me busy. The second bad news is that I
will be on vacation for the next week.
So I will definitely need some serious sprinting after I'm back. The admin
will be mainly the target of tha
On Wed, Jul 27, 2011 at 05:05:00AM -0700, akaariai wrote:
> It might be a little late to comment on this, but here is some
> opinions from somebody knowing something (but not much) about the ORM.
> My first feeling is that from the django/db/models/sql/query.py point
> of view it doesn't matter tha
Just a quick note: It could be a good idea to have concrete_fields in
addition to virtual_fields in the Meta class. Concrete fields would be
the fields having a database column directly attached to it, the rest
would be in virtual fields. The fields attribute would be these two
joined together. Thi
On Jul 20, 4:18 pm, Michal Petrucha wrote:
> The last week I've been looking into related fields and all that
> stuff. As it turns out, the issue is much more complex than I
> originally anticipated and at the moment I have some doubts whether
> this can be achieved as part of this GSoC.
>
> Basic
So I did most of the actual implementation work for the tags which were
proposed on the mailing list. Only some small bits are missing and some edge
cases needs to be tested. But I'm quite happy with the progress so far.
Next will be completing the documentation and going on to the second part of
The last week I've been looking into related fields and all that
stuff. As it turns out, the issue is much more complex than I
originally anticipated and at the moment I have some doubts whether
this can be achieved as part of this GSoC.
Basically, there are two approaches to the task:
1) Make Fo
Basic support in the admin is now working: adding, editing and
deleting single instances with composite primary keys.
Obviously, there's no inline support yet since relationship fields are
not yet ready.
Michal
[1] https://github.com/konk/django
signature.asc
Description: Digital signature
On Jul 6, 1:11 pm, Michal Petrucha wrote:
> Hmm, this is exactly what I had in mind when thinking about this
> problem. I see that even despite keeping the changes to a minimum, the
> patch looks quite big. I'll definitely review this once I start
> working on relationship fields.
No wonder the
On Wednesday, July 6, 2011 2:30:12 AM UTC+12, Gregor Müllegger wrote:
>
> Hi, Chris.
>
> Seems that I'm now unemployed as GSoC Student,
> looks like you already did all the work! ;-)
>
I prefer to show prototype code than just discussing things. It's more fun
:)
> Besides this, great work. If
On Tue, Jul 05, 2011 at 03:39:53PM -0700, akaariai wrote:
> I did a glance-over of your github branch. I was especially looking
> for how you will handle LEFT OUTER JOINS involving composite primary
> keys / foreign keys. If I am not missing something, I think this
> haven't been done yet. I have m
On Jul 6, 1:39 am, akaariai wrote:
> Having said all this, for this project "extend the connection tuple"
> approach seems to be the only sane choice.
I implemented this in my github branch
https://github.com/akaariai/django/tree/composite_join
With this you can do:
a = Article.objects.all()
a.
On Jun 27, 4:22 am, Michal Petrucha wrote:
> some visible progress on my project at long last. I spent most of the
> last week digging deep inside the ORM's entrails to make composite
> field lookups possible and finally it looks promising.
>
> While working on this I found out the extra_filters a
Hi, Chris.
Seems that I'm now unemployed as GSoC Student,
looks like you already did all the work! ;-)
Besides this, great work. If I understand the source code right (haven't run
it yet), then it's already feature complete, isn't it?
I also like the idea of "extends", I will definitely bring th
Hi folks,
Sorry about this delayed post. My repo now supports using
CompositeField as a model's primary key, as far as models are
concerned, that means, Model.pk and friends.
For the next week, expect admin to work. THe work is underway, nothing
worthy of publishing just yet.
Michal
[1] https:/
Hi Gregor, I've just put up a new version of django-forms [1] which implements
a similar version of the proposal with the main difference being "extends".
Take a look.
1. https://github.com/SmileyChris/django-forms
--
You received this message because you are subscribed to the Google Groups
Hi,
I wrote mainly documentation in the last week for how to use the new form
rendering as well as references in the template tag listing. I've also
implemented the form, formrow and formfield tags, I thought we might want to
have something to play with sooner than later. The docs/tests etc can be
Hi,
some visible progress on my project at long last. I spent most of the
last week digging deep inside the ORM's entrails to make composite
field lookups possible and finally it looks promising.
While working on this I found out the extra_filters approach I
intended to use was a dead end (which
Hi,
we finally found (IMO) a really good API for the form rendering related
template tags. There is currently an ongoing discussion on the mailinglist
[1]. Jacob raised some concerns related to the performance impact that future
form rendering will have. I will make this a more important point in
Hi Mikhail,
2011/6/22 Mikhail Korobov :
> Hi Gregor & others,
> I've noticed the https://github.com/idangazit/formrendering and it reminds
> me the approach I'm using for all my django 1.3 projects:
> {# forms/fields/as_dl.html #}
> {{ field.label_tag }}} {{ field }}
> {% include "forms/fields
Hi Gregor & others,
I've noticed the https://github.com/idangazit/formrendering and it reminds
me the approach I'm using for all my django 1.3 projects:
{# forms/fields/as_dl.html #}
{{ field.label_tag }}} {{ field }}
{% include "forms/fields/errors.html" %}
and then:
{% csrf_token %} {
Another weekly update.
First off, I'd like to apologize for not posting one last week; I've
been completely buried under exams and other school-related stuff
during the past three weeks...
Things have settled now at last so I'm back at my SoC and cathing up.
My repo [1] now contains support for i
Hi,
I unfortunatelly missed the last weekly check-in. However during this time I
was already on my travel to Amsterdam for DjangoCon Europe. During this
Conference and mostly during the sprints have I spoken to some of the core
contributors to get their opinion about my current form rendering
All right, time for another check-in.
This isn't a lengthy one -- unfortunately last Tuesday my laptop
failed me, leaving me with no replacement, which means I have to wait
for it to return from the service center to be fully up and running.
In the meantime, I managed to borrow an old one a coupl
Hi,
this week was the first week with official coding for my GSoC project. I
merged Bruno Renié's template based widget rendering branch in my django fork.
This will be the base of my on going work. I also made sure that all tests are
passing, since there were some issues with changes in the white
Checking in with some actual results. At the moment, my repo [1]
contains a bit of documentation (look at the model field reference and
the model topic guide) and a basic implementation with some trivial
tests.
Some remarks:
* I ended up using namedtuple anyway, providing a fallback
implementati
Hi,
Carl and me had a vital discussion about the syntax that we will
propose for a RFC.
There is already a mailing list thread to which I warmly invite you to join:
http://groups.google.com/group/django-developers/browse_thread/thread/e4836b5a9d36349e
Read the templatetag syntax proposal there a
Thanks Mathieu,
I already knew this library, however I wanted to have a quick implementation
that doesn't use classytags or any other thirdclass library. But thanks to
your link I looked in the documentation of sekizai again and saw the
restrictions page [1]. And after having a look at the my samp
Hello Gregor,
just FYI, one of the guy from django-cms created django-sekizai, which is
used just for that (injecting stuff in template blocks) :
https://github.com/ojii/django-sekizai
Mathieu
--
You received this message because you are subscribed to the Google Groups
"Django developers" g
Hi,
I used the last week to setup the 'test environment' for proof-of-concept'ing
the API we will be implementing. The first thing there is that I setup a (yet)
simplistic template for
1. the form tag, the monolithic approach how I have proposed it
2. multiple tags like proposed by Russell.
Both
Hello again,
time for the second weekly check-in.
I apologize for not having posted the API as I promised yet, there's a
lot of things going on in school. However, I started working on a
ticket [1] as we're supposed to for the interim period.
Not much else to report, hopefully the n
Hello everyone,
I hope the introductions aren't necessary since I've already
introduced myself in the past [1].
Just a recap, I'll be working, under the guidance of Jacob
Kaplan-Moss, on support for composite model fields which will allow
users to define models with composite primary keys. The fu
Hi once more,
So there was 0 check-in to start the thread and now meritum. People
who
have read, commented and evaluated my proposal already know me, but
for
others I will introduce myself. My name is Jan Rzepecki, I'm going to
work on django schema alteration API this year for GSoC 2011. I'm on
Hi once more,
So there was 0 check-in to start the thread and now meritum. People
who
have read, commented and evaluated my proposal already know me, but
for
others I will introduce myself. My name is Jan Rzepecki, I'm going to
work on django schema alteration API this year for GSoC 2011. I'm on
Hi,
let me introduce myself a bit before I start talking about my upcoming work
during the summer. My name is Gregor Müllegger and I was accepted as a Google
Summer of Code Student for Django, doing the project called "Revised form
rendering". Next Monday will start my fourth year at the universit
41 matches
Mail list logo
