Unfortunately, the answer will have to be the dreaded "it depends".
The SOAP Web Services are still present in SharePoint 2013, though Microsoft has decided to deprecate them. What that will mean in reality is anyone's guess. There are lots of deprecated pieces of functionality (think sandbox) that would very difficult to remove.
The bigger question is around what you do with the results and such. The DOM in SharePoint 2013 has changed, just as it did from 2007 to 2010. If your code is nice and modular and you are using clean selectors, I would guess that you will have to re-test, perhaps adjust the code, and most likely adjust the CSS.
Keep in mind that many of the adjustments my be outside SPServices itself and just in your own jQuery / JavaScript and CSS.
Think this is a blog post in the making!
M.
The SOAP Web Services are still present in SharePoint 2013, though Microsoft has decided to deprecate them. What that will mean in reality is anyone's guess. There are lots of deprecated pieces of functionality (think sandbox) that would very difficult to remove.
The bigger question is around what you do with the results and such. The DOM in SharePoint 2013 has changed, just as it did from 2007 to 2010. If your code is nice and modular and you are using clean selectors, I would guess that you will have to re-test, perhaps adjust the code, and most likely adjust the CSS.
Keep in mind that many of the adjustments my be outside SPServices itself and just in your own jQuery / JavaScript and CSS.
Think this is a blog post in the making!
M.