Hi Marcel, On Wed, Feb 9, 2022 at 1:09 PM Marcel Bootsma <[email protected]> wrote:
> Hello Pepijn, > I just started on Celix and have trouble working through the install/first > example help pages as you can see in my recent mail to this list. > So if you ask what is needed for a new release: rework the getting started > pages so they work properly. > Greetings, > Marcel Bootsma > As mentioned in the previous email, I am currently updating the documentation and indeed updating the starter pages (or integrating them in the general intro) is part of that. Although still work in progress, not yet finished and also still in flux you could have a look at the intro documentation I am working on: https://github.com/pnoltes/celix/tree/feature/update_documentation/documents/intro Maybe that helps and works better. Greetings, Pepijn > > > > On 2022/02/08 15:23:41 Pepijn Noltes wrote: > > Hi All, > > > > It has been a while since the last Celix release and I think it is time > to > > prepare for the next release. > > > > One of the recent changes is that Celix now also has C++ support. > > The C++ support is done by a header-only C++17 implementation that is > built > > on top of the Celix C framework and utils libraries. > > A benefit of a header-only C++ implementation is that the Celix > > framework and utils libraries can be kept pure C libraries and thus no > > unwanted C++ dependency is introduced for C only users. > > > > The reason why I did not propose a release earlier, also has to do with > C++ > > support and specifically which version of C++ (C++11, C++14, C++17 or > maybe > > even C++20) to support. > > Releasing a new Celix version earlier could have meant we were "stuck" > with > > C++11 or we needed to release a major (backwards incompatible) update. > > > > Another change is that celix now handles all service registration, > service > > un-registration, service tracker start and service tracker stop events > on a > > single Celix event thread. > > This was done to be able to prevent multithreading programming for users > in > > certain situations. Please note that this is a deviation from the OSGi > > spec. > > > > Additionally to new features in the framework and utils libraries, there > > are also other new features: > > - Celix::Promise library. This is an implementation and adaptation of > the > > OSGi Promises specification [1]. Note this lib is still experimental. > > - Celix::PushStreams library. This is an implementation and adaptation > of > > the OSGi Push Stream specification [2]. Note this lib is still > experimental. > > - Celix::ShellCxx bundle. A C++ implementation of the Celix::shell which > > also supports a C++ Shell Command interface. > > - C++ Remote Service Admin bundles. A set of bundles which is an > > implementing and adaptation of the OSGi Remote Service Admin > specification > > [3]. > > - Support for multiple cmake build types (Debug, RelWithDebInfo) > > > > [1] > https://docs.osgi.org/specification/osgi.cmpn/7.0.0/util.promise.html > > [2] > https://docs.osgi.org/specification/osgi.cmpn/7.0.0/util.pushstream.html > > [3] > > > https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.remoteserviceadmin.html > > > > Lastly, a lot of stability improvements were added and a lot of bugs were > > fixed. > > > > Before releasing I would like to update some of the documentation and I > am > > currently busy with preparing a pull request for that. > > Are there any other requests, remarks or things that need attention > > concerning a new Celix release? > > > > Greetings, > > Pepijn > > > > > > -------- Disclaimer -------- > This email and any files transmitted may contain proprietary and > confidential information of ICT Group or any of its subsidiaries ("ICT") > and is intended only for the (use of the) named recipient(s) above. If you > have received this message in error or are not the intended or named > recipient(s) of this message, please immediately notify the sender by > return and delete this email message from your computer. Any views or > opinions presented are solely those of its author and do not necessarily > represent those of ICT. You are hereby notified that unauthorized > disclosure, use, dissemination, forwarding, printing or copying of this > e-mail and its attachments either whole or partial of its contents is > strictly prohibited. ICT cannot guarantee that email communications are > secured and error-free and does not accept any liability for damages > resulting from the use of email. The general terms and conditions of > purchase respectively sale and delivery of ICT are applicable to all > transactions and undertakings resulting therefrom. > >
