James Bennett wrote:
> If you'd be interested in helping to develop useful models for that
> using this data, that'd be great :)
James, I also developed the Django model and a loader.
http://webda.python-hosting.com/browser/trunk/Django/I18n
But now it's necessary that Django developers help
I also developed the Django models for those data:
http://webda.python-hosting.com/browser/trunk/Django/I18n
Please, post your message in this group
http://groups.google.com/group/webda
I would to have all discussion related to globalization data in the
same group. So it could be usefull
On 10/14/06, GinTon <[EMAIL PROTECTED]> wrote:
> Now I would that Django developers could to integrate these tables with
> django, because without a doubt it has many advantages to both the
> administrators and the users.
I've tinkered once or twice with the idea of doing a
I have been working in creating tables in format CSV for the
globalization (G11n), so that they can be used in any project where it
could be necessary or useful.
You can see the tables on:
http://satchmo.python-hosting.com/browser/trunk/satchmo/G11n/data/
And here you have the files for
Please, post your message in this group
http://groups.google.com/group/webda
I would to have all discussion related to globalization data in the
same group. So it could be usefull for that anothers frameworks could
implementing those data too.
Thanks
I usually hate drop-downs as well, especially long drop-downs like
country-fields with more than 130 selectable items. Therefore we mostly
use such lists in combination with an AJAX autocomplete and select
widget which makes filling in such forms way more convenient.
I must say, I **hate** drop-downs for the state postal abbreviation. The
vast majority of the time, when people are filling in a form where they
need a postal abbreviation, they are either:
a. putting their own address and know the abbreviation
b. filling in an address they've been given, which
I've created a new group for integrating G11n data in Django and
Turbogears:
http://groups.google.com/group/webda
Please I need ideas to get the best possible integration.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
I've moved all files about globalization to
http://svn.webda.python-hosting.com/trunk/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
Todd O'Bryan wrote:
> I've actually been thinking about this, recently. How would people feel
> about a Field type that took a regex to validate input against.
>
> Or, to be even more wacky, how about providing callables that would
> validate the input and normalize it? Something like
>
> def
Jeremy Dunck wrote:
> On 10/15/06, GinTon <[EMAIL PROTECTED]> wrote:
> > And here you have the files for add/integrate them to any Django
> > project:
> > http://satchmo.python-hosting.com/file/trunk/satchmo/G11n/
> > http://satchmo.python-hosting.com/file/trunk/satchmo/load_G11n.py
>
> It may
I've actually been thinking about this, recently. How would people feel
about a Field type that took a regex to validate input against.
Or, to be even more wacky, how about providing callables that would
validate the input and normalize it? Something like
def __init__(self, validator=lambda x:
On 10/15/06, GinTon <[EMAIL PROTECTED]> wrote:
> And here you have the files for add/integrate them to any Django
> project:
> http://satchmo.python-hosting.com/file/trunk/satchmo/G11n/
> http://satchmo.python-hosting.com/file/trunk/satchmo/load_G11n.py
It may be too much work, or you may not be
Thanks Russ for your message. I became angry because I have been
working very hard during 2 or 3 months.
I hoped that somebody said some idea for its possible implementation
Using those data we could have fields as USStateField and
PhoneNumberField for all countries (and validators). But I
On 10/18/06, GinTon <[EMAIL PROTECTED]> wrote:
>
> I see that it isn't interesting for django developers so "I go away
> with the music to another part".
>
> In the first I prefer to work with another community where there is
> more support.
Don't read too much into the lack of response; the
I see that it isn't interesting for django developers so "I go away
with the music to another part".
In the first I prefer to work with another community where there is
more support.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
16 matches
Mail list logo
