What about Mulet?

B2G OS
#21

I have some question about debugging into mulet.
I used to debug addons or apps into the WebIde and Mulet is a little bit different. The WebIde has the list of the apps installed on the phone and you can launch them clicking on one name. I don’t know if Mulet has a list like this one. I just check urls into iframes and use them to debug.

To debug a specific app, I can access by an url like this one:
chrome://gaia/content/clock/index.html Is it the right way to debug an app?

Moreover, what is the procedure to restore an app on kanikani branch?
Move one dead_app from the dead_apps folder into the apps folder and make it work as chrome. That’s it?

I notice that the homescreen has a lot of logs into the console but for example when I launched the clock app, there are absolutely no warnings or errors into the console. It seems really strange… So I’m not sure, I’m debugging with the good method.

Thanks for your help.

#22

That seems right. Is clock not showing anything? Maybe you should add it to the prepopulated list to launch?

#23

As previously discussed, I don’t think the clock app should be chrome, it should be a web app. See bug 1270736 where @TitanNano is working on this.

We haven’t yet figured out what to do with these restored web apps. One possibility is that we move the core system chrome our of apps/ into a new chrome/ folder (they are not apps any more) and put the web apps in apps/. Or create a new webapps/ folder. I think @albertopq is working on a way to pre-populate hosted web apps on the homescreen.

We also need to figure out whether the static hosting is enough (e.g. http://mozilla-b2g.github.io/gaia/dead_apps/clock/) or whether we need some kind of build step for web apps. Let’s see how far we can get with static web content with Jovan’s patch.

Mulet is useful for debugging the system chrome, but shouldn’t even be necessary for debugging the web apps which are just like any other website. Probably the best way to do this is to run a local web server, point it at your Gaia folder and just load the web app in your browser by its URL. You can use Mulet for this if you want (either loading the URL directly or setting it as a pinned site on the homescreen) but it isn’t essential.

There isn’t yet a built-in way to run a local server for the new Gaia web apps, maybe we can re-use the web server from the DEBUG build option for this purpose.

#24

I said as chrome but I was thinking webapp. All url are beggining by chrome into mulet, that’s why I said chrome. Whatever.
Thank you a lot for the link to the bug, it was exactly the problem I was facing when I tried to debug the app directly into Firefox. That’s why I was trying into mulet.