Correct, so because of that the free text field can be shown in that
same spot (anywhere you want) on the front end when a visitor views
the page (not just the bottom - or I believe the top - like it was
before). Again, sorry for the catch-up here. I had surgery on my
shoulder which has kept me away. :/
On Nov 25, 11:37 am, "Yaron Koren" <[EMAIL PROTECTED]> wrote:
> If I understand your question correctly, the answer is that you can now
> place the "free text" field anywhere within a form definition.
>
> -Yaron
>
> On Tue, Nov 25, 2008 at 11:16 AM, robertuva <[EMAIL PROTECTED]> wrote:
>
> > Yaron - sorry, I'm behind on the new versions. Does this only allow
> > positioning of the free text field in a form, or does it allow for
> > placement of the free text field contents in various places in a
> > template (so on the front end the user might see free text in an area
> > in the middle rather than at the top or bottom.
>
> > On Oct 13, 10:34 am, "Yaron Koren" <[EMAIL PROTECTED]> wrote:
> > > Hi all,
>
> > > Version 1.3.4 of Semantic Forms has been released. It has the following
> > > changes:
>
> > > - the 'free text' field is no longer defined as "{{{field|free text}}}" -
> > > it's now "{{{standard input|free text}}}". This was mainly done so that
> > the
> > > free text field could be placed among the various fields of a template -
> > > currently, the parser assumes that, if it's placed between "for template"
> > > and "end template", it's just another template field. Also, this change
> > > makes it clearer, when reading a form definition, that the free text
> > field
> > > is different from regular fields. The old definition still works, for
> > > backwards compatibility.
>
> > > - the combination of "autocomplete on property" and the textarea input
> > type,
> > > which wasn't working before, now works.
>
> > > - the YUI Javascript library has been upgraded from 2.5.2 to 2.6.0.
>
> > > - the #forminput parser function was doing incorrect URL-encoding that
> > was
> > > causing a problem in some non-English languages: this has been fixed -
> > > thanks to Jung Gun Lim for the fix.
>
> > > - the #formlink parser function no longer adds a newline before the link.
>
> > > - the 'UploadWindow' mini-page has a new meta tag that fixes the encoding
> > of
> > > Cyrillic and possibly other character sets; thanks to Dmitriy.
>
> > > - for email validation, the suffix no longer has to be at most 3
> > characters
> > > - now it can be up to 6 (this may have to be increased again later).
>
> > > - a fix was made so that autocomplete values that contain a newline won't
> > > break the Javascript.
>
> > > -Yaron
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Semantic Forms" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/semantic-forms?hl=en
-~----------~----~----~----~------~----~------~--~---
