MySQL was just my choice, and most all the code in Skyscraper itself is just plain old SQL. There may be a few things in there that are specific, but for the most part it'll work anywhere. But Flightaware isn't going to use something like this. You guys have in development of your stuff, and this is a whole new framework. You're not going to go through and rewrite all your pages in this. 0-]
I haven't looked at generating JSON at all as I don't have a need for it, but it's certainly something that should be added out of the box. Being that I develop my stuff in one way while others develop in completely different ways, this is the kind of thing that needs to be brought up. What is the list of things that should be in a modern framework built on Rivet. Someone with some Ruby and Rails experience should pipe in here. Oooh, maybe we can get ol' Welton over there to wake up for a quick response! 0-] D On Jan 27, 2011, at 11:09 AM, Karl Lehenbauer wrote: > I like the name. We are down with jQuery. But it would need to support > PostgreSQL to get any traction at FlightAware. > > You might have a look at yajl-tcl for generating valid JSON really > quickly. The library includes returning PostgreSQL query results as JSON. > It can parse, too, but the results are left-to-right so it's gotta be > taken further to be useful. > > On 1/27/11 10:49 AM, "Damon Courtney" <[email protected]> wrote: > >> With this latest project of mine I actually started work on a framework >> built solely around Rivet. I'm not shooting for something that works >> across web servers or something that is portable, I'm writing something >> that takes advantage of all the things Rivet has to offer. I call it >> Skyscraper. >> >> It kinda sucks right now because I've only really just started it, but >> it's coming along. It's based on many of the ideas used in Rails but in >> a Tcl way. When I looked at Ruby and Rails once before, there was a lot >> to like about it. Right now it's sort of hardwired for MySQL and jQuery >> as the external components, but that's purely because it's what I'm >> using. The ties to jQuery at this point are not much more than just >> including the tags to include it, and MOST of the SQL code is generic >> with only a few MySQL-specific things. >> >> It uses TDBC as the database backend, so it can easily support any >> database Tcl does, and the rest is all straight Tcl or Rivet. It doesn't >> use TclOO though it probably could if someone had a strong feeling about >> it. I found when using Rails that the object stuff felt kinda' forced. >> Like you didn't really need it, but because you're in Ruby, that's just >> the way you do it. Do you really need a new object for each request? >> Isn't that what Rivet's ::request namespace is doing for you? >> >> I'm open to hearing what people have to say on this topic. I needed a >> good MVC framework for writing Rivet apps, so I made one. I'm up for >> taking suggestions as I write it if anyone has any. I hope to include it >> as part of Rivet one day. Unlike TclOO that was supposedly made to build >> other OO frameworks on top of, I'd like to see Rivet ship with one >> framework to rule them all and right out of the box. >> >> D >> >> >> On Jan 27, 2011, at 8:12 AM, Massimo Manghi wrote: >> >>> Arnulf's work is the only serious attempt I know to endow Tcl >>> programming with a consistent framework for web development. Still, the >>> SF site has no download to offer. Do you know if Arnulf moved it on to >>> some other resource? >>> >>> -- Massimo >>> >>> >>> On 01/27/2011 02:31 PM, Harald Oehlmann wrote: >>>> >>>> Maybe ATWF, the port of the zend framework to Rivet by Arnulf Wiedemann >>>> may be interesting? >>>> See: >>>> http://wiki.tcl.tk/25821 >>>> or the presentation at TC2010. >>>> >>>> Harald >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
