Dear ebase Community Members,
We're working hard on getting the port of ebasePro 2.20 to the newer FileMaker file format done. While we're adhering to the scope of our project -- to convert the features of ebase 2.20 to FileMaker's new file format (.fp7), and not spend time coming up with new features--FileMaker's newer format has prompted us to make a few key decisions. Over the holidays, we delayed release of an alpha version to testers so we could establish how the new version of ebase, and versions to come, will interact with new aspects of FileMaker. New FileMaker features have already allowed us to condense ebase's 40+ files into one file, making for much easier installation! Right now, we're integrating aspects of FileMaker's new format to support
• a two file installation, which will permit easy drag-and-drop upgrade as new versions come out
• easier creation and installation of add-on modules that extend ebase's functionality
• possibly sharing ebase among users in a small office without setting up a database server (like so many did with ebase v.1)
• possibly sharing ebase among remote users over the Internet
We'll update the ebase community news again with updates and as this version goes into alpha testing, and again for beta testing. If you're interested in joining either testing team, or in being an early adoption site for the new ebase after beta testing is finished, please contact Allen Poole at allen [at] cdsnw.com. In the mean time, as always, questions are welcome in the forums.
We've recently updated the ebase community web site to Drupal 6 and are researching ways to possibly implement a hybrid of the listservs and forums to facilitate better community support.
We will post updates as we have it, but for now, please consider a donation to really help our efforts and build the ebase community. We are excited by the commitment and direction to update ebase... but we need your support.
All the Hope for a Wonderful New Year, yours in ebase - the ebase Board of Directors and the ebase TAC (Technical Advisory Committee).