disableProgrammerFacilities

'Preferences disableProgrammerFacilities' doesn't do much, currently :)
It would be good to have this disable the IDE at some point. It does seem to kill
commands cmd-d and cmd-c but the browser et al remain available.

Interesting. :) Can elaborate on what it means to "disable the IDE" in terms of Squeak?

- System Browser, Inspctor, Explorer, Message Set, ...
- Morphic Halos, Meta menus
- Distinct keyboard shortcuts such as CMD+P, CMD+D, ...
- Shrinking down the world menu to Transcript/Save/Quit
- ...

Is it a deployment scenario? What might happen if a debugger wants to pop up?

...What does eToys do? =)

Best,
Marcel

Hi,
in 3.8 times I used a changeset (SqueakLockdown-nk.1.cs) from 3.4 times
to create deployment images. After loading the changeset and doing some
magic with addToStartupList you'd get an image that behaved like a
conventional application. There would be a pre debug window with the
only option to close it.

Today I'll check if the changeset still works in 4.5 though I have some
doubts.

Below I will paste the comment of the cs.

Cheers,

Herbert

'From Squeak3.4 of 1 March 2003 [latest update: #5170] on 26 March 2003
at 7:07:40 pm'!
"Change Set:        SqueakLockdown-nk
Date:            26 March 2003
Author:            Ned Konz

26 Mar 03: Minor change for 3.4, made it append to existing personal
menu instead.

Also added disabling of readDocumentAtStartup.

20 Oct 02: Fixed bug that allowed cmd-shift-W to pop up World menu when
locked down.

This change set makes it easier to lock down an image for application
delivery.

By executing:
     Preferences disableProgrammerFacilities
from your personalized World menu and saving the locked image under a
new name, the following features are disabled:

* Halos
* Meta and Debug menus
* Command keys in world
* Command-dot interrupts
* Debuggers (though notifiers will still come up)
* World menu (from mouse or key)
* Command keys other than editing & cursor in text
* Reading scripts/projects at startup.

The yellow-button menus in text panes will still come up.
It is assumed that text panes in your app will have their own
yellow-button menus.

Two existing preferences have been made available in the Preferences tool:
cmdKeysInText        -- enables the use of many cmd (or alt) keys in
text editors
cmdGesturesEnabled    -- enables halos, debug menus, etc.

Another two new preferences have been added:
appendToErrorLog     -- appends to the error log rather than replacing it
noDebugButton         -- suppress the ability to open a debugger from a
notifier

You can add this to your personalized World menu:
     aMenu add: 'disable pgrmr' target: Preferences action:
#disableProgrammerFacilities.

Or you can add:
     Preferences disableProgrammerFacilities

to your do... menu list.

Am 04.05.2015 um 07:26 schrieb Marcel Taeumel:

Am 04.05.2015 um 08:30 schrieb Herbert König:
> Hi,
> in 3.8 times I used a changeset (SqueakLockdown-nk.1.cs) from 3.4
> times to create deployment images. After loading the changeset and
> doing some magic with addToStartupList you'd get an image that behaved
> like a conventional application. There would be a pre debug window
> with the only option to close it.
>
Ok, here goes:
Without the changeset only command keys are disabled.
Squeak 4.5-13680: UTF-Textconverter complains if I drop the cs into the
image. But I can file in everything from the changes browser.
Squeak 4.5-1367 and 4.4-12332 both accept that the cs is dropped into
the image.
Then sending #disableProgrammerFacilities disables the command keys, the
World menu and the halos.
In the right click World menu the entries to enable the Flaps and the
main docking bar are not removed and give access to the tools.
The docking bar is not disabled automatically.
http://wiki.squeak.org/squeak/518 still has that cs.

So I'd say the method in Preferences should either be removed or the
comment updated accordingly.
No idea if the remaining accesses to the tools should be disabled in the
cs or in the method in Preferences.

Cheers,

Herbert

On 3 May 2015 at 22:26, Marcel Taeumel wrote:

> Interesting. :) Can elaborate on what it means to "disable the IDE"
> in terms
> of Squeak?
>
> - System Browser, Inspctor, Explorer, Message Set, ...
> - Morphic Halos, Meta menus
> - Distinct keyboard shortcuts such as CMD+P, CMD+D, ...
> - Shrinking down the world menu to Transcript/Save/Quit
> - ...

That's a good list. I would like there to be no way for a user to get to any part of the IDE. Also
not be able to determine the programming language.
>
> Is it a deployment scenario? What might happen if a debugger wants
> to pop
> up?
>

Definitely only for deployment of a robust application IMO. The comments and pop-ups in
#disableProgrammerFacilities provide caveats.

> ...What does eToys do? =)
>

Good question.

 - Dan