Bill Keese | 4 Aug 06:09 2010

CSS vs. JS animations

I think for 2.0 we can get rid of most of dijit's JS animations and
replace them with CSS animations. But I noticed one case where it's
difficult, for fade-out, which currently happens for Dialog and Tooltip,
and has been a long standing request for drop downs. The problem is that
we need to know when the fade out is complete so that we can
display:none or move off screen.

Maybe a compromise is to abandon the fade-out animation and just do fade-in.

Just food for thought.
James Burke | 4 Aug 06:12 2010

Re: CSS vs. JS animations

Does ontransitionend help with that?
https://developer.mozilla.org/en/CSS/CSS_transitions#The_JavaScript_code

James

On Tue, Aug 3, 2010 at 9:09 PM, Bill Keese <bill <at> dojotoolkit.org> wrote:
> I think for 2.0 we can get rid of most of dijit's JS animations and
> replace them with CSS animations. But I noticed one case where it's
> difficult, for fade-out, which currently happens for Dialog and Tooltip,
> and has been a long standing request for drop downs. The problem is that
> we need to know when the fade out is complete so that we can
> display:none or move off screen.
>
> Maybe a compromise is to abandon the fade-out animation and just do fade-in.
>
> Just food for thought.
Bill Keese | 4 Aug 07:15 2010

Re: CSS vs. JS animations

Ah cool, I didn't know there was such an event.   I think that will 
solve it.   Of course we need to detect which browsers support that 
event, lest we be waiting forever.

On 8/4/10 1:12 PM, James Burke wrote:
> Does ontransitionend help with that?
> https://developer.mozilla.org/en/CSS/CSS_transitions#The_JavaScript_code
>
> James
>
> On Tue, Aug 3, 2010 at 9:09 PM, Bill Keese<bill <at> dojotoolkit.org>  wrote:
>    
>> I think for 2.0 we can get rid of most of dijit's JS animations and
>> replace them with CSS animations. But I noticed one case where it's
>> difficult, for fade-out, which currently happens for Dialog and Tooltip,
>> and has been a long standing request for drop downs. The problem is that
>> we need to know when the fade out is complete so that we can
>> display:none or move off screen.
>>
>> Maybe a compromise is to abandon the fade-out animation and just do fade-in.
>>
>> Just food for thought.
>>      
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors <at> mail.dojotoolkit.org
> http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
>    
Bill Keese | 4 Aug 08:53 2010

widget watchable properties

I started working on watch() for widgets. My plan was to use it whenever
possible, even for read-only widget state like focus, whichis currently
reported via the onFocus()/onBlur() callbacks.... so that you could do

myWidget.watch("focused", function(name, oldVal, newVal){ ... });

Does that seem like the way we want to go for 2.0, rather than having
onFocus/onBlur callbacks? (In any case the callbacks will be supported
until 2.0, for back-compatibility.)

The advantage of treating focus as a widget "state" is that you can call
get("focused") to check the state, in addition to using the watch
callbacks. The disadvantage is that it doesn't mesh with event callbacks
like onClick.

Also, "focused" as a readonly widget attribute will match other boolean
attributes like "open" for TitlePane's.
Bill Keese | 5 Aug 05:32 2010

wave goodbye

