Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 1 of 4

A set of utilities for creating robust pagination tools throughout a django application. Screencast: History2008-10-24: Version 1.0 Released

5.0
 
  0 reviews  |  6 users  |  308 lines of code  |  0 current contributors  |  Analyzed 8 days ago
 
 

Django Endless Pagination can be used to provide Twitter-style or Digg-style pagination, with optional Ajax support and other features like multiple or lazy pagination. The initial idea, which has guided the development of this application, is to allow pagination of web contents in very few ... [More] steps. **Documentation** is `avaliable here: http://django-endless-pagination.readthedocs.org/ To file **bugs and requests**, please use https://github.com/frankban/django-endless-pagination/issues. The **source code** for this app is hosted on https://github.com/frankban/django-endless-pagination. The **Mercurial repository** of this project is hosted on https://bitbucket.org/frankban/django-endless-pagination. [Less]

5.0
 
  0 reviews  |  1 user  |  3,253 lines of code  |  7 current contributors  |  Analyzed 7 days ago
 
 

This library of Adobe Flex components and skins enables seamless use of remote data sources where a single call to load all data is impractical. The components are designed to work with the Flex SDK. Flex 4 is recommended, but the components will work with Flex 3.

0
 
  0 reviews  |  1 user  |  1,819 lines of code  |  1 current contributor  |  Analyzed 5 days ago
 
 

Tiny Javascript Slideshow

0
 
  0 reviews  |  1 user  |  270 lines of code  |  1 current contributor  |  Analyzed 10 days ago
 
 

Easy integration between jQuery DataTables and Django.

0
 
  0 reviews  |  1 user  |  14,118 lines of code  |  3 current contributors  |  Analyzed 8 days ago
 
 

python-paginationFeatures:Simple and minimalist API Most of the common functionality required in dealing with generating page navigation etc. Generic and not tied to any frameworks Sourcesvn checkout http://python-pagination.googlecode.com/svn/trunk/ python-pagination CreditsThe API and ... [More] implementation are heavily borrowed from Perl CPAN. See also the ff: Data::Page - http://search.cpan.org/perldoc?Data::Page Data::Pageset - http://search.cpan.org/perldoc?Data::Pageset [Less]

0
 
  0 reviews  |  0 users  |  226 lines of code  |  0 current contributors  |  Analyzed 2 days ago
 
 

Cornweb is an umbrella project for four separate libraries, each dedicated to a different part of Web development: Depot: Basic WSGI application framework, built to handle the routing of URLs and dispatch of requests Backfire: High-level wrapper atop Depot for building sophisticated Web ... [More] applications. It includes facilities for the integration of Genshi and SQLAlchemy, as well as the encapsulation of common application behaviors, such as pagination and form processing. Formosa: Processing of user input to Web applications. Unlike most other form processing packages, Formosa allows for declarative, higher-level constraints on user input. Facade: Library for the generation of interface markup using Genshi. Facade helps to automate the most repetitive parts of HTML user interfaces, namely forms and pagination. These libraries were written after the development of the Chromatin Consortium Database (CCDB), an information system for a multi-institutional genetics project. Having implemented CCDB in Ruby on Rails, it was found that Rails failed to scale to the complexity required by such a project. These libraries were designed based on those lessons learned. Cornweb is released under the MIT license. It was developed by the Functional Genomics of Maize Chromatin Consortium, and is Copyright 2008 by The University of Arizona. [Less]

0
 
  0 reviews  |  0 users  |  0 current contributors
 
 

A framework that allows developers to implement pagination in their application.

0
 
  0 reviews  |  0 users  |  710 lines of code  |  0 current contributors  |  Analyzed 9 days ago
 
 

Pagination for the Zend Framework.

0
 
  0 reviews  |  0 users  |  206 lines of code  |  0 current contributors  |  Analyzed 8 days ago
 
 

Following changes are made in Display Tag 1.0 tag library code and tag library descriptor in order to meet specific requirements. 1. A new tag-attribute “defaultPage” of type “int” has been added to the TableTag. The org.displaytag.tags.TableTag.java code has been modified to add this ... [More] attribute as well as associated getter-setter methods. In the initParameters () method of TableTag class, the logic to initialize the “pageNumber” instance variable has been modified. If user has provided the value to the “defaultPage” attribute, it should be considered to initialize the pageNumber, else the existing logic to initialize the pageNumber (either value of pageNumberParameter.initiValue () or else ‘1’ if pageNumberParameter is null.) has been used to initialize it. The difference in the original code line & modified code is as follows Original Code: this.pageNumber = (pageNumberParameter == null) ? 1 : pageNumberParameter.intValue(); Modified Code: this.pageNumber = (pageNumberParameter == null) ? ((defaultPage <= 0) ? 1 : defaultPage) : pageNumberParameter.intValue(); 2. The tag library descriptor(TLD) file having TableTag definition has been changed to incorporate the new “defaultPage” attribute definition for the TableTag. defaultPage false true Intension for the code changes: In case the records shown are too large to fit in the page, which results in a paginated result, the default page can be set to any page other than the first page, due to this attribute. The records shown by a table using display tag may contain links. If a user traverses the paginated records and reaches on nth page. On this page, he clicks some link contained in one of the records, which takes him/her to some other page. After he wishes to return back to the results page(May be; by clicking some housed “Back” button), he should return to the nth page; the page from where he was redirected to other page and not the first page of the results. The addition of “defaultPage” attribute helps setting it as the page (among the pages from the paginated result set), where he should be brought back, after he has been redirected from it(by clicking link to some other page). [Less]

0
 
  0 reviews  |  0 users  |  0 current contributors  |  Analyzed 2 days ago
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.