http://www.realsoftware.com/feedback/viewreport.php?reportid=oswhlxub
It would be hugely helpful if we could design RB programs that have the option to build into shared libraries instead of standalone applications. Windows applications built in Visual Basic can currently utilize this concept by building ActiveX DLL's with exposed methods and functions, and most compilers provide this - Xcode for example. Delivering updates to products written in RB would be much simpler if we could encapsulate certain code segments into shared libraries so that we don't have one big application but rather a group of smaller, interconnectable modules. Coupled with this, it would be a small extra step to be able to create RB plugins from RB code - since RB plugins - of course - are DLLs/dylibs themselves. This approach protects the code in the shared library (it doesn't get recomplied until you chose to recompile that specific component), and allows better organization for delivery and updating of the final product after it reaches a customer's computer. There are other reasons too: ( particularly applicable to "yours truly" ) Much multimedia software takes the form of DLLS and Dylibs. For example AudioUnits and VST audio effect and instrument plugins. Not to mention RB plugins themselves. It would arguably also make RB much more attractive to future professional developers, as it means a much bigger variety of applications could be written in RB. Since the kind of software written to be housed in dynamic libraries tends to be code that needs to be tuned for performance ( audio/DSP/graphics etc) this would also be an incentive for RS to keep tuning the compiler for performance. Sign on to the feature request here: http://www.realsoftware.com/feedback/viewreport.php?reportid=oswhlxub _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
