Keyboard access to UI Element

[Former Member]

Hi there,

I like to know the if webdynpro supports the following:

1) Capturing client side Keyboard Event in WebDynpro UI Element

2) Incorporating client side scripting in WebDynpro application.

3) Rendering Output of the WebDynpro UI Element layout based on XSL dynamically (similiar to .Net Controls)

Thanks,

Paul

[Former Member]

I think the question about keyboard navigiation is a very important question. Does anyone have an update from SAP on when this development will be available (if only in ramp-up)?

I heard rumours of a Web Dynpro client, but even just being able to specify the tab order on a screen would be an improvement on accessibility for non-mouse users.

i.e. I'd hate to have to go with a JSP solution just so I can support keyboard navigation.

Regards,

Matt

[Former Member]

Accessibility has been addressed and will be supported in the production release.

[Former Member]

Hi Armin,

Can you give some more inputs on the kind of Accessibility that will be supported.

I felt that the CSR version has more accessibility features than SSR. So will all functionality that was provided in CSR also be provided in SSR.

Also will shortcut keys and Function Keys be supported in the production release?

Does SAP have plans to ramp up Webdynpro to International standards of User Accessibility like the different levels 1 to 4 prescribed by W3C.

Regards,

Balaji

[Former Member]

About XSLT:

Can you give a concrete use case? Perhaps there is a "Web Dynpro way" to implement it.

Armin

[Former Member]

Hi Armin,

The purpose of the XSLT was to manipulate the layout of the WebDynpro UI and the tags in the UI Elements. hence, I wanted to add additional custom tags to the UI elements and some client-side JavaScript to the WebDynPro "generated" out to handle user event.

Cheers,

Paul

[Former Member]

Web Dynpro is not a framework where you program using custom tag libraries, scripting etc. Rather it is a model-driven programming model for applications that run on a variety of clients like Web browsers, mobile devices, "smart" clients etc.

Opening the Web Dynpro programming model for client-specific details would break this multi-client-capability.

To say it clearly: Forget about custom tags and client-side Javascript when programming Web Dynpro applications.

Nevertheless, it is possible to create dynamic view layouts, i.e. layouts that are not statically created with the NetWeaver developer studio design tools, but are build at runtime from configuration data.

Armin

[Former Member]

Hi

We had a similar requirement which was to provide short cut keys for some of the actions and we had to ask SAP if this was supported and they replied that this feature is under a development request.

I would also love to know if there is a way to support javascript in web dynpro by any straightforward means or via a hack.

Regards

Pran

[Former Member]

About Javascript:

There is no API for using Javascript and (I hope) there never will be.

The reason is: Web Dynpro provides a programming model for developing applications that run (without changing the application code) in different clients like Web browsers, smart clients, mobile devices etc.

If you want a programming model which works in terms of HTTP, HTML pages, client-side scripting etc., Web Dynpro is not the way to go. IMHO.

Armin

[Former Member]

Hi Armin,

what about an abstract client-scripting API, which provides predefined "scriptlets" (a simple client side date range validation, for example)?

The actual response renderer could transform these (maybe using XSLT) into the corresponding "client format", e.g. JavaScript for Web browsers, no transform for smart clients, which are able to interpret/transform the scripts by themselves and more.

Best regards

Stefan