Inclusion "type" is going to be "soon to be deprecated"

[sve...@seznam.cz]

Hello Ethan,

I was playing around with my own sets today. I have created like how-to set and customized the content with:
{{+(Error) Description | titled}}
{{+Solution | titled}}
{{+Solution Script | titled; type:File}}
{{+Documentation (Manpages) | titled; type:File }}
{{+External links | titled; type:HTML}}

When I was searching for possibility having multiple tags I found out that the "type:HTML" typing is going to be deprecated. (http://www.wagn.org/wagn/Documentation). Is there a "better" way now to create customized set's content? (watched the youtube videos which are superb :))

Regards,

Patrik

[Ethan McCutchen]

Hi Patrik,

The alternative is to use the "*default" setting, which is described in the "Setting Defaults" section of the formatting doc.

In your example below, you could create a *default rule for "+External links" with a card called "External links+*right+*default".  If it's type is "HTML", then the +External links card will have that type.  If it has some default content, then the new card will have that content.

It's a powerful configuration framework that gives you lots of neat alternatives for making the pattern as broad or as narrow as you want, but the user experience for that kind of setting is still pretty weak.  It basically means that as a wagneer you have to shift to a completely different page and context to complete a fairly simple configuration.

The good news is that we have a plan that I think will transform form editing into a fantastic user experience.  It's not fully documented, but it's being tracked on the add wagneer friendly form creation ticket.  In short, the idea is that you'll be able to edit rules from within the form itself.

The pre-release of Wagn 1.8 is coming out this week, and you'll see that there is some major improvement to the rules editing interface, which is a big step towards the wagneer-friendly forms.

As for the deprecation, that won't be happening until we introduce the new form editing, and I expect that we won't fully deprecate it until we've made a migration to transfer the form inclusions into the new representation. So you shouldn't worry too much about work you've already done that uses that syntax.

- Ethan

P.S. Sorry for all the boldfacing -- I know lots of folks prefer to skim these emails, and I wanted to make it easy for them

--
You received this message because you are subscribed to the Google Groups "Wagneers" group.
To post to this group, send email to wagn...@googlegroups.com.
To unsubscribe from this group, send email to wagneers+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/wagneers?hl=en.

--
Ethan McCutchen

One of the Wagneers, Wagn.org

Wagn. How pioneers roll.

s: ethan.mccutchen

t: @intogreater