ChromeRestClient
ChromeRestClient copied to clipboard
jarrodek
Reminder: make a regular extension from this app
This app is cooooool. Thanks for this good work.
But maybe it will be not more installable. It would be nice, if this project will be a regular extension (which maybe is easier to realize) or a standalone application.
Refer to: http://blog.chromium.org/2016/08/from-chrome-apps-to-web.html
Hi,
Thank you for issue report. It's a bigger problem actually. According to Chromium blog (http://blog.chromium.org/2016/08/from-chrome-apps-to-web.html?m=1) Chrome apps are deprecated and soon it will be removed from Chrome.
I'm not planning to make a extension though. Extensions has different Chrome API access and has different permissions. Also not all apps API as available in open web (sockets for example which is an important API used in the app). While I can easily port most of the app to be an extension it is also not the direction of the development that I'm planning for the app. Next year I'll move towards standalone app with wither Electron or NVjs. I want the app to be available on every platform as an installed app.
This also mean to be available in Chrome OS which will require an extension because the apps will be removed. At this point making an extension will make sense and then I'll create one. But it require complete app's refactoring and redesign (which I'm doing right now) and new approach to app's modulation so it can be easily incorporated into different environments. The original code wasn't ready for this and now it requires some time to update the app.
How's this going? According to that blog, these Chrome apps will no longer load by early 2018.
I'm finalising moving the code from the app to a web components ecosystem so it will be much faster to build different apps from it. After it is ready first step is to build native apps on the Electron platform. Then the extension will be created.
To be discussed: should it be an extension as a regular extension (with browser action icon and all) or is it going to be a Chrome Dev Tools extension available as a panel in the Dev Tools.
IMHO the extension should be located as a tab in the dev tools, as i'm using the REST client usually together with the other dev tools. That would be from my sight the logically best place.
But this question belongs to the opinions of the users. Others may use the client otherwise. I think i could also live with an additional icon. The icon can be moved by chrome/-ium to the main menu.
Thanks for the input. I will investigate if it's possible to run an extension as both regular extension and dev tools extension within the same package. That may be a way to go.