As I replied to Brian, to use a drop down for your attributes, you need to use the source_model attribute of your attributes to be able to use a drop down. For your particular case (having the drop down populated by products) I'd make the attributes type int which will store the products id. Then, in the custom source model you create use a collection to select the list of products (You might find Chris' post on the efficient use of collections helpful for this) and iterate across the list of products producing an array that is in the same format as the one in the Boolean source file.
As for the calendar, the best thing I can suggest is that you look at how the calendar has been achieved in other frontend areas. Briefly, you need to include the calendar block into your page (which has a number of definitions in it), include the calendar JavaScript and the relevant skin CSS files into the page, create an image for the user to click on and then in JavaScript instantiate the calendar.
As I replied to Brian, to use a drop down for your attributes, you need to use the
source_modelattribute of your attributes to be able to use a drop down. For your particular case (having the drop down populated by products) I'd make the attributes type int which will store the products id. Then, in the custom source model you create use a collection to select the list of products (You might find Chris' post on the efficient use of collections helpful for this) and iterate across the list of products producing an array that is in the same format as the one in the Boolean source file.As for the calendar, the best thing I can suggest is that you look at how the calendar has been achieved in other frontend areas. Briefly, you need to include the calendar block into your page (which has a number of definitions in it), include the calendar JavaScript and the relevant skin CSS files into the page, create an image for the user to click on and then in JavaScript instantiate the calendar.