Mixing and matching frameworks

There are so many excellent frameworks out there, each with
its own
disadvatnages and
benefits.  It's really difficult to evaluate what to use
when and
where, and obviously they won't all work together.

I think the first decision you have to make is:

Am I going to use Stephenson's prototype?

That'll determine whether you can go with complete framework
replacements like
mootools or whether a prototype based solution like Rico is
the right
path.

Even then, there are those that prefer to use
proto/behaviour and
script.aculo.us

other other effects only libs.


Has anyone encountered specific issues with using Ben
Nolan's behavior
lib at the
same time as using Rico or other All-Up frameworks?


--~--~---------~--~----~------------~-------~--~----~
 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:/
/groups.google.com/group/behaviour?hl=en
-~----------~----~----~----~------~----~------~--~---

Ash,
There are no issues using prototype.js with behaviour.js.  I
use both
together all the time.  If you want behaviour.js's
functionality with
performance tweaks tuned for prototype.js, consider using
event-selectors.

Ben

On 11/12/06, Ash <raiteriagmail.com> wrote:
>
> There are so many excellent frameworks out there, each
with its own
> disadvatnages and
> benefits.  It's really difficult to evaluate what to
use when and
> where, and obviously they won't all work together.
>
> I think the first decision you have to make is:
>
> Am I going to use Stephenson's prototype?
>
> That'll determine whether you can go with complete
framework
> replacements like
> mootools or whether a prototype based solution like
Rico is the right
> path.
>
> Even then, there are those that prefer to use
proto/behaviour and
> script.aculo.us
>
> other other effects only libs.
>
>
> Has anyone encountered specific issues with using Ben
Nolan's behavior
> lib at the
> same time as using Rico or other All-Up frameworks?
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
 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:/
/groups.google.com/group/behaviour?hl=en
-~----------~----~----~----~------~----~------~--~---

On Nov 13, 7:02 am, "Benjamin West" <bew...gmail.com> wrote:
> There are no issues using prototype.js with
behaviour.js.  I use both
> together all the time.  If you want behaviour.js's
functionality with
> performance tweaks tuned for prototype.js, consider
using
> event-selectors.
   <snip>

    I know for sure that event:Selectors is too slow; when
using
Prototype.js, it's better to use Low Pro. You might be
knowing that I
documented it at
<http://rajeshanbiah.blog
spot.com/2006/09/behaviorsjs-alternative-to-behaviourjs.html
>

--
  <?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:/
/groups.google.com/group/behaviour?hl=en
-~----------~----~----~----~------~----~------~--~---