Hi Amanda -
I think I may need more information to figure out what you are trying to do, but maybe this will help.
Actual form entities in Reason contain an XML description of a form, and various other options and settings for that form. The "form" module in Reason uses a number of other classes and utilities to implement form display, editing, e-mailing, and saving capabilities. The translation of the form XML into a disco form is done using a class called ThorCore.
If you are writing some custom module and only care about getting the HTML representation of a particular form entity, you can do something like this:
<?php
include_once( 'reason_header.php' );
include_once( THOR_INC . 'thor.php );
include_once( DISCO_INC . 'disco.php );
$form = ... // this is our form entity, obtained however you want.
$xml = $form->get_value('thor_content');
$disco = new disco(); // a blank disco form
$thor_core = new ThorCore();
$thor_core->set_thor_xml($xml);
$thor_core->append_thor_element_to_form($disco); // thor will add the elements described in the XML to the form.
$disco->run(); // this should output the form.
Note however, that many features of forms that you are used to are implemented in the reason form module. Depending upon what you are trying to do, maybe one or both of the following is what need to look at:
1. If you want a form module running in the sidebar instead of main content area you should create a custom page type which runs the form module in a different region.
2. If you want all the features of the basic form module, but need to add functionality on top of that, you may need to write a custom form view that provides some customization on top of the standard Reason form module.
Nate