On Google code playgorund, I tried to load multiple library like below
google.load("jquery", "1");
google.load("mootools", "1.2.1");
But it breaks the code, why ? Thanks
EDIT: In the left hand pane in playground, I select Library and then jquery, its runs just fine but when I also add mootools in the code, it won't work and I don't see any message even when clicking on debug.
Since you don't provide any information what breaks, all I can say is: It should work. Next time, post an error message or something similar.
[EDIT] Maybe there is a bug in google.load(). I suggest to set a breakpoint and to step through the function to see where it hangs.
Related
I find a interesting website:http://www.brightpointinc.com/interactive/political_influence/
I want to learn its visualization using d3.
But when I download it, using right click button-------- save as The download page seems does not work. It seems lack some data, so I get back to the website to download some data, but it lacks some of them, can anyone send me an work version? thanks
As Lars says, your best bet is to look at the source code. To do this, you can use something like Chrome Developer Tools or Firebug for Firefox. I use the latter, so I'll take that as an example.
First, I'd right-click on the visualization itself, and click on Inspect Element with Firebug. This will pull up the HTML, which is only semi-helpful, since it only shows the output rather than the JavaScript code which created it.
To get at the JavaScript, you can use Firebug's Script tab. Most websites have more than one script, so you can hunt through the scripts being used by browsing through the dropdown menu in the second toolbar. The _buildChords.js script looks the most promising; that has some recognizable d3 code in it. You could check out the others to see what else they're calling (since it looks like there might be others - data.js, events.js, and so on).
Happy learning.
Ok this may be a vague question but I have an issue recognizing a webelement in one module (tab) but works completely fine in another tab. This is the same webelement. Everything seems to be same. It's the same form on the gui side with same properties and values.
Now this is another weird part, I can add one to the object repository but when I go to the other tab and try the same qtp becomes extremely slow. The + sign for adding it to the repository appears but when I click it, it gives me a message saying this object cannot be added to the repository.
The Web app uses extJS if that matters and this is a high level webelement that has a constant html id. I'm just puzzled as to why it works in one module but not the other.
There are also some subtabs where you can click on this form. Those work fine but when it comes to capturing this element the issue persists.
Any hypothesis as to why this is happening?
Okay it looks like it works when I took off the visible identification and just identifying it by the html id. I still don't get why taking the visible made a diff but it works.
I'm trying to import a script from one DB into another in FMP12 and found no other way then using UI scripting.
Most of the time the script stuck when I need to mark the checkbox, complaining that the UI element cannot be found, but as visible on the picture, it is referenced properly, at least this is how I see it:
Pls visit the link for the picture showing the problem, it is much clearer then if I write it down: https://www.dropbox.com/s/y8c7xuazrb5cvlq/Screenshot_25_4_13_3_08_PM.jpg
The funny think is that sometimes the script works fine and I cannot figure out what is making it working fine sometimes.
Any idea what am I doing wrong, or if there is some other way to refer to that UI element?
Thanks
Zsolt
Overview
I am running a Plone 4.2.4 server, it is a standalone install and doesn't have any add-ons installed other than Solgema.fullcalendar. Everything installed a-ok (I can see nothing in my buildout output regarding errors or missing dependencies and running my instance in foreground mode shows no problems).
Buildout
Inside of my buildout I have: (as they request on this link)
eggs =
[...]
Solgema.fullcalendar
zcml =
[...]
Solgema.fullcalendar
Process
I followed the instructions in the documentation, going to Add New... > Collection
Then on my collection selecting View > Solgema Fullcalendar
I leave the Calendar Properties tab alone and besides changing the view to `Month' everything else remains the same.
Problem
When clicking on a blank date block, I see a little spinner.gif signifying something is loading, but in my Javascript console I see:
Error: uncaught exception: cannot call methods on dialog prior to initialization;
attempted to call method 'destroy'
This happens via the right click menu also, the right click menu loads but throws the above error once I click any of the buttons contained in it.
I can drag events, and resize them without any problems (however I think something is missing as after either dragging or resizing the event, the browser takes me to the page for that event).
Summary
It seems like I'm missing a Javascript file that was not included in Solgema.fullcalendar however I have no idea what script it was and I am unable to decipher this Javascript error (above).
If anyone has any experience with this, ideas or your thoughts would be greatly appreciated.
We're having a very peculiar problem with a site that is using mod-pagespeed. Here's the link in question -
http://www.microsemi.com/applications/
If you try to expand one of the sections by clicking on the '+' sign you need to click twice to open.
However if you disable pagespeed using http://www.microsemi.com/applications/?ModPagespeed=off
The link works correctly.
What is the best way to debug this ? Is is possible to selectively disable javascripts from being processed by mod-pagespeed ?
I'd start first of all with looking at the errors that are thrown up on the page in chrome console:
Uncaught ReferenceError: Tips is not defined www.microsemi.com:43
Failed to load resource http://www.microsemi.com/media/system/js/mootools-more.js.pagespeed.ce.BqakF5Rbjl.js
These are presumably related as the errors vanish on the second link without page-speed. I'd assume the second one must be the reason why two clicks is needed - for some reason there is a javascript file missing using mod_pagespeed - also presumably containing jQuery UI.
I should probably add that it says here mod-pagespeed only seems to be of use for badly written sites. Joomla is well written so as long as you have well functioning extensions there should be negligible difference on your site!