Hi Alexandro, > DBA applications are not all that requried for many organizations. > However they do have legacy applications that they need to convert > from access. > > First issue is the mapping of converting the forms that access have on > these files and how to re-generate them on Base. This might be the > primary issue to fix in Base. > > How can I get my access files and open them on OOo and have everything > that I had before with their forms and reports. I think this should be > priority no. 1. > > I would like to know what will it require both technically and > user-experience so we can get an idea of how many resources will it > take to take it there.
For the technical part, I can say that in the other application's teams, there are people dedicated to developing the import/export filters and reverse-engineering the file formats; plus the "normal" application developers who implement (with huge efforts, often) the changes in the application itself, which is needed to mirror MSO functionality. So, my guess would be that for importing, say, forms and reports from MSO, we would need man years, say 5. And as always, the million-monkey-approach won't work here. That is, the work probably doesn't scale too good, so putting more and more people on it will quickly become useless. > Once that, we really need more open dialog with > developers of DBA and what is their agenda and oportunity to start > hacking on these branches. > > If I had 5 developers to work full time on DBA: > - who should I contact? > - how can I start hacking? > - who should I send my commits, when will I see the patches work there? > > Obviously this information is out there for the whole OOo but there is > slim if no information regarding Base, and here is where we need to > improve documenting the Base project. Hmm, I think I don't understand the problem here. 1. Contact the project's mailing list, or the project owner. 2. Just do it. If you need help finding your way in the code, ask in [EMAIL PROTECTED] 3. Per IssueZilla, if they're larger, per CWS where you commit your changes to a dedicated branch. All of this isn't really different from the other applications, and I don't see a process documentation anywhere saying "This applies to all projects, but not DBA.". A recent example that this works pretty well is the SQL syntax highlighting feature, developed by Max Odendahl. Perhaps I misunderstood your request, in this case please elaborate which kind of documentation you miss. Thanks & Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