Looks like goggle wave is being shut down
(http://www.ft.com/cms/s/2/c8d0b62e-a01e-11df-81eb-00144feabdc0.html) by
the end of the year.

We have a few dojo conversations there that need to be moved, a 2.0
thread and maybe something about the website? Maybe move to google docs,
or to the mailing list, which is after all our de facto place for
discussion. Actually I've been keeping 2.0 notes in google docs.
Eugene Lazutkin | 5 Aug 06:32 2010
Picon

Re: wave goodbye

It is a big blow for GWT inside Google I guess.

I am pretty sure that we are not alone in this. I suspect we will see
several backup tools for wave before it goes out. Google Docs is my
second choice, so we'll migrate there unless somebody has better idea.

Cheers,

Eugene Lazutkin
Dojo Toolkit, Committer
http://lazutkin.com/

On 08/04/2010 10:32 PM, Bill Keese wrote:
> Looks like goggle wave is being shut down
> (http://www.ft.com/cms/s/2/c8d0b62e-a01e-11df-81eb-00144feabdc0.html) by
> the end of the year.
> 
> We have a few dojo conversations there that need to be moved, a 2.0
> thread and maybe something about the website? Maybe move to google docs,
> or to the mailing list, which is after all our de facto place for
> discussion. Actually I've been keeping 2.0 notes in google docs.
David Schwartz | 6 Aug 22:00 2010
Picon

IBM ORIA Team v.1.6 plans

As was requested during Wednesday's meeting, here are the IBM ORIA team's original plans for Dojo v.1.6. This will have to be re-evaluated given the significantly shorter runway available to us than we anticipated.

https://docs.google.com/document/pub?id=14gqarV_esfF5JkNxAR_gl7d8UCY6zKFIQtnQXfvGa88


Thanks,
David
_______________________________________________
dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
Tom Trenka | 12 Aug 18:58 2010
Picon

Link for the Etherpad + Dojo 2.0 discussion

Hi all,


I figured I'd post the link for the public/Etherpad DTK 2.0 discussion here:


regards--
Tom
_______________________________________________
dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
Eugene Lazutkin | 13 Aug 11:05 2010

Fwd: JetBrains' WebStorm's group license for Dojo

For those of you who do not attend our weekly meetings (you know who you
are, and we know you too!):

Dojo as an open-source project got a free group license for JetBrains'
WebStorm. JetBrains is the company behind InelliJ IDEA --- probably the
coolest Java IDE around. They branch out into other languages and
recently released WebStorm --- IDE for web developers with enhanced
support for JavaScript, HTML, and CSS. It includes a bunch of usual
goodies like refactoring and what not, but my personal favorite is the
ability to cross-reference names, which is faster and better implemented
than in other IDEs I tried.

On top of that WebStorm has Dojo-specific features --- it understands
Dojo-style structured comments for enhanced code-completion (e.g.,
parameter types) and quick doc lookup. Basically we are supported on the
same level as JSDoc. I don't know any other IDE, which has this feature.

The home page for WebStorm is http://www.jetbrains.com/webstorm/ --- you
can read more about it and even download 45-day free trial. If you like
it, write to me and I'll send you a free license, *providing* that you
are a *contributor* of Dojo
(http://docs.dojocampus.org/developer/contributors) and use it *strictly
to work on Dojo*. If you need it for other personal needs, I am sure you
can afford $40 for a copy.

Cheers,

Eugene
Karl Tiedt | 16 Aug 01:53 2010
Picon

Interesting annouce on node.js ML - [nodejs] ANN: UglifyJS, a JS parser/compressor/beautifier

Thought this might be interesting to James and the others that play
with the build system... maybe nix our JVM requirements is possible
with this?

-Karl Tiedt

---------- Forwarded message ----------
From: Mihai Călin Bazon <mihai.bazon <at> gmail.com>
Date: 2010/8/15
Subject: [nodejs] ANN: UglifyJS, a JS parser/compressor/beautifier
To: nodejs <nodejs <at> googlegroups.com>

Hopefully this is a welcome addition to the Node package list.

http://github.com/mishoo/UglifyJS

It includes:

- a tokenizer/parser that produces a clean AST from JavaScript code.
A lot of interesting stuff can be done once you have an AST. ;-)  The
parser itself is ported to JavaScript from Common Lisp [1].

- an AST mangler, compressor and code generator.  It's a lot faster
than YUI compressor and GoogleClosure, it compresses better than the
YUI compressor and it's safer than GCL. ;-)

[1] http://marijn.haverbeke.nl/parse-js/

Have fun!

-Mihai

--
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs <at> googlegroups.com.
To unsubscribe from this group, send email to
nodejs+unsubscribe <at> googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en.
_______________________________________________
dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Gmane