Re: Could use some help with the HomeVision Plug In

["gmotichka" <gmotichka@xxxxxxxxxxxxx>]

If you could get the filter to work, that would be great

George M




--- In ukha_xpl@xxxxxxx, "Mal Lansell" <mlansell@f...>
wrote:
>
> Thanks, Ian.
>
> I'll get on to that soon (probably tomorrow).  It looks like I'll
> need to release a new version of the W800 service anyway - with
some
> form of filtering of multiple messages (except for dim commands!)
> included.
>
> Mal
>
>
>
> --- In ukha_xpl@xxxxxxx, "Ian Lowe" <ian@w...> wrote:
> > Hi Mal - the xml plugin is a great user-side feature - it's what
> allows
> > the determinators to work, and is basically a well structured xml
> > description of what your app can do, written by the person that
> knows it
> > best - you!
> >
> > John posted an excellent article on how to do the plugin, I have
> > included it here to save you trawling yahoo's archive.
> >
> > >---
> > What is an xPLHal Plug-in?
> > ------------------------------------------
> >
> > A plug-in is an XML file that describes the xPL devices released
by
> a
> > particular vendor.
> > It is worth noting that plug-ins are unrelated to the xPL
protocol
> > itself - they are just a feature of the xPLHal product to enhance
> > usability.
> > Plug-in files are stored within the xPLHal Manager installation
> folder,
> > in a directory called "plugins".
> > They are loaded at startup by the manager, and are used in a
> variety of
> > places within the user interface to enhance the end-user
experience.
> >
> > A mechanism for updating plug-ins via the web is provided via
the
> Help
> > -> Update Plug-in Library menu option.
> > Developers who wish to make their plug-in available via the web
> update
> > mechanism should post their requests to this group. They should
> include
> > their vendor name, and the URL to where their plug-in is hosted.
> Note
> > that plug-in files must end with the file extension .xml, and
must
> be
> > hosted on an HTTP web server. We may be able to host plug-in
files
> on
> > behalf of developers if they do not have their own hosting
> facilities.
> >
> > How do I write a plug-in?
> > --------------------------------------
> >
> > The best way to begin writing a plug-in is to take a look at the
> > plug-ins that are already available.
> > This should give you a good understanding of the structure of a
> plug-in
> > file.
> >
> > A reference plug-in is available at:
> > http://www.xpl.myby.co.uk/info/vendor-plugin.txt
> >
> > This file demonstrates every possible feature of a plug-in,
complete
> > with full documentation.
> >
> > Should you have any questions about writing a plug-in, or
> suggestions on
> > how we can improve the plug-in interface, please feel free to
post
> them
> > to this group.
> >
> > Regards,
> >
> > John