Databrowse - text overlapping

2008-06-06 Thread Kless 

There is a little issue. The name of the tables -on the left- is
overlapping to the name of the objects -on the right-, when there are
large names.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---

Re: Databrowse - text overlapping

2008-06-06 Thread Justin Lilly 
As its a visual issue, I'd also probably include a screenshot.

On Fri, Jun 6, 2008 at 8:48 AM, Russell Keith-Magee <[EMAIL PROTECTED]>
wrote:

>
> On Fri, Jun 6, 2008 at 7:55 PM, Kless <[EMAIL PROTECTED]> wrote:
> >
> > There is a little issue. The name of the tables -on the left- is
> > overlapping to the name of the objects -on the right-, when there are
> > large names.
>
> Please log suspected errors and bugs in the ticket tracker. Bug
> reports in the mailing list tend to get lost over time.
>
> Yours,
> Russ Magee %-)
>
> >
>


-- 
Justin Lilly
Web Developer/Designer
http://justinlilly.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---

django-updates group broken?

2008-06-06 Thread Andrew Durdin 

I was looking at django-updates in google groups , and noticed the most recent
posting from it was from the 18th of March.  It looks like something
is broken there...

Since updates don't seem to be going through there, can I ask that
someone review ticket #3349 ("If an ImportError occurs within a custom
template tag library, a rather confusing error message is produced")?
It was approved before the September sprint, and I wrote a patch at
that time.  I just updated the patch against the current trunk a
couple of days ago, and would like to see it checked in, as I quite
often run into errors that result in a failed import of a view module,
and the tracebacks don't show the original fault without this patch.

Cheers,

Andrew.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---

Re: Aggregation Updates

2008-06-06 Thread Nicolas Lara 

>
> My point is that the user shouldn't ever need to worry. A list that
> contains multiple versions of similar things is easy to process by
> iteration. A list that contains "similar things except for the one the
> isn't" is not as trivial to process.
>
>
> Bleh. Adding methods to clean up after the mess made by a different
> feature? -1 to that.
>

Agreed.

>> The problem I see with the tuple approach is that, well, you have a
>> tuple instead of a dict. So values would in some cases return a list
>> of dicts and in others a list of tuples, which I found more
>> inconsistent than mixed types inside a dict. Also you would need to
>> handle the tuple just to get to your data.
>
> Well, you're going to have to handle the data no matter what format
> the output takes. The upside of my approach is that you can assign the
> different return types to different variables, and handle them
> differently:
>
> for values, members in Author.objects.values('age','name',groups=True):
>   ...
>
> whereas your approach requires some manipulation of the return type to
> extract the data that doesn't match everything else before you can do
> any sort of iteration over the returned value data.
>
> As for having a single method with two different return types
> depending on context - there are already examples of Django APIs that
> do this. For example, values_list returns a list of tuples, unless you
> provide the flat=True argument, in which case you get a list of
> values.
>
> You are explicitly asking for different output, so the fact that
> different output happens shouldn't be entirely surprising. And
> remember - In your propsal, you're getting back different output as
> well - one version has the magic 'groups' member, one doesn't.
> However, you can't tell that it's different output until you iterate
> over the result you get back from the call.

I see your point on the problems of mixed output and it is truly a not
desired flow for working with the data.
The tuple seems like a solution from the python point of view, but it
becomes problematic when it comes to templates. What would be the
method in templates for accesing the data?

{% for old_authors in authors_by_age %}
...
{{ old_authors.0.avg_num_books }}

 {% for same_age in old_authors.1 %}
...
{% endfor %}

This would not play well especially with generic views.Of course it is
always possible to wrap it in a view and add 2 separate variables to
the context.

The alternative to this would be using a dictionary. So the return
type would be something like:
{'values': {...all the values here... }, 'group' : [...list of the
groupings ...]}

This option seems to accomodate better the use of the querysets in the
templates but complicates a little the python case:
for element in queryset:
for name, age in element['values'].items():
print name, age

I am especially not thrilled about the depth of the datastructure in
when using a dictionary (a list of dicts that contain another dict and
a queryset). but so far I haven't come up with a better solution.

