Projects tagged ‘ajax’ and ‘django’

django-simp is a simple django based image manipulation programm with a easy to use ajax interface. it's programmed with: * django * dojotoolkit * python-pil it's designed for: ... [More] * easy inclusion in other applications * a easy to use ui [Less]

Getting StartedOut of the box, django-seeker supports building a filter-based search interface driven from a django model. To get started, we'll walk through adding a search interface for a model to ... [More] an existing project. Keep in mind that the backend is pluggable, allowing you to write code to search on any data model. PrerequisitesjQuery json2.js jQuery UI Datepicker jQuery Form Plugin (for AJAX file imports) URLsIncluding the seeker application is easy: from seeker.plugins.model import ModelSearchPlugin params = { 'plugin': ModelSearchPlugin(MyModel), 'base_template': 'search.html', } urlpatterns = patterns('', ( r'^search/', include('seeker.urls'), params ), ... )The base_template parameter is the name of a template that the seeker template will derive from. By default, it looks for a template named search.html. This allows you to embed the search interface into your site using your own base template. The base template can also take care of including the required CSS and javascript files. There is also a media_url parameter to specify the location of the images that seeker needs to load. By default, media_url defaults to settings.MEDIA_URL + '/images/seeker/', so if your MEDIA_URL was set to http://media.mysite.com, media_url would be http://media.mysite.com/images/seeker/. We'll get into media more below. MediaSeeker relies on some external javascript libraries, as well as it's own javascript code. As mentioned before, including these files in a base template makes things very easy. Your base template (search.html in the example above) may look something like this: {% extends "site_base.html" %} {% block extra_head %} {% endblock %} {% block content %} {% block seeker %} {% endblock %} {% endblock %}In this template, jquery.js was not included, since it was already included as part of the site_base.html template. You'll notice that we override the content block, and set up a seeker block -- this is where the interface will be rendered. This template also assumes that you have either copied or symlinked the necessary files into the appropriate MEDIA_ROOT directories. Basically, as long as all the required files are included, seeker doesn't care how you get them there. CustomizationThe interface is fully customizable using CSS. You can also customize the HTML by using your own template, and passing template_name as a parameter when you include the URL configuration. As of r7, you can create an inner Search class (much like Meta) to define excluded fields, initially displayed fields, and follow relationships. For example: class OtherModel (models.Model): data1 = models.CharField( max_length=100 ) data2 = models.CharField( max_length=100 ) class MyModel (models.Model): label = models.CharField( max_length=100 ) status = models.ForeignKey( Status ) active = models.BooleanField() other_info = models.ForeignKey( OtherModel ) class Search: exclude = ('active','other_info__data2') initial = ('label','status','other_info__data1') follow = ('other_info',)Note that you can exclude related fields from being searched/displayed, as well as specifying related fields to be initially displayed. The follow argument tells ModelSearchPlugin that fields from the related model should also be included for search/display. If the followed model has a Search inner class, those rules as respected as well. Caching and PerformanceBy default, the ModelSearchPlugin uses Django's cache system to cache result sets. This is controllable by the cache_results and cache_time properties on the plugin object. As of r7, the ModelSearchPlugin takes an optional select_depth argument, which defaults to 1. This is passed as the depth argument to select_related(). Ideally, it should be set to the maximum depth of any related fields that are available as display fields. This will greatly improve performance when rendering and sorting result sets. [Less]

This projects uses the great Mootools javascript framework to make a ajax datepicker. It uses Ajax because with the server-side language it's possible to have features like i18n and it's possible to ... [More] get data from a datababase, and the javascript code will be significantly smaller. The server-side will have PHP and Django(Python) versions, but it will be easy to make it work with other languages/frameworks. [Less]

Online chat, built on XMPP protocol, working on GAE

django_evserver is simple http server for Django applications. It's based on libevent library. The main advantage of django_evserver is that it provides methods of preempting django views. You can ... [More] render a site in several chunks, each of them can be handled by different django view. Using this idea it's possible to use django_evserver as comet server for django applications. Yes! Now you can write comet applications in django! [Less]

