[Typo3-dev] Project proposal: TypoG

[Matteo]

Hi to all :)

I'm a t3-newbie (but a internet developer), so this wouldn't be the thread for me.. however I like very much the project and all the community, so I thought that giving a user-newbie point of view in this discussion may help the thread.
So, first of all, "pardon" for all the technical (deep or not) problems or advantages I don't touch..others are better skilled. (ah, second: sorry for my ugly english!)


The first thought, reading this, was: "WOW! Exciting! Great Bernhard!" (I think also most of you :) )
SOAP, synchronization, all things I've read about but never view at work.
The second thought.
The second thought was like Andreas Otto: "But there are more important things on the TYPO3 todo list than developing a fat client"
I try to explain: I know that all of us are free to develop (respecting rules etc) and most of us work programming and debugging Typo in spare time (or when they can). 
I have as primary "mental target" the growth of T3 in CMS world (I'm spreading the word as I can), and I think it would be a good (I don't know if first, but good) target for everyone :)
Perhaps if I was a developer my primary question would be: ok, typo is growing; how can we make our system more usable, more friendly, more consistent..how can we make thousands "Dassult-case study"? Not for earn money for us, but for growing! For have an opportunity to develop new features...I always think "one of the most user-friendly and amazing features, TemplaVoila, perhaps was developed primarily because partnership with Dassault" (but it's only a thought, I really don't know..)
For the not-t3-world there are some features very important, and my fear is that t3 could be in the next future a "powerful-but-buggy" or "not-coordinated" thing.
Real life example: I propose t3 as cms for a very big company client of the software house where I work. Why my boss don't choose this? Response: "no database support (other than mysql) already present and running for a long time, Templavoila bugged, lack of extension documentation, permission system not flexible." (I know, DBAL is coming, TV bug will be fixed ecc...but how about my boss?)
This is only an example (and please! this is NOT a j'accuse to any of you..I have great respect for all the devs!) to say: there are many features very important from the point of view of the "outside-typo world", and these features can make typo a fastly growing environment (I hope this!! :) ).
I may be in error, so one of this features could be "TypoG", but in my opinion one of the rule of thumb is: never forget about "common final users" triyng our system, perhaps a bit of our growth is in their hands. ;)

However, good luck...typoG can be a wonderful feature, anyway :)

- Matteo (ancem)

-----------------------
This thread is located in the archive at this URL:
http://typo3.org/documentation/mailing-lists/dev-list-archive/thread/110111788/
					
> Hi!
> 
> On Thu, 24 Feb 2005, Andreas Otto wrote the following:
> > Why not use QT for this?
> > Plattform independent, nice widgets...
> >
> > But there are more important things on the TYPO3 todo list than
> > developing a fat client ;-)
> >
> 
> Hmmm, another project that is condemned to fail... TYPO3 is not well
> designed (from a programmers perspective) (ok, it's PHP, that's another
> reason ;-)), otherwise it would be relatively easy to put another view
> above the "backend"... soooo you'll have to write much code!
> Thousands of lines... unpaid, as nobody really needs that...
> I think it will fail, but we'll see ;-)
> Bernhard is often good for a surprise ;-)
> 
> just my 2 cents...
> 
> 
> bye
> Wolfgang
> 
> ps: if you examine the dev-list threads you'll find so many good ideas
> that never made it to anything more than, .. uhm.. nothing ;-)
> 
> 
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
>