Quoting Christopher Nelson <[EMAIL PROTECTED]>: > Let me be clear here. In order to use AWS2 you have to either create > widgets via Javascript code, or you have to use the XML definition > syntax. You don't exactly *have* to write any Javascript, except in > defining event/action couples...which is not really writing javascript. > Events which you are interested in will be forwarded to the notification > objects which you register and connect to event generators as sinks.
> > However, it is important that you understand that *ALL* events are > processed at their terminators in Javascript. It is not possible for > your native code to ask AWS2's manager to forward events to it. > Technically this could be added in some cases, but it is not something > that I will add. Nor is it possible to listen for any given event via > AWS2. The manager understands mouse and keyboard events, period. It > provides access to mouse and keyboard events, period. All other events > originate from, and are delivered through, Javascript. So on an event (lets say "button X pressed") there will always be the chain CS mouse event -> AWS2 manager -> (internal dispatch in AWS2?) -> SpiderMonkey -> JS-script (even if just a tiny bit) -> AWS2 -> my notification -> (internal dispatch in my game library) -> my scripting interface Sounds both very efficient and very nice to debug :) > > I could technically provide a way to have AWS2 forward unused or unknown > events to the app, but that is silly since AWS2 *receives* events from > your app. If your app has it's own little events here and there, then > that's where you should handle them. Why does AWS2 need to know about > them? I am not talking about internal events in my application, but rather events _generated_ by AWS2 such as "button X pressed" > > All of that being said, if you hate JS and you don't want to use it, > then AWS2 is not really for you. All of the labor-saving features, the > flexibility, and power of expression come from it's binding with JS. > I'm sorry that you don't like JS, but there are plenty of people who > don't like whatever scripting platform I might possibly choose. My main concern here is generality and uniforimty within CS. We already have a very general and well-working system for event dispatch, but as it seems AWS2 won't even consider using that. Same thing about scripting interface (they need to be worked on, sure, but that is also done by other people). The more plugins that go and do stuff their own way the harder it becomes to learn, debug, maintain and document. Also considering that CS is a SDK the main thing should not be how to make it as simple as possible in CS itself, but rather make it easy for the client (the user) to get the information he needs into his framework (be it CEL or any other system that you definitly will have on top anyhow) Oh well, enough for now.. back to the damn documents ;) -Marten ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
