[Modularization] About adding sub-modules?
Hi, some libraries can be seen as a set of sub-modules, as it is Math, Numeric or Thread. Could we add these sub-modules ? * Chrono/Stopwatches * Thread/Executors * Detail/WinApi Best, Vicente
Andrey Semashev wrote:
On Wed, Jun 4, 2014 at 11:03 AM, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote: ...
Could we add these sub-modules ?
* Detail/WinApi
Yes, this was discussed before. +1.
I'm not very fond of sub-sub-modules. Why not just winapi? This could be very useful for those odd people outside Boost who don't really like including <windows.h>.
On Wednesday 04 June 2014 20:59:34 Peter Dimov wrote:
Andrey Semashev wrote:
On Wed, Jun 4, 2014 at 11:03 AM, Vicente J. Botet Escriba
<vicente.botet@wanadoo.fr> wrote: ...
Could we add these sub-modules ?
* Detail/WinApi
Yes, this was discussed before. +1.
I'm not very fond of sub-sub-modules. Why not just winapi? This could be very useful for those odd people outside Boost who don't really like including <windows.h>.
I'm ok with winapi name (actually, it sounds better). But I don't want to make it a public library. People might get the idea that we're trying to cover WinAPI in our headers while they only exist to cover Boost needs. Really, this is just an implementation detail. A pretty ugly one, but useful to multiple libraries.
Andrey Semashev wrote: On Wednesday 04 June 2014 20:59:34 Peter Dimov wrote:
I'm not very fond of sub-sub-modules. Why not just winapi? This could be very useful for those odd people outside Boost who don't really like including <windows.h>.
I'm ok with winapi name (actually, it sounds better).
But I don't want to make it a public library.
OK. So we (read I) make a sub-module winapi, in libs/winapi, with you and Vicente having write access, but don't add it to libraries.htm. Right?
On Wednesday 04 June 2014 21:18:50 Peter Dimov wrote:
Andrey Semashev wrote:
On Wednesday 04 June 2014 20:59:34 Peter Dimov wrote:
I'm not very fond of sub-sub-modules. Why not just winapi? This could be very useful for those odd people outside Boost who don't really like including <windows.h>.
I'm ok with winapi name (actually, it sounds better).
But I don't want to make it a public library.
OK. So we (read I) make a sub-module winapi, in libs/winapi, with you and Vicente having write access, but don't add it to libraries.htm. Right?
That would be ok with me.
On 4 June 2014 19:18, Peter Dimov <lists@pdimov.com> wrote:
Andrey Semashev wrote:
On Wednesday 04 June 2014 20:59:34 Peter Dimov wrote:
I'm not very fond of sub-sub-modules. Why not just winapi? This could be
very useful for those odd people outside Boost who don't really like > including <windows.h>.
I'm ok with winapi name (actually, it sounds better).
But I don't want to make it a public library.
OK. So we (read I) make a sub-module winapi, in libs/winapi, with you and Vicente having write access, but don't add it to libraries.htm. Right?
It could possibly have a 'meta/libraries.json' file, with an extra attribute, say "public": false. Then I could hide it on the website, but add a link to show private libraries.
On Wednesday 04 June 2014 19:26:01 Daniel James wrote:
On 4 June 2014 19:18, Peter Dimov <lists@pdimov.com> wrote:
Andrey Semashev wrote:
On Wednesday 04 June 2014 20:59:34 Peter Dimov wrote:
I'm not very fond of sub-sub-modules. Why not just winapi? This could be
very useful for those odd people outside Boost who don't really like
including <windows.h>.
I'm ok with winapi name (actually, it sounds better).
But I don't want to make it a public library.
OK. So we (read I) make a sub-module winapi, in libs/winapi, with you and Vicente having write access, but don't add it to libraries.htm. Right?
It could possibly have a 'meta/libraries.json' file, with an extra attribute, say "public": false. Then I could hide it on the website, but add a link to show private libraries.
That would be even better.
On 4 June 2014 19:28, Andrey Semashev <andrey.semashev@gmail.com> wrote:
On Wednesday 04 June 2014 19:26:01 Daniel James wrote:
It could possibly have a 'meta/libraries.json' file, with an extra attribute, say "public": false. Then I could hide it on the website, but add a link to show private libraries.
That would be even better.
On second thoughts, probably should try to avoid having true as the default value, so it would be better to use "private": true. Another possibility is to add a new private category. Btw. I just started documenting the file format. http://www.boost.org/development/library_metadata.html It's not set in stone, so suggestions are welcome. I'll put out a full request for feedback when it's a bit more complete.
Le 05/06/14 01:06, Daniel James a écrit :
On Wednesday 04 June 2014 19:26:01 Daniel James wrote:
It could possibly have a 'meta/libraries.json' file, with an extra attribute, say "public": false. Then I could hide it on the website, but add a link to show private libraries. That would be even better. On second thoughts, probably should try to avoid having true as the default value, so it would be better to use "private": true. Another
On 4 June 2014 19:28, Andrey Semashev <andrey.semashev@gmail.com> wrote: possibility is to add a new private category.
Btw. I just started documenting the file format.
http://www.boost.org/development/library_metadata.html
It's not set in stone, so suggestions are welcome. I'll put out a full request for feedback when it's a bit more complete.
Hi, could I start adding this |libraries.json file to my libraries myself? Which file must be changed to add a new category? Best, Vicente |
On 9 June 2014 09:30, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote:
could I start adding this |libraries.json file to my libraries myself?
Yes, although there's a php script to generate them for existing libraries. I was going to wait until after the release before adding them to more modules, but could do so now if you want. I was mainly waiting in case any more changes were needed, but I think it's pretty stable now.
Which file must be changed to add a new category?
It's currently at: https://github.com/boostorg/website/blob/master/doc/libraries.xml
Le 09/06/14 12:04, Daniel James a écrit :
could I start adding this |libraries.json file to my libraries myself? Yes, although there's a php script to generate them for existing
On 9 June 2014 09:30, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote: libraries. I was going to wait until after the release before adding them to more modules, but could do so now if you want. I was mainly waiting in case any more changes were needed, but I think it's pretty stable now.
Hi, I see that after my commit to create a module there is a chrono/example separated regression test that I was not expecting. I have not yet modified the status.jamfile to add the chrono/stopwatches module. What i did wrong? Vicente
On 9 June 2014 23:36, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote:
Le 09/06/14 12:04, Daniel James a écrit :
On 9 June 2014 09:30, Vicente J. Botet Escriba <vicente.botet@wanadoo.fr> wrote:
could I start adding this |libraries.json file to my libraries myself?
Yes, although there's a php script to generate them for existing libraries. I was going to wait until after the release before adding them to more modules, but could do so now if you want. I was mainly waiting in case any more changes were needed, but I think it's pretty stable now.
Hi,
I see that after my commit to create a module there is a chrono/example separated regression test that I was not expecting.
I have not yet modified the status.jamfile to add the chrono/stopwatches module.
What i did wrong?
I think 'sublibs' causes it to think every immediate subdirectory is a sub-library.
participants (4)
-
Andrey Semashev -
Daniel James -
Peter Dimov -
Vicente J. Botet Escriba