Though non of these are the end-all solution, I feel comfortable with
both (+0). By now I am leaving the tuple solution implemented because
it is already done and it is very easy to change the output to
something else (like a dict) in the future (also this feature is not a
priority).

cheers =)


-- 
Nicolas

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---

Understanding HTML, XML and XHTML

2008-06-06 Thread Rob Hudson 

I'm pretty sure this has been beaten to death, and I was going to pass
on sending this in, but this paragraph made me ask, "What would it
hurt to ask?":

{% block quote %}
Unfortunately, sometimes you are not fully in control of the content
you produce. For example, this very blog, published with WordPress
tags. If you find yourself in this same boat, encourage your tools
vendors to provide support for generating valid HTML.
{% endblock %}

That came from this article which puts up some very strong points
regarding HTML and XHTML and browser rendering (preferring HTML4), and
points out that many leading web standards experts are also
recommending HTML4:
http://webkit.org/blog/68/understanding-html-xml-and-xhtml/

(Donning flame retardant suit b/c I'm sure I'll get flamed for being a
retard here...)

Is Django really the web framework for *perfectionists* if it, by
default, prefers the imperfect XHTML in newforms and the admin (and
other places)?  If not a complete switch, could we at least not make
those who are anal about outputting HTML4 not have to work[1]
harder[2] than[3] those who are ok XHTML?

-Rob

[1] http://www.djangosnippets.org/snippets/618/
[2] http://www.djangosnippets.org/snippets/716/
[3] http://code.djangoproject.com/ticket/6925


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---

Fwd: GSoC Weekly Report (#2): Django on Jython

2008-06-06 Thread Leo Soto M. 

As nobody said anything against forwarding my SoC reports here, I'm
assuming it is OK to continue doing it :)

-- Forwarded message --
From: Leo Soto M. <[EMAIL PROTECTED]>
Date: Fri, Jun 6, 2008 at 11:16 PM
Subject: GSoC Weekly Report (#2): Django on Jython
To: JythonDevelopers <[EMAIL PROTECTED]>


Hi again!

So another week has passed and more progress has be done :)

