Comments on: AJAX book, Web 2.0 Workgroup and T-dot Enablr http://davidcrow.ca/article/724/ajax-book-web-20-workgroup-and-t-dot-enablr Commentary about high tech happenings in hogtown Tue, 07 Feb 2012 05:42:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Ken King | King Marketing http://davidcrow.ca/article/724/ajax-book-web-20-workgroup-and-t-dot-enablr/comment-page-1#comment-175 Ken King | King Marketing Wed, 12 Oct 2005 22:18:46 +0000 http://blog.davidcrow.ca/?p=250#comment-175 <p>David,</p> <p> Thanks for the kind words. </p> <p> Enablr is indeed a front-end for wetware, at least to start. Down the road we will add an automated speech-to-text option for transcribr, among other technological improvements to the services.</p> <p> Our decision to go this route was motivated by two things â€' making it simple for the user to get what they want, and doing something <strong>now.</strong> The frontend experience came first, wetware was what we could do right away, and next we’ll move on to refining the backend.</p> David,

Thanks for the kind words.

Enablr is indeed a front-end for wetware, at least to start. Down the road we will add an automated speech-to-text option for transcribr, among other technological improvements to the services.

Our decision to go this route was motivated by two things â€' making it simple for the user to get what they want, and doing something now. The frontend experience came first, wetware was what we could do right away, and next we’ll move on to refining the backend.

]]> By: Ken King | King Mark http://davidcrow.ca/article/724/ajax-book-web-20-workgroup-and-t-dot-enablr/comment-page-1#comment-10384 Ken King | King Mark Wed, 12 Oct 2005 15:18:00 +0000 http://blog.davidcrow.ca/?p=250#comment-10384 <p>David,</p> <p><br /> Thanks for the kind words. </p> <p><br /> Enablr is indeed a front-end for wetware, at least to start. Down the road we will add an automated speech-to-text option for transcribr, among other technological improvements to the services.</p> <p><br /> Our decision to go this route was motivated by two things â€' making it simple for the user to get what they want, and doing something <strong>now.</strong> The frontend experience came first, wetware was what we could do right away, and next we’ll move on to refining the backend.</p> <p>David,</p> <p><br />
Thanks for the kind words. </p> <p><br />
Enablr is indeed a front-end for wetware, at least to start. Down the road we will add an automated speech-to-text option for transcribr, among other technological improvements to the services.</p> <p><br />
Our decision to go this route was motivated by two things &Atilde;&cent;&acirc;&sbquo;&not;' making it simple for the user to get what they want, and doing something <strong>now.</strong> The frontend experience came first, wetware was what we could do right away, and next we&Atilde;&cent;&acirc;&sbquo;&not;&acirc;&bdquo;&cent;ll move on to refining the backend.</p>

]]>