[TYPO3-hci] 4.1 = menubar/iconbar/dashboard; lets go!

Kasper Skårhøj kasper2006 at typo3.com
Thu Oct 12 10:25:25 CEST 2006


Thanks for your view Elmar, I don't expect you to invest your  
resources into something you don't believe in. I feel exactly the  
same way which is why I will continue to do what I think is right or  
good enough to scratch my itch.

- kasper



On Oct 12, 2006, at 9:58 , Elmar Hinz wrote:

> Kasper Skårhøj wrote:
>> Hi Folks,
>>
>> The week before the TYPO3 conference I spend 5 days playing around  
>> with
>> prototype library and scriptaculous and implemented the first  
>> draft for
>> the menu/icon bar we have kind of agree to do. In addition I'm  
>> trying to
>> see if I can get my head around the framework for a dashboard.
>>
>
> Hi,
>
> I need to tag this moment, cause it is an interesting one. With the
> decision to choose client side programming a decision has been  
> made, not
> to develop TYPO3 towards real accessibility, but away from it. I
> personally think this is a wrong step, because accessibilty is of
> imporatance today even for the backend of a CMS. Accessibiltiy is much
> more than building pages for blind people. It is a way of thinking,  
> that
> in general and on all levels leads to better pages and results for
> everybody.
>
> Also more programming will be doubled in the client and in the  
> server. A
> pattern of programming of the past is continuid that was justified in
> times, when AJAX wasn't available, but isn't in place today. Typical
> bugs in the TCE caused by conflicting evaluations in server and client
> will stay for longer, like that with float numbers.
>
> I think it wouldn't require extra work, to choose a trak to get a  
> better
> backend that develops into a direction of a broader accessibility. It
> would merely require a decision to do it. In this moment a chance is
> passing by and isn't taken.
>
> Reading the contribution in this list indicates to me, that there are
> still to few heads in the TYPO3 community aware of this. The train is
> currently rolling into a track that does a detour of one or two years.
> Some people and companies will decide for other systems in the  
> meantime,
> provided that alternatives become available. It is not the end of the
> TYPO3 project just a detour and maybe my estimation is wrong.
>
> I don't will make an effort to lead the train onto the other trak  
> here,
> because I don't see enough heads, that could run it there. So it would
> not be a rational try. I just want to tag the moment. I will stand
> beside, smilling that a better trak could have been taken but is  
> not. I
> wonder how long the detour of TYPO3 will take and when the project  
> finds
> back to the direct way.
>
> I think it's obvious that I will not invest my personal resources into
> something that seems like a detour to me. So don't expect my  
> support in
> this field there are other things to work on.
>
> Regards
>
> Elmar
> _______________________________________________
> TYPO3-team-hci mailing list
> TYPO3-team-hci at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-hci

- kasper

"Necessity is the mother of invention"
-------------------------------
kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej |  
gizmo: kasper_typo3








More information about the TYPO3-team-hci mailing list