Basically, every problem found with the postgresql_zxjdbc driver which
would also be a problem with other *_zxjdbc driver (mysql, oracle,
etc) has been fixed on the proper place. On my jython.doj branch,
zxJDBC automatically maps dates and times between Java and Python. And
my django.doj branch worked around the problems found with respect to
dates, times, booleans and even integers parameters being converted to
strings before passed to the backend (JDBC didn't liked that). The
missing bit is timezone support. I plan to add that really soon.

Bottom line: creating an oracle and/or mysql backend for django/jython
should be easiest now. I may even give them a shot next week. However,
I have other goals too (see below), so this may have to wait a bit.

With respect to particular issues with postgresql_zxjdbc, I wasn't
able to solve the JDBC mapping for inet types. The PostgrSQL JDBC
driver doesn't like String instances as values for them. As as
workaround, now IPAddressFields are mapped to CHAR(15), which makes us
incompatible with tables created with CPython/Django/psycopg
containing inet values. As I've found some JDBC driver extensions[1]
that could help here, not everything is lost yet.

The goal for the next week is to pass the test suite. I advanced a bit
the last couple of days, and now the failure count is around 25 (from
~35 which was our previous "record").

Now, I think that the goal is not going to be _strictly_ met, because
we have problems with missing unicode data, source encoding support
and problems with unicode+re which I won't be able to address right
now.

Other than that, by next Friday I should have fixed the following:

 - AttributeErrors raised from descriptors are swallowed[2]
 - Problems with DateQuerySet (they give datetimes with one or three
hours more than expected)
 - Dispatcher test failures (they seem related to some GC assumptions)
 - SQLExceptions coming from PostgreSQL integrity errors are not
mapped to DB-API standard IntegrityError

And if time suffices, also:

 - Support for string constants bigger than 32k chars.
 - Make doctest a bit smarter with respect to HTML, XML and JSON output

[1] http://archives.postgresql.org/pgsql-jdbc/2007-08/msg00089.php
[2] http://bugs.jython.org/issue1041
--
Leo Soto M.
http://blog.leosoto.com



-- 
Leo Soto M.
http://blog.leosoto.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---

الخاتم الهزاز بالصور لاول مرة

2008-06-06 Thread a7labnt 


الخاتم الهزاز بالصور لاول مره

http://www.antya7la.com/vb/t26679.html

إقرأ هذا الدعـاء ولو مرة واحدة في حياتك

http://www.antya7la.com/vb/t26026.html

تاامر حسني يهرب من مطاردات الجزائرياات

http://www.antya7la.com/vb/t22796.html

محشش يحكي لصديقه قصة حزينة ههه

http://www.antya7la.com/vb/t26481.html

ازياء تنكرية للاطفال

http://www.antya7la.com/vb/t26260.html

هل تعرفين متى يرغب زوجك بالجنس؟؟؟

http://www.antya7la.com/vb/t26610.html

نزف من وحي الحزن يدفق

http://www.antya7la.com/vb/t26760.html

بصراحة شي فظيع ..لماذا يقاطع الأمريكيون كنتاكي؟؟

http://www.antya7la.com/vb/t26618.html

بنات عز وقلبهم ماعزهم >رواية رومنسية جريئة خياليه(سعوديه) لنملة طربانه
او فرفوشة

http://www.antya7la.com/vb/t26556.html

 للزوجات حركة تسوونها تخلي زوجك يبوس راسك

http://www.antya7la.com/vb/t26605.html

الاوزي مع اسامة اطيب

http://www.antya7la.com/vb/t4319.html

سندويييششات سهلة ولذيذة تستحق التجربة (بالصور)

http://www.antya7la.com/vb/t20985.html

وسائط صوت مجموعة

http://www.antya7la.com/vb/t25924.html

مجموعة رسائل وسائط توصل المعنى للمحبوب رومانسية صور وفيديو

http://www.antya7la.com/vb/t11109.html

شاب يتحدى الله أن يميته بعد ساعة!!!

http://www.antya7la.com/vb/t26564.html

سر إشراقة الوجه

http://www.antya7la.com/vb/t24447.html


وسائط مسلسل نور

http://www.antya7la.com/vb/t26729.html

°•.¸.•?إذا كنت  لا يعني ??.¸.•°

http://www.antya7la.com/vb/t21440.html

ملابس داخلية للعروس

http://www.antya7la.com/vb/t26416.html

حلى بالشعيريه الباكستانيه بالصور

http://www.antya7la.com/vb/t21884.html

طريقه عمل حلى جلد النمر

http://www.antya7la.com/vb/t26702.html

طلبات التواقيع هووون ياحلوووين

http://www.antya7la.com/vb/t26510.html

ستايل تذهيب النص

http://www.antya7la.com/vb/t21643.html

توبيكآت + صور .. جديد "
http://www.antya7la.com/vb/t1855.html

كيكة باربى بالصور

http://www.antya7la.com/vb/t26696.html

طريقة عمل المتبل بالصور

http://www.antya7la.com/vb/t26682.html

 البيتزا السائله بالصور

http://www.antya7la.com/vb/t26684.html

دواء يحل جميع مشاكلك

http://www.antya7la.com/vb/t26594.html

Me and My Father

http://www.antya7la.com/vb/t26265.html

ماذا يرى الجنين وهو في بطن امه...

http://www.antya7la.com/vb/t26252.html

نصف ساعة قضاها هذا الشاب بين أصحاب القبور !! انظر ماذا رأى فيها ؟؟

http://www.antya7la.com/vb/t26424.html

أترغب بملامسة النجوم؟؟

http://www.antya7la.com/vb/t26338.html

بعد 60 سنه زوااج كشفت له السر وهي على فراش الموت

http://www.antya7la.com/vb/t21799.html

صور مهند صور نور صور مسلسل نور المدبلج صور شخصيه و تواقيع ...

http://www.antya7la.com/vb/t26557.html

 فندق الحب {$وااو}
http://www.antya7la.com/vb/t26664.html

خدع بصرية ...

http://www.antya7la.com/vb/t26439.html

صور بناتية للماسنجر ّ ~

http://www.antya7la.com/vb/t26390.html

تشكيلة قصات وتلوين شعر

http://www.antya7la.com/vb/t24327.html

تعليم قص الشعر بالفديو

http://www.antya7la.com/vb/t24400.html

×..سكربات روعة.. ×


http://www.antya7la.com/vb/t4499.html

احواض سمك روعه

http://www.antya7la.com/vb/t26318.html

وسائط غنائيه رومانسيه ( لميس ويحيى )


http://www.antya7la.com/vb/t26422.html

خامات ضوئية

http://www.antya7la.com/vb/t5400.html

{ خطوط + صور + خآمات .. }

http://www.antya7la.com/vb/t26555.html

 حكم نتف وقصّ المرأة حواجبها
http://www.antya7la.com/vb/t26446.html

خروج النساء إلى الأسواق والمحلات التجارية

http://www.antya7la.com/vb/t26445.html

اتبع السيئة الحسنة

http://www.antya7la.com/vb/t26512.html

لاتتم الا أن تأتي بخمسة أشياء

http://www.antya7la.com/vb/t26663.html

انا ماقدر اكون حبيب في بعض الأحوال...،،// Mms+sms
http://www.antya7la.com/vb/t26763.html#post286324

مقطع مضحك للفنان محمد عبده
http://www.antya7la.com/vb/t17051.html


 °¨¨™¤? ? خٍلَفٍيًهُـ جَهُآزٍيً صِوٍرٍتِگ ?¤™¨¨°
http://www.antya7la.com/vb/t26376.html


 عودتّنـي ترجـع..اذا الغيـرٍ خلاك mms ..!!
http://www.antya7la.com/vb/t26379.html#post286320


اغرب سيارات العالم
http://www.antya7la.com/vb/t26437.html


فتاة مصرية يخرج من عينها اسراب نمل -- حالة اعجزت الاطباء فيديو
http://www.antya7la.com/vb/t5523.html


شوف البنت تسوق بالجسر المعلق ـ بالرياض


http://www.antya7la.com/vb/t26573.html


نزف من وحي الحزن يدفق
http://www.antya7la.com/vb/t26760.html#post286055
شوف عيونه شيء مو طبيعي
http://www.antya7la.com/vb/t26572.html


مطعـم (( للعراة )) في نيويورك  صور
http://www.antya7la.com/vb/t5370.html




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---

Re: Aggregation Updates

2008-06-06 Thread Russell Keith-Magee 

On Sat, Jun 7, 2008 at 2:54 AM, Nicolas Lara <[EMAIL PROTECTED]> wrote:
>
>> You are explicitly asking for different output, so the fact that
>> different output happens shouldn't be entirely surprising. And
>> remember - In your propsal, you're getting back different output as
>> well - one version has the magic 'groups' member, one doesn't.
>> However, you can't tell that it's different output until you iterate
>> over the result you get back from the call.
>
> I see your point on the problems of mixed output and it is truly a not
> desired flow for working with the data.
> The tuple seems like a solution from the python point of view, but it
> becomes problematic when it comes to templates. What would be the
> method in templates for accesing the data?
>
> {% for old_authors in authors_by_age %}
> ...
> {{ old_authors.0.avg_num_books }}
>
>  {% for same_age in old_authors.1 %}
> ...
> {% endfor %}

Well, you could do it that way - or you could use the tuple syntax in
the for loop:

{% for values, authors in authors_by_age %}

> This would not play well especially with generic views.Of course it is
> always possible to wrap it in a view and add 2 separate variables to
> the context.

This would be unfortunate, but:
1) it's an edge case limitation - worst case, we could live with this
as a limitation
2) We could always update generic views to handle the alternate output syntax.

> Though non of these are the end-all solution, I feel comfortable with
> both (+0). By now I am leaving the tuple solution implemented because
> it is already done and it is very easy to change the output to
> something else (like a dict) in the future (also this feature is not a
> priority).

Agreed. Just make sure that you make a note of this change in a
feature list somewhere. When we get to the point of merging this to
trunk, one of the steps will be to write an email to the other core
developers with a summary of the  changes. This sort of thing is
something that will definitely need to be blessed by other core
developers before it goes into trunk, and we don't want to
accidentally forget to tell them about it.

Yours,
Russ Magee %-)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~--~~~~--~~--~--~---