Back to Release Notes

Contents 1 New Features 2 Bug Fixes 3 Known Issues

[edit] New Features

• Interface List Editor Dialog Revamp: We have completely re-built the dialog used to modify the list of interfaces associated with a form. We’ve made the dialog more in-line with the new form and new class dialogs that we introduced in our last release. The dialog is easier to use and more logically organized to handle interfaces from Bungee Runtime, Your own classes, or Dependencies.
  • http://docs.bungeeconnect.com/wiki/index.php/How_To_:_Adding_a_Form_to_a_Class
• New User Registration Improvements: This is more visible to new users (obviously), but it’s worth calling out that we’ve made several important changes to the user creation and management workflow, especially in the cases of resetting a password or if a user forgets their username. Since our last release, we’re no longer requiring a Bungee “hands-on” approach to creating new users, so that’s exciting. Anybody who wants in on the Beta can just sign up and get an account with 0 wait time.
  • http://docs.bungeeconnect.com/wiki/index.php/How_To_:_Creating_a_Bungee_Development_Account
• New Form Interface Set in Runtime: In preparation for increased collaboration among developers, we’ve added several new interfaces in Runtime. By having a very large set of template interfaces, developers can keep their projects consistent.
  • http://docs.bungeeconnect.com/wiki/index.php/Concept_:_Understanding_Interfaces#Form_Interface
• Named Styles: Style sheets used to be able to only hold 1 style of each type (1 font, 1 background, 1 margin, etc). This was a bit limiting, and made maintenance difficult as complex projects would have many style sheets with overlapping information. We have changed the style sheet machinery so that each style sheet can hold multiples of each type of style. There is a default for each category (default font, default background, default margin, etc), and you can add any number of alternative styles for that category, each with a name. Each control has been given a list of style names that is used to associate that control with the named style within the category. Existing style sheets will be upgraded to use the categories when first modified, and styles are still inherited the same way as before this change.
  • http://docs.bungeeconnect.com/wiki/index.php/Property_:_StyleSheet

[edit] Bug Fixes

We’re continuing our emphasis on stability and usability with this release. Here are a few of the more visible bug fixes:

• Paste dialog upgraded

• Inline WSDL docs import now

• Speed of WSDL importing improved

• Refreshing revision status is now recursive

• SMTPClient template class has been updated to be more flexible, address recipient name and message corruption issues.

• Separator bar position now displays correctly when they’re inside an embedded form

• We’ve improved the workflow on actions that will require a checkout. We now warn that an object will need to be checked out before showing dialogs that the developer will interact with – that way you don’t end up making a ton of changes in a dialog just to find out you have to check something out afterwards

• Resource Project hierarchies remain intact after an import

• Labels bound to a date/time now show a default value on a form

• You can now horizontally scroll in the style sheet properties view.

• Interface list in the properties show more path information in case you have two interfaces with the same name

[edit] Known Issues

• For Time Zone formatting in the TimeUtil class:  In the past, if you’ve depended on format() to give you GMT you should convert to formatToZone() or else you’ll get MST.