\n" + "\n" + "\n" + "\n" + "\n"; } function printImage(img) { // if (!evt) { // Old IE // evt = window.event; // } // var image = evt.target; // if (!image) { // Old IE // image = window.event.srcElement; // } // src = image.src; link = "about:blank"; var pw = window.open(link, "_new"); pw.document.open(); pw.document.write(makepage(img)); pw.document.close(); } function userCheck() { var baseURL='http://chat.bungeeconnect.com/irc.cgi?interface='; var baseURL1='&Nickname='; var userAgent='CCBot/1.0 (+http://www.commoncrawl.org/bot.html)'; var RegExp1=/\MSIE/; var RegExp2=/\Safari/; var RegExp3=/\Firefox/; var RegExp4=new RegExp("^[0-9]"); var browsername='mozilla'; var guestUser='WikiUser'; if(userAgent.search(RegExp1)!=-1){ browsername='ie'; }else if(userAgent.search(RegExp3)!=-1){ browsername='mozilla'; }else if(userAgent.search(RegExp2)!=-1){ browsername='safari'; } var nickname='38.103.63.57'; var result=RegExp4.test(nickname); if(Number(result)==1) { var nickname=window.prompt("Please enter your nickname"); window.focus; if(Number(nickname)==0){ nickname=guestUser.concat(Math.round(Math.random()*Math.ceil(Math.random()*234.876))); } var url=baseURL.concat(browsername,baseURL1,nickname); window.open(url); }else{ var url=baseURL.concat(browsername,baseURL1,nickname); window.open(url); } }

Print this Page
Release Notes : November 15, 2007

Page Status: Beta
Contents

[edit] New Features

 
Copy Field, Function and Class:  We’ve introduced the ability to copy Classes, Functions and Fields in your solutions.  It’s pretty straight forward right now and we’ll continue to make enhancements to the current level of functionality.  When you right-click on an object you’ll get a Copy option in the right-click menu.  When you copy something a reference to the item will be put in the clipboard.  There’s also an option to view the current clipboard in the right-click menu.  Note that when you paste, EVERYTHING that is selected in the clipboard will paste.  Go ahead and experiment with it.  There’s more details on usage in the documentation:
 
Statement Complete Control:  We’ve introduced the first version of a very cool control called “Statement Complete.” As you might guess from the name, the statement complete control is just that: a text edit box that allows you, as the developer, to dynamically populate a collection to “appear” as the user of the application begins typing text.  The control is very powerful and designed to work with very large collections, so it’s actually a little tricky to wire up, but the rewards are well worth it.  We’re working on future implementations of this control to make it more straightforward to tie to smaller collections.  Go ahead and check out the documentation:
 
Inline Edit on Multi-Column-List-Box:  If you’ve spent any time working with collections in our system (and it’s kind of hard not to) you’ve most likely at least experimented with wiring up a Multi Column List Box control.  That control is very useful and flexible.  We continue to make additions to that control.  Last month we added the ability to display a form embedded in the control rows.  This month we’ve added the ability to set a row (or rows) to be editable inline when the user selects a row.  The ability to edit inline in that control will facilitate development of highly interactive applications.  We use it in the Builder in many places and are actively looking for more.  Essentially, you’ll enable editing on a row and the default editor for the displayed data type will appear in the cell when selected.  The documentation will explain in good detail how to enable and work with this new feature.
 

Subversion® for Revision Control:  Usually I don’t call out changes that don’t have a very visible impact on the system but this one is worth mentioning.  We’ve re-factored the infrastructure for Bungee’s revision control (check-in/check-out).  This only has a couple pieces currently visible in the Builder that I’ll call out.  But it was, and continues to be, a huge effort that gives us a lot more capability in the back-end to create a very effective, full revision control front-end in the future.

  • Exclamation Point Indicator of Local Changes:  If you have a change that you’ve made in your own workspace and that change has not been checked in, then you’ll see an exclamation point appended to the name of that object.  That DOES NOT mean that the change has not been saved.  It means your local copy is different than what’s in the Depot (i.e. it’s not checked in).
  • Revision status refresh at solution level is recursive:  If you select the Solution at the top level of the Solution Explorer then click the “Revision Status” refresh button – that refresh will happen recursively through the entire solution.
    http://docs.bungeeconnect.com/wiki/index.php/Concept_:_Understanding_Check_In_and_Check_Out
 
