Hosting for MetaEdit+ API utility code

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   The MetaEdit+ SOAP/WebServices API is intended to allow anyone to use their favourite language to write programs that interact with MetaEdit+. The SOAP API interface is supplied as a WSDL file, which any programming languages SOAP framework can read and generate a set of classes / functions that allow the MetaEdit+ API functions to be called transparently.

Most SOAP calls really are transparent - it feels like calling a local function on local data, e.g.
   surname=parentObject.valueAt(2);
   childObject.setValueAt(2, surname);
Some things in SOAP however require a bit of work, e.g. converting data between SOAP types and native types. Our examples show the conversion - the code is only a couple of lines, and it's best for people to see what's actually going on. But as you write longer programs those lines get repeated often, so it's probably best to put them into their own utility function. 

With so many languages and SOAP libraries, plus their different versions, it's impossible for MetaCase to provide these utility functions for everyone. Our hope was that the community of users, each knowing more about their own programming language and SOAP framework than MetaCase can, would share any utility functions or frameworks they made. 

It's taken a while, but now there are quite a few such bits of code floating around - and the question is what is the best way to share them. We'd love it if people were able to share, improve and extend these things, to help themselves and others. So pick your favourite(s) of the above set, whichever would be easiest for you to grab from and to partcipate in.

Thanks,
Steve

Poll Question: Where should MetaEdit+ API utility code be hosted?
Poll Choice	Votes	Poll Statistics
Google Code (SVN, Mercurial)	3	[50.00%]
Github	0	[0.00%]
MetaCase site (SVN)	0	[0.00%]
MetaCase site (git)	2	[33.33%]
MetaCase site (HTML/zip)	1	[16.67%]
You can not vote in this poll

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
stevek Members Profile Send Private Message Find Members Posts Add to Buddy List MetaCase Joined: 11.Mar.2008 Points: 643	Post Options Post Reply Quote stevek Report Post Thanks(0) Quote Reply Topic: Hosting for MetaEdit+ API utility code Posted: 22.Jun.2011 at 15:10
	The MetaEdit+ SOAP/WebServices API is intended to allow anyone to use their favourite language to write programs that interact with MetaEdit+. The SOAP API interface is supplied as a WSDL file, which any programming languages SOAP framework can read and generate a set of classes / functions that allow the MetaEdit+ API functions to be called transparently. Most SOAP calls really are transparent - it feels like calling a local function on local data, e.g. surname=parentObject.valueAt(2); childObject.setValueAt(2, surname); Some things in SOAP however require a bit of work, e.g. converting data between SOAP types and native types. Our examples show the conversion - the code is only a couple of lines, and it's best for people to see what's actually going on. But as you write longer programs those lines get repeated often, so it's probably best to put them into their own utility function. With so many languages and SOAP libraries, plus their different versions, it's impossible for MetaCase to provide these utility functions for everyone. Our hope was that the community of users, each knowing more about their own programming language and SOAP framework than MetaCase can, would share any utility functions or frameworks they made. It's taken a while, but now there are quite a few such bits of code floating around - and the question is what is the best way to share them. We'd love it if people were able to share, improve and extend these things, to help themselves and others. So pick your favourite(s) of the above set, whichever would be easiest for you to grab from and to partcipate in. Thanks, Steve