No, too involved, can’t be bothered. I am back to setting it up with TS template.
So .. I have gotten it to work.
First of all, a little explanation.
The tx_gstselectpro extension *can* be used as a flexible content element with templavoila - but only if it is the only instance in your whole site.
Otherwise it is better to call each instance as a lib.myObject, in order to configure it more accurately.
My typoscript looks like this (taken from the file gst_selectpro-1.0.0-ext_typoscript_setup__txt which is included in the extension download):
#latest artlicles teasers
lib.latestarticles < plugin.tx_gstselectpro_pi1
lib.latestarticles = USER
lib.latestarticles {
   // Set the administration parameters.
   debugSQL = {$plugin.gstselectpro.debugSQL}
   // Set the administration parameters.
   useResForTempl = {$plugin.gstselectpro.useResForTempl}
   useParseFunc = {$plugin.gstselectpro.useParseFunc}
   useStripTags = {$plugin.gstselectpro.useStripTags}
   unsetLastSeparator = {$plugin.gstselectpro.unsetLastSeparator}
   useContUid = {$plugin.gstselectpro.useContUid}
   // Set the query parameters.
   queryPid = 1121
   // Set the imgage directories parameters.
  directories {
         path = {$plugin.gstselectpro.directories.path}
         all = {$plugin.gstselectpro.directories.all}
   } // end directories
   // Set the css parameters.
   classTdBrowse = {$plugin.gstselectpro.classTdBrowse}
   // Set the parseFunc parameters.
   text_parseFunc {
   } // end text_parseFunc
   // Set the standard wrap parameters.
   text_stdWrap {
   } // end text_stdWrap
   image_stdWrap {
   } // end image_stdWrap
   date_stdWrap {
   } // end date_stdWrap
   link_stdWrap {
   } // end link_stdWrap
/* -disabled by default-
   // Change local language variables.
   _LOCAL_LANG.default.dateFormat = %A, %m-%d-%Y
   _LOCAL_LANG.de.dateFormat = %A, %d.%m.%Y
   _LOCAL_LANG.fr.dateFormat = %A, %d/%m/%Y
*/
}
NOTE: that I set the queryPid exactly for this lib.myObject, rather than leaving it as queryPid = {$plugin.gstselectpro.queryPid}My constants are exactly the same as the sample constants file, gst_selectpro-1.0.0-ext_typoscript_constants__txt. My constants are exactly the same as the sample constants file,Now, while it is possible to use the extension with TV, it is still necessary to create a template file containing the markers used by the extension for the data to render correctly.The extension includes three sample templates to give you an idea how to do it.
My constants are exactly the same as the sample constants file,Now, while it is possible to use the extension with TV, it is still necessary to create a template file containing the markers used by the extension for the data to render correctly.The extension includes three sample templates to give you an idea how to do it.The most important thing to realise is where the ###MARK1### etc comes from. It is essentially ###MARK[column_number]### from the column numbers you assigned to each one of the SelectPro Column Definitions as you created the query.
The template needs to be structured along the following lines:
< !– ###SELECTPRO_TABLE### –>Â
<!– ###CONTENT### –>
<!– ###CONTENT_ITEM### –> <div>###MARK1###</div>
<div class=”###CSSCLASS2###”>###MARK2###</div>
<div class=”###CSSCLASS3###”>###MARK3###</div>
<div>###LINK###</div>
<!– ###SEPARATOR_ITEM### –>
<div><img height=”10″ src=”/clear.gif” width=”1″ ></div>
<!– ###SEPARATOR_ITEM### –>
<!– ###BROWSE_ITEM### –>
<div class=”###CLASSTDBROWSE###”>###BROWSEFROMTO###
###BROWSELINKS###</div>
<!– ###BROWSE_ITEM### –>
<!– ###CONTENT### –>
<!– ###SELECTPRO_TABLE### –>
There is probably something else I meant to include here, but it is too late … I will reread tomorrow and add whatever I forgot 
)
