Elijah Insua wrote: >> Has there been any thought, discussion, or interest in providing >> jQuery as a backend, or being able to provide another library as >> another API to jQuery. >> > > > Sizzle might be of interest to you, although it is *just* a selector > engine.. > ya, I know about it. I actually had some fun writing my own selector system for the js framework being used in the project I'm hired to work on. I was going to do another for a new framework outside of the project, then I saw the selector system for jQuery was improved and turned into a different project. So I thought, maybe I'll just create the new framework and use Sizzle, along with adding in some new selectors and changing a few. Then I ended up reading over the code used in jQuery to do animations. Bleh, that was enough to make me dread the fact I have to write my own animation code for the framework used in the project at work. >> Beyond rolling a library as a modified API using jQuery as a backend >> does have potential use elsewhere. One of the special things about the >> system I have at work is that the JavaScript framework being used >> (since it's part of the system) can do nice things like taking a >> Widget object as input, and knowing how to handle the actual nodes >> it's associated with. >> > Dojo does have this sort of feature set.. however dojo is not 'light' > Maybe I'll look a bit more at sizzle... I wonder if it's able to work in a way where applications can feed in object types from itself and tell Sizzle how to handle them. >> nice, but only if you do it without losing information. Sometimes you >> go to far in shortening the size of code, and end up losing >> information that makes it readable." >> Along with that 'toggle' irks me as well. For the very well integrated >> jQuery user, "Huh, 'toggle', that just flips my visibility.", but for >> anyone that is just looking at the code "Toggle? What does it >> toggle?" >> > Basically the thought I've had is. "Keeping code short and sweet is > > > reading the documentation suggests : http://docs.jquery.com/Effects/toggle > > "Toggle displaying each of the set of matched elements." > > I don't know how one would properly use anything without reading the > documentation! > Well sure you read documentation, but at the same time it's good to stick with names that can't be misinterpreted. You do have to admit: $('#formtogglebutton').click(function(e) {$(checkbox).toggle();}); Would be a fair bit confusing to read of the #formtogglebutton was meant to show or hide a checkbox form element. > >> . Toggle could flip a checkbox, it could show or hide >> something, if it shows or hides something then how does it do it? does >> it slide, does it fade, or does it just disappear? >> Honestly toggleVisibility working like the .hide I mentioned above >> makes more sense to me. >> > > > $.fn.toggleVisibility = function () > { > return $(this).each(function() > { > $(this).toggle(); > }; > } > > > I hope this helps! > > -- Elijah > > > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com] -Nadir-Point (http://nadir-point.com) -Wiki-Tools (http://wiki-tools.com) -MonkeyScript (http://monkeyscript.nadir-point.com) -Animepedia (http://anime.wikia.com) -Narutopedia (http://naruto.wikia.com) -Soul Eater Wiki (http://souleater.wikia.com)
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
