[TYPO3-ttnews] newscalendar & news vs. tt_news?

[Jordan van Bergen]

>I will quit answering here for some days as I am tired of giving always
>the same anwers over and over and over and over and over and over again.
>I hope we all get better things to do on a rainy sunday - at least me

I will do the same. I am on holiday abroad ;-) LOL But because of this
I have finally time to look at some things. One of them is TYPO3 and
what's going on with it. Normally I work 65 hours a week and have
little spare time. As you can see I had 1 spare day today and it was
time to put my frustrations on paper about TYPO3. I will stop after
this thread but know that users really look differently to solutions.
We speak a different language and this was very clear in the answers
to my question. 

I could (and will) reply one more time:

Please don't confuse other users by adding yet another news module ;-)
You see: we speak a different language. 

But let's end the discussion. I'm making a local backup of a website
using tt_news and trying to import the records into news to see what
news has to offer and if I can do what I can do with tt_news now. I'm
not starting from scratch and a lot of TYPO3 users have the same of
course. 

Last remark about speaking a different language: you tell users that
tt_news can still be used as YATNE (Yet Another Typo3 News Extension)
and standalone news extension. You are right but you are also wrong.
As "everyone" is telling in this typo3.projects.tt-news discussion
list that tt_news is not really maintained any longer and news will be
... what choice do you really have as an user? 

Don't reply please. Let's stop it but really know that we speak a
different language and we look at other things/solutions. 

Best regards,
Jordan

On Sun, 18 Sep 2011 18:30:06 +0200, Georg Ringer <typo3 at ringerge.org>
wrote:

>Hi Jordan,
>
>please don't confuse other users!
>
>Am 18.09.2011 17:07, schrieb Jordan van Bergen:
>> As news will be the follow up extension instead of tt_news nobody will
>> be working on tt_news anymore because of this. 
>
>news is *not* the follow up of tt_news. It is a standalone extension
>which does sometimes the same things but it is not the successor of
>tt_news. You can use both extensions in the same system on the same
>page. There is no conflict and no connection.
>
>> So we all should switch
>> to news and start using it but the most of us already have an up and
>> running system. 
>
>You should use the system and extension you need. If features are
>integrated into tt_news (or any other extension which extends tt_news)
>you can of course stay with tt_news. You can also stay with any other
>extension.
>
>There is no pressure or whatsover to use the news extension.
>
>> The newscalendar extension we sponsored won't be usable anymore within
>> news because of this being a total new extension  I assume? 
>
>Of course it is not usable with news, it is also not usable with
>extensions like mininews, news_plus,  news_flexible, tgm_news and some
>extensions I forgot which all do kind of the same: displaying news records.
>
>There are more extensions like tt_news.
>
>> What to do now? This is an example of the dilemma people face because
>> of the new news extension:
>> 
>> 2. having to pay again to have the same functionality of newscalendar
>> into news
>
>paying is not always the same as sponsoring, just to be clear.
>
>> 3. Stick to tt_news while knowing it won't work anymore soon. I
>> already see a lot of bugs and complaints about tt_news not working in
>> v4.6beta's. 
>
>but this is certainly not the fault of any other news extension! This is
>not my fault!
>
>5.) Let someone else implement the feature
>
>
>> Hope to let all of you see why I am so disappointed about what's going
>> to happen. 
>
>are you disappointed about all the other news extensions as well? Are
>you disappointed about jQuery because nobody else now uses mootools?
>Disappointed about DVD because no you can't buy any new VHS anymore,
>Bluray because of DVD. You know what I mean? There are always multiple
>solutions to a certain problem and of course better doesn't aways mean:
>better in every feature.
>
>> Maybe news is going to be the best thing ever happened to
>> TYPO3 but without an import from tt_news 
>
>damn that is not true.
>
>
>I will quit answering here for some days as I am tired of giving always
>the same anwers over and over and over and over and over and over again.
>I hope we all get better things to do on a rainy sunday - at least me
>
>over and out
>Georg