# HG changeset patch # User Sebastien Jodogne # Date 1466581997 -7200 # Node ID 98c0c61e793159795455075c175e0ff72a34de6f # Parent c98317fedf879e32ff46b00b70da6cc16318af03 contributing diff -r c98317fedf87 -r 98c0c61e7931 Sphinx/source/contributing.rst --- a/Sphinx/source/contributing.rst Tue Jun 21 11:21:11 2016 +0200 +++ b/Sphinx/source/contributing.rst Wed Jun 22 09:53:17 2016 +0200 @@ -24,12 +24,19 @@ Matlab/Octave, Python, Horos, dicompyler...). Check the `already supported frameworks `_. * Develop `C/C++ plugins - `_, - some ideas of which can be found in the `official roadmap - `_. + `_. + Here are some ideas of plugins: + * Check the right-hand column of the `official roadmap `__. + * Create a :ref:`more advanced Web interface ` than the built-in Orthanc Explorer. + * Extend the :ref:`sample modality worklist plugin ` so that it manages the worklists + (i.e. add/remove items) with a REST API or HL7 messages, instead of reading them from + some folder on the filesystem. -The **recommended way of contributing to the source code of Orthanc is +* Have a look at the `Orthanc Wishlist board `__, + where users can submit their ideas for the future features of Orthanc. + +Always remember that he **recommended way of contributing to the source code of Orthanc is by creating C/C++ plugins**. If the current plugin SDK is insufficient for you to develop some feature as a plugin, do not hesitate to request an extension to the Orthanc SDK on the `mailing list diff -r c98317fedf87 -r 98c0c61e7931 Sphinx/source/faq/improving-interface.rst --- a/Sphinx/source/faq/improving-interface.rst Tue Jun 21 11:21:11 2016 +0200 +++ b/Sphinx/source/faq/improving-interface.rst Wed Jun 22 09:53:17 2016 +0200 @@ -1,3 +1,5 @@ +.. _improving-interface: + Orthanc Explorer is not user-friendly enough for my use ======================================================= @@ -24,7 +26,8 @@ staff...) **might expect an user interface that is more user-friendly than Orthanc Explorer**, and/or that integrates more features (such as sorting resources, access control lists, tagging images, beautiful -layout...). If you need such a more advanced `user experience +layout, tunable anonymization, modification of instances...). If you +need such a more advanced `user experience `__ so that Orthanc better fits your clinical workflow, you will have to develop a separate, custom Web interface on the top of the :ref:`rest`, maybe as diff -r c98317fedf87 -r 98c0c61e7931 Sphinx/source/faq/worklist.rst --- a/Sphinx/source/faq/worklist.rst Tue Jun 21 11:21:11 2016 +0200 +++ b/Sphinx/source/faq/worklist.rst Wed Jun 22 09:53:17 2016 +0200 @@ -1,3 +1,5 @@ +.. _worklist: + Does Orthanc support worklists? =============================== @@ -142,4 +144,4 @@ - of course, you'll automate this worklist generation workflow with some scripting language. - \ No newline at end of file +