sebzur / synergy Goto Github PK

The fileds that are choicable should be rendered witth get_{field_name}_display when tables are used to render the variant. No it is the raw data showed there..

An option to preselect lookup should be available in prospects

It should be possible to setup prospects fileds to use template filters priori to render them

Of course, the Synergy should have some tests included... We have none of them at the moment... :/

Prospect aspect should have the option to enable/disable its existance while the data are being filtered. This will prevent from the very wide (not limited) queries on the tables with the big number of entries.

When record is available only in update mode, there is no point in success_url after creation... This should be handled somehow...

Now in synergy.ui.* apps there are some static files (mainly jquery code) from 3rd party software (like jQuery Datatables, FullCalendar, etc) fhat should be removed.

This should be the user thing to download the latest version of the 3rd party software that are used by Synergy.

At the moment prospects handle only callable on the model instances of the source. It should be allowed to use related instances callable attributes as well, i.e. to define a field with application__personal_data__get_age, where get_age is an instance method...

There should be something possible to be done in this context.

When a record is setup with argument (which is basicly needed to create an instance) then the update action or delete should probably not use the argument

Some additional text that are already present in the models should be used whe the variant is presented as table or any other list views

Whe usnig o2o lookup in prospects aspect theres something wrog happening..

Traceback (most recent call last):

File "/usr/lib/python2.6/site-packages/django/core/handlers/base.py", line 111, in get_response
response = callback(request, _callback_args, *_callback_kwargs)

File "/usr/lib/python2.6/site-packages/django/views/generic/base.py", line 47, in view
return self.dispatch(request, _args, *_kwargs)

File "/usr/lib/python2.6/site-packages/django/utils/decorators.py", line 28, in _wrapper
return bound_func(_args, *_kwargs)

File "/usr/lib/python2.6/site-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view
return view_func(request, _args, *_kwargs)

File "/usr/lib/python2.6/site-packages/django/utils/decorators.py", line 24, in bound_func
return func(self, _args2, *_kwargs2)

File "/codebase/Synergy/synergy/contrib/prospects/views.py", line 22, in dispatch
return super(ProspectView, self).dispatch(_args, *_kwargs)

File "/usr/lib/python2.6/site-packages/django/views/generic/base.py", line 68, in dispatch
return handler(request, _args, *_kwargs)

File "/usr/lib/python2.6/site-packages/django/views/generic/edit.py", line 138, in post
return self.form_valid(form)

File "/codebase/Synergy/synergy/contrib/prospects/views.py", line 61, in form_valid
return self.render_to_response(self.get_context_data(form=form))

File "/codebase/Synergy/synergy/contrib/prospects/views.py", line 51, in get_context_data
results = self.get_results(self.kwargs.get('variant'), **dict(kwargs['form'].cleaned_data))

TypeError: get_results() keywords must be strings

Record setup should allow to enable Create/Update/Delete selectively, i.e. one should have option to turn off the C|U|D in record

Aspect defined with related fields should be able to use multiple choices (__in lookup).