But you don't need the compat layer if there's no existing Moo code.
Thank you for the extra pair of eyes on this Sergio! I also found a
couple more and fixed them, which brought the player back, but now
it just sits there stuck on the first image. I have scanned all the
files and don't see any other problems. Do you see anything? I
appreciate you looking for
Are you all clear on this now? I hate to leave people confused about what is
and isn't valid modern HTML.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an
[No need to CC: me directly as I use the list via -mail.]
Thanks for the help. Actually, I misspoke. I was using the validation URL
you provided.
For some reason, I thought it was W3Schools.
Well, the validator is not case-sensitive, so I don't know how you got
a failure.
Here is the very
Hi all,
A longtime client of mine (for whom I do db and infrastructure work,
not front-end) has a full-time opening for what they describe as an
HTML/CSS developer with growing scripting responsibilities (you would
be replacing an person who had her going-away party yesterday).
They're a
2. One problem could be that its onload not onLoad.
HTML attr names are case-insensitive, so w/inline events it doesn't
matter.
Still better to use lowercase for script interaction, though.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
The error's saying ID top already defined. Ok, I understand,
IDs are supposed to be unique. But when I change
it to class=top it stops working.
Don't really understand the conundrum. The browser's automatic
hash-based scrolling (which happens without JavaScript, but on which
smoothscrolling
#2 I'm putting the following in the head of my doc and it's not working:
window.addEvent( 'load', function() {
ScrollLinks.start()
});
I guess I can't do it like that?
That's the way to do it; what error do you get in the JS console?
http://jsfiddle.net/Ajr35/1/
Thanks much @D_mitar.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mootools-users+unsubscr...@googlegroups.com.
For more options, visit
If you can come up with some environment in which this can be debugged
remotely, I'll look at it. However, I don't use Socket.io myself and
it's a bit much to start using it to check out this issue.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
I have make you SSH account in my test bed, how can I pass you the
credentials?
Mmm... can we see what Dimitar comes up with first?
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop
I might be wrong, but these are invalid css values. Choose 'repeat'
or 'no-repeat' and 'auto' or '100%', not both!
Actually, they are valid CSS values -- when the browser supports
multiple backgrounds.
That's the source of the error. IE8 fails because within IE8,
backgroundRepeat is a known
When I inspect the problem, I seem to get an awful lot of these:
Uncaught ReferenceError: _ is not defined
Surely this is because Underscore (a different, complimentary JS
framework) is not being loaded, not Moo.
That in turn seems to be because RequireJS isn't finding it.
Where do you see
Thanks for the tip. I looked into the underscore file and for some
reason the code was missing within the .js file. Very strange.
Yes indeed.
But now I've replaced the code, the site seems to be very jittery
whilst scrolling. Do you think that this might be a Mootools issue?
Hard to say.
Please put this in a jsFiddle and the problem will be easily apparent.
The code/markup you supplied isn't sufficient to replicate this.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop
Unfortunately, I'm on a DoD network, and jsfiddle is blocked.
OK, then just paste runnable markup/code and we'll make the Fiddle.
With all these functions that don't exist it is basically impossible
to test your setup.
-- S.
--
---
You received this message because you are subscribed to
My hope is that this interests the MooTools community.
Yes. Yes it does.
Well, me at least! Thanks for posting.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it,
Solved off-list via search/replace as above.
(Wow, Joomla! really does love late static binding + dynamic function
name assembly, eh?)
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop
What I need to know is; Which files within Joomla Site, or which third party
extensions, do I need to search in.
Do you know the name of your template? You're not giving us much to go
on.
You can't go wrong by searching every .php file and doing a
search-and-replace.
-- S.
--
---
You
Joomla Forums have not been of much help, even though it was the
Joomla upgrading process that produced this resulting Error.
A core CMS upgrade isn't trying to upgrade your custom code, and that
is good.
You have to know where themes are, though. Neither Aaron nor I know
where exactly to
As far as I can see, all extensions are up to date.
They may be, but up to date just means their own latest version, not
that that version is compatible with Joomla! 3.
What I'm not understanding is why you aren't simply searching all your
PHP files for the old function call. You _cannot go
OK, contact me off-list if you want... maybe you're using a
regex-capable search app and you're not properly entering (escaping)
the search string.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group
OK, You want to search for
JHtmlBehavior::mootools()
and replace with the new
JHtmlBehavior::framework()
If this fixes the error, I still can't guarantee this is the only
problem you are having, because Joomla might just stop on a later
error. But this should help you get
The decline of MooTools rests on the MooTools core devs and no one
else.
Yep, it is/was principally an internal problem (including the
community as well) but I think you're whitewashing if you think
Microsoft didn't buttress jQuery *in part* because jQ couldn't
possibly compete design-wise
on jQuery to a dead mailing list you could try contributing to MooTools or jQuery to make them better, maybe get MooTools to version bump to support IE11 while you're at it.
- JDDOn Tue, Dec 24, 2013 at 2:40 PM, Sanford Whiteman sa...@figureone.com wrote:
The decline of MooTools rests on the MooTools
It's not trolling to defend the reason this list exists.Trolling is deliberately injecting negativity into a discussion among friends of an idea or of a product in order to provoke a response: the disrupt-and-get-the-popcorn approach. I can think of few better examples than chiming in on a list
Something else left out of the Hater's History of Moo.
Perhaps general distraction and disillusionment of the core devs
brought maintenance to a standstill, but there was a specific major
issue: it had been decided that Moo.next would *definitely not* extend
natives. This meant that fixing and
I've been around before you and will be around long after you lose
interest in going tit for tat in this mailing thread.
I'll grant that you can sustain your present level of service to the
MooTools user community for a very long time: I see a grand total of
one (1) message from you to this
Sorry I miss-spelled your name Arian
Actually the Moo-Boo layer is Aaron (Newton)'s.
I feel ya though!
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an
This old 1.11 demo page handily demonstrates this:
http://demos111.mootools.net/DomReadyVS.Load
It does?
I don't see it.
http://jsfiddle.net/W7e22/5/show/
In Chrome 25, 30 (Windows) I can't break it.
-- S.
--
---
You received this message because you are subscribed to the Google
If I later find out that something is a Cow, how can I change it to
be so? I know the once frowned upon method of setting __proto__
works in non-IE, but is there another way, or through MooTools? I
only need IE9+ support.
MooTools can't do anything as deep as creating __proto__ where it
Maybe a little more encapsulation if you felt like it (I don't like
how critical `var`s end up lingering outside linked sequences
sometimes):
var show = {
start : function() {
carousel.next();
show.continuous();
},
There appears to be a bug in the Sortables.serialize() method. If
you do not specify the 2nd parameter, it returns null for each item
in the list. Am I doing something wrong here or is this a legitimate bug?
serialize() returns an array of strings -- the ids of the elements --
not an Elements.
Search the archives of this list for my posts that involve XML and you'll get at least a few pointers (I'm on the road so can't find the salient points right now). I can check more tomorrow.-- Sandy
--
---
You received this message because you are subscribed to the Google Groups MooTools
Check this Fiddle out:
http://jsfiddle.net/sanford/5YS66/5/show/light/
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
You should never use two libraries together. You won't ALWAYS have
issues, like this, but the chances are high that you will. Usually due to
conflicting variables.
IME, the chances are more intermediate than high.
jQuery.noConflict(), using document.id in place of Moo's $(), and
using the
It is not working in IE7, 8, or 10. Any suggestions?
(1) What is the actually error in IE (8, for example)? Using SEH makes
it impossible for you to get errors logged to the console... try-catch
is fine for production but is only hindering you here. I'd need to
know where it says it's throwing
1- Since it was never meant to run under anything less than IE9, I
get a 'inspector.source' is null or not an object message.. that's
it. Even when hard-coded into the HEAD tag.
You didn't mention at first that you're trying to run something that's
documented by the developer to _not work_.
According to another developer that I've been asking about this:
IE has no event order management system, it is totally random.
That is (a) an overstatement and (b) may not be relevant to this
issue. You have no proof that it has to do with event firing order, do
you? Just pointing out
The problem turns out to have nothing to do with event triggering
order (nor with any quirk that isn't widely known about IE).
All you actually needed to do was
• comment out the check that begins // Ensure pre-requisites are supported on
Line 18
• any line that calls addEventListener needs
OP says it works in Chrome, which suggests that Moo is technically loaded in all cases but is hitting a security sandbox in FF.latest. Unless there some browser sniffing code which prevents from even loading in some UAs.-- S.
--
---
You received this message because you are subscribed to the
Can you please provide (preferably) a jsFiddle with your modal class
in it to demo the problem, or at the very least a link to the .js
file? While I have a pretty good idea what the problem is, I can't
really debug something without the library code.
-- Sandy
--
---
You received this message
Plus, it's for DoD; my development system is isolated from the
internet, so I can't copy/paste anything. The .js file that creates
the class is quite large (340 lines of code.)
Doesn't matter to me how big it is, but there's no way to fix it if I
can't see it.
-- S.
--
---
You
// too much code to type
Seriously?
Normally I'd jump to help out, but if you can't provide the actual
code I'm gonna back off.
Like Dimitar said,check the changelog
http://www.mozilla.org/en-US/firefox/23.0/releasenotes/
You might look into the change regarding CSP:
I'm sorry.. do YOU have time to type 340 lines of code to get help
with something that you're having issues with?? I seriously doubt it.
If I couldn't fix it myself, sure. Such are the terms and conditions
of getting free support.
You are the one who said that you suspect you know what it is
It's likely (though not certain) that they are both attempting to use the $
macro, so try
jQuery.noConflict();
after jQ and before loading Moo.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group
You may not even realize it, but you had to become a better raw JS
developer to get MooTools, and it's to your credit that you didn't
flinch.
I didn't mean to imply that only experienced devs could learn
MooTools, but rather that that was the group most vital for publicity
because they would be
MooTools itself isn't that interesting anymore
Show MooTools code to a jQiddie who's never seen it before, but who is
actually proficient at OO, and I guarantee they'll find it
_interesting_. They won't both learning it because it won't get them
hired, but that's just self-interest. MooTools
I'm with you completely. I always demo with MooTools to try to show
people who've never seen something so clean what else is out there.
But at this point they actually perceive it as hard-to-read because
it's different. Even people that are real OO (.NET) people somehow
can handle reading/writing
getSelected()[0].get('text')
http://jsfiddle.broadleafsystems.com/urnD5/1/
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I forgot to get the mutex on the mailing list, damn. :)
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mootools-users+unsubscr...@googlegroups.com.
For
think you won by a second. meh!
Huh, I thought you won, but I had a Fiddle.
Cheerz...
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
runAll() is not normally what you want as it subverts the concurrent request
limit (it short-circuits smart queueing). The method has a disproportionately
attractive name.
I don't see a bug in it, though, it's just not clearly documented (the class
should have clearer standard use/special use
Ive tried a few things using FX and FX.Tween but I cant seem to get
any response when trying to use the box-shadow CSS property.
I think your problem is alluded to here:
http://stackoverflow.com/questions/3012899/box-shadow-is-there-a-box-shadow-color
There is no separate property for each
Please put an example in jsfiddle.net to check out. There is certainly
nothing in Moo that will break for-in in JS.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it,
Very nice!
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mootools-users+unsubscr...@googlegroups.com.
For more options, visit
Sorry to leave your post hanging... you might consult the official
demo code for chaining and delays -- http://jsfiddle.net/6YeKf/.
-- Sandy
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop
Yep. other people are also concerned/confused:
https://github.com/mootools/mootools-more/issues/1158?source=cc
I think this thing works a bit strangely. You still have to send()
your requests until there are too many concurrents, and only _then_
will the queue fill up. The queue
1st problem :
This means that the droppablesoption in Element.makeDraggable must
be refreshed. I did not find on the net and the http://mootools.net
any informations about how to do this. The call of checkDroppables
in the onDrag function does not deal this thing. So I looked into
the source
I've been known to do it like this:
var reusecb;
document.id( 'myInput' ).addEvents ({
blur: reusecb = function(e){ alert( 'event: '+e.type ); }
, mouseout: reusecb
});
Obvs. it's also just saving the reference to the function obj but
helps me see the function definition as an event
Can you put up a jsFiddle for this?
-- Sandy
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mootools-users+unsubscr...@googlegroups.com.
For more
Whilst this is all true, it should be negated by your access
authentication and authorisation schema: no bot should have permission
to change anything, because no non-authorised user has permission to
change anything.
I consider HTTP method safety, method idempotence, and change
Hartum, something else to keep in mind: JSONP implies GET, and GET should be
implemented as a safe method (safe == not substantively altering server state
-- think updates to transactional databases).
This guideline should be followed _whether or not_ you are sending stuff like
A php script is always pending and will push a data to the browser
once detected a changes in the database (And its already done). But
the problem is I cant catch the pushed data in onSuccess event or in
onComplete event of Request object.
This pattern is called Ajax long polling. It's quite
It can return 10 data in different time(more like a delayed loading
of data, but data loaded is based on the changes in the database).
But that data cant be catched by Request handler.
In this case, you're looking at streaming approaches such as HTMLFile
in IE and Server-Sent Events on other
Do you have a jsFiddle?
-- Sandy
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mootools-users+unsubscr...@googlegroups.com.
For more options, visit
Geez guys, I thought I was just that guy who loves the IE8 Dev
Tools. :)
Have a great weekend!
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
That is indeed what I have done but I was interested in the how and whys and
Ive been enlightened!
Just for tidiness, what Johnny was referring to:
http://jsfiddle.net/CjNyJ/4/
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users
Heh, thanks for seeing it my way.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mootools-users+unsubscr...@googlegroups.com.
For more options,
getElementById is probably simply restricted to the DOM.
Not really, it is restricted to _documents that have a known attribute
of type ID_. Simply having an attribute called `id` doesn't make it an
ID: that's the root cause.
If you wrap your returned (X)HTML with proper NS and DTD (and you
I 100.00% support using VM UI for this. It is an accomplished effort, and
having built it even while MooTools was in the publicity crisis we are
currently addressing, I think Benjamin deserves this reward. And all the
better if people get come to know the VM UI look on other sites over time.
If the browser recognizes real, NSed XML in the Ajax response and the linked
DTD has `id` as an ID... you will be able to use getElementById on it. This is
old-school Ajax, when the x had one meaning.
Getting there is the fun part.
As you're building the server from scratch, you should be in
OK, found my old work on IE XML for your continued reference.
http://jsfiddle.broadleafsystems.com/FrTQc/21/
Uses getElementById when available, falls back to selectSingleNode
otherwise. Then also runs w/Slick if possible.
I also do a getElementById on similarly structured HTML markup
http://felixge.de/2013/03/11/the-pull-request-hack.html
Interesting post. It at first seems radical, but on further reading
Felix is clear that he means that quality, bug-free code is a
prerequisite for committer status -- and that status can still be
revoked. So while it's less despotic than
Cool, enjoy it over there... maybe someone can help you understand
https://groups.google.com/forum/?fromgroups=#!searchin/mootools-users/destructing$20views/mootools-users/sPtml4mGFvA/jvv0JO3MxFQJ
-- S.
--
---
You received this message because you are subscribed to the Google Groups
LOL, allow me to plug my own coinage from last year: jQiddies.
Chad, I like the snark: I guess we are not that smart. We like stuff
that is simultaneously elegant, simple, capable, and extensible. Maybe
someday we'll get smart. :)
And thanks for the personal CC's, guys. Reassures me that we have
And posting this to the newsgroup is useful how? You don't come here to help
the community, just to declare it dead? Just SEO spam by another name,
methinks.
Then there's your n00b interpretation of commit rates and questions asked.
First, comparisons to 800lb gorillas are rarely
That's not to say it's better code (I don't think it is), but it's a
more successful product in almost every way.
I can't remember ever _celebrating my use_ of a product that has
crappy internals when I know I'm using it just because most people
do.
There is nothing, absolutely nothing to
I was about to report some 404s as well -- Benjamin, maybe you should fade out
those pending links.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
Perhaps you'd be better off leaving data read-only in the onRequest()
phase and overriding initialize() instead, like so:
http://jsfiddle.broadleafsystems.com/sanford/pUeTs/
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
so what's the correct format of url ???
Depends on the relationship between the URLs of the two pages!
If your main page (from which you make the AJAX call) is right off the
web root at http://example.com/main.php, and the AJAX service is at
http://example.com/services/myservice.php, then you
All that, plus I don't understand why a Moo Class is not being used here.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
If you Element.set('text',...), the string will be HTML-escaped (corresponds to
native innerText).
It sort of sounds like you want to parse the response as (X|HT)ML before
injecting it into the DOM, rather than escaping the markup tags. You can do
this, with some cross-browser quirks, by
Sorry Sandy, I will try to use jsFiddle again. Hope I get you to help me
again... Thanks you.
Please try, it helps separate our concerns, if you will.
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this
Carl, you really, really, really need to get in touch with the notion
of relative paths, including scripts etc. You can't just go dumping in
script tags, img srcs, CSS background-images, etc. that are all
404 errors.
I have just now gotten the Fiddle into a more workable state; the
slideshow is
Nice solutions; I think the one with the delay is the keeper. Even
better would be exponential backoff delays.
@rlk27, it's not fair to client nor server to fire requests in a tight
loop (no delay). If your server routinely fails and recovers within
the same second, there's something much worse
Yes you are right. There always should be a delay, but I just
wanted to make clear the point how it's done and doesn't provide a perfect
solution :)
Sorry, didn't mean to critique. More @rlk27, I wanted to point out how
important the delay is, because if you choose to machine-gun a server
Put this in a jsFiddle and I guarantee someone'll help you out.
-- Sandy
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
$$('.cmd .normalise') doesn't seem to work
— is there an efficient way todo this?
Take out the space. http://jsfiddle.net/HXhNv/
-- S.
--
---
You received this message because you are subscribed to the Google Groups
MooTools Users group.
To unsubscribe from this group and stop receiving
http://mootools.net/docs/more/Element/Element.Shortcuts#Element:isVisible
-- Sandy
Pretty simple but I find users who are not web savvy find this
easier to user than dragging and dropping.
Thanks for sharing this, Trevor.
I agree that drag-and-drop is not as easy a progressive upgrade as
people think. We had a devil of a time rolling out a drag-and-drop
data tree; people
I say use *only* CSS3 animations, so it only works in newer browsers.
You'll blow minds!
-- S.
span class=clicked
div id=clickmeClick Me/div
/span
Whereas I need it the other way round like so:
span class=clickme
div id=clickedClick Me/div
/span
SPANs can't contain DIVs, so this is a misleading goal.
These two new element need to sit inside the 'clicked' element so
the
http://jsfiddle.net/m92Lu/7/
You might think wraps() is doing something neater than this, but
really it isn't. The way you're relocating innerText within new child
elements means that you end up deleting and creating text nodes no
matter what.
-- S.
It is neither an illegal operation nor a bug.
Wrapping an empty span in an extant div as in his should not throw a
TypeError -- this is being gracelessly handled and against Moo design
principles. That is the bug.
-- S.
Wrapping an empty span in an extant div as in his
(sorry, as in his initial question and Fiddle)
The bug can be see when I want to do the same thing as:
http://jsfiddle.net/m92Lu/7/ but using wraps: http://jsfiddle.net/m92Lu/8/
Exactly, wraps() has a bug with elements that aren't in the DOM but
you can use inject() just as well.
-- S.
the JResponse::toString() method does not respect the HEAD method
Isn't that a Joomla! PHP method?
Where does Moo come into it?
-- S.
maybe this one is helpful: https://github.com/visionmedia/superagent
There's no Ajax framework that can work around these limitations.
Frameworks cannot circumvent native browser security, only simplify
access. So if you're not wrapping CORS, you do not solve the prob.
-- S.
Flash as proxy is beyond XHR. You might add in Silverlight and Java bridges,
too!
The obvs. point is that you can't use JSONP as it is commonly understood
(script injection) w/custom headers, nor is there a modern-browser-native
XHR/XDR/XHR2 solution that will work (largely because of MS'
1 - 100 of 922 matches
Mail list logo
