Proposal for a Topic for the bachelor/master list [safe-image for teaching]
Hi, I don't know where to send the proposal and I think that the list would be a good place to talk about it. The main idea is to have a "safe" image, or a way to block or restrict the modificable parts in the system, in order to avoid mistakes during the learning. It could include protected packages, reduced browsers showing by default user packages, configurable rules (by example: you can not create a class with empty category, you can not create a class with the same name that a known one). Maybe we can have a way to configure or to ask for permission to modificate some parts of the system. Also, some filters during debugging, to avoid "protected" code. An easy way to obtain that image The idea is to reduce the common errors that we make when we start programming also to help teachers.
I think thatâs a good idea. Obviously thatâs something that none of us developers want in the system but it would be good to have it from a promotional point of view I guess. Could applications like Dr. Geo benefit from such an environment? Max On 01.11.2013, at 19:56, Gisela Decuzzi <giseladecuzzi@gmail.com> wrote:
Hi, I don't know where to send the proposal and I think that the list would be a good place to talk about it. The main idea is to have a "safe" image, or a way to block or restrict the modificable parts in the system, in order to avoid mistakes during the learning.
It could include protected packages, reduced browsers showing by default user packages, configurable rules (by example: you can not create a class with empty category, you can not create a class with the same name that a known one). Maybe we can have a way to configure or to ask for permission to modificate some parts of the system. Also, some filters during debugging, to avoid "protected" code. An easy way to obtain that image
The idea is to reduce the common errors that we make when we start programming also to help teachers.
Another similar project is a real working Image Locker for deploying... but not sure how much important it is... On Fri, Nov 1, 2013 at 5:10 PM, Max Leske <maxleske@gmail.com> wrote:
I think thatâs a good idea. Obviously thatâs something that none of us developers want in the system but it would be good to have it from a promotional point of view I guess. Could applications like Dr. Geo benefit from such an environment?
Max
On 01.11.2013, at 19:56, Gisela Decuzzi <giseladecuzzi@gmail.com> wrote:
Hi, I don't know where to send the proposal and I think that the list would be a good place to talk about it. The main idea is to have a "safe" image, or a way to block or restrict the modificable parts in the system, in order to avoid mistakes during the learning.
It could include protected packages, reduced browsers showing by default user packages, configurable rules (by example: you can not create a class with empty category, you can not create a class with the same name that a known one). Maybe we can have a way to configure or to ask for permission to modificate some parts of the system. Also, some filters during debugging, to avoid "protected" code. An easy way to obtain that image
The idea is to reduce the common errors that we make when we start programming also to help teachers.
-- Mariano http://marianopeck.wordpress.com
Hi mariano Benjamin did a User and locking package for Pharo 20 and 30. Stef
Another similar project is a real working Image Locker for deploying... but not sure how much important it is...
On Fri, Nov 1, 2013 at 5:10 PM, Max Leske <maxleske@gmail.com> wrote: I think thatâs a good idea. Obviously thatâs something that none of us developers want in the system but it would be good to have it from a promotional point of view I guess. Could applications like Dr. Geo benefit from such an environment?
Max
On 01.11.2013, at 19:56, Gisela Decuzzi <giseladecuzzi@gmail.com> wrote:
Hi, I don't know where to send the proposal and I think that the list would be a good place to talk about it. The main idea is to have a "safe" image, or a way to block or restrict the modificable parts in the system, in order to avoid mistakes during the learning.
It could include protected packages, reduced browsers showing by default user packages, configurable rules (by example: you can not create a class with empty category, you can not create a class with the same name that a known one). Maybe we can have a way to configure or to ask for permission to modificate some parts of the system. Also, some filters during debugging, to avoid "protected" code. An easy way to obtain that image
The idea is to reduce the common errors that we make when we start programming also to help teachers.
-- Mariano http://marianopeck.wordpress.com
Gisela I will add this idea to the topics list :) Thanks for the reminder. Stef On Nov 1, 2013, at 7:56 PM, Gisela Decuzzi <giseladecuzzi@gmail.com> wrote:
Hi, I don't know where to send the proposal and I think that the list would be a good place to talk about it. The main idea is to have a "safe" image, or a way to block or restrict the modificable parts in the system, in order to avoid mistakes during the learning.
It could include protected packages, reduced browsers showing by default user packages, configurable rules (by example: you can not create a class with empty category, you can not create a class with the same name that a known one). Maybe we can have a way to configure or to ask for permission to modificate some parts of the system. Also, some filters during debugging, to avoid "protected" code. An easy way to obtain that image
The idea is to reduce the common errors that we make when we start programming also to help teachers.
participants (5)
-
btc＠openinworld.com -
Gisela Decuzzi -
Mariano Martinez Peck -
Max Leske -
Stéphane Ducasse