2009-05-27, 20:08
so would the same be done for the create search functions? for instance
CreateAlbulmSearch: $$2 =
Then GetAlbumSearchResults: $$2 =
It would be perfectly fine to leave those functions as is of course, but why not a blanket standard for all functions, leaving no question as to where the info is going to be, in this way $$1 would ALWAYS be the string data gathered from the url in the case of creating the search the input field would just move from $$1 to $$2 for all info. $$1 would always be the data to search(be it filesystem or html link) and $$2 will always be info passed from XBMC.
(which is partially what the argument against using the XBMC scrapers as the standard is, though i am not suggesting to cater to those who are against it, it just makes it more... uniform)
CreateAlbulmSearch: $$2 =
Code:
<search>
<album>Dark+Side+Of+The+Moon</album>
<artist>Pink+Floyd</artist>
</search>
Then GetAlbumSearchResults: $$2 =
Code:
<searchpage>
<url post="yes">http://www.allmusic.com/cg/amg.dll?P=amg&SQL=Dark+Side+Of+The+Moon&OPT1=2</url>
</searchpage>
It would be perfectly fine to leave those functions as is of course, but why not a blanket standard for all functions, leaving no question as to where the info is going to be, in this way $$1 would ALWAYS be the string data gathered from the url in the case of creating the search the input field would just move from $$1 to $$2 for all info. $$1 would always be the data to search(be it filesystem or html link) and $$2 will always be info passed from XBMC.
(which is partially what the argument against using the XBMC scrapers as the standard is, though i am not suggesting to cater to those who are against it, it just makes it more... uniform)