Add `VDBStartupA` into `jv:vdb/application`
This class is just a placeholder, all logic is in its superclass,
`VDBStatup`. The reason for this is the way the initial package
path is computed (see `AbstractOpratingSystem >> defaultPackagePath`)
The code there assumes that startup class is from the same package
as the application itself.
This way, we have a startup class in the application package but still
have `VDBStartup` available when only `jv:vdb` is loaded (like when
developing and.or using VDB from Smalltalk/X IDE.
"/ VDB init script
"/ Current VDB instance (instance of VDBDebuggerApplication) can be accessed
"/ in via variable `vdb`
"/ Current GDB instance (instance of GDBDebugger) can be accessed via
"/ `vdb debugger`.
"/ Load plugins.
"/
"/ Smalltalk loadPackage: 'jv:vdb/plugins/bee'
"/ Set console prompt
"/
"/ vdb debugger send: 'set prompt (vdb) '.
vdb debugger send: 'set prompt (vdb) '.
"/ Set default text font for all text and list views
"/
"/ VDBAbstractApplication defaultTextFont: (FontDescription family:#'DejaVu Sans Mono' face:#normal size:12).
"/ VDBAbstractApplication defaultTextFont: (CodeView defaultFont asSize: 16).
"/ Choose debugger layout. For list of layouts, see VDBDebuggerApplicaton class,
"/ protocol 'interface specs - layouts'. Default is #layoutEclipseSpec.
"/
"/ vdb layout: #layoutEclipseSpec.
"/ vdb layout: #layoutIDAProSpec.
"/ vdb layout: #layoutSingleSpec.
"/ Enable pretty printers and frame filters in user interface.
"/ Very likely you want this, if you want to turn the off
"/ (not recommended), comment out following:
vdb debugger enablePrettyPrinting.
vdb debugger enableFrameFilters.