oqapi/webgui
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

allowing UI levels for assets to be overridden in the config file, and allowing developers to specify a default UI level in the definition rather than creating a getUiLevel() method

Browse source
This commit is contained in:
JT Smith 2005-07-28 21:56:02 +00:00
parent c9cefeca93
commit c7864a0c24
15 changed files with 31 additions and 116 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/changelog/6.x.x.txt
View file

@ -1,6 +1,8 @@
6.7.0
- Added the ability to override the UI Level of any field in the edit form of
any asset in the WebGUI config file.
- Added the ability to override the UI Level of an entire asset in the config
file.
- fix [ 1229042 ] crumbtrail should show full path...
- Added asset versioning.
- fix [ 1229188 ] typo in Help: Collaboration, Post List Template Variables
@ -34,9 +36,9 @@
Struts or Ruby on Rails this will be very familiar. For all other
developers, just know that it will make writing wobjects that much easier.
For an example, take a look at the Article wobject's definition() method.
- Added an optional specification of the asset icon and name in the
definition to have getName() and getIcon() autogenerated for WebGUI::Asset
subclasses.
- Added an optional specification of the asset icon, ui level, and name in the
definition to have getName(), getUiLevel(), and getIcon() autogenerated for
WebGUI::Asset subclasses.
- fix [ 1239601 ] Thread::getName is not Internationalized (and many other Assets, too)
- fix [ 1240316 ] Doc erro in Folder template thumbnail => thumbnail.url
- The Navigation template variable "unfolded_page_loop" was removed a long