Hi Kevin,
>>TurboGears, unlike some packages, is *not* a CMS... I like that clear statement. Hopefully the community has (to some extent) a common understanding of the implications... > http://www.rubyonrails.com/ Quite often TG looks what ROR does. In my opinion, TG could profit through inspiration from SAP Web DynPro, which is database-driven web application "par excellence". Although it's heavyweight, and application development might be measured in months rather than minutes ;-) https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d Roman Kevin Dangoor wrote: > On 12/12/05, Jorge Vargas <[EMAIL PROTECTED]> wrote: > > Since Kevin is talking about redesign I think we should discuss this. > > > > My point, we should run TG site on top of TG even if it isn't necessary, > > just because we should be the 1st ones to use our product. > > Make it more interactive, add test site, like the one that was set up for > > catwalk before it was part of tg, implement identity right on TG site, etc. > > I think the best implementation of turbogears should be on it's site. > > > > In fact I remenber reading an article comparing frameworks that criticized > > tg because of that. > > TurboGears, unlike some packages, is *not* a CMS, and the website is > too important to run on a half-baked CMS. Consider this website: > > http://www.rubyonrails.com/ > > There's nothing dynamic on the front page. The blog there is likely to > be Rails-powered (now, at least). Unless they've switched recently, > Rails is using Trac for their issue tracking! (I'm sure they'll switch > to the Rails-powered Collaboa soon, if they haven't already). > > The more popular TurboGears gets, the more likely it is to get all > kinds of taunts for perceived shortcomings. There's not enough time in > the day (for anyone here, I'm sure) to try and follow all of those. > It's more important to ignore the taunts to try to add real value. > > This has been my focus in thinking about the next major iteration of > the site. What kind of dynamic stuff can we add that would really make > the site a better tool for people using the project? My thought was a > "project dashboard" (some of which would leak to the front page). This > could include a whole bunch of stuff: latest tickets, checkins, > mailing list messages, postings on the Planet, "official" blog > postings, etc. > > All of that stuff is available via RSS, so a simple periodic grab of > the data, hold it in memory, is all it takes. > > I don't think TurboGears.org should be the best example of a > TurboGears app. TurboGears.org needs to be the best place to go for > information about TurboGears development. My hope is that better apps > (diggdot!) show up all over the place. > > If a better Trac or a better CMS or whatever comes along that is > written in TurboGears, running that on turbogears.org would be a great > thing and I'd be happy to do that. Otherwise, I'm pushing for more > features for TurboGears itself and better docs. > > > by the way i'm not an active contributor (yet) i'm still learning how each > > part works, and what exactly is TG and what is not, but i'm willing to put > > time into the website if it's needed. > > All kinds of contributions are welcome! > > If someone wants to contribute the project dashboard or some other > really cool gizmo for TurboGears.org, that's a good thing to me. I'm > just saying what my priorities on the project are. > > Kevin > > -- > Kevin Dangoor > Author of the Zesty News RSS newsreader > > email: [EMAIL PROTECTED] > company: http://www.BlazingThings.com > blog: http://www.BlueSkyOnMars.com
