Line 30: |
Line 30: |
| <dgd> bemasc, ? | | <dgd> bemasc, ? |
| <dgd> not possible to run activities from jhbuild is that what you mean bemasc | | <dgd> not possible to run activities from jhbuild is that what you mean bemasc |
− | <bemasc> dgd: sugar activities cannot run outside of sugar, and more than a java applet can run outside of the JVM, or a flash applet can run outside of a flash interpreter. | + | <bemasc> dgd: sugar activities cannot run outside of sugar, and more than a java applet can run outside of the JVM, or a flash applet can run outside of a flash interpreter. |
| <bemasc> s/and/any/ | | <bemasc> s/and/any/ |
| <dgd> ok, so running just the activity in sugar? | | <dgd> ok, so running just the activity in sugar? |
− | <dgd> just one activity, none of the home stuff etc.
| + | <dgd> just one activity, none of the home stuff etc. |
| <bemasc> also not possible | | <bemasc> also not possible |
| + | <dgd> I thought for sure I read in the docs that you can run just an activity... |
| + | <bemasc> by "not possible" I mean "requires you to modify the code for the Sugar shell". |
| + | < bemasc> You can probably cause Sugar to launch and immediately start an activity. You might be able to do this using a .xsession script. |
| + | <bemasc> However, users will still be able to bring up the frame and switch to the home view, etc. |
| | | |
| ====Where are the activities stored?==== | | ====Where are the activities stored?==== |