Could you please expand on comment that you are working on xmlrpc implementation. FRom what I can see the response to the existing xmlrpc methods have changed considerably.
I concur that ngg.editimage and ngg.deleteimage are broken. ngg.deleteImage actually works but responds with an error.(its actually an empty response) And ngg.editimage does not work responding with false (0).
I note that the response is “probably” better formatted but the functionality seems the same and looking at current web functionality does not need major change.
questions;
1) are you creating a new set of xmlrpc methods?
2) are the existing methods going to be supported (maybe deprecated)
3) Is there a reason that the response to existing methods has changed; has this been done knowingly? Are changes going to remain.
One feature needed is to be able to edit/change/view the keyword tags via xmlrpc for images. Currently tags are not supported by the ngg.editImage method and tags are not provided in ngg.getImages.
I am also seeing issues with the full path for image thumbnails. Thumbnail paths are provided in “ngg.getImage” but not in “ngg.getImages”. The path can be constructed but not clear that they are always in /thumbs/ subdirectory.
Happy to help out and test xmlrpc but would like to know dev plans. Changes in the interface with no backward compatibility have dramatic follow-on effects on clients using the interface
