Reuse admin for views when some fields are from remote sources

2011-09-26 Thread cesar.ortiz
Hi,

We have some fields that will appear in the view that we won't to be
part of the model. They are from other system and we don't wish to
store them in order to avoid the problems that will arise with the
duplication of data.
We also would like to reuse the admin as much as possible in order to
avoid to create our own templates.

Those remote fields will be read/written to the remote system.
Which would be the best way to implement this behaviour in django?

Thanks,

-- César

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



Re: Reuse admin for views when some fields are from remote sources

2011-09-26 Thread cesar.ortiz
It works for the List View, but it doesn't work for the Edit View

On 26 sep, 13:40, Ilian Iliev  wrote:
> If these fields are not field in the model class you won't see them in the
> add/edit of the admin.
> If you want to show them in the view(list) section of the admin you can
> define them as properties,
> example:
>
> class MyModel(models.Model):
>     # field here
>
>     @property
>     def remote_property(self):
>         return remote_property
>
> class MyModelAdmin(admin.ModelAdmin)
>     list_display = ( 'remote_property', 'other_model_field')
>
> --
> eng. Ilian Iliev
> Web Software Developer
>
> Mobile: +359 88 66 08 400
> Website:http://ilian.i-n-i.org
>
>
>
>
>
>
>
> On Mon, Sep 26, 2011 at 2:11 PM, cesar.ortiz  wrote:
> > Hi,
>
> > We have some fields that will appear in the view that we won't to be
> > part of the model. They are from other system and we don't wish to
> > store them in order to avoid the problems that will arise with the
> > duplication of data.
> > We also would like to reuse the admin as much as possible in order to
> > avoid to create our own templates.
>
> > Those remote fields will be read/written to the remote system.
> > Which would be the best way to implement this behaviour in django?
>
> > Thanks,
>
> > -- César
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django users" group.
> > To post to this group, send email to django-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > django-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/django-users?hl=en.

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