Pro+v21.9 Widget - HTML Tidy Editor

[xtom]

That's really cool Acorn, looks like people could create custom widgets with this. Is there any further documentation on it or did you just figure it out yourself?

Edit: Here are some additional things I've found in some other xwr files. Not sure what they all do but you can add classes to the exported div which is good to know too. Helplink adds a button to the help that opens web page for further help.

<RenderDelay>6000</RenderDelay>
<Force100Percent/>
<Classes>xr_reset</Classes>
<SnippetWidth>550</SnippetWidth>
<SnippetHeight>600</SnippetHeight>
<HelpLink>http://www.xara.com/us/widgets/forms</HelpLink>

Edit2: For reference SnippetWidth and SnippetHeight add width and height to the exported div.

I see now you have a bunch of older posts on this so you probably know already but just posting for reference.

[Acorn]

xtom, thank you for your contribution.

Yes the whole rationale behind the Xara Widget file type was to make third-party widgets accessible and updatable
Until XPro+v21.9, Xara has never updated the widgets and as they ran under IE, thy were failing one by one.

Here is my interpretation of the XWR Schema:

<!-- A Comment can be added anywhere -->
<XaraWidget> <!-- (Mandatory - M) Start of outer widget wrapper -->
<WidgetName> </WidgetName> <!-- (M) Title of Xara's wrapper reads as - Create new widget: WidgetName value -->
<CreateURL> </CreateURL> <!-- (M) Full URL of the on-line widget page -->
<BrowserWidth> </BrowserWidth> <!-- (Optional but better declared - O/M) Value in pixels of the first-opened width of the widget - can be dragged -->
<BrowserHeight> </BrowserHeight> <!-- (O/M) Value in pixels of the first-opened width of the widget - can be dragged -->
<RenderDelay> </RenderDelay> <!-- (O) Delay in milliSeconds to allow remote resource to synchronise all its assets -->
<SnippetWidth> </SnippetWidth> <!-- (O) Value in pixels of the populated widget on the design page and when rendered -->
<SnippetHeight> </SnippetHeight> <!-- (O) Value in pixels of the populated widget on the design page and when rendered -->
<Force100Percent /> <!-- (O) Set the rendered widget to display at a minimum of its intrinsic width and height -->
<ControlID> </ControlID> <!-- (O) Location the the expected code to be copied before the Insert button is pressed -->
<WidgetHelp> </WidgetHelp> <!-- (O/M) Descriptive text that fills a Help pop-up when the Widget Help button is clicked -->
<HelpLink> </HelpLink> <!-- (O) Add a More Help button to the Xara wrapper that opens another remote web page in your default browser -->
<NotIE6 /> <!-- (Redundant - R) Blocks IE6 as the default browser - not needed in XPro+ v21.9 -->
<TaskPilotLogin /> <!-- (R) Invokes a rather specific login to Xara Hosting -->
<EditURL> </EditURL> <!-- (Question - Q) Link to go to when the inserted widget is double-clicked -->
</XaraWidget> <!-- (M) End of outer widget wrapper -->

I have repeatedly asked Xara for the proper specification.
I have not encountered <Classes> doing what you suggest but I am open to persuasion.

The one thing that would make this all work better would be the means to direct a <CreateURL> to the local filestore.
That way, one could use a locally hosted control file rather than having to publish it to the web or set up a local server (which I do).
With this, you can add IDs to text areas, buttons to add to the Clipboard, and other code to embellish the captured detail.

I will upload an XWR that uses <Force100Percent/> to ensure the saved SVG Icon has the right-sized Placeholder.
If you scale the Placeholder at any time the SVG Widget adjusts its size.

Acorn

[xtom]

Thanks for the extra reference information Acorn. I imported a few of the widgets from the catalog and opened the downloaded xwr files which is how I found <Classes>xr_reset</Classes> so I reckon it should work if it's not redundant, I didn't actually try changing it though.