MORE Blog modules!MORE Blog modules!MORE Blog modules! 07/07/2004 12:55 PM Imagine my shock and delight as I trolled through Roland Tanglao's page yesterday and discovered Flickr's 'Zeitgeist! It's YA blog gutter display module - picking up where Laszlo's Photoblox leaves off. Now instead of having to build XML files of your slide show/photo album - it takes the images directly from your Flickr collection - PERFECT! Another win for integration! Aren't built-in constructs fun - once you KNOW they're there? Then I found a post by Stewert Butterfield on it. This all happened while I was down and off-line (fighting malware), so my apologies to Stewert and the rest of the Flickr team. Great job guys and gals! Now my Flikr photos get sent to this coolio checkerboard, puzzle display (even if it's done in Flash - it's still cooolio - the Flickr people are Flash masters.....) My only request is for a larger and even largest size. I can get over 50%-60% more display space in my gutter! I hate wasting space. Here's Stewert's post.....
It's the first step towards making all kinds of slices through the
giant pool of photos. This one grabs a selection of recent photos to
cycle through and pops new ones in as they are uploaded. This is a GrokNews Entry: (what is grok?)MORE Blog modules!Grok Headline matches for MORE Blog modules!SAS Modules I 0.1.0SAS Modules I 0.1.0 12/03/2003 07:34 AM Modules for the Site@School content management system. SAS Modules I 0.0.12SAS Modules I 0.0.12 11/18/2003 10:21 AM Modules for the Site@School content management system. Tivo VLC modulesTivo VLC modules 03/26/2005 04:46 PM Tivo VLC modules first release E-Xoops ModulesE-Xoops Modules 01/02/2004 07:17 AM Welcome XML 4 Merge ModulesXML 4 Merge Modules 09/19/2004 05:52 PM from components to modulesfrom components to modules 01/11/2004 07:52 AM Right now I'm refactoring/rebuilding the user interface of a new release coming out soon (oh right... Note to self: talk about that) and I'm facing the fight against "sticky" APIs. Or, in more technical terms, their coupling. Ideally, a certain component set that is self-contained (say, and HTML component) will be isolated from other components at the same level. This makes it both simpler, easier to maintain and, contrary to what one might think, often faster. While I was at Drexel, at the Software Engineering Research Group, I did work on source code analysis, studying things like automatic clustering (paper) of software systems, that is, creating software that was able to infer the modules present on a source code base using API cross-references as a basis. Since then I've always been aware (more than I was before that, that is) of the subtle pull created by API references. The holy grail in this sense is, for me, to create applications that are built of fully interchangeable pieces, that connect dynamically at runtime, thus avoiding compile-time dependencies. In theory, we have many ways of achieving this decoupling between components or component sets; in practice there are some barriers that make it hard to get it right the first time. Or the second. Or... First, the most common ways of achieving component decoupling are:
Achieving decoupling in non-UI components is not too difficult (the data model has to flexible enough though, see below). But UIs are almost by definition something that pulls together all the components of a program so they can be used or managed. The UI references (almost) everything else by necessity, directly or indirectly, and visual components affect each other (say, a list on the left that changes what you see on the right). In my experience, MVC is an absolute necessity to achieve at least a minimal level of decoupling. Going further is possible by using a combination of data (ie., config files) to connect dynamically loaded visual components removes the coupling created at the UI level, but that is difficult to achieve, because it complicates the initial development process (with dynamically loaded components bugs become more difficult to track, the build process is more complex, etc.) and development tools in general deal with code-units (e.g., classes, or source files) rather than with modules. They go from fine-grained view of a system (say, a class or even a method) to a project, with little in between. We are left with separating files in directories to make a project manageable, which is kind of crazy when you think how far we've come in other areas, particularly in recent years. The process then becomes iterative, one of achieving higher degrees of decoupling on each release. One thing I've found: that the underlying data model of the application has to be flexible enough, be completely isolated (as a module) and relatively abstract, not just to evolve itself but also to allow the developer to change everything that's "on top" of it and improve the structure of the application without affecting users, etc. Yes, this is relatively "common knowledge", but I'm a bit frustrated at the moment because I know how things "should be" structured in the code I'm working on but I also know that time is limited, so I make some improvements and move on, leaving the rest for the next release. Final thought: Until major development tools fully incorporate the concept of modules into their operation (and I mean going beyond the lame use of, for example, things like Java packages in today's Java tools), until they treat a piece of user interface as more than a source file (so far, all of the UI designers I've seen maintain a pretty strict correspondence between a UI design "form" and a single file/class/whatever that references everything else), it will be difficult to get things right on the first try. Unrealircd modulesUnrealircd modules 01/25/2004 04:13 PM updated modules Installed Perl Modules in RSSInstalled Perl Modules in RSS 07/09/2004 08:32 AM Another interesting use for RSS for your delectation and pleasure. This one is for Perl coders, and is proving deeply useful. Installed Perl Modules in RSS. Automatically listing which modules you have installed yourself, and linking to their documentation. Very... Jon's Python modulesJon's Python modules 04/11/2004 12:04 PM jonpy 0.06 released MOM FAQ: NetIQ AppManager ModulesMOM FAQ: NetIQ AppManager Modules 04/11/2004 05:02 PM Payroll Perl Modules 0.8Payroll Perl Modules 0.8 08/12/2004 10:17 PM A Perl API for calculating payroll taxes. Modules drop in for v1.2 BluetoothModules drop in for v1.2 Bluetooth 06/17/2004 05:09 AM Electronics Talk Jun 17 2004 9:52AM GMT Payroll Perl Modules 0.7Payroll Perl Modules 0.7 07/30/2004 07:21 PM A Perl API for calculating payroll taxes. Payroll Perl ModulesPayroll Perl Modules 01/19/2004 04:16 PM Payroll 0.6 released Kernel Modules that Lie About Their
|
Also check out: |