Wagn 0.10 and beyond
We're very excited about the incremental releases we've made since Wagn 0.10. Wagn 0.10+2 introduces a new look — cleaner, bolder, less busy (what do you think?); we appreciate Paul Bloch's mockup for getting this started. With Wagn 0.10+3 we're taking compatibility more seriously — we're already well on our way to having things look good and work properly in Internet Explorer and Safari, and have started on Google's new Chrome browser too.
There are a bunch of changes that came with Wagn 0.10 that we want to share with you too, from the technical — we're compatible with Rails 2 — to the spectacular:
HTML cards are as powerful as the web itself, making it possible to embed videos, Twitter feeds, live chats, and any other web service that's out there directly into a Wagn card. Welcome, YouTube:
We also upgraded the text editor (now using TinyMCE). This made it possible for editing to work well in Safari, and handles a bunch of other longstanding annoyances, for example now you can resize text boxes. There's no link editor for now, so linking means learning to use double brackets.
Wagn is easier to customize now — you can decide what information will be requested of new users and what their welcome email will look like, and changing the sidebar is now as simple as editing *sidebar. These and other configuration cards which let you control the site logos, the Wagn's home page, etc. can be gathered into a Config card.
We changed names from "template" to "form" for talking about the cards that can control other cards' layout, card type, default permissions, etc. We also separated the two ways a form is applied — instead of using +*template cards in all cases, we now use +*tform cards for forms that are applied based on a card's Type, or *rform for forms that are applied based on the Right-most part of a card's name. (((((We also came up with more ways to apply forms — a given pattern of cardtype-cardtype or cardtype-rightside can now determine a card's form. ??not done yet, check)))))
You can now set the view of cards returned by a Search when you include a Search card. Until now they could only be in closed view. See "Specifying view of cards in lists" on nesting for more details and an example.
In nesting and CQL, you can now use _self to reference a card's name. On a compound names you can also use _left or _right to reference the names of a card's left and right parts. For more on both of these, see contextual references. This can be combined very powerfully with HTML cards and web services, sending variables based on the name of the card you're in to get back appropriate information for the context — you can see this in action at Connectipedia. The map, chart and tables there are pulled in from DataPlace, using an HTML card with an iframe with src="http://{ {Dataplace+uri base|raw} }table/{ {_left|name} }" (similarly, the link is generated with [ [http://{ {Dataplace+uri base|raw}}table/{ {_left|name} }|table] ] )
Simpler web addresses for searches and new cards — see web address for everything.