It's my turn to apologize for the delay: my pesky webmail silently moved Damon's message into the trash....
On Mon, 24 Jan 2011 14:15:07 -0600, Damon Courtney wrote > I'm just looking at some of the code for the first time in a while > so forgive me for not commenting sooner. > > Are you talking about just moving the rivet commands into a ::Rivet > namespace? It sounds like from this and your previous "Rivet > command scope" email that you're trying to unify everything. I > think that's a great idea. It makes Rivet more of a package that > can easily be loaded or not based on the user. > yes, precisely. After I wrote a couple of sample pages where commands were prefixed with their namespace I also happily rediscovered the obvious: readability of the code had improved by highlighting the lines of code where Rivet was involved. A 'namespace import ::Rivet::*" restores the usual way to access to the module, but I wont't use it, I think. > Does anyone else have an opinion here? Are there any other Rivet > requests on the horizon we should be looking at? It sounds like > Karl is waking up a bit, at least as regards to ideas and thoughts, > but maybe some code too. I'm working on a pretty big project in > Rivet right now, so my activity level is sure to increase soon > enough. Clif Flynt has thrown his hand in a few times now. > > Combine that with Massimo's tireless work, and we may actually be > able to wake the sleeping giant. At least until we all go back to > our regular lives. 0-] > > D > Glad to know you're working on a rivet based project. Suggestions and experiences that might come from the applicative field are obviously of great interest to find new developments that may tickle the giant (pun intended). A few months ago the proposal of creating an infrastructure for better support of advanced web programming (Ajax etc) was put forward. I don't have the experience for designing such a tool (I mostly made some Ajax stuff with the purpose of teaching myself the technique), but I understand it's not just about a buzzword, the problem is about creating a real framework for webprogramming (Rails comes in mind in this context) -- Massimo -- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
