Difference between revisions of "Slicer4:DownloadPackage"
From Slicer Wiki
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Slicer4:Developers#Projects|Back to Slicer4 Projects]] | [[Slicer4:Developers#Projects|Back to Slicer4 Projects]] | ||
=Introduction= | =Introduction= | ||
| − | This page | + | This page contains a wishlist, plans, and assignments for the appearance and user experience of the Slicer 4 downloadable executables |
=Feature requests= | =Feature requests= | ||
| − | *Asks if it should be made the default application for .mrml and .nrrd files | + | [[image:May 2011-July2011DownloadDistribution.png|right|thumb|400px|Dowloads as a function of OS for Slicer 3.6.3]] |
| − | *Reduce the size of the download package | + | ==User Side== |
| + | *Asks if it should be made the default application for .mrml and .nrrd files (ron says yes for mrml). | ||
| + | *Reduce the size of the download package | ||
*64bit versions for all supported platforms (or as close as is reasonable) | *64bit versions for all supported platforms (or as close as is reasonable) | ||
*check for old version of Slicer. If present ask if to adopt the preferences and customizations | *check for old version of Slicer. If present ask if to adopt the preferences and customizations | ||
*offer a registration: accept, later or opt out as options, sign up for mailing list: user list checked by default, developer unchecked by default | *offer a registration: accept, later or opt out as options, sign up for mailing list: user list checked by default, developer unchecked by default | ||
| + | |||
| + | ==Server side== | ||
| + | *speed up the download statistics display on the download page | ||
| + | *add monitoring of svn checkouts as a separately tracked entity (users versus developers) | ||
| + | *data base to manage registrations | ||
| + | *registration form schema | ||
| + | *extensions should be available | ||
| + | *SVN number should be the same for all the nightlies as the one showing on the dashboard ("XX files changed by 3 authors as of Wednesday, May 25 2011 23:00:00 EDT") | ||
=Architecture specific= | =Architecture specific= | ||
==Windows== | ==Windows== | ||
| − | *Window uninstall should allow to clean up everything, including the registry settings | + | *Window uninstall should allow to clean up everything, <del>including the registry settings</del>. Note: Ini files are used on windows to store the settings. |
| − | *when | + | *when Slicer is running, the Slicer icon in the Taskbar has a border around the icon. This looks ugly. |
==Apple Mac OS X== | ==Apple Mac OS X== | ||
*Apple install should behave like other apple applications | *Apple install should behave like other apple applications | ||
| − | ** See [http://www.ClamXav.com ClamXav] for an example | + | ** See [http://www.ClamXav.com ClamXav] for an example. |
*When Slicer is running, then the icon in the dock should be the slicer icon. Right now its not. | *When Slicer is running, then the icon in the dock should be the slicer icon. Right now its not. | ||
*should we be present on the Apple mac appstore? | *should we be present on the Apple mac appstore? | ||
| Line 23: | Line 33: | ||
==Linux== | ==Linux== | ||
*The Linux version should make stable releases available through standard linux distribution mechanisms. | *The Linux version should make stable releases available through standard linux distribution mechanisms. | ||
| + | |||
| + | =Platform specific installer issues 2011= | ||
| + | |||
| + | Slicer has three types of storage needs: | ||
| + | *Parameters for the program (such as what layout to start with, how much memory the graphics board has...) | ||
| + | *Plug-ins | ||
| + | *temporary and permanent data (local data base for the dicom widget, results of processing) | ||
| + | |||
| + | *We should review where these things are stored in each platform and whether they follow best practices for that platform. | ||
| + | |||
| + | *We should review, what customizations we should offer at install time. | ||
| + | *We should offer a registration option at install time (register now, later, never). | ||
Latest revision as of 19:19, 27 July 2011
Home < Slicer4:DownloadPackageBack to Slicer4 Projects
Contents
Introduction
This page contains a wishlist, plans, and assignments for the appearance and user experience of the Slicer 4 downloadable executables
Feature requests
User Side
- Asks if it should be made the default application for .mrml and .nrrd files (ron says yes for mrml).
- Reduce the size of the download package
- 64bit versions for all supported platforms (or as close as is reasonable)
- check for old version of Slicer. If present ask if to adopt the preferences and customizations
- offer a registration: accept, later or opt out as options, sign up for mailing list: user list checked by default, developer unchecked by default
Server side
- speed up the download statistics display on the download page
- add monitoring of svn checkouts as a separately tracked entity (users versus developers)
- data base to manage registrations
- registration form schema
- extensions should be available
- SVN number should be the same for all the nightlies as the one showing on the dashboard ("XX files changed by 3 authors as of Wednesday, May 25 2011 23:00:00 EDT")
Architecture specific
Windows
- Window uninstall should allow to clean up everything,
including the registry settings. Note: Ini files are used on windows to store the settings. - when Slicer is running, the Slicer icon in the Taskbar has a border around the icon. This looks ugly.
Apple Mac OS X
- Apple install should behave like other apple applications
- See ClamXav for an example.
- When Slicer is running, then the icon in the dock should be the slicer icon. Right now its not.
- should we be present on the Apple mac appstore?
Linux
- The Linux version should make stable releases available through standard linux distribution mechanisms.
Platform specific installer issues 2011
Slicer has three types of storage needs:
- Parameters for the program (such as what layout to start with, how much memory the graphics board has...)
- Plug-ins
- temporary and permanent data (local data base for the dicom widget, results of processing)
- We should review where these things are stored in each platform and whether they follow best practices for that platform.
- We should review, what customizations we should offer at install time.
- We should offer a registration option at install time (register now, later, never).
