Bit Freezing For Dummies

...you would ask sugar for permissions, and sugar would do it for you. the intended behavior here is that activities ask sugar to present a dialogue to a user to pick a file or mimetype under one of thse capabilityes. sugar asks rainbow, should I do this? does the activity have the authority ot make the request?" if rainbow returns 'affirmatibve', sugar should display the dialogue box and notify rianbow of the result; then sugar needs to tell rainbow "please make these files available" and rainbow will make the files available to the activity.

Okay, I think I see this; but I don't think we've even solved basic opening from te journal; right now activitie request files diretly to the datastore.

not very often, right? or is that true?

Today, they constantly request from the datastore. this needs to be mediated through sugar.

So when an activity starts up...

in that circumstance, sugar should say to rainbow, when you start the activity, please provide this file. these suggestions are not set in stone; the ipomrtant things here are that rainbow trusts sugar to make requests. in return, sugar needs to discriminate b/t when thea ctivity wants to do something, and when the user wants to do something. When the user wants to do something, sugar tells rainbow 'please do this'. when the activity wants something, sugar should ask rainbow 'should the activity do this?'...

I was concerned by the current mailing list thread saying 'use the current API and ew will provide a wrapper'. I don't think it is sufficient at the moment.

The question is, is it sufficient for the activities? It may be insufficient for sugar-to-rainbow. the former is most important...