Recent changes to feature-requests

Provide ability to attach "transformations" to binding spec

Jeff Roberts — Fri, 12 May 2006 01:37:36 -0000

The BindingSpecification already provides the ability
to attach individual transformations to each binding.
This allows an XML node value to be extracted and then
transformed for display in an HTML form and vice versa.

However, there are scenarios where the same
transformation should be applied to each and every
binding. For forms/documents with large numbers of
elements/nodes, it is too tedious to create the same
transformation(s) on each binding.

Ideally, you could declare some transformations that
would apply to each binding, unless it is explicitly
excluded. This would allow, for example, the ability
to uppercase every form input element before it is
copied into an XML node.

Provide for ability to display/log a formatted XML document

Jeff Roberts — Fri, 12 May 2006 00:54:50 -0000

Currently when you want to view an XML document that is
either retrieved from the server or submitted to the
server, you can view it using a combination of the
Javascript alert command and usage of the
AbstractBrowser's getXMLDocumentAsString() function.
You can also log the XML document.

However, neither choice provides an optimal solution.
Often, the XML document is large and viewing it in an
alert box is not practical. None of the browser's
format the resulting XML string very well and what you
can see is difficult to read. If you log the XML using
the xWire Logger, it renders the content using the
document.write() function. The browsers display this
differently. Both strip out the XML tags. IE allows
you to see the true XML content by viewing source.
However, Firefox does not.

What you really want is the capability to get the XML
content so that you can copy it to another location for
viewing.

Some suggestions for solutions are to:
A) Encode the XML tags so that they render properly
B) Log the XML into a read-only HTML text area
C) Somehow open the document in a separate window
allowing the browser to display it
D) Implement an "Echo" capability where the client can
submit an XML document to the server, have the server
parse and format it and return it to the browser in
another window

Trimming in the FormBinder

RBrandt — Wed, 05 Apr 2006 17:48:30 -0000

It seems to me that nearly 100% of the time the
developer would rather have leading and trailing
blanks (certainly trailing) trimmed off when using
both CopyToForm and CopyFromForm methods.

It would be a nice feature if that just happened in
the form binder automatically.

Allow registration of event listeners for selection of tab

Mark Nabours — Fri, 11 Nov 2005 05:20:17 -0000

Please add support so that users can register interest
in the selection of a particular NotebookPage within a
notebook. Currently, the Notebook fires events in a
Global manner.

FIner tune event specification should make page
handling easier for users of xwire.

Register event listener for particular xml request

Mark Nabours — Fri, 11 Nov 2005 05:17:54 -0000

Please add support for users to register interest in
events for a particular XML request. Currently, the
framework only fires global events for each XMLHttp
request.

The added functionality would allow for cleaner handling
when needed for particular requests.

Please add support for multi-row tabs on the Notebook

Mark Nabours — Fri, 11 Nov 2005 05:14:01 -0000

The current implementation of the client-side notebook
does not handle multiple tab rows well. Please either
modify the notebook to automatically handle multiple
rows when needed or allow the user to specify the
number of rows and tabs per row.