2008/03/05 12:55:51 fs 1.38.84.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 12:55:51 fs 1.27.82.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 12:55:51 fs 1.49.70.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 12:55:51 fs 1.8.170.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 12:55:51 fs 1.157.80.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 13:10:43 fs 1.35.82.2: #i10000#
2008/03/05 12:55:51 fs 1.35.82.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 12:55:50 fs 1.5.166.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 13:10:43 fs 1.13.28.2: #i10000#
2008/03/05 12:55:50 fs 1.13.28.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 12:55:50 fs 1.15.72.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/03/05 12:55:50 fs 1.9.170.1: #i86720# some re-factoring, owed to the fact that we now have a stand-alone dialog for entering text/csv settings, which re-uses existing functionality
2008/02/18 13:48:37 fs 1.1.2.1: #i10000#
Our framework needs a "menubar" folder for each module's description (modules/dbbrowser/menubar
in this case), even if it doesn't contain a menubar.xml. Otherwise, it will fail to load all
UI elements for this module.
Unfortunately, the place where our uiconfig.zip is packaged doesn't respect empty folders,
so we need to have a folder with a dummy file - "preserve.txt", in this case.
2008/01/24 14:10:20 fs 1.7.98.1: during #i49133#: its not necessary at all to have an own implementation for the authentication request - the generic interaction handler can easily do this
2008/02/20 13:28:05 fs 1.15.196.2.2.1: some DBG_UNHANDLED_EXCEPTIONs
2008/02/04 13:08:26 fs 1.15.196.2: RESYNC: (1.15-1.16); FILE MERGED
2008/01/24 14:10:20 fs 1.15.196.1: during #i49133#: its not necessary at all to have an own implementation for the authentication request - the generic interaction handler can easily do this
2008/02/20 13:28:03 fs 1.22.98.6.2.2: some DBG_UNHANDLED_EXCEPTIONs
2008/02/14 12:35:31 fs 1.22.98.6.2.1: #i49133# re-enable the macros in DBDocs, which had been temporarily disable to finalize CWS odbmacros2
2008/02/14 08:37:41 fs 1.22.98.6: temporarily disable scripting support for database documents, so we have an intermediate version of the CWS which we can integrate
2008/02/11 13:49:01 fs 1.22.98.5: #i10000#
2008/02/06 21:43:23 fs 1.22.98.4: #i49133# don't support XScriptInvocationContext if our associated document does not support XEmbeddedScripts
2008/01/26 21:22:12 fs 1.22.98.3: m_aModelConnector not used anymore
2007/12/18 21:25:10 fs 1.22.98.2: #i49133# some re-factoring
2007/12/13 11:21:27 fs 1.22.98.1: #i49133# +getAssociatedModel / some minor refactoring, mostly related to the m_xCurrentFrame->m_aCurrentFrame change
2008/01/24 14:12:01 fs 1.13.82.2: #i49133# connect: use the document's interaction handler, if there is one
2007/12/19 13:26:25 fs 1.13.82.1: m_xDatabaseContext is not needed
2008/01/02 20:27:38 fs 1.1.2.7: #i49133# don't rely on frame notifications for activity: window events seem to be more reliable
2007/12/22 13:35:53 fs 1.1.2.6: #i49133# just learned that the ActiveFrame attribute of a frames collection is maintained by the framework itself, no need to update it manually
2007/12/20 10:19:28 fs 1.1.2.5: #i49133# never reset the CurrentComponent to NULL. Even upon deactivation, it stays untouched, until another component is activated and sets it to itself. / #i84767# set the parent frame's active frame
2007/12/19 15:04:22 fs 1.1.2.4: comment corrected
2007/12/19 11:29:40 fs 1.1.2.3: thread safety
2007/12/18 21:24:51 fs 1.1.2.2: #i49133# set the XController as CurrentComponent (i.e. AppBasic's ThisComponent) if it has no model
2007/12/13 11:20:32 fs 1.1.2.1: encapsultaing the frame which a controller is attached to
2008/02/06 21:44:22 fs 1.69.82.5: #i49133# don't support XScriptInvocationContext if our associated document does not support XEmbeddedScripts, or if we cannot unambiguously be associated with with a dooc
2008/01/24 10:08:19 fs 1.69.82.4: implDirectSQL was never used
2007/12/19 07:20:35 fs 1.69.82.3: #i10000#
2007/12/19 06:12:01 fs 1.69.82.2: #i49133# +m_xCurrentDatabaseDocument
2007/12/18 21:21:23 fs 1.69.82.1: #i49133# implement XScriptInvocationContext
2008/02/20 13:28:02 fs 1.38.98.3.2.1: some DBG_UNHANDLED_EXCEPTIONs
2008/02/06 08:30:58 fs 1.38.98.3: copying the fix for #i85879# into this CWS: cleanup the toolbar mess in the data source browser
2007/12/18 21:21:43 fs 1.38.98.2: #i49133# some re-factoring
2007/12/13 11:22:37 fs 1.38.98.1: #i49133# some refactoring, mostly related to the m_xCurrentFrame->m_aCurrentFrame change
