search

jecisc / Bazard

0 stars 0 forks source link

We should have a deployment method. #158

Closed jecisc closed 5 years ago

jecisc commented 5 years ago

Migrated case from Manuscript.

Original case: https://pharo.fogbugz.com/f/cases/17042 Status: Work Needed Project: Usability Original Author: CyrilFerlicot Date: 18 November 2015 1:06:39 pm

Description:

If we build a Pharo desktop application we should have a deployment method to block the code access (We should also get a way to revert it).

So we should:

If we include this feature we should add it to UpdatedPharoByExample and/or DeepIntoPharo and/or EnterprisePharo.

jecisc commented 5 years ago

Reply: Author: Henrik Nergaard Date: 18 November 2015 1:25:02 pm

Message:

Why Disable? if those packages aren't used in the production would it not be better to just remove them instead of introducing a lot of checking if they are enabled or not? (this would also reduce the size of the application...)

Some of these steps could also be done by just having a recompiling script that removes some of these possibilites, for example; to disable the worldMenu one just have to recompile PasteUpMorph>>#invokeWorldMenu: evt to just: '^self'

jecisc commented 5 years ago

Reply: Author: CyrilFerlicot Date: 18 November 2015 1:31:10 pm

Message:

For now most of the application are based on the common Pharo image. We take an image and just execute a configuration.

Maybe in the future when the Bootstrap and the layers of Pharo will works we will be able to just ignore those.

And if we disable it we still have the possibility to revert the changes if we have a bug.

jecisc commented 5 years ago

Reply: Author: Pavel Krivanek Date: 27 January 2017 9:51:09 am

Message:

Low priority issue. Not for Pharo 6. The milestone "Later" was set automatically.

jecisc commented 5 years ago

Reply: Author: Vincent Blondeau Date: 28 September 2018 5:29:06 pm

Message:

WIP here: https://github.com/VincentBlondeau/Cruiser/issues/7