VT: Difference between revisions
m (Protected "Ft" ([edit=sysop] (indefinite) [move=sysop] (indefinite))) |
No edit summary |
||
Line 22: | Line 22: | ||
So Ft BizCard, a use of the fw to support an video version of my flash biz card planned for some time before Ft, is a pilot polished app the be so cranked in 2012-01. | So Ft BizCard, a use of the fw to support an video version of my flash biz card planned for some time before Ft, is a pilot polished app the be so cranked in 2012-01. | ||
== Approach == | |||
Ft is meant to be 100% agile, extreme, UNIT_XP (an old derivative of agile/XP I defined) whatever, the opposite of my supporting, infrastructure projects which are support as projects with Cliubooks and the like. Ft stresses rapid deployment of finished parts of that infrastructure, including much 3rd party software, already in a production state, mashed up and pushed out into a production context. |
Revision as of 01:47, 31 December 2011
Facetime Whiteboard
Designation
"Ft", "Ftwb", "Ft <X>"
Purpose
Disseminate other products and services thru the FB API.
Domain
Description
Facetime is a pilot framework for a later commercial service to be made generally available and currently used to support my programming practice.
Whiteboard refers to a sample app used to exemplify the framework. It's therefore fulfilling design intent if it looks crude and samplish, but the polished apps cranked out in the fw should not, subject to them having or not having custom artistic graphic treatments (see The Chosen Ones) or not needing one.
Typically I'm using the notation Ft X of which Ft Whiteboard, is the defining use case, to refer to this variability of the model app.
So Ft BizCard, a use of the fw to support an video version of my flash biz card planned for some time before Ft, is a pilot polished app the be so cranked in 2012-01.
Approach
Ft is meant to be 100% agile, extreme, UNIT_XP (an old derivative of agile/XP I defined) whatever, the opposite of my supporting, infrastructure projects which are support as projects with Cliubooks and the like. Ft stresses rapid deployment of finished parts of that infrastructure, including much 3rd party software, already in a production state, mashed up and pushed out into a production context.