Re: DB_DataObject and Structures_DataGrid integration

Marcus Whitney wrote:

I think that with the oncoming demand for rich web applications, event handling is becoming a necessity in web applications. I say this with the experience of having written a pretty high use web application with Jackson

Miller, and a couple of not so great ones on my own :) .    Web Applications have to move from the 'page load' paradigm if they are going to evolve.  Web programmers need to make embeddable components.  That is when we will start to see the velocity of development that we see with projects like KDE (KPart).  And, it is possible.  [...]

Possible, yes. But PHP IMHO isn't the right language for that. And is it really needed? Let's see what you say next:

PEAR is not a framework, but the packages in PEAR should be built to be easily incorporated in a framework. Wouldn't that bring us all closer to PEAR and cause less reinventing of the wheel? I mean, that's why I work on CEP, because every framework I have seen does not embrace PEAR, and at the end of the day, PEAR is what I want to use. And just a note about desktop vs. web apps: XUL, xmlhttprequest and remoting in general should be a clear indicator that web programmers needs to start learning some desktop app concepts. Programmers typically have there own opinions, but as an architect who is used to crafting the web to be as user friendly as possible for over 500 customers who I speak to regularly, let me assure you, they want desktop ease of use.

Yes, they want desktop-like web apps. Precisely what I'm thinking as well. But XUL, which you mentioned, is the perfect example how this should look like: Having a strong application frontend at the user's machine. This can be XUL, which handles all real user events using Javascript, or a Flash Remoting application (again, using Javascript internally to handle events). There must be a distinction between frontend and backend. A non-request-based frontend will have to handle events. A request-based backend will not have to do that. It handles requests. PEAR provides 95% backend components. If event systems are introduced here, then not to handle user events, but to allow loose interactions between components. CU Markus