Changeset 260

Timestamp:

05/10/04 12:53:57 (5 years ago)

Author:

paul

Message:

Prep for Dabo-0.1 release.

Files:

• trunk/ChangeLog (modified) (1 diff)
• trunk/INSTALL (modified) (1 diff)

trunk/ChangeLog

@@ +1 @@
+Dabo-0.1:
+
+------------------------------------------------------------------------
+r259 | paul | 2004-05-07 20:06:34 -0700 (Fri, 07 May 2004) | 4 lines
+
+I messed up earlier, intending to move the app name/version stuff to be 
+more accessible, I instead moved it to a point too late in instantiation
+for the main form to notice.
+
+------------------------------------------------------------------------
+r258 | paul | 2004-05-07 16:43:43 -0700 (Fri, 07 May 2004) | 2 lines
+
+Put the dabo icon on the forms by default.
+
+------------------------------------------------------------------------
+r257 | paul | 2004-05-07 16:22:53 -0700 (Fri, 07 May 2004) | 5 lines
+
+Make column definition items tuples instead of lists, so that they are
+immutable. dGrid can alter its copy of the columndef for its own use,
+and when it was a list it was altering the shared copy. Making it 
+immutable forces a pass-by-value instead of pass-by-reference.
+
+------------------------------------------------------------------------
+r256 | paul | 2004-05-07 16:09:25 -0700 (Fri, 07 May 2004) | 3 lines
+
+Change the order of the setting of the appInfo properties, to allow 
+user code to set these properties in dApp.setup().
+
+------------------------------------------------------------------------
+r255 | paul | 2004-05-07 15:42:42 -0700 (Fri, 07 May 2004) | 3 lines
+
+Fix some long-standing, really funky problems with repositioning and resizing
+grid columns. It should be way more stable now.
+
+------------------------------------------------------------------------
+r254 | paul | 2004-05-07 15:31:46 -0700 (Fri, 07 May 2004) | 2 lines
+
+This fixes the __setattr__ problem.
+
+------------------------------------------------------------------------
+r253 | ed | 2004-05-07 12:35:35 -0700 (Fri, 07 May 2004) | 5 lines
+
+Corrected a bunch of dumb typos.
+
+Note: I have to run out now, but next on the list is to update the demos,
+etc., to import dException instead of dError.
+
+------------------------------------------------------------------------
+r252 | ed | 2004-05-07 12:31:14 -0700 (Fri, 07 May 2004) | 2 lines
+
+Removed extra parenthesis
+
+------------------------------------------------------------------------
+r251 | ed | 2004-05-07 12:09:31 -0700 (Fri, 07 May 2004) | 8 lines
+
+Changed all of the references to dError to dException to emphasize the
+deliberate nature of these exceptions. Removed all the 'errorMsg'-related
+code in the bizobj and cursor classes, as these now raise exception rather
+than returning False.
+
+Modified the beforeXX() methods so that returning any non-empty string
+raises an exception with that string as the error message of the exception.
+
+------------------------------------------------------------------------
+r250 | paul | 2004-05-07 11:25:07 -0700 (Fri, 07 May 2004) | 5 lines
+
+Change dApp.homeDir from the location where Python was started to the location
+where the startup script lives. This allows shortcuts to appRecipes/main.py to
+find the dbConnectionDefs.py, for example.
+
+
+------------------------------------------------------------------------
+r249 | paul | 2004-05-06 20:07:20 -0700 (Thu, 06 May 2004) | 2 lines
+
+Some mods to ANNOUNCE
+
+------------------------------------------------------------------------
+r248 | paul | 2004-05-06 14:22:53 -0700 (Thu, 06 May 2004) | 6 lines
+
+Fix to the MySQL int/bool problem. This still isn't the correct 
+solution I don't think, but at least it happens where it should:
+at the cursor level, and only when there is a type mismatch 
+between the old val and the new val.
+
+
+------------------------------------------------------------------------
+r247 | ed | 2004-05-06 11:18:51 -0700 (Thu, 06 May 2004) | 3 lines
+
+I've edited the original ANNOUNCE, adding some stuff and switching other
+stuff around.
+
+------------------------------------------------------------------------
+r246 | paul | 2004-05-05 21:46:02 -0700 (Wed, 05 May 2004) | 4 lines
+
+Fix bug in flushValue code: self shouldn't have been prepended
+to curVal.
+
+
+------------------------------------------------------------------------
+r245 | paul | 2004-05-05 16:05:58 -0700 (Wed, 05 May 2004) | 6 lines
+
+Modify the property names of dConnectInfo to match the conventions
+elsewhere in Dabo of capitalized property names.
+
+Add a dMessageBox.info() message box.
+
+
+------------------------------------------------------------------------
+r244 | paul | 2004-05-04 10:49:55 -0700 (Tue, 04 May 2004) | 15 lines
+
+Fix dGrid's checkboxes to reflect the true value, instead of just being
+checked no matter what.
+
+The strict name checking won't work for parentless windows, such as a 
+top-level frame. For now, turn off strict checking for parentless windows,
+allowing possible duplicate names.
+
+Fix the test.py script to use unique object names.
+
+Call activeControlValid() when the user leaves a page. This allows, for
+example, the values in dGrid to reflect the new value without the user
+having to leave the control first.
+
+
+
+------------------------------------------------------------------------
+r243 | paul | 2004-05-04 09:43:28 -0700 (Tue, 04 May 2004) | 9 lines
+
+Add code in dGrid to display boolean values in a checkbox. Fix bug
+in dGrid which would cause an IndexError when assigning default column
+widths.
+
+Fix dPageDataNav.EditPage to put the caption in the checkbox instead
+of in the label.
+
+
+
+------------------------------------------------------------------------
+r242 | ed | 2004-05-04 08:59:58 -0700 (Tue, 04 May 2004) | 6 lines
+
+When a the flushValue() method was being called to flush changes to a
+control before a Save was run, the _oldVal property was not being updated.
+Subsequent calls to the control's flushValue() method would fail if the new
+value was equal to the original _oldVal. While this would not be common in
+text fields, it is very common in boolean fields.
+
+------------------------------------------------------------------------
+r241 | paul | 2004-05-04 06:56:35 -0700 (Tue, 04 May 2004) | 10 lines
+
+Add convenience function dBizobj.getChildByDataSource().
+
+Since dPageFrame sets a default number of pages now in __init__, 
+fix dPageFrameDataNav to set this back to zero, so that when 
+pages get added later they are the only pages.
+
+Fix dPageDataNav to not expect to get the child bizobj references
+directly from dForm, since dForm doesn't manage child bizobjs.
+
+
+------------------------------------------------------------------------
+r240 | paul | 2004-05-03 19:21:20 -0700 (Mon, 03 May 2004) | 14 lines
+
+Add PageClass and PageCount properties to dPageFrame, for specifying
+the number of pages (new pages will be based on PageClass, allowing
+the user to override with their own base class). User still has the
+option to use AddPage() directly.
+
+Reworked the setting of the default number of pages... does that work
+for you, knowing that we aren't encouraging passing values to the
+constructors? The only drawback to setting a positive number of pages
+is that user code will have to first set to zero if they want to add
+their own subclassed pages.
+
+Add TabPosition to the list of properties that require recreation.
+
+
+------------------------------------------------------------------------
+r239 | paul | 2004-05-03 17:36:32 -0700 (Mon, 03 May 2004) | 25 lines
+
+Handle NoRecordsError in dBizobj.getParentPk().
+
+Childviews in dFormDataNav use dGrid in the childview pages just like in
+the main browse page. Add logic so that when new/edit/delete is selected
+in the popup menu, it gets directed to the proper place.
+
+Raise NameError if user code tries to set a dObject's Name property to 
+a sibling's name. If this happens inside the init phase of the control, the
+error won't propagate up but the object will get assigned a new name 
+instead.
+
+Make control's init's call private methods _beforeInit() and _afterInit()
+instead of the user-code beforeInit() and afterInit() hooks. This is to 
+offer a level of guarantee that the basic stuff happens even if the user
+forgets to doDefault(). _beforeInit() and _afterInit() now call the user-
+code hook methods.
+
+Add initChildObjects() hook, which is where daboDesigner should put its
+addObject() code. Called from dPemMixin._afterInit().
+
+Fix dSlider's docstring.
+
+
+
+
+------------------------------------------------------------------------
+r238 | ed | 2004-05-02 13:01:04 -0700 (Sun, 02 May 2004) | 3 lines
+
+Added the new TypeID property to the list of props that are hidden in the
+designer.
+
+------------------------------------------------------------------------
+r237 | ed | 2004-05-01 03:36:15 -0700 (Sat, 01 May 2004) | 2 lines
+
+Er, ah... you might need this file... ;-)
+
+------------------------------------------------------------------------
+r236 | ed | 2004-04-30 20:31:57 -0700 (Fri, 30 Apr 2004) | 3 lines
+
+Added dSlider control.
+
+
+------------------------------------------------------------------------
+r235 | paul | 2004-04-30 11:45:42 -0700 (Fri, 30 Apr 2004) | 2 lines
+
+More info in INSTALL.
+
+------------------------------------------------------------------------
+r234 | paul | 2004-04-30 10:11:55 -0700 (Fri, 30 Apr 2004) | 3 lines
+
+When I made the bizobj changes, I inadvertantly set the default value of
+RestorePositionOnRequery to False instead of True.
+
+------------------------------------------------------------------------
+r233 | paul | 2004-04-30 09:30:26 -0700 (Fri, 30 Apr 2004) | 9 lines
+
+Dabo Announcement Version 0.1, dated 5/1/2004. Please read and augment. I'll send this
+to:
+
+ProFox/ProLinux/ProPython
+San Jose VFP SIG
+wxPython-users
+python-users
+
+
+------------------------------------------------------------------------
+r232 | paul | 2004-04-29 16:23:33 -0700 (Thu, 29 Apr 2004) | 6 lines
+
+Change docstring style from ''' to """, dabo-wide. 
+
+Make some of the bizobj changes as discussed, but didn't do the RI stuff
+as I'm unclear on what, if anything, we've decided to do.
+
+
+------------------------------------------------------------------------
+r231 | paul | 2004-04-29 11:23:57 -0700 (Thu, 29 Apr 2004) | 3 lines
+
+Add the new dabo icon in various sizes. They will likely get
+modified but at least they are there as placeholders.
+
+------------------------------------------------------------------------
+r230 | paul | 2004-04-29 08:05:34 -0700 (Thu, 29 Apr 2004) | 8 lines
+
+When I moved dError into its own namespace in dCursorMixin last week, I
+neglected to specify the namespace in some places where errors are raised.
+Fix that.
+
+Fix dGrid to call setRowNumber() instead of the now-nonexistent moveToRowNum().
+
+Fix a couple bugs in dPageDataNav.
+
+------------------------------------------------------------------------
+r229 | ed | 2004-04-29 07:13:19 -0700 (Thu, 29 Apr 2004) | 8 lines
+
+Changed the names of the moveTo* methods to _moveTo* to indicate that they
+should not be called directly from outside the bizobj,
+
+Added the setRowNumber() method, which allows navigation to a particular row
+in the result set, with a resultant requeryAllChildren() call. It also has
+the standard before- and after- hooks.
+
+
+------------------------------------------------------------------------
+r228 | ed | 2004-04-29 04:48:48 -0700 (Thu, 29 Apr 2004) | 4 lines
+
+Didn't realize that the SetRange() method of the Gauge control did not
+require re-creation, so I removed that property name from the
+preInitProperties.
+
+------------------------------------------------------------------------
+r227 | ed | 2004-04-29 04:42:53 -0700 (Thu, 29 Apr 2004) | 3 lines
+
+Accidentally restored the wrong line when merging my changes in with the
+ones you made yesterday.
+
+------------------------------------------------------------------------
+r226 | ed | 2004-04-29 04:35:00 -0700 (Thu, 29 Apr 2004) | 26 lines
+
+Removed the calls to requeryAllChildren() and afterPointerMove() from the
+bizobj. Added those calls as an option to the seek() method.
+
+The first two methods are "for internal use only", and should never be called from
+an app. They exist so that the bizobj can move the pointer to where it needs
+to be without triggering a slew of additional effects. 
+
+moveToPK() is only used in a requery() to try to restore the record pointer
+to the PK of the record it was on before the cursror was requeried. It is
+followed by a call to requeryAllChildren() and afterPointerMove() in that
+method; calling it again from this one is just inefficient..
+
+moveToRowNum() is called by the validate() method so that a bizobj can check
+all of its records. You don't want it requerying its children, as they will
+need to be validated separately, and will be called in turn.
+
+In VFP Codebook, these methods are protected. For record pointer movement
+from within an app, the public methods first(), next(), etc., should be used
+to move the record pointer.
+
+Since seek() is intended to be called both internally and from developer's
+code, I've added a parameter 'runRequery' which defaults to False. If this
+value is passed as True, requeryAllChildren() and afterPointerMove() will be
+called if the cursor moves the pointer.
+
+
+------------------------------------------------------------------------
+r225 | paul | 2004-04-28 23:38:17 -0700 (Wed, 28 Apr 2004) | 4 lines
+
+Make dGauge not data-aware, and fix range and value to work correctly.
+BackColor and ForeColor don't seem to work, neither does BorderStyle.
+
+
+------------------------------------------------------------------------
+r224 | paul | 2004-04-28 23:18:00 -0700 (Wed, 28 Apr 2004) | 2 lines
+
+Child view pages now show data browse grid.
+
+------------------------------------------------------------------------
+r223 | paul | 2004-04-28 16:22:00 -0700 (Wed, 28 Apr 2004) | 2 lines
+
+Further work on child views for the dFormDataNav thing.
+
+------------------------------------------------------------------------
+r222 | ed | 2004-04-28 13:36:41 -0700 (Wed, 28 Apr 2004) | 5 lines
+
+Added the Gauge control. It's generally working (although there are some
+funky background changes when being reCreated), but I haven't been able to
+get the ability to change the Range of the control at design time. Guess I
+need to grok the whole preInit stuff better.
+
+------------------------------------------------------------------------
+r221 | paul | 2004-04-28 13:11:48 -0700 (Wed, 28 Apr 2004) | 50 lines
+
+Refactor the API of dBizobj, making most of the 'properties' into actual
+Python properties complete with getters, setters, and docstrings. Here is
+a list of the new bizobj properties:
+
+    Caption (new: friendly name for communicating with the user)
+    DataSource (was dataSource)
+    SQL (was sql)
+    RequeryOnLoad (was noDataOnLoad)
+    AutoPopulatePK (was autoPopulatePK)
+    Parent (was _parent)
+    KeyField (was keyField)
+    LinkField (was linkField)
+    ErrorMessage (was _errorMsg, and I think this one can go because of the exception-refactor)
+    RequeryChildOnSave (was requeryChildOnSave)
+    NewChildOnNew (was newChildOnNew)
+    NewRecordOnNewParent (was newRecordOnNewParent)
+    FillLinkFromParent (was fillLinkFromParent)
+    RestorePositionOnRequery (was savePosOnRequery)
+
+Obviously, I've FUBAR'd the original API so all the demos that use bizobj's 
+will have to be changed, which I'll do after lunch.
+
+Refactor getPropertyList() and getPropertyInfo() out of dPemMixin and into the
+new dabo.common.PropertyHelperMixin, since these functions can be useful at a
+lower level than our wx interface. Make dPemMixin and dBizobj inherit from
+PropertyHelperMixin, which means that dBizobj can now theoretically be represented
+on the designer and have its properties edited there.
+
+Add beforeInit() hook to dBizobj, which allows the user code an opportunity to 
+modify properties such as RequeryOnLoad before they take effect.
+
+dBizobj.__setattr__ had old-style class code that was causing my new property API
+to fail silently, and it drove me crazy for an entire hour at least. :)  Changing
+to the new-style super() call for non-cursor field attributes fixed the problem.
+Lesson learned: __getattr__ will be called only after the attribute was not found, 
+while __setattr__ gets called before Python looks for the attribute at all. Sounds 
+like a subtle difference on paper but the implications are huge!
+
+Add method getChildren() to dBizobj, which returns a tuple of object references
+to the children. 
+
+Add icon childview.png, which represents a child bizobj in the runtime dFormDataNav.
+
+In dFormDataNav, delay instantiation of the pageframe until the primary column def
+has been assigned, which allows the childviews to appear in the nav menu and in the
+page frame.
+
+The UI for the child view stuff isn't working yet, but it is a little closer. I started
+out this morning working on that and got sidetracked with the bizobj changes.
+
+------------------------------------------------------------------------
+r220 | paul | 2004-04-28 08:42:09 -0700 (Wed, 28 Apr 2004) | 10 lines
+
+Make changes to BackColor do an implicit self.Refresh(), as it appears to 
+be necessary with most controls, although it appears that dEditBox needs to
+actually be recreated...
+
+The borderstyle thing isn't working right, as different controls have different
+default borders. For instance, dEditBox with no border style flags set has a
+simple border, while dPanel does not. Add a 'Default' setting to let the value
+get set back to that control's default (no border flags set).
+
+
+------------------------------------------------------------------------
+r219 | paul | 2004-04-28 08:10:24 -0700 (Wed, 28 Apr 2004) | 4 lines
+
+Fix bug in dCheckbox where setting alignment back to Left would raise
+a ValueError.
+
+
+------------------------------------------------------------------------
+r218 | ed | 2004-04-28 04:23:43 -0700 (Wed, 28 Apr 2004) | 3 lines
+
+Refactored out the prop/val saving and prop/val restoring sections of
+reCreate so that they could be called from other places.
+
+------------------------------------------------------------------------
+r217 | paul | 2004-04-27 17:21:34 -0700 (Tue, 27 Apr 2004) | 25 lines
+
+Import dError into separate namespace, instead of into global namespace,
+in dBizobj and dCursorMixin.
+
+Make dBizobj inherit from DoDefaultMixin. Add an afterInit() hook in 
+dBizobj so that subclasses don't need to know what to send to __init__().
+
+In dBizobj, there were lots of structures like:
+        try:
+            self._cursor.first()
+            self.requeryAllChildren()
+        except dError, e:
+            # Pass the error back to the UI
+            raise dError, e
+            return False
+        
+Since nothing else is being done except re-raising the error, I simplified
+these by taking out the try block completely. The error will propagate back
+to the UI by default anyway.
+
+Fix bug in dBizobj: moveToRowNum() and moveToPK() were not requerying the
+child bizobjs nor calling the afterPointerMove() hook.
+
+Put a couple try blocks in dGrid and dDataControlMixin.
+
+
+------------------------------------------------------------------------
+r216 | paul | 2004-04-27 13:00:11 -0700 (Tue, 27 Apr 2004) | 3 lines
+
+Text of GPL to COPYING. Addition of LICENSE.TXT which specifies copyright
+and license.
+
+------------------------------------------------------------------------
+r215 | ed | 2004-04-26 17:58:00 -0700 (Mon, 26 Apr 2004) | 3 lines
+
+Changed the setSQL() method so that passing no argument results in the same
+thing as calling biz.setSQL(biz.getSQL()).
+
+------------------------------------------------------------------------
+r214 | ed | 2004-04-26 15:45:11 -0700 (Mon, 26 Apr 2004) | 2 lines
+
+Cleaned up the copying of ToolTipText.
+
+------------------------------------------------------------------------
+r213 | ed | 2004-04-26 13:35:27 -0700 (Mon, 26 Apr 2004) | 4 lines
+
+Added a list of properties to ignore. These are properties that are either
+calculated props, such as 'Right', or properties that cannot be set, such as
+'BaseClass'.
+
+------------------------------------------------------------------------
+r212 | ed | 2004-04-26 12:17:36 -0700 (Mon, 26 Apr 2004) | 10 lines
+
+Modified the reCreate() method to better assign properties. There are still
+some artifacts to work out that mostly involve property assignment order;
+for example, the method was restoring the Left, Right, and Width properties
+in such a way that controls were being moved every time they were
+re-created. I added some extra code to handle this, but there are some
+similar problems with fonts that need to be addressed.
+
+I left in a line that prints out all failed property assignments, so that we
+remember to handle these exceptions.
+
+------------------------------------------------------------------------
+r211 | paul | 2004-04-24 17:06:40 -0700 (Sat, 24 Apr 2004) | 2 lines
+
+Fix inconsistency in dRadioGroup.
+
+------------------------------------------------------------------------
+r210 | paul | 2004-04-23 16:19:27 -0700 (Fri, 23 Apr 2004) | 4 lines
+
+Experimenting with a print preview of the browse records - push the
+preview button when on the browse page. Ugly but at least it's a 
+start.
+
+------------------------------------------------------------------------
+r209 | paul | 2004-04-23 15:51:36 -0700 (Fri, 23 Apr 2004) | 2 lines
+
+Change name of dOptionGroup to dRadioGroup.
+
+------------------------------------------------------------------------
+r208 | paul | 2004-04-23 15:33:55 -0700 (Fri, 23 Apr 2004) | 10 lines
+
+Fix some bugs in dOptionGroup.
+
+Experimental: I'm actually scared at how easy this was to implement, but I added
+a reCreate() function to dPemMixin, so now any object can reinstantiate itself
+by calling self.reCreate(). The intent is really for the daboDesigner to be able 
+to reinstantiate an object at will, such as when a property changes that won't
+take effect at runtime, such as Alignment, BorderStyle, PasswordEntry, and all the
+useful properties of dOptionGroup.
+
+
+------------------------------------------------------------------------
+r207 | paul | 2004-04-23 13:38:39 -0700 (Fri, 23 Apr 2004) | 2 lines
+
+Fix typos causing TypeError on instantiation.
+
+------------------------------------------------------------------------
+r206 | paul | 2004-04-23 12:50:36 -0700 (Fri, 23 Apr 2004) | 13 lines
+
+Add dOptionGroup, based on wx.RadioBox. 
+
+Modify icon for dLabel. Still not happy with it, but it is better 
+than the last one.
+
+Simplify all constructors of the dControls with new PostCreate()
+feature of wxPython.
+
+Remove the echoing of the icon file name from dIcons, which Ed noticed
+while running daboDesigner.
+
+
+
+------------------------------------------------------------------------
+r205 | paul | 2004-04-23 08:54:16 -0700 (Fri, 23 Apr 2004) | 2 lines
+
+Make FontFace read-only.
+
+------------------------------------------------------------------------
+r204 | ed | 2004-04-23 05:43:10 -0700 (Fri, 23 Apr 2004) | 3 lines
+
+Corrected copy/paste bug: _getBackColorEditorInfo was not present; instead,
+_getForeColorEditorInfo was listed twice.
+
+------------------------------------------------------------------------
+r203 | ed | 2004-04-23 05:35:17 -0700 (Fri, 23 Apr 2004) | 4 lines
+
+Changed the spelling of the editor for colors to 'colour', to be consistent
+with the rest of wxPython. It's odd having to remember when to write which
+spelling, so 'colour' it is.
+
+------------------------------------------------------------------------
+r202 | paul | 2004-04-22 18:42:04 -0700 (Thu, 22 Apr 2004) | 2 lines
+
+Add other control icons, and make a better dEditBox icon.
+
+------------------------------------------------------------------------
+r201 | paul | 2004-04-22 18:01:11 -0700 (Thu, 22 Apr 2004) | 4 lines
+
+Add icon dEditBox.png, which will display in the daboDesigner if you make
+the changes I'm about to commit.
+
+
+------------------------------------------------------------------------
+r200 | paul | 2004-04-22 18:00:22 -0700 (Thu, 22 Apr 2004) | 6 lines
+
+Make the daboDesignerClass dict have a prompt key as well that can include
+a hotkey value.
+
+Fix dIcons.getIconBitmap() to really return null bitmaps when the file
+doesn't exist.
+
+------------------------------------------------------------------------
+r199 | paul | 2004-04-22 15:26:07 -0700 (Thu, 22 Apr 2004) | 2 lines
+
+Add the font editor info to the Font property.
+
+------------------------------------------------------------------------
+r198 | paul | 2004-04-22 14:54:54 -0700 (Thu, 22 Apr 2004) | 5 lines
+
+Move property SelectOnEntry from dDataControlMixin to dTextBox and
+dEditBox as it only applies to text controls. I should probably make
+a dTextControlMixin to avoid the code duplication - another day.
+
+
+------------------------------------------------------------------------
+r197 | ed | 2004-04-22 13:53:28 -0700 (Thu, 22 Apr 2004) | 2 lines
+
+Corrected indentation in the docstring for the class.
+
+------------------------------------------------------------------------
+r196 | paul | 2004-04-22 12:29:23 -0700 (Thu, 22 Apr 2004) | 5 lines
+
+Extract doDefault() from dPemMixin and put in new dabo.common submodule,
+and make dPemMixin inherit from dabo.ui.common.DoDefaultMixin. This was 
+because doDefault() has broader use than just inside the UI part of dabo.
+
+
+------------------------------------------------------------------------
+r195 | paul | 2004-04-22 10:53:13 -0700 (Thu, 22 Apr 2004) | 5 lines
+
+Reimplemented addObject() to take a classRef directly instead of className and
+moduleName strings. This is better because it leaves it up to the subclass to 
+make sure the proper module is imported, which is where that belongs.
+
+
+------------------------------------------------------------------------
+r194 | paul | 2004-04-22 10:27:06 -0700 (Thu, 22 Apr 2004) | 4 lines
+
+Keep the details of building daboDesignerClasses from polluting
+the module's namespace.
+
+
+------------------------------------------------------------------------
+r193 | paul | 2004-04-22 10:22:04 -0700 (Thu, 22 Apr 2004) | 11 lines
+
+Update dabo.ui.daboDesignerClasses to be a list of dictionaries, with
+keys on 'name', 'class', 'topLevel', 'icon', and 'doc'. The
+topLevel key can be used to determine if the object can be added
+to another control, or if it must be the top level object. The icon 
+key will have a picture of the control suitable for displaying in a 
+menu or toolbar control-picker. The doc key provides some help text.
+
+After adding the doc key above, I finally got around to writing short
+docstrings for the various dControls.
+
+
+------------------------------------------------------------------------
+r192 | paul | 2004-04-22 06:59:43 -0700 (Thu, 22 Apr 2004) | 6 lines
+
+Add daboDesignerClasses list to dabo.ui module, which is a list of class references
+to the valid dabo classes to show in the designer.
+
+Our users can do the same thing with their modules, to control what of their custom
+classes show in the designer.
+
+------------------------------------------------------------------------
+r191 | paul | 2004-04-21 19:26:19 -0700 (Wed, 21 Apr 2004) | 5 lines
+
+Add the promised addObject() method to dPemMixin, allowing code like:
+    self.addObject("dTextBox", "dabo.ui", "txtLastName")
+    self.txtLastName.FontBold = True
+
+
+------------------------------------------------------------------------
+r190 | paul | 2004-04-21 17:29:14 -0700 (Wed, 21 Apr 2004) | 6 lines
+
+Tabs!
+
+Or, a review of the entire source base of Dabo. <g>
+
+Also, removed the appRoot directory.
+
+------------------------------------------------------------------------
+r189 | paul | 2004-04-21 16:23:33 -0700 (Wed, 21 Apr 2004) | 23 lines
+
+Increase robustness of property setters by coercing proper data types
+and raising exceptions with improper values.
+
+Fix a few places where my strategy for setting/deleting window style
+flags wasn't up to snuff.
+
+Add 'showInDesigner' key to the getPropertyInfo dict. This tells the 
+designer whether to show the property at all. Set WindowHandle, Size,
+and Position to not show in the designer.
+
+Add 'preInitProperty' key to the getPropertyInfo dict. This tells the
+designer where to put this property setting in the class's source code.
+Some properties need to be set before the object is fully constructed,
+while most need to be set after the object is fully constructed. Set 
+the few properties I know about that need to be defined early.
+
+Add some editorInfo overrides to some properties, where the defaults 
+wouldn't be adequate. For instance, the default for integers is -65536
+to 65536, which is completely inappropriate for properties like Width
+and Height, which can't go below 0.
+
+
+
+------------------------------------------------------------------------
+r188 | paul | 2004-04-21 14:16:36 -0700 (Wed, 21 Apr 2004) | 22 lines
+
+Separate out the property initialization, based on whether the property
+needs to be passed as a style parameter to the constructor (property will
+be read-only at runtime), or whether the property must be set after the
+object is fully instantiated (property will be read/write at runtime 
+unless specified differently in the property assignment).
+
+Add getPropertyInfo() to dPemMixin, which returns a dict of useful information
+on the passed property name, including the data type, the editor to use, and 
+the docstring. This is to make the designer much more generic: it can just
+query the object for most of the information it needs.
+
+Part of the logic of the above involves checking for the editor to use by
+calling a special method which is named similarly to the given property.
+If that method doesn't exist, a default value for editor info is returned, 
+based on data type, which is how I've left it for most of the properties.
+The only properties I've specifically defined editors for so far are the ones 
+that have a set number of choices to be presented in a list, such as 'Alignment'.
+
+Add property 'AutoResize' to dLabel.
+
+
+
+------------------------------------------------------------------------
+r187 | paul | 2004-04-20 17:44:14 -0700 (Tue, 20 Apr 2004) | 17 lines
+
+Change some of my " to ' <g>.  Localize some strings.
+
+Change multi-state properties, such as Alignment, to have string
+identifiers instead of integer identifiers.
+
+Give dForm the wx interface, just like I did for the dControls earlier.
+Remove setupResources() from dForm as I don't think that is the interface
+we'll use (I don't think we'll use resources at all).
+
+Fix some properties to work correctly. This was after testing with 
+dTextBox in daboDesigner. I need to figure out how to deal with the 
+styles that have to be passed to the constructor, not altered after the
+object has already been created (Alignment, for example). I'm thinking
+that we'll have to get a copy of the object's properties, destroy it, 
+and then recreate it. 
+
+
+------------------------------------------------------------------------
+r186 | paul | 2004-04-19 22:46:27 -0700 (Mon, 19 Apr 2004) | 16 lines
+
+Fix some import statements. Fix bug in property 'ToolTipText'. Fix ui test
+script to use the new property interface.
+
+Rework the dControl's constructors to pretty much conform to wx's constructor
+format. There are some exceptions, and I haven't done the dForm's yet. To be
+completely safe, anything beyond parent and id should use named arguments even
+though theoretically positional arguments should work.
+
+Add a requery button to the select page of dFormDataNav, and try to set it as
+the default button (click on <Enter>) but at least on Linux that isn't working
+as advertised. Rework the select page to use dControls instead of wx controls
+directly and use the property interface.
+
+
+
+
+------------------------------------------------------------------------
+r185 | paul | 2004-04-19 16:25:37 -0700 (Mon, 19 Apr 2004) | 16 lines
+
+Simplify icon names. Add a couple new icons.
+
+Add new actions to edit menu: cut/copy/paste/find. Surprisingly, I
+had to implement cut/copy/paste myself using the clipboard object,
+even though cut/copy/paste is one thing that is pretty much universal
+among the various platforms.
+
+Decorate various menu items with appropriate icons. Make dMenu inherit
+from dPemMixin. 
+
+Add property 'WindowState' to the forms, which provides one interface to
+get/set whether the form is minimized, normal, maximized, or full screen.
+
+
+
+
+------------------------------------------------------------------------
+r184 | paul | 2004-04-17 14:00:44 -0700 (Sat, 17 Apr 2004) | 55 lines
+
+Make dLabel not auto-resize to the length of the text. Fix a couple minor
+bugs.
+
+Add the following properties, most of which are saved in the WindowStyleFlags
+and so otherwise would be kind of difficult to use:
+
+dCheckBox:
+    .Alignment (left, right)
+    
+dEditBox:
+    .Alignment (left, center, right)
+    .ReadOnly
+    
+dLabel:
+    .Alignment (left, center, right)
+    
+dPageFrame:
+    .TabPosition (top, left, right, bottom)
+
+dSpinner:
+    .SpinnerWrap (does the value wrap from low to high, and vice-versa)
+    .SpinnerArrowKeys (can the user spin up/down with the keyboard)
+    
+dTextBox:
+    .Alignment (left, center, right)
+    .ReadOnly (like Enabled=False but allows text selection)
+    .PasswordEntry (if True, echoes asterisks instead of Value)
+
+All forms:
+    .BorderResizable
+    .ShowMaxButton
+    .ShowMinButton
+    .ShowCloseButton
+    .ShowCaption
+    .ShowSystemMenu
+    .TinyTitleBar
+    
+All controls and forms:
+    .BorderStyle (none, simple, raised, sunken)
+    .WindowHandle (platform-specific Hwnd)
+
+Note that in most cases I haven't tested any property interactions yet, but 
+in theory they should all work. Some of these won't work on live objects, so
+in the future when integrating with the designer we'll probably have to recreate
+the object after some of these properties change. My feeling is that most testing
+of the properties can wait until the designer is instantiating these controls, at
+which point we'll have a convenient interactive testing environment.
+
+Note also that I chose to skip over some possibilities, such as making a 3-state
+checkbox control and some other styles that only work on this or that platform.
+We can revisit these in the future and choose to put them in, but my feeling is
+that if it doesn't apply to all platforms, it shouldn't apply to any platform.
+Keeping Dabo at the lowest common functionality will reduce surprises and headaches
+for our users later, when they try to port their app from Windows to Mac.
+
+------------------------------------------------------------------------
+r183 | paul | 2004-04-16 15:50:29 -0700 (Fri, 16 Apr 2004) | 11 lines
+
+Change name of property 'ParentClass' to 'SuperClass'.
+
+Add flat Font* properties, including FontInfo which is a text-string
+representation of the current font.
+
+Add properties 'Right' and 'Bottom' just because I guess...         
+
+Fix a bug that was returning the object's position instead of the 
+object's size.
+
+
+------------------------------------------------------------------------
+r182 | paul | 2004-04-16 11:49:55 -0700 (Fri, 16 Apr 2004) | 9 lines
+
+Add property 'Class' to dPemMixin, and give meaningful values to properties
+'Class', 'ParentClass', and 'BaseClass'. self.Class will return a classref
+to the class the object is based on. self.ParentClass will return a classref
+to the parent class, or None if the parent class is higher up than self.BaseClass.
+self.BaseClass will return a classref to the base dControl of the class, NOT 
+the base class of whatever UI is in use (wx.EventHandler in wxPython).
+
+
+
+------------------------------------------------------------------------
+r181 | paul | 2004-04-15 11:52:29 -0700 (Thu, 15 Apr 2004) | 15 lines
+
+Fix Linux segmentation fault and Windows Fatal Error c0000005 that
+was happening on destruction of the main frame. This appears to be
+a problem way down in the bowels of wx that I exposed with yesterday's
+addition of the dPemMixin.__getattr__() code, which was doing a
+self.GetName() to be able to display the name of the object in the
+raised AttributeError exception. I think the base C++ object is 
+already destroyed which resulted in GetName() segfaulting. My workaround
+saves self.GetName() to _name at opportune times, and __getattr__ uses
+the value of _name for the AttributeError.
+
+Add class dPanel, and make dPage inherit from that instead of from
+wx.Panel.
+
+
+
+------------------------------------------------------------------------
+r180 | paul | 2004-04-14 17:45:07 -0700 (Wed, 14 Apr 2004) | 16 lines
+
+Add a classmethod doDefault() to dPemMixin, which allows superclass
+methods to be called using the VFP-like syntax of:
+    
+    retval = class.doDefault([args])
+
+For instance:
+    
+    class MyTextBox(dTextBox):
+        def afterInit(self):
+            print "afterInit"
+            MyTextBox.doDefault()
+
+This can replace the super(class,self).methodName([args]) syntax, which
+I think is much friendlier.
+
+
+------------------------------------------------------------------------
+r179 | paul | 2004-04-14 13:12:25 -0700 (Wed, 14 Apr 2004) | 18 lines
+
+Split the __init__ phase into 2-stage, for future accomodation of loading
+properties from resource files, and to accomodate setting certain extra
+styles that cannot otherwise be set. Add beforeInit() and afterInit() 
+hooks to dPemMixin which is an ancestor of all the dControls and dForms, 
+and provide docstrings to encourage users to put their code in these methods
+instead of in __init__() directly.
+
+Add a __getattr__() in dPemMixin which will try to resolve attributes to
+child windows, allowing references like 'self.myPanel.myTextBox.Value', for
+example.
+
+Remove dControlMixin.setDefaultFont(), as this was cruft from the previous
+Dabo which doesn't appear to be necessary anymore.
+
+Add properties 'SpinnerHighValue' and 'SpinnerLowValue' to dSpinner.
+
+
+
+------------------------------------------------------------------------
+r178 | paul | 2004-04-14 08:14:36 -0700 (Wed, 14 Apr 2004) | 9 lines
+
+Simplify dForm.activeControlValid() and dDataControlMixin.SetFocus() by 
+determining which control has the focus using wx's Window.FindFocus() 
+method instead of saving this information manually.
+
+Add property Default to dCommandButton, which specifies if this command
+button will raise a EVT_BUTTON when the <Enter> key is pressed and not
+handled elsewhere on the form.
+
+
+------------------------------------------------------------------------
+r177 | paul | 2004-04-13 17:35:31 -0700 (Tue, 13 Apr 2004) | 1 line
+
+Fixes to make Dabo behave better on Mac, including not showing the main frame
+------------------------------------------------------------------------
+r176 | paul | 2004-04-13 16:37:57 -0700 (Tue, 13 Apr 2004) | 1 line
+
+Fix for Mac to make the about menu appear in the app menu
+------------------------------------------------------------------------
+r175 | paul | 2004-04-13 14:27:39 -0700 (Tue, 13 Apr 2004) | 1 line
+
+Oops, I left in a debug line with my last commit.
+------------------------------------------------------------------------
+r174 | paul | 2004-04-13 14:26:19 -0700 (Tue, 13 Apr 2004) | 1 line
+
+Minor fixes for Windows. One remaining problem is that Windows dForm's don't fire an implicit Activate event when first instantiated, so my logic for restoring size and position isn't working. I think this will fix itself when I move to three-stage creation, which is on my list for the ability to integrate resource files.
+------------------------------------------------------------------------
+r173 | paul | 2004-04-13 12:28:50 -0700 (Tue, 13 Apr 2004) | 8 lines
+
+Brainstorm of our eventual announcement of Dabo. We need to review 
+and modify and make clear anything that is opaque, and once we are
+happy with it we can decide when to announce. We can decide if we
+want to announce before we have a workable install, or if we should
+wait until all that is documented, but I thought I'd get started on
+the ultimate announcement now rather than later.
+
+
+------------------------------------------------------------------------
+r172 | paul | 2004-04-12 18:43:15 -0700 (Mon, 12 Apr 2004) | 24 lines
+
+General skim/review of everything in dabo/ui/uiwx/classes. This led to
+some rearranging of things:
+
+In general, I fixed the import statements to import into private namespaces
+instead of into the module-global namespace. 'Namespaces are good', I think,
+is the quote on the back of our PyCon 2004 shirts. :)  Seriously, this is 
+much safer as we don't risk separate modules stepping on each other's names.
+
+The way I had it, dPageFrame and dPage were not base-class-like, in that
+they both tied in intimately with dFormDataNav. I made new dPageFrame and
+dPage base classes, with just basic behavior that would apply to all
+subclasses, not just the data nav form. I then subclassed dPageFrame
+to create dPageFrameDataNav, and I subclassed dPage to create dSelectPage,
+dBrowsePage, and dEditPage. 
+
+I fixed some naming issues inside some of the page classes.
+
+There was still some old-Dabo cruft in dMainMenuBar, which I removed.
+
+Switched to the new-style super(class, instance).method() style of 
+running the parent-class behavior wherever possible.
+
+Added a commandbutton to the test.py script.
+
+------------------------------------------------------------------------
+r171 | paul | 2004-04-09 10:51:04 -0700 (Fri, 09 Apr 2004) | 7 lines
+
+Make dform.ask2Save into a real property, and renamed it to AskToSave (sorry,
+I hate the 2 meaning 'to'. Always bugged me.)
+
+Make dform._set* coerce the values into boolean, so that if someone says:
+self.AskToSave=1, it will save True instead of 1.
+
+
+------------------------------------------------------------------------
+r170 | ed | 2004-04-09 05:18:35 -0700 (Fri, 09 Apr 2004) | 6 lines
+
+Changed all loc() calls to _() in the bizobj and data classes.
+
+Wrapped the "Do you want to save?" request in dForm with a boolean property
+to allow suppression of the call.
+
+
+------------------------------------------------------------------------
+r169 | paul | 2004-04-08 22:19:32 -0700 (Thu, 08 Apr 2004) | 2 lines
+
+Wrapped some strings in dForm to dLocalize.
+
+------------------------------------------------------------------------
+r168 | paul | 2004-04-08 22:04:01 -0700 (Thu, 08 Apr 2004) | 15 lines
+
+There is an inconsistency in dBizobj.isChanged() versus dCursorMixin.isChanged().
+dBizobj's docstring states that it is going to just check the current record, while
+dCursorMixin's docstring states it will check all records, which is what it does.
+
+I didn't change the docstrings, but I did add an allRows argument to both of these
+functions, along with logic in dCursorMixin to act appropriately based on the 
+parameter. I made the default value of these arguments match the docstrings, so
+allRows=False in dBizobj, and allRow=True in dCursorMixin.
+
+Changed the name of dLocalize.loc() to dLocalize._() to match the il8n conventions,
+but loc() still works as well. Changed dForm's loc() calls to _() calls.
+
+Added a 'save changes' prompt to dForm.requery() when there are unsaved changes,
+allowing Yes/No/Cancel choices.
+
+------------------------------------------------------------------------
+r167 | paul | 2004-04-07 22:25:11 -0700 (Wed, 07 Apr 2004) | 1 line
+
+win32 compatibility
+------------------------------------------------------------------------
+r166 | paul | 2004-04-07 19:43:52 -0700 (Wed, 07 Apr 2004) | 1 line
+
+Fixes for win32 compatibility.
+------------------------------------------------------------------------
+r165 | paul | 2004-04-07 18:06:30 -0700 (Wed, 07 Apr 2004) | 2 lines
+
+I was testing on wxPython2.5/Win and found a couple minor problems.
+
+------------------------------------------------------------------------
+r164 | paul | 2004-04-07 11:18:24 -0700 (Wed, 07 Apr 2004) | 7 lines
+
+Use new Bind() syntax for dForm's custom events.
+
+Also, remove dVCR from __init__ in the classes directory, which I 
+swear I removed before. I just wiped my Dabo and did a new checkout,
+at which point I got a 'no module dVCR' error. Weird.
+
+
+------------------------------------------------------------------------
+r163 | paul | 2004-04-06 17:42:40 -0700 (Tue, 06 Apr 2004) | 11 lines
+
+Add class method getPropertyList() to dPemMixin, which provides a convenient
+way to get a listing of the defined properties, either on a classref or on
+an instance. Add some extra print statements inside dForm.addControl() to
+show this in use.
+
+Fix some problems with the property accessors for some properties, specifically
+initialize the values to None if not previously initialized.
+
+Implement Value property for data-aware controls.
+
+
+------------------------------------------------------------------------
+r162 | paul | 2004-04-06 15:36:22 -0700 (Tue, 06 Apr 2004) | 17 lines
+
+Set more property definitions in controls and forms, matching up wx 
+get/set functions to VFP property naming styles. One good side
+effect is that you can now always refer to self.Parent to get the 
+containing object. As soon as only dControls are in use everywhere,
+we'll be able to say 'self.Parent.Parent...'. Next, I'll probably add a 
+self.Form property which would be analagous to VFP's ThisForm.
+
+Make messagebox's center themselves on top of the active form, not on 
+top of the top level form.
+
+Make the main menu bar appear on all forms, which is more Linux-like. This
+should have no effect on Windows where there is just one main menu bar on the
+parent MDI form but I have yet to test that.
+
+
+
+
+------------------------------------------------------------------------
+r161 | paul | 2004-04-06 11:35:34 -0700 (Tue, 06 Apr 2004) | 2 lines
+
+Forgot to follow through converting SelectOnEntry to a property.
+
+------------------------------------------------------------------------
+r160 | paul | 2004-04-06 11:24:48 -0700 (Tue, 06 Apr 2004) | 35 lines
+
+Remove extraneous getSQL() from the bizobj, now that getSQL() is a 
+passthrough to the cursor's sqlbuilder.
+
+I found another example in dCursorMixin where we catch all exceptions
+and then raise dError. This isn't right, as we want the actual exception
+to propagate up to the global error handler, not to hide it.
+
+Remove sqlBuilder from dFormDataNav, as it is now exposed in the bizobj.
+Set up the requery funct