Skip to main content

PyCon: The Wonderful World of Widgets for the Web

This was a talk on Tosca Widgets by Kevin Dangoor, the leader of TurboGears. Overall, Kevin's a pretty charismatic guy, and the talk was well received.
  • These days, users require nicer, more featureful forms. Things like WYSIWYG widgets, date picker widgets, and autocompletion are becoming ubiquitous.
  • The goal of Tosca Widgets is to provide a way to encapsulate the HTML, CSS, and JavaScript necessary for things such as a WYSIWYG widget into a convenient package.
  • A Tosca Widget knows how to output HTML to link in the CSS and JavaScript.
  • Conceptually, this is part of the view layer (i.e. the V in MVC).
  • You are responsible for passing a value into the widget.
  • They are using FormEncode for validation.
  • The library knows how to aggregate individual widgets into a form.
  • Because the HTML, CSS, and JavaScript are packaged together, it's easy to add Ajax behavior to the widget.
  • However, they don't yet have built in JavaScript validation. JavaScript validation routines built on top of FormEncode would be a natural progression.
  • It's easy to package a widget into a Python egg. The widgets installed are discoverable because they provide a setuptools entry point.
  • Unlike Dojo widgets, the emphasis is on packaging things together from the server's point of view. (I'm a little unclear about the correct overlap between these two projects. I get the feeling that he was hand waving a bit. However, it's clear that packaging widgets into Python eggs is helpful.)
  • They're using a templating engine (Kid?) for the HTML, but they're thinking of getting rid of that, per Ben Bangert.
  • There is a Tosca Widgets browser that lets you play around with all of the widgets you have installed.

Comments

kdsfjaskldf said…
However, they don't yet have built in JavaScript validation. JavaScript validation routines built on top of FormEncode would be a natural progression.

That's the current plan. I've talked to Ian about this and he's said that he'll accept patches for this. One more thing on my todo list...

Unlike Dojo widgets, the emphasis is on packaging things together from the server's point of view. (I'm a little unclear about the correct overlap between these two projects. I get the feeling that he was hand waving a bit. However, it's clear that packaging widgets into Python eggs is helpful.)

Dojo widgets (and GWT/Pyjamas) provide similar goals but the emphasis is purely on building up things in the browser while ToscaWidgets builds things on the server and provides form processing and handling as well. You can package dojo widgets as ToscaWidgets if you so desire.

BTW, I find that yui and yui-ext widgets better fit my style than the dojo equivalents.

They're using a templating engine (Kid?) for the HTML, but they're thinking of getting rid of that, per Ben Bangert.

ToscaWidgets can use any Buffet interface templating language to define widgets. Ben is concerned about perf and has requested that they be strings. Not sure what will come of this.

There is a Tosca Widgets browser that lets you play around with all of the widgets you have installed.

It's rough right now. I'm hoping to get this done and a preliminary version out this weekend.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p