Changes between Version 50 and Version 51 of SummerOfCode2006
- Timestamp:
- Apr 23, 2006, 12:44:11 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SummerOfCode2006
v50 v51 9 9 * James Bennett 10 10 * [http://www.simonb.com/ Simon Blanchard] 11 * [http://postneo.com Matt Croydon]12 * Kenneth Gonsalves13 * [http://www.holovaty.com/ Adrian Holovaty]14 * [http://feh.holsman.net/ Ian Holsman]15 * [http://jacobian.org/ Jacob Kaplan-Moss]16 * [http://lazutkin.com/ Eugene Lazutkin]17 * [http://lovebox.ath.cx/ Andreas Neumeier]11 * [http://postneo.com Matt Croydon] 12 * Kenneth Gonsalves 13 * [http://www.holovaty.com/ Adrian Holovaty] 14 * [http://feh.holsman.net/ Ian Holsman] 15 * [http://jacobian.org/ Jacob Kaplan-Moss] 16 * [http://lazutkin.com/ Eugene Lazutkin] 17 * [http://lovebox.ath.cx/ Andreas Neumeier] 18 18 * ... 19 19 … … 34 34 Try to scope ideas/proposals to the 4-month timeline -- simply proposing to fix a ticket or two will probably result in your proposal being rejected in favor of a more ambitious one. The SOC '''does not cover activities other than coding''', so certain ideas ("Write a more detailed tutorial" or "Create demonstration screencasts" or "Add a pony") are not suitable for inclusion here. 35 35 36 * Build a public repository for reusable Django applications. This probably includes:36 * Build a public repository for reusable Django applications. This probably includes: 37 37 * a standard way of packaging Django apps for distribution 38 * inf astructure for automatically downloading and installing packaged Django apps.38 * infrastructure for automatically downloading and installing packaged Django apps. 39 39 40 * Create Django packages and buildscripts for Linux (various), FreeBSD (There already is one www/py-django), OS X (Fink and Darwinports), etc.40 * Create Django packages and buildscripts for Linux (various), FreeBSD (There already is one www/py-django), OS X (Fink and Darwinports), etc. 41 41 42 * Create a generic, reusable search/indexer component (capable of htmlentities).42 * Create a generic, reusable search/indexer component (capable of htmlentities). 43 43 44 * Enhance the admin's support of rich media:44 * Enhance the admin's support of rich media: 45 45 * richtextfield using tinymce integrated with file explorer mentioned below 46 46 * create a file explorer for MEDIA_ROOT in the admin: browsing and making directories, uploading files … … 49 49 * support for uploading large files through the admin with a pretty progress indicator 50 50 51 * Implement ModelInheritance.51 * Implement ModelInheritance. 52 52 53 * Make something like models.!RequestModel allowing to pass request to the model, so it would be possible to access the current user etc. from the model, the admin should be made to pass request if the model inherits from models.!RequestModel53 * Make something like models.!RequestModel allowing to pass request to the model, so it would be possible to access the current user etc. from the model, the admin should be made to pass request if the model inherits from models.!RequestModel 54 54 55 * Implement SchemaEvolution.55 * Implement SchemaEvolution. 56 56 57 * Implement a set of reusable AJAX components using Dojo and Django as a backend, including:57 * Implement a set of reusable AJAX components using Dojo and Django as a backend, including: 58 58 * Non-admin widgets 59 * Admin widgets to bring Django closer to, e.g., !MicrosoftAccess (''NB: if Django ever bec ames anything LIKE Access, I'm leaving. -- JKM'') for creating database applications:59 * Admin widgets to bring Django closer to, e.g., !MicrosoftAccess (''NB: if Django ever becomes anything LIKE Access, I'm leaving. -- JKM'') for creating database applications: 60 60 * !MultiSelectComboBox that works for thousands of rows and can display multi-column results 61 * Easily create any levels of in lined editing widgets61 * Easily create any levels of in-lined editing widgets 62 62 * Compose admin pages of !AjaxPortlets that can be connected together 63 63 64 * Add spell checking to !CharField and !TextField with a well thought out interface (getting the interface right will be significantly harder than the backend code).64 * Add spell checking to !CharField and !TextField with a well thought out interface (getting the interface right will be significantly harder than the backend code). 65 65 66 * Change the permissions system to be more flexible (ACL's, Zope-style role based authorization, etc.)66 * Change the permissions system to be more flexible (ACL's, Zope-style role based authorization, etc.) 67 67 68 68 * Implement custom redirects and field templates for the admin system. (This isn't very ambitious as-is.) 69 69 70 * Refactor package settings so things like {{{django.template}}} are usable outside of django. [http://groups.google.com/group/django-developers/tree/browse_frm/thread/5b590b5487e500c1/c0f0d30cec89b107?rnum=1&q=GvR&_done=%2Fgroup%2Fdjango-developers%2Fbrowse_frm%2Fthread%2F5b590b5487e500c1%2Fdcce2e4ee4114894%3Fq%3DGvR%26rnum%3D1%26#doc_5aa26d41ed06ae7c details]70 * Refactor package settings so things like {{{django.template}}} are usable outside of django. [http://groups.google.com/group/django-developers/tree/browse_frm/thread/5b590b5487e500c1/c0f0d30cec89b107?rnum=1&q=GvR&_done=%2Fgroup%2Fdjango-developers%2Fbrowse_frm%2Fthread%2F5b590b5487e500c1%2Fdcce2e4ee4114894%3Fq%3DGvR%26rnum%3D1%26#doc_5aa26d41ed06ae7c details] 71 71 72 * A better built-in webserver and an '''officially''' supported methodology to connect to lighttpd and similar servers. While the apache+modpython solution is highly performant there are numerous situations where that setup is unfeasible or overkill. It is great that Django scales up well, if would be great if it scaled downwards as far as setup and deployment goes.72 * A better built-in webserver and an '''officially''' supported methodology to connect to lighttpd and similar servers. While the apache+modpython solution is highly performant there are numerous situations where that setup is unfeasible or overkill. It is great that Django scales up well, if would be great if it scaled downwards as far as setup and deployment goes. 73 73 74 * Streaming uploads and downloads. Uploading a large file can break django as the files are stored in the request. This is a security flaw as well, denial of service attacks could be as simple as uploading one large or more smaller files simultanously.74 * Streaming uploads and downloads. Uploading a large file can break django as the files are stored in the request. This is a security flaw as well, denial of service attacks could be as simple as uploading one large or more smaller files simultaneously. 75 75 76 76 * Parametrized templates. Currently the only way to use the content of another template in a place that does not contain blocks is to include it. But that includes the whole template. It would be very nice if one could include blocks defined in other templates to be evaluated in a certain context. (this turned out to be harder to explain than I thought, basically what I'm saying is to introduce a new kind of block that works like a function, where you could call/import a block and pass it some parameters)