Slashdot Mirror

← Back to Domains

Domain: fforw.de

Stories and comments across the archive that link to fforw.de.

Comments · 7

  1. Unbloated Javascript library by fforw · · Score: 1 · on Five AJAX Frameworks Reviewed
    Some posts here have mentioned the large size of most javascript libraries.. I personally had the same problems and wrote myself a minimal javascript library with only:
    • HttpRequest related functions
    • IE compatibility layer for style classes and events
    • a DOM builder
    • firebug simulation
    • a few helper functions
    The whole thing is about 8kb for the js-compressed version (about 4kb if you also serve it gzipped) and is available under a BSD-like license from my blog site
  2. Unpopular AJAX library by fforw · · Score: 1 · on Open Source AJAX toolkits

    I'd like to advertise my own, unpopular javascript library:

    The ff javascript library
    A ultra lightweight (below 7k normal / below 3k gzipped) javascript library offering crossbrowser support for:

    • AJAX requests
    • Events
    • DOM element class handling
  3. Re:So How Do You Code an AJAX Web Page? by fforw · · Score: 1 · on So How Do You Code an AJAX Web Page?
    1. Not all all js libs are that large. (shameless plug: my ff javascript library is below 7k)
    2. Use Javascript compression
    3. Use gzip compression / gzip precompression ( ff javascript libray shrinks to below 3kb )
    4. Use Firebug
  4. Re:So How Do You Code an AJAX Web Page? by fforw · · Score: 1 · on So How Do You Code an AJAX Web Page?
    1. Not all all js libs are that large. (shameless plug: my ff javascript library is below 7k)
    2. Use Javascript compression
    3. Use gzip compression / gzip precompression ( ff javascript libray shrinks to below 3kb )
    4. Use Firebug
  5. New Turbogears features by fforw · · Score: 2, Informative · on Web Development with TurboGears and Python

    While the article mentions Catwalk (toolbox app to set up initial database objects) it does not mention some of the very nice new features in Turbogears 0.9a6 (supposed to be real close to 1.0 now):

    • Identity Management
      The turbogears quickstart can now create a set of customizable standard classes to handle standard authentication and authorization. A User Group Permission model coming with easy-to-use identity decorators for exposed methods. ( Identity Management Documentation )
    • Widgets / Forms
      A system to create reusable Form Widgets (with optional scripting / styles) and to use them in forms -- including support for error display and data retention.
    • Internationalization support
    • Optional support for SQLAlchemy instead of SQLObject
    The newly added toolbox offers the following tools:
    • Catwalk (mentioned in the article)
      Database tool meant to ease the creation of initial data. Sure, you can always just use plain SQL to set them up, but managing relations between tables can be slow and bothersome, especially for N-to-M relations (RelatedJoins in SQLObject terms)
    • Model Designer
      Toolbox tool helping to design your models. (Showing diagrams etc)
    • Web based python console
    • Widget Browser
      Allows browsing through all available Widgets with working examples, example code and configuration help
    • admi18n localization tool
      Tool to collect internationalized strings and create new language catalogs

    I started playing around with Turbogears some time ago and like it very much. The documentation is a bit thin at times, but the source code is easy to read and accessible (using ipython to interactively explore things also helped a lot.) I implemented my blog in python and had only minor problems. And the code size also turned out to be relatively small.. For the metrics fetishists:

    Blog with tagging, User handling (subscription, email confirmation etc), Image handling (upload, admin, thumbnails), atom feeds (general + tag based feeds) plus some minor things:

    • python code : 1181 lines, 40762 bytes
    • kid templates : 610 lines, 21200 bytes
    plus some style sheets, javascript code and images..
  6. Japano AJAX Integration by fforw · · Score: 2, Insightful · on Better Web Apps With Ajax
    The article is surely a good entry to developing java webapplications with "AJAX" (Can't someone invent a better name?).

    For me (I am the author of japano, an MVC/JSP engine also containing dynamic javascript integration features), the following additional principles are were important:

    • Usability first. Don't use AJAX without a decent fallback. Don't use AJAX just because you can. Use semantic, standard-conform HTML/CSS layouts.
    • Use JSON instead of XML
    • Keep it simple. No object brokering or other fancy things. JSON transports data. Javascript requests and browser requests uses the same mechanisms.
    • Integrate. AJAX has quite some complexity overhead. Try to minimize that complexity by offering framework assistance. Japano offers two different AJAX mechanisms. Javascript views, and Partial updates.
  7. Japano AJAX Integration by fforw · · Score: 2, Insightful · on Better Web Apps With Ajax
    The article is surely a good entry to developing java webapplications with "AJAX" (Can't someone invent a better name?).

    For me (I am the author of japano, an MVC/JSP engine also containing dynamic javascript integration features), the following additional principles are were important:

    • Usability first. Don't use AJAX without a decent fallback. Don't use AJAX just because you can. Use semantic, standard-conform HTML/CSS layouts.
    • Use JSON instead of XML
    • Keep it simple. No object brokering or other fancy things. JSON transports data. Javascript requests and browser requests uses the same mechanisms.
    • Integrate. AJAX has quite some complexity overhead. Try to minimize that complexity by offering framework assistance. Japano offers two different AJAX mechanisms. Javascript views, and Partial updates.