I followed the instruction at:
https://developer.blackberry.com/html5/documentation/use_the_ripple_emulator_chrome_extension_2007542_11.html
to run remote site app project, it works.
But when I tested sample (bbui.js sample) on local disk
BB10 document said:
https://developer.blackberry.com/html5/documentation/accessing_a_local_project_in_ripple_1948645_11.html
So I copied the bbuijs samples project to
Mac OS: /Users//RippleSites.samples
But when I pointed chrome to
localhost:9910/samples/index.htm (Ripple emulator extension)
Chrome said
could not connect to localhost:9910
Is there anything wrong?
Do I need to run web server sharing?
Welcome any comment
Easiest thing to do here it got to enable "web sharing" (your last pic). create a symbolic link from the Web Server's home dir to your samples. So:
cd /Library/WebServer/Documents/
ln -s <path to your samples> <name of dir>
Note: you might have to use "sudo" ahead of that last command.
You should then be able to go to 127.0.0.1/(name of dir) and it should work for you.
Hope this helps.
I have the same problem ("could not connect to localhost:9910") on Windows 7 in Chrome with Ripple emulator version 0.9.10 (beta)
The documentation at https://developer.blackberry.com/html5/documentation/accessing_a_local_project_in_ripple_1948645_11.html
does mention how to install the Chrome extention. But it does not mention that the Ripple button in Chrome has a popup where you can start the local service running on port 9910.
My steps taken were:
Open the kitchensink example by following https://developer.blackberry.com/html5/documentation/enabling_the_ripple_emulator.html
This allows you to see the Ripple emulator working.
Create the local directory as described in https://developer.blackberry.com/html5/documentation/accessing_a_local_project_in_ripple_1948645_11.html
Then you will be able to see the services button and start the service.
Open your local project via loaclhost:9910/
Image of the option menu:
(source: escay.nl)
Related
I cannot open Appium inspector on Linux Ubuntu.
In the same folder I have 3 files:
Appium-Inspector-linux-2022.2.1.AppImage /
Appium-Server-GUI-linux-1.22.2.AppImage /
latest-linux.yml
When I open the Appium-Server-GUI-linux-1.22.2.AppImage file, start the server e click on the button to open Appium Ispector, it open a web page.
to fix this, it was necessary:
1: Start Appium Server
I did this, executing Appium-Server-GUI-linux-1.22.2.AppImage file.
2: Start Appium Inspector through of file Appium-Inspector-linux-2022.2.1.AppImage
3: Create the capabilities
After that, the Appium Inspector still don't open throught on Appium Server button, but it make it open and you can use.
Since the release of Appium v1.22 they have changed how the Appium Inspector works. I refer you to their official documentation on GitHub https://github.com/appium/appium-inspector, citing:
Appium Inspector is released in two formats:
As a desktop app for macOS, Windows, and Linux. You can get the most
recent published version of this app at the Releases section of this
repo. Simply grab the appropriate version for your OS and follow
standard installation procedures (but see the note below for macOS).
As a web application, hosted by Appium Pro. (It's currently a known
issue that the web version does not work on Safari). Please make sure
to read the note below on CORS as well.
If you like to work the old way, download Appium Desktop v1.21 or below.
install latest appium-inspector
open appium-inspector and insert "/wd/hub" in Remote Path
I'm currently using vscode-tomcat extension within a RHEL7 container and developing over SSH using the vscode-remote extension. However, I am unable to launch the tomcat debugger due to this unresolved issue.
"TypeError: Cannot set property 'readableListening' of undefined"
The issue only occurs when trying to launch the Tomcat debugger while doing remote SSH development. I am making an attempt to debug the issue, but I'm not sure how to debug a VSCode extension within a remote container.
Any tips would be greatly appreciated. Let me know if I can provide any additional details.
There is now documentation for all of this. Read
https://code.visualstudio.com/api/advanced-topics/remote-extensions#debugging-using-ssh
and then keep reading because further down you will find this
https://code.visualstudio.com/api/advanced-topics/remote-extensions#debugging-using-ssh
in fact read all of it, there's a lot of stuff there that initially made me think "So?" but which is vital knowledge in specialised problems.
Here's the portion relating to the immediate problem.
Debugging using SSH
Follow steps:
After installing and configuring the Remote - SSH extension, select Remote-SSH: Connect to Host... from the Command Palette (F1) in VS Code to connect to a host.
Once connected, either use File > Open... / Open Folder... to select the remote folder with your extension source code in it or select Git: Clone from the Command Palette (F1) to clone it and open it on the remote host.
Install any required dependencies that might be missing (for example using yarn install or apt-get) in a new VS Code terminal window (Ctrl+Shift+` ).
Finally, press F5 or use the Run view to launch the extension inside on the remote host and attach the debugger.
Note: You will not be able to open the extension source code folder in the window that appears, but you can open a sub-folder or somewhere else on the SSH host.
The extension development host window that appears will include your extension running on the SSH host with the debugger attached to it.
Installing a development version of your extension
Anytime VS Code automatically installs an extension on an SSH host, inside a container or WSL, or through GitHub Codespaces, the Marketplace version is used (and not the version already installed on your local machine).
While this makes sense in most situations, you may want to use (or share) an unpublished version of your extension for testing without having to set up a debugging environment. To install an unpublished version of your extension, you can package the extension as a VSIX and manually install it into a VS Code window that is already connected to a running remote environment.
Follow these steps:
If this is a published extension, you may want to add "extensions.autoUpdate": false to settings.json to prevent it from auto-updating to the latest Marketplace version.
Next, use vsce package to package your extension as a VSIX.
Connect to a codespace, development container, SSH host, or WSL environment.
Use the Install from VSIX... command available in the Extensions view More Actions (...) menu to install the extension in this specific window (not a local one).
5.Reload when prompted.
Tip: Once installed, you can use the Developer: Show Running Extensions command to see whether VS Code is running the extension locally or remotely.
The File->Open command will show Windows' Explorer dialog screen and thus uses Windows file path format, C:\abc\xyz. However, I'd like the command to work with Linux file path, e.g., /home/foo/test.py. Is that possible? Thank you.
You need the vscode extension "Remote - WSL" installed which will enable a little green box in bottom left corner.
Clicking it will give you the option to "Remote-WSL: Reopen Folder in WSL" | Select WSL distro, e.g. Ubuntu.
note 1 - details on this is also covered in https://code.visualstudio.com/remote-tutorials/wsl/run-in-wsl
note 2 - it may not be required but i'm running with wsl2 tech preview update inplace [ "windows wsl2 docker setup" | past year -> https://docs.docker.com/docker-for-windows/wsl-tech-preview/ ]. I have it in place to enable docker service to be hosted using new wsl vm versus outgoing hyper-v vm approach. Don't think its required for vscode wsl integration to work.
I've looked on the Node-Webkit site and it appears to say that I can make an application with HTML5 and compile it for Windows, Linux of Mac so it will run without the need for the user to install Node.js separately. However, when I try their sample apps (e.g. https://github.com/leanote/desktop-app found on the official NW.js page: https://github.com/nwjs/nw.js/wiki/List-of-apps-and-companies-using-nw.js ), the ".exe" file does not run the app (on either Win 7 or XP). It just opens a simple browser window with the address "nw:blank" and a gray page says "NW.JS" and does nothing.
Can these apps be packaged and run without requiring the user to install node.js?
https://github.com/leanote/desktop-app 's nw folder is not the distribute leanote app, it's just the NW. You must build the desktop-app. The README has written How to build it, How to develop it
You can download the distributed version via: https://github.com/leanote/desktop-app/releases
You might try... node-webkit-builder ... which is supposed to build a huge .EXE file which is self-contained for you. Otherwise, the instructions for distributing... how to package and distribute, see Step 2b.
I get an error while trying to install IIS manager from "Turn on off windows features" on a windows 8 machine. Just before trying to install this I install Visual Studio community online and rebooted my machine. Visual Studio works fine.
I also made sure all updates are installed on my machine and also rebooted and tried installing IIS manager.
The error that I get is "The function attempted to use a name that is reserved for use by another transaction"
Thanks
Ranjith
Try to turn off your antivirus before install IIS.
I had the same problem and spent hours trying to find out the root cause. Tried to disable anti virus and other options as discussed in forums on the internet.
Here is how i resolved the problem.
Open up msconfig -> go to boot tab -> select Safe boot (Minimal) -> Apply -> Okay
Your machine should restart in safe mode and you should be able to successfully install IIS from the "Turn Windows Feature On/Off" section as described by others.
After the installation is complete, run msconfig again to unselected Safe boot so that you log in to the normal desktop environment on restart. Enjoy!
Just now i also faced that problem and this is how fixed the problem.
The reason can be another server which running on your pc, is using the same port as IIS. (e.g: 80 or 8080).
According to my solution, I started the wampserver. then click on wamp icon on the task bar. then opened the httpd.conf file from Apache.
find (ctrl+F) the "Listen 80" and replace it to "Listen 8080" or any other. save it.
restart your pc and try to install the IIS manager again.
hope it will works!! Good luck.