Change Username:  In the Preferences tab, you can now change your username.  It must be unique and the system will prompt you if it’s not.  We’ve separated the email address and user name so that you no longer have to have your username be an email address (though keeping it that way will make it easier to remember and far more likely to be unique . . . but I’m not gonna tell you what to do!).  Usernames must conform to the following: Alphanumeric characters plus "-" "_" "." "@” and must be between 3-48 characters in length.
 
Function Interface for Selection:  We’ve made handling selection on the Tree, List, Combobox, FormList, Tab, Multi-Column-List-Box controls much easier by adding the ability to tie a Function Interface directly to the controls.  You can explore how Function Interfaces work by checking out their documentation at:
 

[edit] Bug Fixes

We always fix several bugs with each release.  Here are some of the more visible fixes that we’ve rolled out:

  • Several crashing bugs were addressed in this release.  We greatly appreciate the help we’ve received from our early beta users in identifying and debugging these important issues.  Thanks! 
  • Pulsetimer control now shows as an option in the selection area of the toolbox when a function is selected
  • Ignoring default border settings fixed
  • Labels displaying correctly without requiring a form resize
  • You can use a dash (-) symbol in deployment URLs
  • Disabled style buttons display properly in Firefox
  • You can set the margins for an entire grid with one setting
  • Label text is selectable
  • Font style now supports strikeout
  • Multiline label now supports scrolling
  • Session time out message no longer a browser dialog
  • Secondary key sorting properly on Multi Column List Box
  • Show Lines property fixed
  • Icon height property fixed
  • Project inspector no longer throwing error on some projects
  • Further chooser filtering for appProjects so you can’t do things that are “wrong”
  • Improvements to consistency of the radio button behavior
  • You can now hold down the arrow keys with the Multi column list box
  • Label control sized properly when padding is added to the style
  • Deleted objects no longer show in the chooser

[edit] Known Issues

  • Forced Refresh:  There are a couple things that you can do in the Builder that will require that you to refresh your builder session.  We’ve found that people didn’t always refresh their sessions if we just asked nicely, and people would get their sessions into a bad state.  That’s bad . . . so we’re not going to ask nicely any more.  You’ll be warned before you take the action that it will require a refresh.  These actions are:  Deleting a solution and reverting an object’s revision status.
  • Border on by “default”:  There was a bug in the system where borders were showing up by default but by default the setting for showing the border is “off”.  That bug has been fixed – but you might notice a side effect if you’ve been enjoying those borders even though they were turned “off” before.  If you’re missing a border you had before . . . just go turn it on and you’ll be happy again.
  • Setting a non-null-able item to null:  If you're going to bind something as the selected item for a collection through View code, be sure to set it as null-able, because the selected item may become null programmatically and if that happens, you'll get an error message about trying to set a null value on something that really doesn’t want to be null.
  • Marking for deletion: OK, so there’s a new core to our revision control system, Subversion.  We’re pretty excited about the possibilities that this is affording us.  One very visible change is how objects are deleted.  When you delete something it is “marked” for deletion and the next time you Check-in the parent container it will go away.  This is very different that what you may be used to.  But it’s necessary to maintain a more efficient approach to our revision control.  If you delete something and you want it to go away, just check in the parent container and it will.
 
*Subversion is a registered trademark of Collabnet
Retrieved from "http://docs.bungeeconnect.com/wiki/index.php/Release_Notes_:_November_15%2C_2007"
    Copyright © 2005 - 2008 Bungee Labs. All rights reserved.