Wendell Piez | 22 Sep 2010 19:02
Favicon

Making the XInclude switch more accessible

Hi,

As you know I've been using XInclude more intensively for a couple of 
projects. I'm grateful for oXygen's settings, including the setting 
to switch XInclude on and off per project.

However, sometimes one wants to turn it on or off even more readily, 
for example before running a transformation or Schematron validation. 
Since the settings are fairly deep in the XML/XML Parser pane of 
Options/Preferences, this is a bit hard to do (and to instruct others to do).

What would be great would be buttons to control this, and/or menu 
options, available at the top level. Maybe those are already there 
and I just haven't found them?

Any ideas?

Cheers,
Wendell

======================================================================
Wendell Piez                            mailto:wapiez@...
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
(Continue reading)

Syd Bauman | 24 Sep 2010 02:49
Favicon

Re: Making the XInclude switch more accessible

Hear, hear!

> As you know I've been using XInclude more intensively for a couple
> of projects. I'm grateful for oXygen's settings, including the
> setting to switch XInclude on and off per project.
> 
> However, sometimes one wants to turn it on or off even more
> readily, for example before running a transformation or Schematron
> validation. Since the settings are fairly deep in the XML/XML
> Parser pane of Options/Preferences, this is a bit hard to do (and
> to instruct others to do).
> 
> What would be great would be buttons to control this, and/or menu
> options, available at the top level. Maybe those are already there
> and I just haven't found them?
Wendell Piez | 24 Sep 2010 22:21
Favicon

Re: Making the XInclude switch more accessible

Hi again,

As long as Syd is on the case, don't forget it would also need a 
keyboard binding, actual or settable.

(Syd knows that whenever I write "button" he is to resolve the entity 
reference.)

FWIW, as far as the functionality is concerned, I'm in the habit of 
simply commenting out any XInclude references I don't want. But I 
have at least one client who doesn't want to require their users to 
do this (for understandable reasons) -- and who says the global 
switch would be very nice.

Cheers,
Wendell

At 08:49 PM 9/23/2010, Syd wrote:
>Hear, hear!
>
> > As you know I've been using XInclude more intensively for a couple
> > of projects. I'm grateful for oXygen's settings, including the
> > setting to switch XInclude on and off per project.
> >
> > However, sometimes one wants to turn it on or off even more
> > readily, for example before running a transformation or Schematron
> > validation. Since the settings are fairly deep in the XML/XML
> > Parser pane of Options/Preferences, this is a bit hard to do (and
> > to instruct others to do).
> >
(Continue reading)

George Cristian Bina | 24 Sep 2010 22:27
Favicon
Gravatar

Re: Making the XInclude switch more accessible

Hi Wendell,

I will explore the possibility to implement this through an workspace 
access plugin.

Best Regards,
George
-- 
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 9/24/10 11:21 PM, Wendell Piez wrote:
> Hi again,
>
> As long as Syd is on the case, don't forget it would also need a
> keyboard binding, actual or settable.
>
> (Syd knows that whenever I write "button" he is to resolve the entity
> reference.)
>
> FWIW, as far as the functionality is concerned, I'm in the habit of
> simply commenting out any XInclude references I don't want. But I
> have at least one client who doesn't want to require their users to
> do this (for understandable reasons) -- and who says the global
> switch would be very nice.
>
> Cheers,
> Wendell
>
(Continue reading)


Gmane