View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003230||Slicer4||Module Welcome||public||2013-07-16 15:29||2018-05-30 20:22|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||backlog||Fixed in Version|
|Summary||0003230: Welcome: Refactor the Welcome module to be only html.|
Currently "ctkCollapsibleButton" and "ctkFittedTextBrowser" are used to display the different section.
Instead the content of the module should be full html. It would make the maintenance easier and would open to the possibility of also serving the same pages online.
Web widget is quite unstable in Qt5. Maybe use rich text editor widget instead.
Retarget stale issues to backlog.
Were you thinking about a particular problem ?
@sjh267 should work on the remaining of the Extension Manager issue, this should help identify and address remaining issues.
Otherwise, QML could be used.
Overall, I feel that web browsers have become monsters - complete standalone operating systems. They are just too big and complex to be embedded them into applications. Google or Microsoft should worry about building and deploying them (they can do a much better job in optimizing hardware acceleration, deliver security updates, etc.). We could just show the default web browser in a separate window for extension manager, on-line help, data store, etc. I don't think it is necessary to use a webpage to render scene views, plotting, or welcome module.
I appreciate lassoan's point of view on this - QtWebEngine has been much more trouble than expected. But I do think there's a lot of value both current and future in being able to seamlessly use web technologies in slicer even if there are currently some issues. The main reason to bundle QtWebEngine with Slicer is to have a consistent cross-platform behavior which is never going to happen if we rely on vendor provided browsers.
I like seamless web technology integration, but there are already many seams and the as web browser performance, tightness of security, new features are developed at extreme speed, I don't see a chance that a niche use case such as embedded web browser can be maintained for too long. My impression is that applications are forced into run in a web browser and not vice versa.
Of course we don't know what will happen, but minimizing our dependency on having an embedded browser is a safe bet. If we need web integration maybe we should follow the mainstream and look into how Slicer could run in/from a web browser.
|2013-07-16 15:29||jcfr||New Issue|
|2013-07-16 15:30||jcfr||Summary||Refactor the module to be only html. => Refactor the Welcome module to be only html.|
|2013-07-16 15:30||jcfr||Target Version||=> Slicer 4.3.0|
|2013-07-16 15:30||jcfr||Status||new => assigned|
|2013-07-16 15:30||jcfr||Assigned To||=> yuzheng|
|2013-07-16 15:31||jcfr||Relationship added||child of 0003229|
|2013-07-16 15:31||jcfr||Relationship added||related to 0001839|
|2013-07-16 15:32||jcfr||Relationship added||related to 0001293|
|2013-08-07 07:42||yuzheng||Target Version||Slicer 4.3.0 => Slicer 4.4.0|
|2013-09-23 06:45||jcfr||Relationship replaced||parent of 0003229|
|2014-05-13 15:40||jcfr||Assigned To||yuzheng => jcfr|
|2014-05-13 15:41||jcfr||Tag Attached: help-wanted|
|2014-09-10 11:14||jcfr||Summary||Refactor the Welcome module to be only html. => Welcome: Refactor the Welcome module to be only html.|
|2014-09-10 11:14||jcfr||Target Version||Slicer 4.4.0 => Slicer 4.5.0-1|
|2015-11-02 05:03||jcfr||Status||assigned => acknowledged|
|2015-11-02 05:03||jcfr||Target Version||Slicer 4.5.0-1 =>|
|2017-10-03 10:38||pieper||Assigned To||jcfr => pieper|
|2018-05-30 01:03||lassoan||Note Added: 0015822|
|2018-05-30 01:03||lassoan||Target Version||=> backlog|
|2018-05-30 01:03||lassoan||Note Added: 0015823|
|2018-05-30 13:39||jcfr||Note Added: 0015854|
|2018-05-30 16:04||lassoan||Note Added: 0015857|
|2018-05-30 19:54||pieper||Note Added: 0015858|
|2018-05-30 20:22||lassoan||Note Added: 0015859|