Yesterday

• 28 hours ago

  FormIntegration (Help - How to enable Dojo's form functionality in dojango.) Wiki page edited by tobias.klipstein   -   Revision r247 Edited wiki page through web user interface.

  Revision r247 Edited wiki page through web user interface.
• 31 hours ago

  r246 (added two new form widgets: - ComboBoxStore - FilteringSelec...) committed by tobias.klipstein   -   added two new form widgets: - ComboBoxStore - FilteringSelect Both widgets receive their data from the passed data-url.

  added two new form widgets: - ComboBoxStore - FilteringSelect Both widgets receive their data from the passed data-url.
• 32 hours ago

  r245 (using the right mimetype: application/json ) committed by tobias.klipstein   -   using the right mimetype: application/json

  using the right mimetype: application/json

Last 30 days

• Dec 22, 2009

  issue 38 (1.4.0 !) commented on by myersjj   -   I've tested my code with latest Dojango and Dojo 1.4 and it's now working ok. Dojo 1.4 surfaced a few of my bugs. I'd like to have an updated package on PyPi because I use buildout to deploy so I can't use 1.4 on my real systems without patching conf/settings.py on the fly.

  I've tested my code with latest Dojango and Dojo 1.4 and it's now working ok. Dojo 1.4 surfaced a few of my bugs. I'd like to have an updated package on PyPi because I use buildout to deploy so I can't use 1.4 on my real systems without patching conf/settings.py on the fly.
• Dec 17, 2009

  issue 40 (dojango datagrid does not handle function-call field correct...) reported by pichot.fabien   -   What steps will reproduce the problem? 1. create a model with a function inside, 2. create a datagrid-list and add the function call in the list_display 3. once rendered, try to sort by the function-call fiedl. What is the expected output? What do you see instead? the output is "une erreur est survenue" instead of a sorted list. What version of the product are you using? On what operating system? svn, rev 244, ubuntu 9.10 Please provide any additional information below. it seems that the target.order_by() can't order by a function-call field. i solved the problem with a ugly hack of the view datagrid_list in views.py (sorry for my english, i'm french..)

  What steps will reproduce the problem? 1. create a model with a function inside, 2. create a datagrid-list and add the function call in the list_display 3. once rendered, try to sort by the function-call fiedl. What is the expected output? What do you see instead? the output is "une erreur est survenue" instead of a sorted list. What version of the product are you using? On what operating system? svn, rev 244, ubuntu 9.10 Please provide any additional information below. it seems that the target.order_by() can't order by a function-call field. i solved the problem with a ugly hack of the view datagrid_list in views.py (sorry for my english, i'm french..)
• Dec 16, 2009

  issue 39 (dojobuild on Windows: if Python is installed on other drive ...) Status changed by tobias.klipstein   -   Hi Michal, thanks for your bugfix and that you are testing dojango with Windows. Added within r244.

  Status: Fixed

  Hi Michal, thanks for your bugfix and that you are testing dojango with Windows. Added within r244.

  Status: Fixed
