Hi Dib, Thanks for your comments! I am very happy that you think that this library can be useful! About your comments:
- let the user set callbacks for more signals (eg. SIGHUP is often used). Maybe you can use asio's signals here for better portability?
I agree, and I will take a look in how to extend handlers types of application class! All other mentioned features, I think that are very important, but, I think that can be done, in future releases! The problem is that now I don't have time to do this now.
I would probably have started something like this in the near future, but not with "boost-compliant quality", so I'm quite happy about your effort :)
Well, I will ask to you! Do you have any free time to contribute with some of those mentioned features? :)
Do you have a development-code repository somewhere or just the archives you linked to?
I don't have any repository, because, this lib is only one idea that I sent to boost group to see interest! And for my surprise, several people are interested! :)
What is your roadmap for further development and/or acceptance into boost?
Well, I have no idea! Depends on what the community request! My development time is limited, so at some point I have to close the scope and try to submit! The documentation need a lot of work too! I am not a Native English Speaker! I do not know exactly, I never submitted anything to boost before. I do not know how it will be! Do you have some experience in this submission process? Thanks a lot -----Mensagem original----- De: Boost [mailto:boost-bounces@lists.boost.org] Em nome de dib Enviada em: segunda-feira, 23 de setembro de 2013 05:04 Para: boost-devel-archive@googlegroups.com Cc: boost@lists.boost.org Assunto: Re: [boost] Is there any interest in a library for application : Boost.Application, new version: Boost.Application_beta_3a_release_2 Hi, I think this is very useful and am looking forward to seeing this as an official boost lib. There are a couple of features that come to mind when I think about using this, which are: - let the user set callbacks for more signals (eg. SIGHUP is often used). Maybe you can use asio's signals here for better portability? - integrate boost.programoptions a little more. I think about reading a config file and maintaining some "config-state" inside application.ctrl? Then, if I change some config values they get written back to the config file.. - for the above feature it might be useful to introduce an "initalisation-handler", so the user can separate the code for eg. setting up program options and the actual program logic - option to turn on some "general exception handling" - _optional_ incorporation of boost.log - offering a threadpool or sth (or even asio?) I think this was already mentioned I would probably have started something like this in the near future, but not with "boost-compliant quality", so I'm quite happy about your effort :) Do you have a development-code repository somewhere or just the archives you linked to? What is your roadmap for further development and/or acceptance into boost? -- regards dib _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost