The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: xFx How-To #2: creating a simple xFx plugin


  • Subject: Re: xFx How-To #2: creating a simple xFx plugin
  • From: Stuart Booth
  • Date: Wed, 03 Mar 2004 18:41:00 +0000

I was asked if this was the default way to develop new xFx-based
xAPplications.

Well, I think that there is a bit of a balance required, depending on
the application in question. But in essence, yes. The Slim Connector
is one of my most interesting applications, is reasonably complex with
it, and also fully supports the plugin mechanism. In fact it drove its
recent enhancements so that I could do a good GUI.

Then again, an application might not sit as comfortably in this style
as the Slim Connector does.
- If the application fits into being run as a Windows Service, it's
probably
ideal for this particular plugin mechanism.
- If its output can be column-ised into time-stamped events with a number
of
columns for different information displays, then again I'd say it fits.

Ie if it is an output only application, with limited user interaction
required, it's ideal.

The SlimConnector's user interaction is limited to setup and
configuration, and then viewing what's going on, where the GUI version
provides the most interesting and useful interface because you can
delve into the events and messages that are flying between the xAP
network and the SlimServer. As well as replay them. My other plugins
are much the same, once configured they can be left to run on their
own.

As soon as the app needs a more specialised UI than a simple grid
(which is all the console and GUI containers offer) then a complete
standalone application is more appropriate e.g. Hub or Viewer. I
wouldn't dare try and shoe-horn audio playlist editing into the
SlimConnector for instance. That's a job for somebody elses xAPp.

About a year ago I got fed up writing the same application over and
over, just to implement one little routine such as in that xAP Echo
Target sample I described last night. That was the genesis of the
plugins and the runtimes - just trying to reduce the amount of work I
have to do in the first place and then later maintain (groan!).

S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=li1-6LxZ_IHCGhf8EMWMYLj3qsSD18hItZqngFL5_CB1qoeq4ikMounxTV5w-KX27zhCsBIZDQYLElM4MGRv">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net

<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>





xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.