On Sun, Mar 11, 2012 at 9:33 AM, Travis <[email protected]> wrote: > I remember not to long ago there was a Windows > installer for OpenBD, but as of version 2.0 that is no longer > available. Well this be coming back?
It's still available and will be updated soon: http://openbd.viviotech.net We just need to link to that from the downloads page, and I'm going to be working with Jordan Michaels (once I get up to speed on the process) to take some of the burden off him to keep the installers up to date. > Maybe a YouTube video of the entire installation process > would be beneficial (for both development and production purposes)? > Great idea--I was just thinking about that this morning so we'll coordinate and get some of those going. > > 2.) What is the goal of OpenBD long term (feature wise)? To match what > Adobe and Railo are doing? Short answer is we'll always be compatible on core features but our mission is not necessarily to always be in lock-step with what Adobe is doing. They have a vastly longer release cycle than we do so we definitely won't wait to innovate. We want to get new features in your hands as quickly as possible. > I was wondering if OpenBD > will continue to add unique features to its platform. Absolutely! This happens on a weekly basis around here. ;-) > One thing that I > really don't understand with Adobe ColdFusion is stuff like Office > integration; they have zero support for doc/docx manipulation, and > their spreadsheet integration is for the old binary XLS format. > That's likely due to the fact that they have to lock in versions of the open source libraries they use to provide this functionality (Apache POI in this case) and stick with those for the life of the release (which is about 5 years or so since they tend to support the current release plus one version back) since it's a known entity. By contrast we have the freedom to upgrade things like that quite rapidly since we're on a much more frequent release cycle. It's a bit of a mind shift to start thinking of releases as a bit more ephemeral but it's a fantastic world in which to live. Since I deploy the vast majority of my apps as self-contained WAR files all I have to do is grab the latest version (even nightly releases!) of OpenBD to start development on a project, and then I can either stick with that or upgrade during development. Once an app goes into production it tends to stay on the version of OpenBD upon which it was built, and then I'll upgrade OpenBD when I need to make modifications to the app. As I said this is a different way of thinking (OpenBD as part and parcel of your application) than the monolithic server installation, though that has its use as well, and it gains you a lot of flexibility since you can always be taking advantage of the latest stuff on a given project without impacting any other apps that may be running on a server. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en
