Hi Folks, It seems that Boost includes (or may include) a mechanism to allow compiled plugins see for example http://boost-extension.redshoelace.com/docs/boost/extension/boost_extension/... - is this in cctbx? is anyone interested in it being available? It seems useful from where I am sat. Thanks, Graeme -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
Hi Graeme,
It seems that Boost includes (or may include) a mechanism to allow compiled plugins see for example
http://boost-extension.redshoelace.com/docs/boost/extension/boost_extension/...
- is this in cctbx? is anyone interested in it being available? It seems useful from where I am sat.
could you give an example of use you foresee in the context of the cctbx? As I am afraid this is one of those advanced software engineering concepts that I can't comprehend even what problem it tries to address! Best wishes, Luc
Hi Luc, The case I foresee is wanting people to add compiled code for reading new image formats in iotbx - it would be great if they could do this at run-time, conforming to some abstract interface. Best wishes, Graeme On 16 Aug 2012, at 16:14, Luc Bourhis wrote:
Hi Graeme,
It seems that Boost includes (or may include) a mechanism to allow compiled plugins see for example
http://boost-extension.redshoelace.com/docs/boost/extension/boost_extension/...
- is this in cctbx? is anyone interested in it being available? It seems useful from where I am sat.
could you give an example of use you foresee in the context of the cctbx? As I am afraid this is one of those advanced software engineering concepts that I can't comprehend even what problem it tries to address!
Best wishes,
Luc
_______________________________________________ cctbxbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/cctbxbb
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
Hi Graeme,
The case I foresee is wanting people to add compiled code for reading new image formats in iotbx - it would be great if they could do this at run-time, conforming to some abstract interface.
All the user-side code in iotbx being in Python, it should be easy to do what you propose already. Best wishes, Luc
Hi Luc, What about if it needed compiled code? For example a new compression scheme? Then they would need to make some quite substantial changes I would think. Also if we (for performance reasons) were working in C++ with the image handling adding the Python code like that would be less helpful. Just a thought - clearly this is not a problem which has occurred yet, but I can see it happening sometime reasonably soon. Best wishes, Graeme On 18 Aug 2012, at 17:23, Luc Bourhis wrote: Hi Graeme, The case I foresee is wanting people to add compiled code for reading new image formats in iotbx - it would be great if they could do this at run-time, conforming to some abstract interface. All the user-side code in iotbx being in Python, it should be easy to do what you propose already. Best wishes, Luc _______________________________________________ cctbxbb mailing list [email protected]mailto:[email protected] http://phenix-online.org/mailman/listinfo/cctbxbb -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
Hi Graeme,
What about if it needed compiled code? For example a new compression scheme? Then they would need to make some quite substantial changes I would think.
I would naively do it as we have always done it: create a new Boost Python extension implementing the new compression scheme, then tweak the Python code to decide when to use that new scheme and when to use the old one. The Python tweak will typically be insignificant an amount of work compared to what will be sunk into implementing the compression scheme in C++. The latter won't be reduced by the technology you advocate, will it?
Also if we (for performance reasons) were working in C++ with the image handling adding the Python code like that would be less helpful.
Pure C++ applications should have a very hard time to use the iotbx anyway as many of the key objects are Python-only (xray.structure, miller.array, etc). Best wishes, Luc
participants (2)
-
Graeme.Winter＠diamond.ac.uk -
Luc Bourhis