Submitted by Mark Birbeck on Tue, 2008-01-29 14:40.
For a long time now we've placed useful XForms links at the bottom of the page on this site. But the problem is that we don't always capture all of the useful sources of information that is available for XForms, and what links we do list are tucked away at the bottom of the page. (You might not even have known it was there!)
So I decided to set up a separate site called Planet XForms, that does nothing other than aggregate a number of XForms-related blogs, as well as various XForms-tagged resources, such as images from Flickr, presentations from SlideShare, videos from YouTube, events from Upcoming, links from Magnolia and del.icio.us, and news from Google. There is also a Feedburner feed if you want to get the whole bundle into your RSS reader in one go.
Planet XForms is completely automated, which means that if you have a screenshot that you want the XForms community to see, you don't need anyone's permission to get it onto the Planet XForms site; just upload it to Flickr, tag it with 'xforms', and it will soon show up. Similarly, if you have a useful tutorial, you could make a YouTube video or upload your slides to SlideShare, and as long as you don't forget the 'xforms' tag, your video or slideshow will quickly be available to anyone interested in XForms.
We'll leave the feeds on this site around for a little longer, but since Planet XForms is going to be so much easier to use, and includes far more material than we have here, we'll wind it down soon.
Submitted by Mark Birbeck on Tue, 2007-12-04 14:56.
XForms 1.1 has just been advanced to Candidate Recommendation status. This is a stage in the W3C's process where the specification is regarded as stable, and all that is needed are implementations of the features. Once there are sufficient implementations the specification can advance to a Full Recommendation.
formsPlayer was the first processor to implement all of the features in XForms 1.0, and by doing so we helped advance that specification to a Full Recommendation. We intend to help the standards process again, by implementing all of XForms 1.1, and whilst we already support most of the major new features, we hope to have the entire standard supported by early next year.
Submitted by formsPlayer on Thu, 2007-11-01 17:58.

On October 29th, the W3C released XForms 1.0 Third Edition as a Recommendation. The main changes are some important clarifications of how parts of XForms work, although there is one new feature--authors can now indicate which version of XForms their forms are targeting.
One clarification concerns more detail on how the rebuild and refresh events should behave, which closes off a few grey areas. Another comprises important information about how controls with an @id should be handled inside repeat; the issue of how triggers, for example, should behave in repeat has been undefined for a long time, so this marks a useful development.
There is also one new feature, which gives authors the ability to indicate which version of XForms their form requires. The new version attribute on the model element can be set to values such as "1.0", "1.1", and so on. If a processor doesn't support the version of XForms that the author has indicated then the xforms-version-error event should be dispatched.
Whilst the key features for web application support will come in XForms 1.1, the Third Edition of XForms 1.0 still contains some welcome refinements.
Submitted by Mark Birbeck on Tue, 2007-10-16 10:49.
On Monday we completed the move of formsPlayer.com from a Windows box sitting in a rack at a hosting company, to a Linux instance running in the virtual world of Amazon's EC2. Along the way we discovered RightScale, which builds on Amazon's excellent product to create something quite revolutionary.
During the course of the move we also upgraded Drupal to 5.2, which should give us more control over projects and releases. There are a number of things that are done differently in this version of Drupal, so please bear with us whilst we iron out the glitches.
Submitted by Mark Birbeck on Tue, 2007-09-04 11:44.
Over in the Upgrade forum Jozef Aerts has asked for clarification on versions 1.5.4 and 1.5.5. As he rightly points out, the 1.5.4 builds of formsPlayer Community Edition are newer than the 1.5.5 ones, which is a problem if you have installed any 1.5.5 builds--you can't upgrade to the newer software, because the version number you are trying to install is lower.
The problem stems from not having made clear in the past which builds are 'previews' (only recommended for brave developers wanting to have a look at new features that are coming down the line) and which builds are part of the main development path.
We've been working for a while on making future developer previews completely separate, to avoid confusion, and whilst we finish this process we've put on hold the new features from 1.5.5 (custom controls based on select and select1 will be easier to create). This means that for 1.5.6 we'll be concentrating on finishing the last few items from XForms 1.1, and resolving any outstanding bugs.
For further information see the formsPlayer Community Edition 1.5 roadmap.
Submitted by Mark Birbeck on Tue, 2007-08-21 13:42.
Since XForms can run on many different devices then it's obviously important for server-based systems such as Orbeon, Chiba and Intalio to be able to use any client-side XForms processor. This means that even if developers are aiming to avoid any installation requirement on the part of their users, it is still possible to make use of an XForms processor such as formsPlayer or the Firefox extension, if it is found to be already present on a user's machine.
To try to make this as easy as possible, we've released a GPL script that can be placed in an HTML or XHTML document, and which tries to assist in the use of client-side XForms processors if they are installed. The script will also help the user to install a processor if necessary.
The key point is to place control over whether or not to use a client-side processor in the hands of the user. When building HTML sites we try to make sure that browser choice is irrelevant, and the goal is to do the same for XForms. In this section we look at how we can do that.
|
Recent comments
3 days 4 hours ago
5 days 3 hours ago
1 week 2 days ago
7 weeks 18 hours ago
7 weeks 1 day ago
7 weeks 1 day ago
7 weeks 2 days ago
7 weeks 4 days ago
7 weeks 5 days ago
8 weeks 4 days ago