I don't want to spam this list with contrived self-important discussions, but without knowing who is/isn't watching the tacos-dev list I wanted to be sure any persons here that may have an opinion on this matter were aware of what's trying to be figured out...
j ---------- Forwarded message ---------- From: Jesse Kuhnert <[EMAIL PROTECTED]> Date: Aug 18, 2005 6:41 AM Subject: ajax engine release opinions To: [EMAIL PROTECTED] How does everyone feel about the idea of releasing the core ajax-ish engine logic of tacos as a seperate entity from the tacos components themselves? Is this just going to confuse the library? How soon do people want this sort of functionality? I think after today I will have more than enough of the core logic in place that I could simply release the core itself, and let other people/libraries worry about how they are going to handle their end of the javascript chain. It doesn't make very much sense in my mind to release an "IEngineService" without the corresponding link component that goes with it, but I could be wrong. Nor does it make a whole lot of sense to release that component, without the additional tacos javascript client handlers that makes the process a little bit easier. So, I've got a branch of tacos sitting in cvs that should be more than enough for any foundational work to start being done by other component developers by the end of the day, how and when do we release the logic? I plan on adding at lease a small tutorial-ish page to the main sourceforge page just to get people started with understanding how this particular implementation is dealing with the logic. All opinions are welcome.. jesse --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
