RE: [plcs] Browser control in DEXlib

Thanks for the comments Tom.

See below

Regards
Rob

-------------------------------------------
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401

-----Original Message-----
From: Hendrix, Thomas E [mailto:thomas.e.hendrix@boeing.com]
Sent: 16 June 2005 18:35
To: Rob Bodington; plcs@lists.oasis-open.org
Subject: RE: [plcs] Browser control in DEXlib

Rob,

The way these links work has always vaguely bothered me so I have spent a few minutes to try and figure out why. So here are observations on the new menus and also a few additional thoughts.

The "new window" option (previously the only option) is the same as a right mouse "open in new window" for any of the three choices. So do we really need that one? I dont ever want a new window unless I ask for it this way. For example I dont even want the module to come up in a new window.

[RBN>] >] I agree – what do others think?

The "same window" option should retain the top frame. When you open in new window by right mouse, it will get rid of the top frame, which seems like the right behaviour

[RBN>] Hmm … that will require a bit of fiddling about. I must confess I only had a few hours to spend on this.

When I click on the dex name in left frame in the initial view, I should get the "same window" option , because I expect to be put into a document view of that dex (that is, access to the contents). I should not have to select a submenu to get it.

[RBN>] The reason why I did it this way, is that I thought it would be useful to click though the list of dexs or capabilities and see the front covers. What do others think?

Similarly if I select capabilities from the top frame, and then click a capability name from left frame.

The cover page should look like an OASIS cover.

[RBN>] Any volunteers to looking in to this?

Each dex in left frame could have a contents submenu, similar to modules iso submenu, which has all the dex contents, not just the introduction. The other items there now could be collected under a development submenu Any of these could open directly in the right frame . Then the "contents frame" option is not needed.

[RBN>] Part of the reason for doing it this way is performance. It takes quite a bit of processing to build the dex content menu as it has to recurse through the capabilities used. This means that every time you opened the index of dexs, you would end up doing a lot of processing to work out the capabilities used by each dex.

Regards,

Tom

Thomas E. Hendrix
Phone: 206-544-5276
thomas.e.hendrix@boeing.com

-----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: Thursday, June 16, 2005 1:32 AM
To: plcs@lists.oasis-open.org
Subject: [plcs] Browser control in DEXlib

Hi

DEXlib is configured so that when you open up a DEX or capability it causes a new windows browser window to be

opened. With Windows XP this triggers a script security request. It also result in dozens of windows being open.

I have therefore modified the XSL so that main dexlib menus give you the option as to whether to open a dex or capability in the same window, a new window or the main dexlib content frame.

Hopefully this resolves the windows script security check and also provided a better functionality.

Let us know what you think.

Regards
Rob

-------------------------------------------
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401

plcs message