Blog

  • Experimenting with Tinderbox XML

    After I sucessfully imported some parts of my old weblog I reconsidered the idea to publish with Tinderbox to a database instead of using it to render HTML. Here is the current idea:

    • A Python script will read the Tinderbox file and publish this into a MySQL database
    • The database will be synchronized with a copy on the server
    • The server uses Zope to publish content (but can use anything that works with MySQL)
    • Server will use meta data, link data and possibly other things to create the site

    Some advantages:

    • No need for agents anymore, the searching/collecting is done entirely on the server
    • No need for export and rendering from Tinderbox
    • A wider range of possibilities when translating data to HTML (full scripting)
    • Agents and HTML export is still possible – e.g. to keep a “internal work site”
    • Can possibly be extended to work for other environments
    • Possibly opens a way to use other ways of translating ASCII text to HTML (e.g. ReStructuredText or Textile)
    • Could allow many authors to contribute to one site (but not edit content created by others)

    Some disadvantages:

    • Obviously there is code needed
    • Needs Python and MySQL on the client and MySQL on the server
    • Concept for a database structure and content specifications needed (how to use actually information from the Tinderbox file in the site)
    • A great deal of development needed on the server to turn the database into a site
    • Changing the Tinderbox file a lot could break the system
    • It is a one-way process – so no edits on the server travel back to Tinderbox

    I investigated PyXML and elementtree which I found via Uche Ogbujis article on XML.com. I also found this XML & Python tutorial by Alexandre Fyolle very helpful. This Devshed tutorial on MySQL & Python reminded me about how to connect to the database. All this worked pretty well in first experiments.

    The translation script will have to do some heavy work:

    • Translate Tinderbox commands (or invent own)
    • Maybe convert links and styles
    • manage images that are inside the Tinderbox file

  • What’s the blogging point?

    James Farmer discusses once again the benefits of weblogging in education. He concludes:

    … in a setting where expression, collaboration, peer support, successful class dynamics, risk taking, sharing and all these recognized characteristics of effective learning are fostered, then personal publishing allows for a revolutionary form of expression and exploration between learners in the same class and the rest of the world.

    So where do we find this setting? And how to set it up if not present?

    Almost every examples I have seen of serious student blogging, took place because running the weblog was more or less a requirement in the course. Students that start (and keep) a weblog without “formal requirement” are quite rare and only a fraction really blog in relation to their learning goals at all.

    What might be the reason?

    As I pointed out in my “Weblogs and Discourse” paper in many cases the learning culture at universities is actually not formally and/or informally valuing free exploration, expression, criticizing, collaboration and sharing beyond the scope of single educators. So if there are only some (often tech-savvy) teachers that are pushing weblogs, most students will spend time on weblogging only if they visit courses of those teachers.

    Following the (mis-)conception of many students, that it is not themselves (or the work group) but mostly the teacher that is responsible for the learning progress, it appears to be a ineffective activity for many of them to maintain blogs that non-blogging teachers do not evaluate (and thus will not influence their strategy for ensuring the learning progress). And even if students are blogging: few of them really will use a self-reflective style that actually displays learning progress and obstacles.

    So we have two questions that relate: one is about why students would blog at all and the second about how and what they blog. I have seen student blogs that are utterly useless from a teachers perspective, because they rarely dealt with issues from the courses. In other words: students were not showing much interest for the course contents at all – or – were hesitating to be explicit about their potential weaknesses or just things they were not sure about.

    But what – instead – I have seen were student initiated discussion groups that were completely unknown to the teachers. In fact, there is good reason for students not to display learning progress but rather to surprise teachers with more or less polished results near the end of a course. It’s a seductive strategy to keep the benchmarks low. This is especially true if students are skeptical or unconvinced about the professional skills of teachers – which happens to be part of the changed image of formal learning nowadays.

    I don’t want to express that many students actually want to learn this way. But I am convinced that they have learned to prefer this vicious cycle instead of the other one: facing a never ending difficulty because of teachers that are always tracking down weak spots (and so potentially narrowing the chances for good marks). The motto is “You don’t need to be good – you just need to be good enough!”.

    So before “personal publishing” can be a valuable tool and students really get more process oriented, we need to introduce a learning environment where teachers change their evaluation method and depart from a result orientation as well.

  • Card sorting: a definitive guide

    Donna Maurer and Todd Wafel get a hold on card sorting in the design process:

    “Card sorting is a simple, reliable, and inexpensive method for gathering user input for an overall structure. It is most effective in the early stages of a (re)design. And while it’s not intended to be a silver bullet, when done correctly, it is instrumental in capturing helpful information to answer questions during the information design phase — ultimately making the product easier to use.”

  • Gurus vs. Bloggers

    Andrei Herasimchuk has posted the first Gurus v. Bloggers Design Shootout, comparing the sites of Richard Saul Wurman, Bruce Tognazzi, Peter Merholz, Jakob Nielsen, Edward Tufte, Gerry McGovern, Donald Norman, and Andrei himself against design bloggers Jeffery Zeldman, D. Keith Robinson, Andy Budd, Didier Hilhorst, John Gruber, Greg Storey, John Hicks, and Josh Williams.

    The Bloggers win 8:0.

  • Open Source software lacks good interface design

    Michelle Levesque contemplates about the role of Interface Design in Open Source Software:

    The lack of focus on user interface design causes users to prefer proprietary software’s more intuitive interface. Open Source software tends to lack the complete and accessible documentation that retains users. Developers focus on features in their software, rather than ensuring that they have a solid core. (…) If Open Source software wishes to become widely used and embraced by the general public, all issues will have to be overcome.

    I can only second this position. I have evaluated many open source projects and I am amazed that the User Interface Design is seen as a followup problem — if at all.

    The animosity of software developers about interface design issues is steady. The problem here is not that they devalue the issue in general, but that there are common misconceptions about the importance. There is usually also minimal or no knowledge about how to ensure usable software at all in many open source projects.

  • RSS-Aggregator with Twisted

    Valentino Volonghi:

    This is a fully featured RSS aggregator with parsing included. It’s scalable to very high numbers of feeds and can be used in multi-client environment through web using Twisted with a little code on top of Nevow, or can easily be integrated inside every app which uses some of the toolkits supported by Twisted.

    [via Der Schockwellenreiter]

  • Unmoderated announce lists and “swarm unintelligence”

    One really odd phenomenon on the Internet is announcement mailing lists that are unmoderated. Especially if the receivers of that announcements never have learned that mail list servers have extra e-mail addresses for unsubscribe commands. Here is a true story:

    An unnamed software vendor announced a new product release through his announcement mailing-list a number recipients had enabled an automatic vacation message going to the Reply-To address of that announcement – which happened to be the whole list itself. So someone on the list thought it might be better for him to unsubscribe. He simply hit “Reply” and typed “unsubscribe” ahead of the fully quoted message that was then again sent out to hundreds of people (instead of unsubscribing him from the list). Few other people were annoyed by this and decided to — what else — do exactly the same. Then numerous replies traveled the net with outrageous utterances like “Stop this bombardment!!!” – generating another load of unsubscribe messages from helpless people. A handful list members sent mails to the list explaining that there is a problem and that everyone who wants to unsubscribe should visit a particular page that explains how to get off the list. But instead of following this advice someone got so upset that he decided from now on to answer every mail coming from this list with a separate unsubscribe message to the whole list (and luckily he did not do so with his own messages he got in return). Someone thanked the whole list saying that this unsubscribe thing is amazing and that he never got so much e-mail in his inbox. Another sent a helpful reminder that it might be worth not replying to the replies.

    I was not upset at all.

    On the one hand I was not upset, because I feel people don’t have the slightest idea how much spam mail people get whose mail addresses have been out there for many years (my Inbox currently lists 1829 unread messages and my Junk mail folder counts 7581 unread mails – and it contains messages from just the last week). I really felt jealous about those who were able to get upset by this.

    On the other hand I was amused watching those people throwing mud around screaming “Don’t throw mud around!”. Didn’t it appear to them that after receiving the first “unsubscribe” message that it has been delivered to the whole list and that probably trying this also would do the same? Obviously not. Very interesting.

  • Virtual Behavior Setting

    In an article in the Journal of Computer-Mediated Communication, Anita Blanchard, Assistant Professor of organizational psychology at the University of North Carolina, shows how Behavior setting theories can be applied to describe interaction within online communities. [via Emerging Communications]

  • Enhancing HTML with CSS+JavaScript

    John Ford does some interesting things on his website with CSS and JavaScript. Look at the “Show” feature on the left and the “Related” link in the top right corner (there is also a funny contact page).

  • What they didn’t teach me in Design & Usability school

    Scott Berkun was program manager at Microsoft for Internet Explorer. He wrote a nice essay about what he missed in university (and what might have been the reasons for it). Looking back on his work experience he summarizes what is important:

    The challenge is that what makes you credible to a developer, marketing executive, documentation manager, or any other person you have to deal with might be different for each one, and what earns you credibility won’t always be tied to your design or usability brilliance. Instead, work towards helping the team get stuff done. Be useful. Then when it comes time to bring your grand design vision to the table, you’ll have built the respect and trust necessary for them to be helpful to you.

  • Twisted based Weblog system

    Alan Green works on a Twisted based weblog system (see here for Twisted). Besides Twisted he uses SQLite (and PySQLite) to store the data.

    In an earlier post Alan also explains the reasons for Twisted. There I found also a very interesting link to Ian Bicking’s Website Framework Shootout.

  • Near-Time Flow

    This appears to be exactly what I need for my seminars: a simple tool that shares data about websites, RSS feeds and documents among participants of a seminar. Unfortunatly 90% of my students run on Windows – so I will probably not be able to use this software even if it would be free. [via schockwellenreiter]

  • Donald Norman on mental models

    Here is an interview with Donald Norman about the concept of mental models. It contains an interesting (and longer) passage about the possible relation between mental models and emotion:

    A mental model provides an immediate expectation about what you think is going to happen and the emotional system will evaluate that positively (positive affect or valence) or negatively (negative affect or valence). […]
    It’s good if we expect something bad that doesn’t happen and it’s bad if we expect something good that doesn’t happen. That impacts the way we feel if we continue using something (like a device) and it may impact what we do about it (continue use or abandon the device). […]
    At the intellectual level there is also the causality issue. That is, do we decide to blame the device or ourselves?

  • IHMC releases CMap v3

    The Institute for Human & Machine Cognition (IHMC) released the version 3 of their concept mapping client/server CMap. We were considering to do a full round of testing of the v2 release during the “Discourse tools” seminar, but developments in the course didn’t leave the time for that.

    Among a large set of new features, a redesigned, simple user interface enables users to share their knowledge and link their concept maps to those of others with simple drag-and-drop operations. The synchronous collaboration tool allows geographically dispersed participants to concurrently work on the same map, and see the others’ changes in real time.”

    The IHMC website is edited with such a collaborative concept map and the server automatically generates a website from that map.

  • Blog styles and antagonisms

    Jay Cross compares two blogging styles: journal and reference book. He suggests to further develop the weblog practice (and suggests his own blog as an practice example):

    The structure of most blogs accommodates their writers more than their readers. It’s time for bloggers to share their goals with their readers. Those goals should inform the way bloggers structure and maintain their blogs.

    I share the motivation of Jay Cross looking for improvement. But I have reservation as to which suggestion to make here. I don’t agree that the authors foremost interest should be to accommodate the expectations of readers. Likewise I don’t want to overrule the readers decisions with the site design, I also think that nobody can talk away the need for a weblog author to figure out his/her style by suggesting a normative approach.