Django application that provides a facility to track file upload progress.

Mainly for project manager, specially who manage several projects at the same time. The main features are: use project concept, which can manage several posts in one page. project has its own page to ... [More] descripe the project info, memo etc. provide a todo list through all projects. provide a mini PIM capability. provide skin [Less]

dinamyc cms for django with ajax and jquery

IntroductionThe Django Framework offers a way to serialize internal objects into xml, json and other formats. django-simple-api extends this to a lightweight API, vaguely following REST principles. ... [More] NewsDownloaduse the SVN version to get the most actual code: svn checkout http://django-simple-api.googlecode.com/svn/trunk/ django-simple-api InstallContributeEvery contribution is welcome! questions feature ideas bug reports suggestions [Less]

This is a ready solution for a simple gallery field. Just add it to your model and you have a full blown ajax image upload, drag and drop reordering and relation management. The project is in very ... [More] early stage - SEE LIMITATIONS below. ScreenshotYay, everybody wants to see the thing first, right? First imaging screenshot FeaturesEasy setup - just add the field to your model Ajax image upload/deletion Drag and drop photo reordering Easy to modify the Image model - no need to change the forms etc. Automatic thumbnail creation handled by imagekit - clean metaclass based configuration jQuery js and jQuery.ui effects (a controvertial one :P ) Self tests (using django unit tests) RequirementsDjango 1.0 django-imagekit get it here Python PIL library Patience. A LOT of it :P feedback for the author about bugs :) Quick start0. Preparation Install imagekit easy_install django-imagekitPut 'imagekit' in your INSTALLED_APPS. 1. Svn checkout svn co http://django-imaging.googlecode.com/svn/trunk/ django-imagingEventually - if you are deploying django-imaging on a test project you can do a fast import (and ommit steps 2, 3): # cd my_project_dir # svn co http://django-imaging.googlecode.com/svn/trunk/ . --forceThis will download the stuff right into your project dir - if your MEDIA_ROOT is called 'media' and is in your project dir, you don't need to do any further copying :) 2. Put "imaging" folder into your python path (easiest way: put it in your django project directory) 3. Put the contents of the media folder in your project's MEDIA_ROOT Make sure the imaging_photos folder has 777 permissions 4. Add "imaging" to your INSTALLED_APPS tuple in settings.py (remember about having imagekit there too!) 5. Include imaging in your urls.py urlpatterns = patterns('', (...) (r'^imaging/', include('imaging.urls')), (...) )Or include('myappname.imaging.urls') 6. Add ImagingField to desired model from imaging.fields import ImagingField class Somemodel(models.Model): photos = ImagingField() 7. Optionally add a related model field for easy image fetching from django.contrib.contenttypes import generic from imaging.fields import ImagingField from imaging.models import Image class Somemodel(models.Model): photos = ImagingField() photos_set = generic.GenericRelation(Image) 8. Optionally add a custom imaging config to your settings.py IMAGING_SETTINGS = { 'image_dir' : 'funny_photos', 'specs' : 'funnyapp.specs', } Above example will make django-imaging put uploaded images in MEDIA_ROOT/funny_photos and will use the PROJECT_ROOT/funnyapp/specs.py as imagekit specs for thumbnail creation and thumbnail manipulation. For details refer to imagekit quick reference steps 3-6. 9. Syncdb to create proper imaging tables. 10. Test your setup (beggining with r9): cd /your/project/home ./manage test imagingHave fun :) Limitationsthumbnailing has serious flaws and only JPG support at the moment fixed in r7, now it's handled by imagekit. Currently only one ImagingField per model. Drag'n'drop doesn't work properly in Opera fixed in r6. No orphaned images management ManyToMany relation with an Image not supported Need to add a GenericRelation field manually, I can't figoure out how to autoadd it Exeptions not handled too well [Less]