Difference between revisions of "Developer Meetings/20150407"

From Slicer Wiki
Jump to: navigation, search
(Created page with '== Updates == == To discuss == * Create a new release: 4.4.1 or 4.5 ? * Failing test: [http://slicer.cdash.org/testDetails.php?test=6177238&build=413981 EMSegCL_Task_HumanEye_B…')
 
m
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
* Create a new release: 4.4.1 or 4.5 ?
 
* Create a new release: 4.4.1 or 4.5 ?
 
* Failing test: [http://slicer.cdash.org/testDetails.php?test=6177238&build=413981 EMSegCL_Task_HumanEye_BRAINS_small]
 
* Failing test: [http://slicer.cdash.org/testDetails.php?test=6177238&build=413981 EMSegCL_Task_HumanEye_BRAINS_small]
 +
* Issue witg DataProbeLib
  
 
== Todo ==
 
== Todo ==
  
 
== Conclusions ==
 
== Conclusions ==
 +
* Python module infrastructure improvement
 +
** Since commit [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=24155 r24155], scripted module are imported as python module.
 +
** The next change will be to support loading of slicer scripted module as regular python module (a folder with __init__.py)
 +
** A landmark file could be added to scripted module folder (slicer.json or slicer-module.json)
 +
** This landmark file could then be used to speedup the startup time by loading only the core scripted module.
 +
 +
* CLI and loadable module infrastructure improvement
 +
** Similarly to scripted module, the Slicer module loader could look for a landmark file
 +
 +
* Python interactor improvement
 +
** Would be nice to have history, support for CTRL-A and CTRL-R
 +
** We discussed the integration of readline or libedit but that could be a lot of work for a small gain
 +
** Instead trying to integrate IPython would provide us with a lot.
 +
*** Some work to integrate ctkPythonConsole and IPython has been started last year (See [https://github.com/commontk/QEmbedIPython/blob/master/CMakeLists.txt QEmbedIPython])
 +
** Could also look at javascript implementation of console (Steve: Could you edit and add reference ?)

Latest revision as of 19:18, 7 April 2015

Home < Developer Meetings < 20150407

Updates

To discuss

Todo

Conclusions

  • Python module infrastructure improvement
    • Since commit r24155, scripted module are imported as python module.
    • The next change will be to support loading of slicer scripted module as regular python module (a folder with __init__.py)
    • A landmark file could be added to scripted module folder (slicer.json or slicer-module.json)
    • This landmark file could then be used to speedup the startup time by loading only the core scripted module.
  • CLI and loadable module infrastructure improvement
    • Similarly to scripted module, the Slicer module loader could look for a landmark file
  • Python interactor improvement
    • Would be nice to have history, support for CTRL-A and CTRL-R
    • We discussed the integration of readline or libedit but that could be a lot of work for a small gain
    • Instead trying to integrate IPython would provide us with a lot.
      • Some work to integrate ctkPythonConsole and IPython has been started last year (See QEmbedIPython)
    • Could also look at javascript implementation of console (Steve: Could you edit and add reference ?)