Can anyone provide the RunRev revlet plugin for the browsers (RevWeb) for OSX as currently the page seems to be updated until Tue. 14th May.
I would be very grateful to have it beforehand if possible, any google search always leads to the runrev-page currently in maintenance.
http://midgard.on-rev.com/uploads/revWebInstallerX86.dmg
Please note that the revWeb plugin is not currently officially supported.
Related
I saw the commercial library for iAd's from Monte but he isn't developping it anylonger due to the coming of InnerActive Ads in Livecode, right? So, I have created an InnerActive account and tried the only lesson I found on Livecode Lessons. That didn't work. So I posted a comment there which is awaiting moderation for quite some time now. I also mailed Inneractive, got a ticket replied, but no answer from them either.
If anyone has Ads with Inneractive running please tell/show us how you did it. I am calling mobileAdRegister with my appID and that seems okay. Then I try mobileAdCreate and mobileAdSetTopVisible and 'the result' tells me 'could not create ad'.
Dictionairy then tells me the app does not have Internet permissions or the registered app key is not valid. But I do check for internet connection and I'm sure I'm using my valid appID..
Regards, Amsterfrank
I have tested ads in the current release of LiveCode and they do indeed seem to be broken.
The LiveCode quality control team is aware of this and are currently investigating what could be the cause of this. A report on this issue can be viewed here-
http://quality.runrev.com/show_bug.cgi?id=11224
A workaround for now is to use an older version of LiveCode. After running a few tests, the last version of LiveCode that does not exhibit the mobile ad bug is LiveCode 6.0.0. This is available to download from here-
http://downloads.livecode.com/livecode/
With that being said, I would recommend holding off until the issue is resolved in a more current releases as there have been many bug/enhancements to LiveCode since 6.0.0
Does anybody knows if there's a browser whith Web MIDI support? ... I've tried the samples on http://webaudio.github.io/web-midi-api/ but they throw me an error that my navigator has not such properties. Im working on google-chrome and firefox. If, there's no browsers that support MIDI, when do u estimate we will have one, maybe in the next 2 years?
According to this posting (dated June 28th 2013), "initial experimental support" for Web MIDI is now available in Chrome Canary.
As of now, there are no browsers that support the Web MIDI API yet. First off, the spec isn't finalized yet and there were a couple of changes made from the original spec (function names and procedures could change anytime).
You can, however, enable your browser to support the API by installing the Jazz plugin and using Chris Wilson's Web MIDI API shim. I have personally tried it and it really works! :)
As of writing this, Web Midi is now available in regular Chrome (not just canary), though it is still an experimental feature, so it must be enabled manually at chrome://flags/#enable-web-midi
try this one, jasmid to play midi files directly on chrome/ff, no plugin needed
One of the authors of the Web MIDI API has created this shim, which enables you to work with the Web MIDI API in today’s browsers:
WebMIDIAPIShim
https://github.com/cwilso/WebMIDIAPIShim
I found my way here from the 3-years-out-of-date page at http://suitesource.netsuite.com/s.nl/it.A/id.82/.f . I have the latest eclipse, with the Aptana plugin and the NetSuiteEclipse plugin.
Just exactly what does Aptana do for me? It's not altogether clear, and it seems Netsuite may have abandoned their end of it.
By far the best environment I have found lately with regards to developing scripts for NetSuite is to just bag the instructions given by NetSuite and go with Aptana Studio 3 (not Eclipse with the Aptana plugin) and then include the NetSuite plugin to allow for direct upload into NS as Jeff mentioned. Aptana Studio is basically just Eclipse for JS and some additional cool features, like built in color themes.
The only other step you need to do (and this is not mentioned in the NS help) is to place SuiteScriptApi.js (and maybe nlapihandler.nl.js) in the root of your main project folder. The above configuration will give you code completion/definition for JavaScript in general and SuiteScript. I forget where I got the files but you can search on SuiteAnswers for them.
The help really needs to be updated to include the changes in IDE's.
The aptana plugin is not Netsuite specific it is a plugin for javascript development and provides code completion for javascript. The code completion of the netsuite objects is limited.
The netsuite plugin to Eclipse allows you to upload your suitescripts to netsuite directly from eclipse. However there are some limitations as to the path of the uploaded files that I can't remember at the moment. It did not allow me to set the paths the way I wanted so I stopped using it.
Use Suitecloud IDE.
Created from Eclipse but customized for Netsuite API.
http://elibeltran.com/suitecloud-ide/
About once a year I try Aptana and I end up uninstalling it each time- recently I tried again for my third time and uninstalled it. In my experience the code completion isn't very good, it doesn't handle complicated inheritance situations, doesn't play well with object literal notation, etc. I don't have proof and I've uninstalled it so if anyone asks me for specific examples I can't produce them.
I always end up back with Eclipse classic (3.7 I think) and JS Eclipse (which is an abandoned plugin that Adobe bought from Interakt but it still works) It's fast and has decent code completion. Is it better than Aptana? I don't think so, but it's snappier and seems to require less restarts.
I wish I had better experience with Aptana, it makes me nervous that JS Eclipse is a ghost that will disapear here at some point. I maintain over 48k lines of SuiteScript in our installation, I REALLY could use a better tool! ;)
Try Visual Studio 11.
It has much better intellisense in my opinion (as long as you configure it with any libraries such as the SuiteScript API.js). It also works well if you are already used to Visual Studio from .NET development (including SuiteTalk web services).
Not really an IDE but here is some suggestion.
Use a Google Chrome debugger. When you are in Edit mode in a record (example: customer), you can use the suitescript API to get the object-tree, very helpful in developing client-side script in Netsuite and understanding how their API works.
I would like to get into Plugin development using the Gmail API and as such I would like to ask those who already have experience in it a few questions.
What language / languages should I be familiar with? I'm not familiar with Python, PHP, or JavaScript. Will I need to pick up on these?
What level of control do I have on what my plugin can do? Can I for example change the interface or add shortcuts or RSS feeds as a sidebar?
I know a lot of the examples mentioned already exist but I would like to try my own hand at it.
Peter posted a solid list of the official Gmail APIs.
On the other hand, most of the major plugins that you may have heard about are browser plugins that just modify the page source directly, even though there's no official API for it. There used to be a GreaseMonkey API that was a good starting point, but that wasn't supported and no longer works. Best place to start is with a copy of Chrome, creating a content-injection plugin that works on the Gmail page.
Happy to provide some further details if you can clarify what you're going for since I went through this myself a few months back.
I would like to know what the members of this great community think of developing and adjusting their web apps and sites in general to recent Google Chrome beta browsers on Linux and Mac OS X and of course Google ChromeOS.
Do you think it's too early and I shouldn't waste my time adjusting myself to something that might change due to bugs resolutions?
Thank you.
Since Google Chrome uses Webkit you could also (as an alternative) test against Safari or Konqueror instead. Chances are your test results will be very portable across these browsers.
I think you answered your own question. While it is good to test against multiple browsers, there is very little point in testing against a beta browser - especially one with as little marketshare as Chrome.
With that said, the only reason I could see testing against a beta browser, is that you want your website to look good in it as soon as it is released and becomes mainstream. But, I really only see this need arising for the browsers that, again, are more popular.
Code against the standard, if you code it right the browsers will move toward you - rather than you constantly playing catchup.