SUMO, GSoC like project, to create sustainable software

[Jean-Christophe Kermagoret]

Hi,
I am Jean-christophe Kermagoret from SIDE-Labs.

SIDE-Labs, founded by BlueXML, is an open source project which created a 
sustainable IDE, SIDE, based on MDA (Model Driven Architecture), to 
quickly develop sustainable software application. Moreover, thanks to 
the use of models, development can be achieved by domain specialist. 
From a technological point of view, a generation process enables to 
build the corresponding application on available frameworks. Alfresco 
ECM is already available as a final technical target, and more 
frameworks should be available soon. I think it could be a good 
opportunity for Django to provide its own implementation.


I know, if I want something, just "write the code" :-)

But I only have 2 hands. So, SIDE-Labs created the SUMO project, GSoC 
like, which stipends students to develop models and code. A SUMO project 
could be, for example, to develop this alternate generator. It could be 
interested for Django community to have access to Alfresco or other one. 
Morevoer, all the available applications could be available in the 
future on the Django platform. In fact, we are trying to build the next 
Babel Tower.


If you think you can be interested by such a project, have a look at 
http://www.side-labs.org/wiki/index.php/SUMO:Home, read FAQ, browse 
projects' list and create a page for your ideas as a mentor 
organization, or a student.


Feel free to ask for information on the forums and/or subscribe mailing 
lists.


Thanks for your time and your interest,

JC

--
Jean-Christophe Kermagoret
Directeur associe

BlueXML
40, bd Jean Ingres
44100 Nantes

Tel. : +33.2.40.46.62.78
Mob. : +33.6.08.56.83.80

BlueXML : http://www.bluexml.com
SIDE-Labs : http://www.side-labs.org
KerBlue : http://www.kerblue.org


--
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Default ordering on User model

[Andy McKay]

On 2010-05-21, at 6:19 AM, Reinout van Rees wrote:
> Another data point: Plone has a checkbox for that: "do you have many 
> users/groups?".  If True, several screens don't attempt to list all users, do 
> sorting, etc.  Instead search fields are used.
> 
> So: best of both worlds.  But there's of course some extra code here and 
> there with "if LARGE_AMOUNT_OF_USERS... else ...".

In that case for the django admin you specify "raw_id_fields" on your model 
that has a ForeignKey to users.

http://docs.djangoproject.com/en/dev/ref/contrib/admin/#raw-id-fields
--
  Andy McKay, @andymckay
  Django Consulting, Training and Support

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Default ordering on User model

[Reinout van Rees]

On 05/21/2010 02:59 PM, Karen Tracey wrote:


Actually there is no default ordering, and yes, there is a reason, see:
http://code.djangoproject.com/ticket/6089, which also shows a workaround
for getting ordering back for specific form fields. Granted that is a
bit of a pain, and there is some dissatisfaction expressed at the end of
the ticket, but I don't see a specific proposal for how to address the
issue while still not introducing problem for sites with large numbers
of users, so that's the way it is now.


Another data point: Plone has a checkbox for that: "do you have many 
users/groups?".  If True, several screens don't attempt to list all 
users, do sorting, etc.  Instead search fields are used.


So: best of both worlds.  But there's of course some extra code here and 
there with "if LARGE_AMOUNT_OF_USERS... else ...".



Reinout

--
Reinout van Rees - rein...@vanrees.org - http://reinout.vanrees.org
Programmer at http://www.nelen-schuurmans.nl
"Military engineers build missiles. Civil engineers build targets"

--
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Re: Default ordering on User model

[s . kuzmenko]

My favourite workaround for this is to register a small dummy apps  
overriding default properties:


from django.conf import settings

if "django.contrib.auth" in settings.INSTALLED_APPS:
# modify User model properties only if contrib.auth is installed
from django.contrib.auth.models import User
# display full name instead of user name where string representation is  
required:

User.__unicode__ = lambda self: self.get_full_name()
# set default ordering by first name and last name:
User._meta.ordering = ['first_name', 'last_name']

This will globally modify default sorting (and unicode representation) for  
User model. It is usually the first thing I put into my project.


This is a bit of hard coded to cater to my specific requirements (in many  
cases I do have first and last names). A more flexible workaround could  
involve special settings, eg:

AUTH_DEFAULT_ORDERING = ( 'first_name', 'last_name' )


On , Karen Tracey  wrote:

On Fri, May 21, 2010 at 8:46 AM, Jeremy Dunck jdu...@gmail.com> wrote:




Even so, you could create a custom ModelAdmin for User, specifying the



ordering option:



http://docs.djangoproject.com/en/1.2/ref/contrib/admin/#django.contrib.admin.ModelAdmin.ordering







The default model admin for the User model already specifies ordering by  
username. The issue, I believe, is that that does not affect things like  
ForeignKey drop-down boxes.




Karen









--


You received this message because you are subscribed to the Google  
Groups "Django developers" group.



To post to this group, send email to django-develop...@googlegroups.com.


To unsubscribe from this group, send email to  
django-developers+unsubscr...@googlegroups.com.



For more options, visit this group at  
http://groups.google.com/group/django-developers?hl=en.


--
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Default ordering on User model

[Karen Tracey]

On Fri, May 21, 2010 at 8:46 AM, Jeremy Dunck  wrote:

> Even so, you could create a custom ModelAdmin for User, specifying the
> ordering option:
>
> http://docs.djangoproject.com/en/1.2/ref/contrib/admin/#django.contrib.admin.ModelAdmin.ordering
>
>
The default model admin for the User model already specifies ordering by
username. The issue, I believe, is that that does not affect things like
ForeignKey drop-down boxes.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Default ordering on User model

[Karen Tracey]

On Fri, May 21, 2010 at 8:38 AM, tiemonster  wrote:

> Is there a reason that the default ordering on the User model is by
> pk? Would it be a reasonable request to ask that the default ordering
> for this model be username? I have several models that have a m2m to
> the User model, and it's very hard to find someone to add using the
> admin when the users are in pk order. I wanted to test the waters
> before opening a ticket.
>

Actually there is no default ordering, and yes, there is a reason, see:
http://code.djangoproject.com/ticket/6089, which also shows a workaround for
getting ordering back for specific form fields. Granted that is a bit of a
pain, and there is some dissatisfaction expressed at the end of the ticket,
but I don't see a specific proposal for how to address the issue while still
not introducing problem for sites with large numbers of users, so that's the
way it is now.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Default ordering on User model

[Jeremy Dunck]

On Fri, May 21, 2010 at 7:38 AM, tiemonster  wrote:
> Is there a reason that the default ordering on the User model is by
> pk? Would it be a reasonable request to ask that the default ordering
> for this model be username? I have several models that have a m2m to
> the User model, and it's very hard to find someone to add using the
> admin when the users are in pk order. I wanted to test the waters
> before opening a ticket.

Actually, the user model's default ordering used to be by username--
but in large deployments, this needlessly caused significant overhead
when using the User model.

Presuming you have many users, your admins will likely still use the
search field to find the user they need.

Even so, you could create a custom ModelAdmin for User, specifying the
ordering option:
http://docs.djangoproject.com/en/1.2/ref/contrib/admin/#django.contrib.admin.ModelAdmin.ordering

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Default ordering on User model

[tiemonster]

Is there a reason that the default ordering on the User model is by
pk? Would it be a reasonable request to ask that the default ordering
for this model be username? I have several models that have a m2m to
the User model, and it's very hard to find someone to add using the
admin when the users are in pk order. I wanted to test the waters
before opening a ticket.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.