<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
My commit message didnt work either. the arguments all show up now and the 'view arguments' link should filter arguments for each behavior. all the arguments can be controlled with jquery now.<br><br>Mike<br><br><blockquote><hr>Date: Thu, 29 Nov 2007 13:53:19 -0500<br>From: lucy@thoughtandmemory.org<br>To: dev-flock@mit.edu<br>Subject: [Dev-flock] hooked up add behavior.<br><br>yo, <br><br>my commit message failed because i included funny characters (i think).<br><br>i hooked up 'add behavior'. the process starts in behaviors.html, which calls addDrop2-- this function renders the provided template in the provided element id, with the provided parameter (currently, one can only provide a single param called 'id').
<br><br>in this case, we drop (insert) the behavior_add.html form. <br><br>onSubmit, this forms passes off the input values plus id (which in this case is for the node that the behavior is being attached to) to create_behavior(), which calls JSON and so on.
<br><br>again, i haven't actually saved any data in the db... still holding off on that until some docs pop up and/or i decided to dive in. <br><br>i'm now going to make a note of 'how to add forms' to the ImplementationOverview wiki page.
<br><br>i'm not exactly sure the form process is the best one-- should we use onClick or onSubmit or $(foo).click( ? mainly, i wanted to show in the html file what other html snippet was going to be dropped, hence making the call to addDrop2 in the html file as opposed to in some javascript file. i don't know much about the speed or efficiency tradeoffs i'm making, though.
<br><br><br>good luck,<br>let me know if ya'll have questions,<br>l.<br>
</blockquote><br /><hr />Connect and share in new ways with Windows Live. <a href='http://www.windowslive.com/connect.html?ocid=TXT_TAGLM_Wave2_newways_112007' target='_new'>Connect now!</a></body>
</html>