Sorry Ablerto,

I think that post came out of left field for you, and I didn't express
myself very well. I don't want to denigrate rum in any way.   I've
used it in apps at work already and love it.

What I wanted in the TG2 release was a form generation library.
Ultimately I also wanted an admin interface too, but a newforms
competitor was at the top of my list for this release.

As chirs mentions we both tried to make rum work as a form generation
tool, but it was somewhat difficult, (all the rum form generation
stuff required lots of request context stuff to be setup and torn
down).

Rum has lots of potential, but it's a mini-framework that creates a
wsgi app, and not a library of form generation tools.   And that
design decision makes tighter integration with a TurboGears app
harder.   Of course it's easy to mount a RUM app in TG2, and we will
always support and document that.

But in my mind integration of admin stuff that can compete with the
new django admin requires a bit more flexibility in embedding forms
and whatnot in pages with content generated by the main app. Sprox
provides both, but what I really care about in terms of shipping with
TG2 is the form generation library stuff.

So, you're right.  Rum is not a form generation library. And that's
why we're including sprox.

Sprox also happens to implement an admin generator thing, but on that
front Rum is still ahead of Sprox.   And that's definitely not why I
agreed to let chris put sprox in the index.

It's possible that Rum could be refactored a bit so that the form
generation stuff was exposed more cleanly.   But I wasn't up to the
task with the other stuff on my plate.   And, even then I'd like to
support jython/ironpython with all the stuff in the TG core, and that
will be difficult while using peak-rules because they have different
byte-code systems, and ByteCodeAssembler would have to be modified to
help them, and that's a task that's definitely over my head.

--Mark Ramm

On Tue, Dec 30, 2008 at 11:25 PM, Alberto Valverde <[email protected]> wrote:
>
> Mark Ramm wrote:
>> Catwalk2 is a part of sprox, which is the successor to DBSprockets, so
>> three of your four options are really all one thing. ;)
>>
>> That leaves a choice between Rum and Sprox.  I would use Sprox at the
>> moment,
> I would use Rum :)
>> because it seems to have developer momentum,
> Rum is more mature, is better designed (Sprox admittedly has "borrowed
> some conceptual ideas from Rum" ;) and has more active developers.
>> and is definitely easier to use/debug than Rum.
> Definitely easier to use/debug, in what way? These kind of blanket
> statements with no further explanation smell like FUD to me.
>> The 2.0b1 release of TG2 includes sprox by default because it has a
>> cleaner interface with TG2 than Rum,
> Cleaner than WSGI? Perhaps the I've made a bad job explaining what Rum
> is [1]. (it's not an auto-form generation library! although it
> implements one)
>
> BTW, could anyone please post a link to the thread the decision of
> including a 9 day old project in a beta release of TG has been openly
> discussed?
>> so that's another reason to use Sprox.
> Stay tuned... before mid February the scheduke of my day job's main
> project will have me back coding on Rum whether I'd like it or not...
> and there's a whole dojo-based rich client reason I left undone this
> summer ;)
>
> Now seriously. I think it's a pity that the scarce human resources TG
> has are being diverted in almost parallel directions, but something good
> will surely come out of the competition :)
>
> Alberto
>
> [1] http://toscawidgets.org/documentation/rum/#introduction
>
> >
>



-- 
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to