[TYPO3-50-general] extJS Library

[Thomas Fritz]

I wanted to say that i also think that there should be a convenient
abstraction layer in the Framework so theoretical every Javascript Lib can
be used and such a PHP OOP Integration is possible for other JS Frameworks
too. So no one has to learn another Lib one doesn't like. Of course.

On Sat, Jan 31, 2009 at 11:35 AM, Thomas Allmer <at at delusionworld.com>wrote:

> hey,
>
> I really believe that progressive enhancement is the way to work with
> javascript. You can find a hole bunch of articles to explain it's
> benefit. Here is a short presentation[1] from 2006 (dam it's old but
> still works) that gives you the basics in 2 minutes.


I have to agree with you in "progressive enhancement". But i think there are
other cases where it is not always possible or necessary. I agree with you
when you create a Website and you do some nice javascript things like
effects, animations, some content loading via ajax. Because in such a case
it is really important to use common standards so browsers display your
website in the right way and also search engines can index your site better.
We all know the benefits of it - hoper so.
Such a case can be a web application within a companys intranet. It is
important that the application works like it should work on the browsers
they use - Thats it. Of course, especially in such web applications
technical design is very important. Even though i am not really a fan of
creating the whole HTML Markup with Javascript but whats wrong about it?
When it is the right way to do it in a specific situation - why not?

But the point is - a Framework should never dictate too much. And thats also
true for JavaScript Frameworks. So as i said in the beginning i think a good
abstraction layer which works for the most popular javascript frameworks
should be a first goal. And on top of such a layer there can be an ExtJS
Integration, a MooTools Integration and so on so you can work with FLOW3 and
in every case you can choose the _right_ tools to work with.


>
>
> If you really wanna get into it there is of course way more to read
> about it. For example "A List Apart"[2] explains it pretty good (read
> also the first article mentioned at the beginning to get the idea).
>
> The reason I'm writing this here, is that it seems that ext isn't really
> good at progressive enhancement. (It just seems to me(!!) like this. I
> haven't used ext at all - just looked at the examples and at the current
> TYPO3v5 or the AOPBrowser code).
>
> To relative the above "insult" I can just repeat Aaron N.[3],[4]:
> "So now, when people ask me why I think MooTools is the better choice,
> I'll still tell them that it's not about what's better than the next one
> [...] All the frameworks achieve similar goals in different ways, but,
> [...] I, personally, prefer to author my work in shallow, extensible
> classes, and [...] The fact that MooTools itself is written this way has
> trade offs, which is why choosing a framework is so much a matter of
> personal preference."
>
> So, as you my guess my personal preference is also MooTools. I choose it
> for the same reason as Aaron N. It's about heaving the possibility to
> write OOP code that looks nice to ME.
>
> == what I want ==
>
> So what I want with all this.
> First: I want you to see the short presentation[1] and decide to create
> things in HTML and anyone can take his personal javascript to replace
> you enhancement javascript (so no extensive creation of dom elements in
> javascript or inline javascript code)
>
> Second: Just have a look at another presentation[5] go to Minute 37 and
> follow it for about 10 minutes. Maybe you also see the same beauty in
> the code as I am.
>
> == conclusion ==
>
> I don't want to choose the javascript framework for your TYPO3v5.
> However I would like to say that please keep in mind that others might
> want to port it so don't create everything with javascript only.
>
> If you need any more info about MooTools or have any javascript related
> question I would be more than happy to try to answer them as good as
> possible. I just don't want to have this "javascript nightmare" (sorry
> about that, but it's like that for me) as we have in TYPO3v4.
>
> cheers
>
> [1]: http://domscripting.com/presentations/xtech2006/
> [2]:
> http://www.alistapart.com/articles/progressiveenhancementwithjavascript
> [3]:
>
> http://www.clientcide.com/best-practices/jquery-and-the-ajax-experience-programming-to-the-pattern-and-what-really-makes-one-framework-different-from-another/
> [4]:
>
> http://www.clientcide.com/best-practices/how-many-flavors-of-linux-are-there/
> [5]:
> http://www.clientcide.com/uncategorized/my-mootoo
>
> 12
>
> ls-talk-from-the-ajax-experience-2008/<http://www.clientcide.com/uncategorized/my-mootools-talk-from-the-ajax-experience-2008/>
>
> --
> +---------------------------------+-----------------------------------+
> | Thomas Allmer                   |   http://www.delusionworld.com    |
> | E-mail: at at delusionworld.com    |   phone: +43 699 16217064         |
> +---------------------------------+-----------------------------------+
> _______________________________________________
> TYPO3-project-5_0-general mailing list
> TYPO3-project-5_0-general at lists.netfielders.de
>
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-5_0-general
>