Javascript in Tortuga, what will be the official toolkit?

1 view
Skip to first unread message

Lee Olayvar

unread,
Jan 4, 2009, 2:26:58 PM1/4/09
to tortuga...@googlegroups.com
I swear i have asked this before, but it is not showing up in any searches i am attempting.. (http://groups.google.com/group/tortuga-coders/search?group=tortuga-coders&q=jquery&qt_g=Search+this+group). Not to mention i don't recall Ian himself answering directly.

So with that said, what will be the officially used toolkit inside the source of Tortuga? I know Tortuga will not have a required toolkit, but i am sure it will include a toolkit with it to have built in ajax/js effects built into the cms for core plugins, etc. Now i used to think Ian was going to use JQuery, but as i was digging i ran into a post in Pagoda about a switch to Dojo (http://groups.google.com/group/pagoda-talk/browse_thread/thread/3e380cba2cd7d46b).

I just want to know so i can actually get a good grasp on whatever framework is chosen. I will be starting one of my bigger projects now, and since its from scratch in TG2, it'll be nice to use the proper framework ahead of time, and limit the conversions needed(wanted, i should say) when changing from full TG2 to a true Tortuga-Plugin.

(Also, been rather quiet on the tortuga front, would be nice to get a small update :)

Happy Holidays All!

Thanks,
--
Lee Olayvar

Ian Charnas

unread,
Jan 8, 2009, 10:55:06 PM1/8/09
to tortuga...@googlegroups.com
It does look like we will be going with Dojo. I've used all the
major JS frameworks in projects, from YUI to EXT to jQuery to Dojo to
Mochikit to Scriptaculous, you name it. It used to be that Dojo
wasn't an option because it was rather large and slow, but times are
a-changing. The new speed, coupled with the existing widgets and
themes and accessibility, makes it very compatible with the goals for
Tortuga. Also this is going to be the default for
TurboGears/ToscaWidgets, so that's another benefit.

I just released the 0.1 final version of Checkpoint, and now I'm
getting ready to release the next developer's preview - which will
contain just about all of the back-end code except for a finalized
rendering system (the current rendering system is just a plaything).
Look for an email tomorrow!

ian
Reply all
Reply to author
Forward
0 new messages