Behaviour is not ready for real apps!

While the idea behind Behaviour is very good the realistic
use of the
library is not so good.

>From my real world test Behaviour is not ready to be
used in web apps.
Simply put it is very slow! Until the browser guys can make
their
browser query the DOM much faster there's not much that we
can do.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

Well even with the fastest library on the web (cssQuery)
it's still
very very slow :(


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

I disagree.  I'm not sure what you're requirements are,
but I've been
using behaviour for an app that deals with thousands of
elements.  The
trick is coming up with strategies that minimize overall
latency
(streamlined code, unrolled loops...), distract the user
(perform
intense computation when the user is busy with something
else), and
flexible code that scales to large numbers well.

My particular application dynamically puts items from an
arbitrary
number of collections on a map in real time.  There is a bit
of delay,
but it's not related to the performance of behaviour.

I'm currently preparing for use of either behavours or
event:selectors
(or whatever its called) on a big site for some large stuff.
 I'm more
concerned about the performance of scriptaculous than I am
about
behaviour/selector code.

Ben

On 6/22/06, xwisdom <xwisdomgmail.com> wrote:
>
> Well even with the fastest library on the web
(cssQuery) it's still
> very very slow :(
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

Benjamin West wrote:
> I disagree.  I'm not sure what you're requirements
are, but I've been
> using behaviour for an app that deals with thousands of
elements.

I couldn't agree more. IE's DOM performace sometimes
leaves a little to
be desired, but that just means I don't let it have some of
the fancy
effects that can slow it down. Once I got my head around
that and
minimising memory leaks (mostly due to the really helpful
people in
this group) Behaviour has been ace!

Cheers,


Olly.
http://thinkdrastic.net/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

Benjamin West wrote:
   <snip>
> I'm currently preparing for use of either behavours or
event:selectors
> (or whatever its called) on a big site for some large
stuff.  I'm more
> concerned about the performance of scriptaculous than I
am about
> behaviour/selector code.
   <snip>

   I used Behaviour and now using event:Selectors. Though I
like it
much I keep on getting "Stop the script" alert
in FF/XP quite often
whenever the elements are just above normal.

--
  <?php echo 'Just another PHP saint'; ?>
Email: rrjanbiah-at-Y!com    Blog: http://rajeshanbiah
.blogspot.com/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

That's where using clever strategies comes in.  For
example, if your
selector starts with an id, that makes it easier for the
routines to
locate elements.



On 6/25/06, R. Rajesh Jeba Anbiah <ng4rrjanbiahrediffmail.com> wrote:
>
> Benjamin West wrote:
>    <snip>
> > I'm currently preparing for use of either
behavours or event:selectors
> > (or whatever its called) on a big site for some
large stuff.  I'm more
> > concerned about the performance of scriptaculous
than I am about
> > behaviour/selector code.
>    <snip>
>
>    I used Behaviour and now using event:Selectors.
Though I like it
> much I keep on getting "Stop the script"
alert in FF/XP quite often
> whenever the elements are just above normal.
>
> --
>   <?php echo 'Just another PHP saint'; ?>
> Email: rrjanbiah-at-Y!com    Blog: http://rajeshanbiah
.blogspot.com/
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

Ben Nolan wrote:
> I agree  - I think xwisdom is a stupid troll but I was
trying to be
> diplomatic.
>
> Ben
>

Many thanks Ben.

I've built an Ajax App using behaviours and it does not
perform at
resonable speeds when certain pages are loded. I noticed a 5
second
delay before user can click on anything on the page. This
normal occurs
when this like a <select> box is loaded with aroun 100
options (yes
that's what the app requires) . I allow have tree that
loads a 500
nodes.

The delays occurs when the Behaviour.apply() option is
called after the
page content is fetch using Ajax. If I remove
Behaviour.apply() then it
loads very quickly but the newly loaded elements will not be
interactive.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

Benjamin West wrote:
> That's where using clever strategies comes in.  For
example, if your
> selector starts with an id, that makes it easier for
the routines to
> locate elements.
    <snip>

   Use of ids wouldn't be possible always. Say, in a case
where I'll
add popup routine to few links using
class="popup" or so.

--
  <?php echo 'Just another PHP saint'; ?>
Email: rrjanbiah-at-Y!com    Blog: http://rajeshanbiah
.blogspot.com/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

It's still possible if you are clever about it.  It's your
choice
whether or not you let behaviour go searching through your
entire dom.
 You can use the same function on several different
selectors, for
example.

As for hundreds of options being slow... again, I've used
behaviour in
apps with thousands of elements, not hundreds.  Behaviour
was not a
critical performance issue, not because it's performance is
good or
bad, but because I used all kinds of tricks and techniques
to minimize
the time it would take.  Most libraries will have similar
problems as
has already been observed several times, so it's not an
issue of
behaviour.js being mature or immature as much as it is that
the DOM
implementations and other browser features are immature or
mature.

Loop contructs have been around much longer than browsers. 
So by this
measure browsers are very immature compared to the
techniques we are
using to program.

Ben West

On 6/27/06, R. Rajesh Jeba Anbiah <ng4rrjanbiahrediffmail.com> wrote:
>
> Benjamin West wrote:
> > That's where using clever strategies comes in. 
For example, if your
> > selector starts with an id, that makes it easier
for the routines to
> > locate elements.
>     <snip>
>
>    Use of ids wouldn't be possible always. Say, in a
case where I'll
> add popup routine to few links using
class="popup" or so.
>
> --
>   <?php echo 'Just another PHP saint'; ?>
> Email: rrjanbiah-at-Y!com    Blog: http://rajeshanbiah
.blogspot.com/
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

Many than Olly and Benjamin for taking the time to highlight
a few tips
and tricks what I can use to make the app run faster.

I'll give these a try


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---

xwisdom wrote:
> Many than Olly and Benjamin for taking the time to
highlight a few tips
> and tricks what I can use to make the app run faster.
>
> I'll give these a try

That above should read:

"Many thanks Olly and Benjamin for taking the time to
highlight a few
tips
and tricks that I can use to make the app run faster.
"

I'm making some progress with the app as I go along. Many
thanks


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Behaviour Javascript Library"
group.
To post to this group, send email to behaviourgooglegroups.com
To unsubscribe from this group, send email to
behaviour-unsubscribegooglegroups.com
For more options, visit this group at http://group
s.google.com/group/behaviour
-~----------~----~----~----~------~----~------~--~---