<!-- ##### SECTION Long_Description ##### -->
<para>
-Long description
+A #SeedContext provides a complete "universe" for the execution of JavaScript. You can use seed_context_new() to create a sandboxed context that lacks the import system, so it can be used to execute somewhat untrusted JavaScript (as it has no way to access the rest of your system). You can also expose the default set of globals (including "print", "imports", and "Seed") to create more powerful but still self-contained environments within which to execute code.
+</para>
+
+<para>
+The "sandbox" module provides access to this system from the JavaScript side of Seed.
</para>
<!-- ##### SECTION See_Also ##### -->
* @global_class: The #SeedClass to use to create the global object, or %NULL to
* create it with the default class.
*
+ * Create a new #SeedContext. By default, this creates a new context
+ * which has no global objects; you can add the default set using
+ * seed_prepare_global_context().
+ *
* Return value: A new #SeedContext.
*
*/
};
#endif /* SEED_ENABLE_DEBUG */
-void
-seed_prepare_global_context (JSContextRef ctx)
+/**
+ * seed_prepare_global_context:
+ * @group: A #SeedContext on which to add the default set of global objects.
+ *
+ * Adds the default set of global objects (imports, GType, Seed, and print)
+ * to a fresh #SeedContext.
+ *
+ */
+void seed_prepare_global_context (JSContextRef ctx)
{
JSObjectRef global = JSContextGetGlobalObject (ctx);