On 2/5/07, DarkBlue <[EMAIL PROTECTED]> wrote: > > > I concur with Ben's opinion concerning certain situations where SO,SA > is > a back step and does not improve programming efficiency. I rather have > some way not to use any of those and just use "raw sql" . > While short queries are ok, complexer ones get messy real fast , > especially > given the lack of full documentation and sufficient examples.
I'm sorry but again your not undestanding the tool SO was never build to be that from the site "SQLObject is a popular *Object Relational Manager* for providing an object interface to your database, with tables as classes, rows as instances, and columns as attributes." going on to the "raw stuff" it says: "SQLObject includes a Python-object-based query language that makes SQL more abstract, and provides substantial database independence for applications." that is two things 1- backend independant and 2- not write SQL. now please top trying to use a Hammer as a screwdriver if you want "raw sql" your better of with a tool that was designed for that "SQLAlchemy is the Python SQL toolkit and Object Relational Mapper that gives application developers the full power and flexibility of SQL." all quotes taken from the first line 2 paragraphs of http://www.sqlobject.org/ and http://www.sqlalchemy.org/ I also think that the current style and formating of documentation > will lead to > difficulties real fast. Why not start documentation from scratch for > TG2.0 as Karl pointed out why? and have something like the apache manual as a style guideline ? that is yet another barrier of entry. > It is paramount that documentation is up to speed with releases. > Maybe any new version should only come out of beta when the docs > are uptodate too. This would give a far better and mature impression. I totally disagree I prefer underdocumented and working than nothing at all. There are many good ideas in the cogbin , but only a few work > out of the box. TG2.0 should also focus on getting some of the > more promising ones to work like the quickstart facility. E.g. tgcrud. pardon? the cogbig is a place for third-party tools that are related to TG, there is no way TG will incorporate any of them, at least for 2.0 since the goal is to take stuff out and not take stuff in. As for tgcrud itself I'm not sure if you know but it has less then a week http://trac.turbogears.org/browser/projects/tgcrud/trunk?rev=2468 As for the maintenance I'm affaid to say that's the bussiness of each one of the tools maintainers in some cases we don't even have access to the repocitories... The documentation also needs to give a better understanding > for the widget browser. The widget browser says source code and > template and I believe many a new user is fooled that what is there > can be copy pasted into the own kid file or controller. Only to find > out it does not work that way. they are already several tentative docs at http://docs.turbogears.org/1.0/RoughDocs#id6 and yes your expect to copy some of the code now you are also expected to undestand what is being copy and make it work on own data. DB > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
