Do we have any plugin or setting to have a good UI inspector for Rhodes App - rhomobile

I'm really bored with RhoSimulator inspect, as its not user friendly and we can't event perfectly inspect the design.
Even we can't right click on that to have the options to go back or go home or inspect. I had seen this on the previous version. But its not available now.
For a single minor UI issue it takes huge time using the inspect. Anybody have any idea how can we make this better.

Why don't you set the local port to a static one, and run the app on the browser. So you can have huge number of inspector for you help.
If you see, on your rhoconfig.xml file, you will found,
#local_server_port = 8080
Just un-comment it, and set to some port, lets say 8081 // if no one is using this port
local_server_port = 8081
Now on the browser, go for http://127.0.0.1:8081/app/, you can see the app running on the browser. That's it.

Related

Can Chromium features that are normally turned on via switches be turned on programatically after starting up?

Is there a way to use Chromium switches after starting it up, or must they be enabled on start up? For example, can switches be passed to the renderer processes, or just to the main process?
I want to turn on paint flashing in Chromium (actually in my Electron app which runs on top of Chromium).
Devtools has a checkbox that turns this on, but I want to be able to turn this on without devtools, and after the app has started.
I know there's a show-paint-rects flag I can use:
chrome.exe --show-paint-rects
In my Electron app, I would need to use app.commandLine.appendSwitch:
app.commandLine.appendSwitch("show-paint-rects");
I also found a ui-show-paint-rects flag that lives in something called the "compositor," but that may be irrelevant for me.
Both of these work, but since Chromium uses a multi-process architecture, I'm hoping that there's a way I can specify that switch, or otherwise, turn on a feature in one process and not have to specify it at startup.
Is there a way to do this in Chromium? (Would be ideal to do this in Electron, but I'm not counting on it)

Execution between docker container

I would like to know if it's possible to create a kind of communication between two docker container.
I've two docker containers, one for Firefox and another one for vscode. I'm looking for a solution to be able to open URL link from vscode in my running Firefox container(create a new tab as we have when we are selecting a link).
Don't know if it's possible to do that. Maybe by sharing some specific resource.
Thanks
I am not sure about the possibility but there are two scenarios:
Either you find a way/extension to make vscode call a browser over network
Mount the needed files/binaries as a volume from firefox container to vscode container to make it able call the firefox binary locally as usual in order to make it able to open the browser (not tested but might be done somehow) but it might not be able to open in the same session, so give it a try and let me know so i can update the answer.

Go offline in Edge like in Chrome

I am doing a POC in PWA and service worker, i hosted to application in localhost and tested in Chrome everything seems to working fine even the indexed db is getting listed properly.
to test the offline functionality :
in Inspector > Network Tab > Offline ( check the option )
When am in Edge i didn't see this option so tried disconnecting the network but still because it reading from localhost everything is working directly and reading from server.
To check the Indexeddb and all i installed the MS Edge DevTools preview, still am not able to see the DB and Store
Is there any way to test this in Edge
At present, Offline mode is not available in MS Edge.
If you want to see index db then you can open the developer tools and go to the debugger tab.
It looks like below.
You also not need to install developer tools additionally because by default it comes with Edge. You can directly use it.
You can try to check on your side. Let us know if you still have problem in finding the index db in Edge, We will try to provide further suggestions.

Ghost CMS weird navigation issue

So I install Ghost CMS and it is working great, but I noticed recently that the navigation settings (where I add new links to the menu and such) are acting strange and not working right.
So in the image above you will notice the ':80' port being added onto the domain. Which is fine I guess, but what is odd is that if i click out the field and then back into it it adds another port ':80' and continues to do that as many times as I click out, also if I tried to delete and save it immediately adds them back in. Look at Teaching and you will see what it ends up looking like.
Also when I go to the site front page and click one of the menu items I see a 404 error in the console saying the page doesn't exists.
I can't figure out what is going on it was working just fine a few weeks ago and I have touched anything on the server. I am stumped, I don't really know enough about Ghost so I am relying on a better expert to help me out here. I am using the Bitnami Ghost Cloud Image. and have the theme bleak installed.
Any Thoughts?

How can step through an Action that is requested from JavaScript during execution?

There is this one action that is requested using javascript during the loading of a page, it takes over 25 seconds to resolve. Looking at the code makes me think there is a scaling issue, but I am wondering if there is any way I can step through the code during the request so I can see what is happening. I try clicking 'debug/start debugging' but it won't launch the proper URL (access to the site is subdomain based), and it will also not find certain dependencies. I am able to browse the site directly via URL locally after mapping a URL via my hosts file to localhost (127...) but the default url that pops up (localhost...) from debug does not work because it is not formatted properly.
Any ideas?
You can attach the debugger to your browser by selecting "Attach to process" under "Debug" menu.
In the past, at least with ASP.NET we have used tracing to debug issues. You will just need to enable it in the webconfig. If you use warn, the messages will show in red and be easier to spot.

Resources