When any of the events that cause the current record pointer to move are handled by the form, it generates a dEvents.RowNumChanged event, to which grids can bind so that they can update their display. The form code looked like:

dabo.ui.callAfter(self.raiseEvent, dEvents.RowNumChanged)

and the event handler in the grid would run this code:

try: self.CurrentRow = self.getBizobj().RowNumber except AttributeError: pass

In other words, the grid knew that the row had changed, but had no idea what the new row was. It had to then get a reference to the bizobj for that grid, if any, and then ask that bizobj for its current row number.

Why is this inefficient? Because the code that raised the event *knew* the old and new row numbers; the fact that they were different was why it was raising the event in the first place. Then I remembered that you can pass data along to raiseEvent(); any keyword parameters you add are set as event data. So I changed the form code to read:

dabo.ui.callAfter(self.raiseEvent, dEvents.RowNumChanged, newRowNumber=biz.RowNumber, oldRowNumber=oldRowNum)

...and now the grid's event handler can just reference those values directly! They will have the same names as the parameter keys:

try: self.CurrentRow = evt.newRowNumber except AttributeError: pass

This may be a small savings overall, but I thought that it illustrated a handy mechanism built into the Dabo event class that you might use to improve your applications.

See the ChangeLog, and download here. Enjoy!

As usual, you can grab it from the Download Page, or via FTP at ftp://dabodev.com/dabo/win.

The Dabo Runtime Engine is designed for people who are curious about Dabo, but who don't want the bother of installing all the required modules just to see what Dabo can do. It doesn't change any Windows Registry settings, so it will not affect any existing applications on your machine.

This version installs several shortcuts that allow you to simple double-click an icon to run the desired file. Such shortcuts include the AppWizard, Class Designer and Report Designer, as well as several of the demo applications, including the new DaboDemo application, which allows you to see the demo and the code behind it. You can then modify that code to see how your changes affect the output.

The Dabo Runtime Engine comes in two versions: the regular version that just runs the applications, and the Console version that display a command line window containing the application output and debuggng information. They are otherwise identical.

You can download either version, along with all other things Dabo, from: the Dabo Download Page.

We'd also like to announce the new 0.7.1 bugfix release of Dabo and DaboDemo. Get all this from the download page.

No worries, though. We know how to proceed, but have decided to wait until after the first release of Dabo-0.7. Once we have the fix in 0.8, we'll backport it to the Dabo-0.7 stable version. So, just be patient for now and keep using wxPython 2.6.x with Dabo.

http://svn.dabodev.com/dabo
http://svn.dabodev.com/dabodemo
http://svn.dabodev.com/daboide

For any given repository, the stable branch is in branches/stable and the development branch is in trunk. Official released versions can be found in tags.

svn switch --relocate svn://paulmcnett.com http://svn.dabodev.com

As usual, grab your copy from the Dabo Download Page: http://dabodev.com/download.

The Dabo Runtime Engine is designed for people who are curious about Dabo, but who don't want the bother of installing all the required modules just to see what Dabo can do. It doesn't change any Windows Registry settings, so it will not affect any existing applications on your machine.

This version installs several shortcuts that allow you to simple double-click an icon to run the desired file. Such shortcuts include the AppWizard, ClassDesigner and ReportDesigner, as well as several of the demo applications.

The Dabo Runtime Engine comes in two versions: the regular version that just runs the applications, and the Console version that display a command line window containing the application output. Besides that, they are identical.

You can download either version, along with all other things Dabo, from: the Dabo Download Page.

In addition to what we've improved in Dabo, we can't forget to mention the Dabo Class Designer, and Dabo Report Designer. Both of these visual design tools are really coming together, and can be found in the DaboIDE repository, which got bumped from version 0.4 to 0.5 today as well. Coming soon will be a graphical menu designer, and coming down the pipe will be an integration of these design tools into an Integrated Development Environment.

Framework: http://www.repocaster.com/main/get_feed/17

IDE: http://www.repocaster.com/main/get_feed/18

Demo: http://www.repocaster.com/main/get_feed/19

The service isn't completed yet, but I like the idea. If you have an RSS reader, you can add these links and keep up with all the latest changes in Dabo!

Let's say you created a 'mover' control: one that moves items between two lists. This can be handy in lots of forms, so you save it as a class. Later on you need to create another form that needs a mover, so you add an instance of your mover class to this new design surface. It will simply work as expected. But now suppose that a few weeks later, after you've used this class in dozens of forms, you discover a bug in your mover code. No problem: just fix the bug in your class, and all the forms that use your mover are also fixed!

Running time is 23 minutes.

View this and our previous screencasts at http://dabodev.com/documentation.

View this and our previous screencasts at http://dabodev.com/documentation.

Now navigate to somewhere else in the document. Do whatever editing you need, and then click on the 'M' button again. Note that the name you gave your bookmark is now in the popup menu. Select that, and the editor moves to that line. What's even cooler is that even if you add or delete lines, the bookmark follows the code that you bookmarked, not the line number!