Platform 4.5.5
2007年5月リリース
新しい機能 (Java)
scrollPane にドラッグによるスクロール機能を追加
- draggable なウィジェットをscrollPaneにドラッグしたとき、scrollPane の端にもってゆくと自動的にするロールする
- scrollPane はネストすることも可能
ステートフルUIDOM では、windowやtableのつぎの状態を取得できる
- windowをベースとしてウィジェット (window, dialog, messageDialog)
- x
- y
- width
- height
- minimized
- maximized
- column
- width
- 新しい属性: visualIndex
columnの表示上のインデックスを示し、ユーザが画面上で操作した状態のインデックスを保持する
XAL Form
XAL でもFormが利用できるようになった。これまでは、NXMLだけでサポートされていた。
XALとプラグンコンポーネントの組み合わせ
プラグンのコンポーネントと XAL のウィジェットを組み合わせることができるようになった。
新しいAPI
- DisplayService
- DisplayService.getVisualColumnIndex()
tree/table/treeTableでcolumnのvisualIndexを返す。番号は0から始まりDOMでのカラムの位置ではなく、表示中のカラムの位置が示される。この番号は、ユーザがカラムを入れ変えたときに更新される。
- PluginDocumentHandler
- PluginDocumentHandler.convertElementToPeer()
ドキュメントハンドラのベースとなるクラスで、プラグインを利用するときのドキュメントの変更をハンドリングする。 4.2 で追加された UiContentHandler はこのPluginDocumentHandler のサブクラスでUIドキュメントに対応したもの。
- FocusService
- FocusService.focusNextWindow()
つぎのウィンドウにフォースを移す。フォーカスが遷移した先のウィンドウのエレメントが返る。
- FocusService.focusPreviousWindow()
前のウィンドウにフォースを移す。フォーカスが遷移した先のウィンドウのエレメントが返る。
修正された不具合 (Java)
|
7558
|
712-4174434 DataFramework のJavaDoc API とサンプルコードcom.nexaweb.util.EscapeSyntaxExceptionについて
|
|
7586
|
712-4174104 Nexaweb PlatformがcreateUiComponent() を使ったときに java.lang.ClassCastException をスローする問題
|
|
7561
|
712-4174209 DataService はbind(String) メソッドを提供していないが、DevCenterのドキュメントではこのメソッドを持つとある
|
|
7557
|
712-4174209 Data フレームワークのjar ファイルがcom.nexaweb.util.EscapeSyntaxException オブジェクトを含まない
|
|
7641
|
712-4280135 PDF をプリントするとArrayIndexOutOfBoundsExceptionが発生する
|
|
7637
|
FocusService で CTRL+Tab とCTRL+Shift+Tab が機能しない
|
|
7259
|
xal タグ内でrootPaneで囲まれていているがペインがない。
|
|
7528
|
712-4285169 com.nexaweb.client.form.Form が XAL で機能しない- XAL formElements が含まれていない
|
|
7638
|
ajax-index.html が新しいプロジェクトを作成したときに含まれていない (Nexaweb サーバを利用したときもしないときも含まれない)
|
|
7644
|
Java Platform - dialogConsumerError.xml とerrorDialog.xml がnxml でxalではない
|
|
7585
|
client.tags.xal のクラスがAPI jarにない
|
新しい機能 (Ajax)
スプラッシュスクリーンのカスタマイズカスタマイズ
ajax-index.html ではXAPコア(Ajaxクライアントエンジン)をロードしているときに"Loading Nexaweb…"とテキストが表示される。 XAPコアがロードてれると、ルートのXALファイルの定義をもとにAjaxの画面がレンダリングされる。
Dojo 3.1 から 0.4 へのアップグレード
XAPはアップグレードされ Dojo 0.4をサポートしている。Dojo 0.4では、多くのバグが修正された。また、i18nへの対応やドラッグ&ドロップもサポートされた。詳細についてはDojoのサイトを参照。
http://dojo.jot.com/Release0Point4.
パフォーマンスの改良:
- プロファイルの最適化
- XapCoreに起動に必要なすべてのJavaScript クラスを含めることで、起動時間が改善された。最適化されたXAPCore ファイルは、ツールキットでもNexaweb Platformでも提供される。
- イベントハンドリングの最適化
- イベントハンドラのインスタンスは、必要なときに生成されるようにした。これまでのバージョンでは、ウィジェットがサポートするすべてのイベントハンドラを生成していた。
- アプリケーションのローディング時間とメモリ消費を削減した。
- メッセージサービスの最適化
- MessagingService で、subscribe() や unsubscribe()メソッドが呼ばれた場合の処理で、サブスクライブ/アンサブスクライブのトピックを配列にしてまとめて処理できるようにした。これまでのバージョンでは、配列に対するループ処理で、ひとつのエレメントに対しひとつのリクエストを生成していた。このバージョンでは、ひとつのリクエストに対しすべてのトピックを生成している。
サーバに対するリクエスト数を減らすことができたため、サーバの負荷が減ることにつながり、起動/停止のパフォーマンスも向上する
Platform 4.5.4
Release date (April 2007)
New features (Java):
New data binding short syntax
A new simpler data binding syntax has been added to platform 4.5.4. After defining your data source you can now bind components "on the fly" to your data source with one simple line of XAL.
New Attribute: rowImageVerticalAlignment (XAL), and rowImageAlignVertical (NXML)
rowImageVerticalAlignment for XAL based projects, and rowImageAlignVertical for NXML based projects have been added to the schema to give developers further control over row image placement in trees, and treeTables.
Improved Sun 1.6 jvm support
Java based Nexaweb project deployed in Sun 1.6 environments no longer has to hit "click to coninue" on start up of the application.
Defects Resolved (Java Platform)
|
Id
|
Description
|
|
7512
|
On start of a java/platform app using jdk6 one needs to hit the "Click to continue loading" button.
|
|
7533
|
712-4144736 Data Binding Inefficiency.
|
|
7543
|
No way to specify one way binding with short syntax.
|
|
6375
|
712-2138243 Align the Tree leaf image to the top.
|
|
7610
|
Quickly reloading application in succession throws a Null Pointer Exception.
|
|
7593
|
tree/treeTable: Not given any error, or informational warning message, to java console when a bad value for rowImageVerticalAlignment, or rowImageAlignVertical is specified.
|
Platform 4.5.3
Release date (February 2007)
New features (Java)
Improved 508 compliance across all widgets
Numerous widgets have improved conformance to accessibility requirements and are now better understood by screen readers.
New Attribute: focusable
To improve 508 compliance a focusable attribute was exposed. All components have a focusable attribute the default is true with the exception of labels.
New Attribute: accessibleName
All components have an accessibleName attribute now. This is meant to be used to provide the JAWS screen reader a means to offer developers additional means to provide users with special needs additional information about the status, or description, of a component.
Accessibility Support: Section 508 Compliance
To create an accessible nexaweb java platform project the accessibility jar, located in the dist/plugins folder of the installed platform location, needs to be added to <project>/WebContent/WEB-INF/client/plugins. Additionally, the nexaweb-client.xml file needs to have <ui-test>true</ui-test> set. The default is to have this set to false.
New features (Ajax)
Implemented all changes from Apache XAP
Performance Enhacement: Compressed File Servlet
CompressedFileServlet is a tool that allows the user's browser to download a compressed version of any needed file from the server. This reduces download time, load time, and bandwidth usage. It works by checking to see if a requested file (see request example below) exists as a gzip file, and whether the user's browser can handle gzips. If both of these conditions are met, the gzip is returned to the user instead of the normal file. If the gzip does not exist or the browser does not support gzip, the normal file is returned instead.
The compressedFileServlet is enabled by default. To take advantage of it, prepend the absolute path with “CompressedFileServlet/”.
For example, to request xapcore.js through this servlet, change:
<script language="JavaScript" type="text/javascript" src="/nxAjax/lib/xapcore.js"></script>
to:
<script language="JavaScript" type="text/javascript" src="CompressedFileServlet/nxAjax/lib/xapcore.js"></script>
Defects Resolved (Java Platform)
|
Id
|
Description
|
|
7251
|
Documentation: docs need to have accessibility attributes added to all the components.
|
|
7341
|
Problems running EasyTraderAjax project's help link
|
|
7377
|
focusable attribute needs to be documented in schema.
|
|
7405
|
textView: The screen reader doesn't always have an acurate cursor position when moving through the text with arrow keys.
|
|
7136
|
comboBox: Screen reader doesn't notice the comboBox when tabbing through a java app.
|
|
7137
|
Need to expose the "focusable" attribute on all components for accessibility.
|
|
7152
|
slider: Screen reader will report an incorrect position for a slider when frequent large changes are made.
|
|
7153
|
comboBox: mousing over a listItem in the comboBox pop-up doesn't trigger the screen reader to read the listItem highlighted.
|
|
7155
|
table: screen reader doesn't read tables when focus is gained via tab key.
|
|
7236
|
comboBox: Selecting a comboBox with the mouse doesn't trigger the screen reader to read.
|
|
7256
|
textView: if the text in the textView is especially long the JAWS screen reader will just stop reading the text after a few sentences.
|
|
7290
|
Screen reader doesn't re-read a component that has focus after an accessible attribute has changed.
|
|
7323
|
Widgets with an onActiveGained event that has fired won't trigger the screen reader to read their text, or accessibleName attributes.
|
|
7328
|
AccessKey of tab not being read when tab gains focus.
|
|
7330
|
JAWS stopped reading the text attribute of a tab in a tabPane after moving between tabs.
|
|
7344
|
textArea: After initiating the JAWS screen reader to read text in a textArea, quickly hitting the down arrow key to move ahead of the reader in the text, then stopping JAWS would cause the reader to read the wrong letters when moving the cursor through the text.
|
|
7351
|
Null Pointer exception when switching between tabs of a tabbed pane.
|
|
7352
|
Null Pointer exceptions being thrown when focusing an Accessible table containing no rows
|
|
7418
|
AccessibleName of textfield incorrectly being read as text of textfield.
|
|
7151
|
Table: Screen reader only reads the first cell in a table when singleRow is specified.
|
|
7138
|
menuBar: menuBar is not selectable, or usable, with only key board use.
|
|
7176
|
scrollPane: manipulating the scrollBar of a scrollPane doesn't trigger the screen reader to read off new position.
|
|
7211
|
Label: For some components putting a label before the component doesn't trigger the reading of the label by the screen reader.
|
|
7231
|
Screen reader doesn't inform a user about any disabled components.
|
|
7252
|
textArea: a screen reader like JAWS doesn't read the text in the textArea.
|
|
7327
|
comboBox: comboBox text attribute value doesn't get read by JAWS.
|
Defects Resolved (Ajax Platform)
|
Id
|
Description
|
|
XAP303
|
Widgets: Table: Removing all rows when one is selected makes selecting a new row impossible.
|
Known issues (Java Platform)
|
Id
|
Description
|
|
7139
|
slider: horizontal or vertical sliders are not modifiable via a keyboard.
|
|
7154
|
radioButton: Screen reader is not picking up the checked state after the space bar is pressed in IE.
|
|
7156
|
Window: can't modify, or access a window in a destopPane via the keyboard only.
|
|
7157
|
window: the window's state isn't being read properly by the screen reader. Also affects dialog and messageDialog components.
|
|
7158
|
scrollBar: scrollBar position is not modifiable via the keyboard.
|
|
7234
|
Inconsistent reading by screen reader when changing focus between readable component, and non-readable component.
|
|
7250
|
Removing an object that is focused doesn't transfer focus to anything else in the browser.
|
|
7338
|
menuBar: accessibleName attribute not read when specified on a menuBar.
|
|
7375
|
dialog: dialogs aren't read by JAWS screen reader.
|
|
7420
|
textView: screen reader will read the text of a textField twice in Firefox only, if no accessibleName attribute is set.
|
|
7422
|
textArea: with wrapped text the screen reader will read the first letter of the next line twice.
|
|
7366
|
comboBox: Changing from the open to closed state doesn't get read by JAWS.
|
|
7367
|
comboBox: JAWS doesn't read the comboBox in IE7 when focus is set via a mouse click.
|
|
7149
|
Table: with row selection the screen reader will only read the cell in the first column.
|
|
7235
|
comboBox: quickly opening, then closing the listbox in a comboBox, and shift-tab'ing won't trigger the screen reader on next tab.
|
|
7254
|
High-lighting text in either a textArea of textView doesn't trigger the screen reader to read the text.
|
|
7326
|
comboBox: tabbing from one open comboBox to one defined right after it doesn't trigger the screen reader to read the second comboBox.
|
|
7329
|
Component not read by JAWS when focus is set at startup using "focused" attribute.
|
|
7336
|
When initially focused, the selected text of a text field is also being read (in Firefox not IE).
|
|
7339
|
table: With selection mode set to singleCell a couple of the needed JAWs hotkeys don't work.
|
|
7407
|
textView: hitting the down arrow key just restarts the reader reading from the first line.
|
Special notes:
7149 Table: with row selection the screen reader will only read the cell in the first column.
When using selection=”singleRow” using the arrow keys to read the cells in the row won’t work. Instead use of JAWS’ desktop application hot keys for maneuvering in a table will need to be employed.
7254 High-lighting text in either a textArea of textView doesn't trigger the screen reader to read the text.
JAWS hot keys must be used instead.
7256 textView: if the text in the textView is especially long the JAWS screen reader will just stop reading the text after a few sentences.
The default behavior for both textAreas, and textViews are that upon focus the screen reader will not start reading until the down arrow is pressed, or a hot key sequence is pressed to start JAWS reading.
7151 Table: Screen reader only reads the first cell in a table when singleRow is specified.
To choose a different cell for JAWS to read, JAWS hot keys for desktop applications for tables should be used.
7138 menuBar: menuBar is not selectable, or usable, with only key board use.
To access a menuBar when only a key board is available use of menu accessKeys must be used.
7176 scrollPane: manipulating the scrollBar of a scrollPane doesn't trigger the screen reader to read off new position.
This is equivalent behavior with java swing applications. Use of JAWS desktop application hot keys will need to be used to manipulate scroll position.
7211 Label: For some components putting a label before the component doesn't trigger the reading of the label by the screen reader.
This is resolved by using the focusable=”true” attribute on the label.
7231 Screen reader doesn't inform a user about any disabled components.
This is consistant with java swing, and desktop applications. Additional, measures from developers would need to be employed to allow an accessible user to know of any disabled components in the application.
7252 textArea: a screen reader like JAWS doesn't read the text in the textArea.
The default behavior is for a screen reader to not start reading the text in a textArea, or textView until some command is issued to start JAWS reading.
7327 comboBox: comboBox text attribute value doesn't get read by JAWS.
A comboBox’s text attribute value will not be read is it has an accessibleName attribte set.
7250 Removing a component that has focus won't transfer focus to anything else in the browser.
When progammatically removing focused components from the UI an additional step of setting focus to some other existing component in the application will be needed to continue keyboard only interaction with the application. This would be accomplished by setting the 'focused' attribute to "true" on some component in the application.
7338 menuBar: accessibleName attribute not read when specified on a menuBar.
This is equivalent behavior with swing applications. Users of accessible applications will need to know of specified accessKeys on the menus in the menuBar as the menuBar is not accessible by use of the 'tab' key, and a menuBar's accessibleName will not be read when focus is set to it either.
Platform 4.5.2
Release date (January 2007)
Patch release aimed at Ajax client.
Platform 4.5.1
Release date (December 2006)
Initial release of the Ajax client.
