[e-lang] simple question

[Matej Kosik]

Kevin Reid wrote:
> On Aug 15, 2006, at 12:49, Matej Kosik wrote:
>
> .e programs exist solely to bridge between the capability world and  
> current OSes.
> 
> <file>, or file__uriGetter, is accessible only in the  
> privilegedScope. When you run an .e program, it is evaluated in the  
> privilegedScope; if it was not, then the it could not do anything  
> useful.
> 
> A well-designed .e program should contain the minimum amount of code  
> needed to properly distribute capabilities to the rest of the  
> program, and be simple enough to read to find out what capabilities  
> it uses.
> 
> The rest of the program will be in .emaker files or other safe  
> loading systems which evaluate code in the 'safeScope'. safeScope  
> contains only references which do not allow such things as file access.
> 
> You can avoid .e by using a launcher such as CapDesk which loads  
> 'caplets' and passes capabilities to the caplets as you specify.  
> CapDesk itself is started by an .e program, of course.
> 

Thank you. Now it makes more sense. I was not sure of such basic thing.

I am not sure how to work with CapDesk (I've launched it; I saw some
directories; I have tried to "install" the capEdit.capplet but it failed
with the following message:

    starting run prep
    made scope 2

    # value: <capEditCapletAuthor>
    shown
    about to get requestsTree
    got requestsTree
    requests retrieval failed: problem: Prefix doesn't match: visit
)

E programs cannot be run in safeMode without CapDesk? For example:
running a E program and giving it (at startup) capability to some
object...which, for example, enables it to write 10 lines to some file.
Or something similar. (just a proposal)

Regards
-- 
Matej Kosik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://www.eros-os.org/pipermail/e-lang/attachments/20060815/720a83e0/attachment.bin