A little more news. A possible second candidate - a Legal Case Management system. This is also a pure Base implementation. Currently the functionality is in place, but for performance reasons the database is being migrated from an embedded Base file to a stand alone HSQLdb server. This application is a good bit more complex then the Arts database.
I can not supply the actual current database for our use, I can supply a very early prototype of the tables and basic forms. It is possible that the finished database can be moved to the Public Domain - but don't count on it. As soon as the migration is finished the application itself will be available to the public, for a small fee. ( I believe that is the actual owners final decision ) But again - the early prototype is already in the public domain, so that is not an issue if anyone wanted to take that and run with it. On 9/29/07, Andrew Jensen <[EMAIL PROTECTED]> wrote: > OK - going to follow up on my own email - "Do I have no sense of shame? " > > I think the first application is starring us right in the face - it is > the reference I made in the other thread http://www.e-easel.org/ > > Julianna is a real OO.org advocate. The database she is distributing > there is one built originally to run her small business. Which it has > been for over a year now. > > The application is a pure OOo Base implementation and is in the public > domain, she wold be keen on our putting it to whatever use we would > like. As she was when I first proposed this a year ago on the wiki. > > So - it appears to me that there are a whole bunch of win-win > possibilities here. > > First - If we used the current v1.1 of the database as a starting > point and then added in the following: > > Use of SRB for new reports > > Change that installation process from manual to either: > A ) An install routine supplied in a script > B) Create an oxt wrapper to distribute the database application - This > allows us to install the libraries, menus and toolbars, etc and create > / register the actual database. ( I have used this B approach a few > times now, and it works well - especially for site wide installations > which is the really nice part if the Base forms, scripts are hitting a > server database ) This was an option not available when the > application was first written. > > Add the 'finishing' to the UI and work flow that our experience makes > possible. > A ) Maybe a menu system > B) Some form navigation functions > C) ....? > > She gets a nice update the application. > > We get the chance to construct a document on the wiki that goes over > how the application is designed, how it hangs together etc. > > She gets a little more visibility for the Artists support organization > she is trying to build. > > We get to point to the source forge repository for letting OOo new > users wanting a copy. > > We also get that first business example - without having to start from > ground zero. > > Anyone interested? > > > > > On 9/29/07, Andrew Jensen <[EMAIL PROTECTED]> wrote: > > Hi guys, > > > > http://wiki.services.openoffice.org/wiki/Category:Base_Example > > > > It is a wiki - if you want to help get one of these done - log in and > > update the page... > > > > If you see that there is not enough of a plan - create one > > Step one we need to do this > > Step two do this > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
