Hi,
I am new to django and i want to make two text boxes appear on the
same row , what should i have to do for it, please help me out.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
On Wed, May 21, 2008 at 3:55 PM, amar <[EMAIL PROTECTED]> wrote:
>
> Hi,
>I am new to django and i want to make two text boxes appear on the
> same row , what should i have to do for it, please help me out.
Please don't ask how-to questions on Django-developers. Django
Developers is for discu
I am doing a project on django and now i want to show two text boxes
on the same row, please help me how to do it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
On Wed, May 21, 2008 at 5:27 AM, Curtis <[EMAIL PROTECTED]> wrote:
>
>
> Has anyone considered using Python's 'warnings' module? It seems like
> it might be the perfect fit for this problem.
>
> For example, if the appropriate warn() calls were added to the
> templating system, by default, proble
Just a quick bump: has there been any progress on this?
Thanks,
Aral
On Apr 11, 9:44 pm, Brian Beck <[EMAIL PROTECTED]> wrote:
> Has anyone started working on this? I don't see a branch, but I'd
> love to help out. I've also been writing similar tags and filters for
> my form rendering (see [
Hi all,
I'll sort out the hg repo (it now needs to point at trunk - not qsrf) and
trac project if I get time this evening and make it public readable for
everyone who's interested.
Is there a ticket in django we could use to track progress on this? We could
use 4747, but if we do decide on a new
I've been a while trying to implement full-text search under
PostgreSQL, I created some code that works, but is not optimal.
I asked Malcolm Tredinnick and he told me:
"In fact, thinking about this a bit more, it might even be possible to
do
it all via a custom Q-like object. You might not need t
> Is there a ticket in django we could use to track progress on this? We could
> use 4747, but if we do decide on a new API that might be a bit confusing...
> We could of course just use the mailing list and trac project, thoughts?
There's also http://code.djangoproject.com/ticket/1142. With the
On Sat, May 17, 2008 at 2:27 AM, Sebastian Noack
<[EMAIL PROTECTED]> wrote:
> I have released a new patch. See
> http://code.djangoproject.com/attachment/ticket/7210/0001-Added-expression-support-for-QuerySet.update.3.patch.
>
> I still have to write tests and documentation, but I would like to he
On Wed, May 21, 2008 at 5:56 AM, Brian Rosner <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> The newforms-admin branch is getting close to finalizing the formset
> API. However, to do so we would like to run it by the developer
> community for ideas. I have posted a diff [1] of documentation showin
On Fri, May 16, 2008 at 9:27 PM, Adrian R. <[EMAIL PROTECTED]> wrote:
>
> Okay, so I've got some additional information for you which are
> hopefully useful for you. I've tried to switch to the dev version but
> I don't think that I'm on the right way right now.
I don't mean to be rude, but this
Hi Brian,
from our uses of the nfa, we found that these API are more than
adequate for any use we could think of, which includes:
generic edit inlines
custom validation if both forms and formsets
added logic (including fields) in forms (even in forms used in inline
formsets) and model creation (.
'warnings' sounds like a subset of 'logging'.
In a similar thread (about template tags and filters failing
silently) two years ago Simon Willison (who started this thread) said:
"We really need an official Django logging framework so stuff like
this can be logged"
http://groups.google.com/gr
I'd like to know too. I especially liked both of Simon Willison's
ideas of 1) Template tags for form rendering, and 2) Outputting and
setting of a _doctype variable that the template tags use to decide
what kind of HTML to output.
If nobody has officially started anything, could we set up a Goog
On Wed, May 21, 2008 at 8:44 AM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
>
> However, that said: I might be missing something here, but we've just
> gone through the process of deprecating form_for_model and
> form_for_instance based upon the reasoning that a class based form
> definition i
On Wed, May 21, 2008 at 4:30 AM, Aral Balkan <[EMAIL PROTECTED]> wrote:
>
> Just a quick bump: has there been any progress on this?
Not really. I started the implementation on the plane ride back from
PyCon, realized that it wouldn't work *quite* the way I'd proposed
(widgets don't have access to
On 21 Mai, 15:50, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Fri, May 16, 2008 at 9:27 PM, Adrian R. <[EMAIL PROTECTED]> wrote:
>
> > Okay, so I've got some additional information for you which are
> > hopefully useful for you. I've tried to switch to the dev version but
> > I don't thi
Graham King wrote:
> And if Django had logging, we could have a SQL log, and I wouldn't
> have to start all my projects by setting up a logger, a SQL logging
> middleware, and an audit log of object create/update/delete.
I trust you've seen the django-logging project on c.g.c?
http://code.googl
I just ran into an issue where i was getting unicode errors when trying
to insert data into mysql (via a model).
I had this code:
--
from django.contrib.markup.templatetags.markup import markdown
def save(self):
self.content_html = markdown(self.content_source)
This appears to be a usage question. This list is for the development
of Django itself, not developing projects that use Django. Usage
questions should be directed to the django-users list [1].
[1]: http://groups.google.com/group/django-users
That said, it appears that you are taking issue with
On Wed, May 21, 2008 at 2:32 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
[snip]
> in mind that markdown knows (almost) nothing about encodings. It only
> works with unicode (or ascii) text. You *must* give markdown unicode
> text and it *only* outputs unicode text. It is your responsibility to
>
Sorry. I passed some UTF-8 text to the
django.contrib.markup.templatetags.markup.markdown function (which is
included with django), and got what appeared to be an incorrectly
encoded string in return.
I thought this MIGHT be a bug with the django markdown function. If it
was, then I would log
that's exactly what I meant, thanks Daryl
On May 20, 4:12 pm, "Daryl Spitzer" <[EMAIL PROTECTED]> wrote:
> Perhaps bedros meant to ask if anyone is working on support in Django
> for any "document based" databases.
>
> strokeDB looks (to my untrained eye) similar to CouchDB. You'll find
> plenty
On Wed, May 21, 2008 at 2:57 PM, Mike Chambers <[EMAIL PROTECTED]> wrote:
>
> Sorry. I passed some UTF-8 text to the
> django.contrib.markup.templatetags.markup.markdown function (which is
> included with django), and got what appeared to be an incorrectly
> encoded string in return.
Ah, OK, I gu
Hi guys --
Sorry for coming late to the party, but I'm just now catching up on django-dev.
I'm really glad to see you get the ball rolling on multiple db
support, and once I'm dug out from my backlog I'll be happy to start
reviewing code and helping out if I'm needed.
However, before we get to
Hi Jacob,
I'd be interested in your thoughts on a declarative approach to defining the
other databases...? I'll have my mercurial repo synced up to trunk tomorrow
(my time) and I'll re-apply the patch I got from Daryl to it as a starting
point. Hopefully people will be able to have a look through
On May 21, 2:16 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> * There needs to be an official API to get a model (or perhaps a
> manager) which references a different "context" --
> ``Model.objects.db`` should be read-only. So you'd call some API
> method, and get back a sort of proxy obj
Dear all,
I think I've found a bug in Django and a solution :-)
In django/db/backends/postgresql/operations.py (svn)
there is a PostgreSQL version check that reads like this:
if self.postgres_version[0] >= 8 and self.postgres_version[1] >= 1
Bug: When PostgreSQL turns 9.0 (a year from n
I really like this line of thought: having the persistence layer of a
model fixed is a good idea.
Relations is a big issue here: unless we can support relations across
databases, switching connections is always a big opportunity to shoot
yourself in the foot.
I would propose a function that can co
29 matches
Mail list logo