• Dec 16, 2009

  r244 (fixes issue #39, detailed message, when a specific dojo vers...) committed by tobias.klipstein   -   fixes issue #39 , detailed message, when a specific dojo version is missing for the build

  fixes issue #39 , detailed message, when a specific dojo version is missing for the build
• Dec 16, 2009

  issue 39 (dojobuild on Windows: if Python is installed on other drive ...) reported by michal.dtz   -   What steps will reproduce the problem? 1. install python on C: 2. unpack dojango on D: 3. try manage.py dojobuild What is the expected output? What do you see instead? the command that manage.py dojobuild is running is "cd c:\python... && build.bat" . The problem is, that if I am on drive D:, doing cd c:\python... changes the current directory of drive C:, but it does not change the current drive. So, for the command to work we need doing "C: && cd c:\python..." I propose adding: if sys.platform == 'win32': exe_command = os.path.splitdrive(buildscript_dir)[0] + ' && ' + exe_command soon after exe_command is initialized in management/commands/dojobuild.py

  What steps will reproduce the problem? 1. install python on C: 2. unpack dojango on D: 3. try manage.py dojobuild What is the expected output? What do you see instead? the command that manage.py dojobuild is running is "cd c:\python... && build.bat" . The problem is, that if I am on drive D:, doing cd c:\python... changes the current directory of drive C:, but it does not change the current drive. So, for the command to work we need doing "C: && cd c:\python..." I propose adding: if sys.platform == 'win32': exe_command = os.path.splitdrive(buildscript_dir)[0] + ' && ' + exe_command soon after exe_command is initialized in management/commands/dojobuild.py
• Dec 15, 2009

  r243 (ComboBox now is extending the FilteringSelect ) committed by tobias.klipstein   -   ComboBox now is extending the FilteringSelect

  ComboBox now is extending the FilteringSelect
• Dec 15, 2009

  FormIntegration (Help - How to enable Dojo's form functionality in dojango.) Wiki page edited by tobias.klipstein   -   Revision r242 Edited wiki page through web user interface.

  Revision r242 Edited wiki page through web user interface.
• Dec 15, 2009

  FormIntegration (Help - How to enable Dojo's form functionality in dojango.) Wiki page edited by tobias.klipstein   -   Revision r241 Edited wiki page through web user interface.

  Revision r241 Edited wiki page through web user interface.
• Dec 15, 2009

  FormIntegration (Help - How to enable Dojo's form functionality in dojango.) Wiki page edited by tobias.klipstein   -   Revision r240 Edited wiki page through web user interface.

  Revision r240 Edited wiki page through web user interface.
• Dec 15, 2009

  FormIntegration (Help - How to enable Dojo's form functionality in dojango.) Wiki page edited by tobias.klipstein   -   Revision r239 Edited wiki page through web user interface.

  Revision r239 Edited wiki page through web user interface.
• Dec 15, 2009

  FormIntegration (Help - How to enable Dojo's form functionality in dojango.) Wiki page edited by tobias.klipstein   -   Revision r238 Edited wiki page through web user interface.

  Revision r238 Edited wiki page through web user interface.
• Dec 15, 2009

  r237 (- form widgets upgraded to Dojo 1.4.0 - Select widget now us...) committed by tobias.klipstein   -   - form widgets upgraded to Dojo 1.4.0 - Select widget now uses dijit.form.Select - the dijit.form.FilteringSelect is now available as a separate widget with the name FilteringSelect - added new component ListInput (dojox.form.ListInput)

  - form widgets upgraded to Dojo 1.4.0 - Select widget now uses dijit.form.Select - the dijit.form.FilteringSelect is now available as a separate widget with the name FilteringSelect - added new component ListInput (dojox.form.ListInput)
• Dec 14, 2009

  issue 38 (1.4.0 !) changed by tobias.klipstein   -   Hi Michal, I've already commited a new revision (r236) including Dojo 1.4.0. Because there was a release recently I don't want to create a complete new version just because of that minor change. At the moment I assume, that a build should work without a problem. Not much has changed in regards to the build system in Dojo 1.4.0. But thanks for the motivational words. I definitely need to have a detailed look into the latest release notes: http://docs.dojocampus.org/releasenotes/1.4 and figure out, if there are new form widgets, that could be added and if there were changes that affect Dojango. Maybe you could give me a hand. Regards, Tobias

  Status: Accepted

  Labels: Type-Enhancement −Type-Defect

  Hi Michal, I've already commited a new revision (r236) including Dojo 1.4.0. Because there was a release recently I don't want to create a complete new version just because of that minor change. At the moment I assume, that a build should work without a problem. Not much has changed in regards to the build system in Dojo 1.4.0. But thanks for the motivational words. I definitely need to have a detailed look into the latest release notes: http://docs.dojocampus.org/releasenotes/1.4 and figure out, if there are new form widgets, that could be added and if there were changes that affect Dojango. Maybe you could give me a hand. Regards, Tobias

  Status: Accepted

  Labels: Type-Enhancement −Type-Defect
• Dec 14, 2009

  issue 38 (1.4.0 !) reported by michal.dtz   -   What steps will reproduce the problem? 1. Dojo 1.4.0 is out 2. Dojango works with it rather well, just modify settings.py 3. ... but, OTOH, I didn't try to build anything. ... just dropping this one to let you know there are faithful Dojango users out there! And, those users are interested in Dojango development ;-) Thank you for a nice and polished django app!

  What steps will reproduce the problem? 1. Dojo 1.4.0 is out 2. Dojango works with it rather well, just modify settings.py 3. ... but, OTOH, I didn't try to build anything. ... just dropping this one to let you know there are faithful Dojango users out there! And, those users are interested in Dojango development ;-) Thank you for a nice and polished django app!
• Dec 13, 2009

  r236 (added dojo 1.4.0 (AOL and Google CDN) and using it as defaul...) committed by tobias.klipstein   -   added dojo 1.4.0 (AOL and Google CDN) and using it as default

  added dojo 1.4.0 (AOL and Google CDN) and using it as default
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r235 Edited wiki page through web user interface.

  Revision r235 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r234 Edited wiki page through web user interface.

  Revision r234 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r233 Edited wiki page through web user interface.

  Revision r233 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r232 Edited wiki page through web user interface.

  Revision r232 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r231 Edited wiki page through web user interface.

  Revision r231 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r230 Edited wiki page through web user interface.

  Revision r230 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r229 Edited wiki page through web user interface.

  Revision r229 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r228 Edited wiki page through web user interface.

  Revision r228 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r227 Edited wiki page through web user interface.

  Revision r227 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r226 Edited wiki page through web user interface.

  Revision r226 Edited wiki page through web user interface.
• Dec 06, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page edited by benwilber   -   Revision r225 Edited wiki page through web user interface.

  Revision r225 Edited wiki page through web user interface.

Earlier this year

• Nov 24, 2009

  r224 (continue working on version 0.5 ) committed by tobias.klipstein   -   continue working on version 0.5

  continue working on version 0.5
• Nov 24, 2009

  dojango-0.4.6.tar.gz ( Dojango 0.4.6 (Bugfix release / JSON RPC 1.1 / Dojo-Dja...) file uploaded by tobias.klipstein   -  

  Labels: Featured Type-Source OpSys-All

  Labels: Featured Type-Source OpSys-All
• Nov 24, 2009

  r223 (changed to version 0.4.6 ) committed by tobias.klipstein   -   changed to version 0.4.6

  changed to version 0.4.6
• Nov 24, 2009

  r222 (moved README to the root directory ) committed by tobias.klipstein   -   moved README to the root directory

  moved README to the root directory
• Nov 24, 2009

  r221 (Fixed generation of source distribution (including all direc...) committed by tobias.klipstein   -   Fixed generation of source distribution (including all directories that are no python modules)

  Fixed generation of source distribution (including all directories that are no python modules)
• Nov 24, 2009

  GettingStarted (Help - How to install, setup and get the dojango test page r...) Wiki page commented on by heidar.rafn   -   I confirm the google import is fixed by dojanga 0.4.5, reinstalled ubuntuone client and my django application works fine with dojango now.

  I confirm the google import is fixed by dojanga 0.4.5, reinstalled ubuntuone client and my django application works fine with dojango now.
• Nov 23, 2009

  GettingStarted (Help - How to install, setup and get the dojango test page r...) Wiki page commented on by tobias.klipstein   -   The problem with the google import should be fixed within dojango 0.4.5.

  The problem with the google import should be fixed within dojango 0.4.5.
• Nov 23, 2009

  issue 35 (Python does have package "google" ) Status changed by tobias.klipstein   -   New dojango version 0.4.5 fixes that.

  Status: Fixed

  New dojango version 0.4.5 fixes that.

  Status: Fixed
• Nov 23, 2009

  dojango-0.4.5.tar.gz (Dojango 0.4.5 (Bugfix release / JSON RPC 1.1 / Dojo-Django M...) file uploaded by tobias.klipstein   -  

  Labels: Featured Type-Source OpSys-All

  Labels: Featured Type-Source OpSys-All
• Nov 23, 2009

  r220 (changed setup.py (added some more information) ) committed by tobias.klipstein   -   changed setup.py (added some more information)

  changed setup.py (added some more information)
• Nov 23, 2009

  dojango-0.4.5.tar.gz (Dojango 0.4.5 (Bugfix release / JSON RPC 1.1 / Dojo-Django M...) file uploaded by tobias.klipstein   -  

  Labels: Featured Type-Source OpSys-All

  Labels: Featured Type-Source OpSys-All
• Nov 23, 2009

  GettingStarted (Help - How to install, setup and get the dojango test page r...) Wiki page commented on by heidar.rafn   -   Hi all I have encountered the same problem as described by robinson.ceng here above. I have analysed it and here are my findings: * This started when I upgraded from ubuntu 8.10 to 9.10 * this line in dojango/templates/dojango/include.html causes this: 'isDebug':{{ DOJANGO.DEBUG|json } * the file dojango/util/__init__.py contains the code for the json filter and in that file this can be found: try: # we need it, if we want to serialize query- and model-objects # of google appengine within json_encode import google except: google = None This import statement succeeds now because a part of ubuntu 9.10 is the package "python-protobuf" drawn in by the ubuntu-one client. And this package contains a "google" module which obviously is not compatible with the one expected by the dojango code. A dirty fix is to change the above try: import block to simple "google=None" statement. If the python-protobuf is removed from the system, dojango works fine.

  Hi all I have encountered the same problem as described by robinson.ceng here above. I have analysed it and here are my findings: * This started when I upgraded from ubuntu 8.10 to 9.10 * this line in dojango/templates/dojango/include.html causes this: 'isDebug':{{ DOJANGO.DEBUG|json } * the file dojango/util/__init__.py contains the code for the json filter and in that file this can be found: try: # we need it, if we want to serialize query- and model-objects # of google appengine within json_encode import google except: google = None This import statement succeeds now because a part of ubuntu 9.10 is the package "python-protobuf" drawn in by the ubuntu-one client. And this package contains a "google" module which obviously is not compatible with the one expected by the dojango code. A dirty fix is to change the above try: import block to simple "google=None" statement. If the python-protobuf is removed from the system, dojango works fine.
• Nov 22, 2009

  issue 37 (dojango formset_factory doesn't support initial) Status changed by tobias.klipstein   -   fixed in r219. there will be a bugfix release soon.

  Status: Fixed

  fixed in r219. there will be a bugfix release soon.

  Status: Fixed
• Nov 22, 2009

  r219 (fixing issue #37. there is a difference between django 1.0 a...) committed by tobias.klipstein   -   fixing issue #37 . there is a difference between django 1.0 and 1.1 handling the total form count

  fixing issue #37 . there is a difference between django 1.0 and 1.1 handling the total form count
• Nov 22, 2009

  issue 37 (dojango formset_factory doesn't support initial) reported by keever   -   What steps will reproduce the problem? 1. from dojango import forms from dojango.forms.formsets import formset_factory class TitleForm(forms.Form): title = forms.CharField() 2. set= formset_factory(TitleForm, can_order = True) 3. set(initial = ({'title':'roar'},)) What is the expected output? What do you see instead? The expected output is a formset, but instead you get AttributeError: 'FormFormSet' object has no attribute '_initial_form_count' What version of the product are you using? On what operating system? dojango .4 ubuntu jaunty Please provide any additional information below. It works without can_order

  What steps will reproduce the problem? 1. from dojango import forms from dojango.forms.formsets import formset_factory class TitleForm(forms.Form): title = forms.CharField() 2. set= formset_factory(TitleForm, can_order = True) 3. set(initial = ({'title':'roar'},)) What is the expected output? What do you see instead? The expected output is a formset, but instead you get AttributeError: 'FormFormSet' object has no attribute '_initial_form_count' What version of the product are you using? On what operating system? dojango .4 ubuntu jaunty Please provide any additional information below. It works without can_order
• Nov 18, 2009

  r218 (added missing __init__.py ) committed by tobias.klipstein   -   added missing __init__.py

  added missing __init__.py
• Nov 11, 2009

  issue 36 (Dojango throws exceptions on Ubuntu 9.10 64bit) changed by tobias.klipstein   -   Seems there needs to be a bugfix-release soon.

  Status: Duplicate

  Seems there needs to be a bugfix-release soon.

  Status: Duplicate
• Nov 11, 2009

  issue 35 (Python does have package "google" ) commented on by tobias.klipstein   -   Issue 36 has been merged into this issue.

  Issue 36 has been merged into this issue.
• Nov 11, 2009

  issue 36 (Dojango throws exceptions on Ubuntu 9.10 64bit) reported by ggreenaway   -   What steps will reproduce the problem? 1. Running Dojango 0.4 on Ubuntu 9.10 64bit What is the expected output? What do you see instead? Visiting any django page which is using dojango elements results in an exception "'module' object has no attribute 'appengine'". This exception are found on the dojango test page as well. What version of the product are you using? On what operating system? 0.4 of Dojango on Ubuntu 9.10 64bit Please provide any additional information below. The version from SVN works and does not result in the exception.

  What steps will reproduce the problem? 1. Running Dojango 0.4 on Ubuntu 9.10 64bit What is the expected output? What do you see instead? Visiting any django page which is using dojango elements results in an exception "'module' object has no attribute 'appengine'". This exception are found on the dojango test page as well. What version of the product are you using? On what operating system? 0.4 of Dojango on Ubuntu 9.10 64bit Please provide any additional information below. The version from SVN works and does not result in the exception.
• Nov 08, 2009

  DjangoModelStore (Using dojo.data.* with dojango.data.modelstore) Wiki page added by benwilber   -   Revision r217 Intro to django-modelstore

  Revision r217 Intro to django-modelstore
• Nov 08, 2009

  r216 (merge django-modelstore r11) committed by benwilber   -   merge django-modelstore r11

  merge django-modelstore r11