Hi developers!
After month of vacations in the States (including Google IO) I'm full of energy to do something more ;)
Some of you complains that Google Drive integration isn't working well. I do my best to fix any issues but it is not simple. Google Dive have poor integration with Chrome Extensions and GWT. So I had to write it from scratch. I've noticed by myself that sometimes after login dialog close nothing happen. Reload the application usually helps but it shouldn't work this way.
Finally I will fix problems with Drive. Once it's ready I will disable app server for storing and sharing requests.
Happy RESTing.
Wednesday, 29 May 2013
Thursday, 16 May 2013
Find me at Google IO 2013
Hi Developers,
If you want to meet me and talk about Advanced Rest Client find me at GDG Lounge. Between sessions I'm there. Or leave a comment/email me to be sure I'm there :)
Cheers!
If you want to meet me and talk about Advanced Rest Client find me at GDG Lounge. Between sessions I'm there. Or leave a comment/email me to be sure I'm there :)
Cheers!
Tuesday, 14 May 2013
Background page for Advanced Rest Client
Hi developers.
Greetings from Googleplex - just befor Google IO ;)
Today I've noticed that you asked me hwy the application use background page. Yes, there are event pages that don't require consistent presence of the application process but it just don't fit.
To know what exactly background page do refer to source file and previous article about ARC API.
Earlier I introduced an API for Rest Client. Now other extensions can cooperate with application - they can run an application with predefined values (like URL, payload, headers list). To make it possible I have to implement handlers for message passing (either for cross-extension communication and for web intents). It require to initialize background page. Without it the application have no place to initialize handlers without actually running the app.
Furthermore, GWT (Google's framework used to develop the application) is not ready to be used with Chrome extensions/applications. Thanks the background page I can actually develop the app using Chrome API (which is required). Without it developing the app would be extremely difficult.
You may have concerns about memory and starting up Chrome itself. Well, there is actually really little code in background page. Most of the function in background page are used when you making a request. It's do nothing when you are not using the app. But still I need to have it loaded in case if related from ARC app would like to use it.
If you have a question post it in an comment. I'll answer you. You may also report an issue if you find one.
Happy RESTing ;)
Greetings from Googleplex - just befor Google IO ;)
Today I've noticed that you asked me hwy the application use background page. Yes, there are event pages that don't require consistent presence of the application process but it just don't fit.
To know what exactly background page do refer to source file and previous article about ARC API.
Earlier I introduced an API for Rest Client. Now other extensions can cooperate with application - they can run an application with predefined values (like URL, payload, headers list). To make it possible I have to implement handlers for message passing (either for cross-extension communication and for web intents). It require to initialize background page. Without it the application have no place to initialize handlers without actually running the app.
Furthermore, GWT (Google's framework used to develop the application) is not ready to be used with Chrome extensions/applications. Thanks the background page I can actually develop the app using Chrome API (which is required). Without it developing the app would be extremely difficult.
You may have concerns about memory and starting up Chrome itself. Well, there is actually really little code in background page. Most of the function in background page are used when you making a request. It's do nothing when you are not using the app. But still I need to have it loaded in case if related from ARC app would like to use it.
If you have a question post it in an comment. I'll answer you. You may also report an issue if you find one.
Happy RESTing ;)
Sunday, 5 May 2013
New feature - CodeMirror support for HTTP headers and payload editor
Hi,
Lately I made some changes to the Rest Client.
One of it is a CodeMirror integration for input panels. Now you can edit HTTP headers or payload using convenient editor.
Lately I made some changes to the Rest Client.
One of it is a CodeMirror integration for input panels. Now you can edit HTTP headers or payload using convenient editor.
Note: It is a experimental feature and not enabled by default. It still may cause some problems.To enable this feature go to Settings page and select checkbox near "CodeMirror headers editor" and "CodeMirror payload editor".
The HTTP headers editor
It will highlight your input. Thanks to autocomplete feature it will display suggestions of common HTTP headers with common values. Hit CTRL + space to run autocomplete. It will also work while you typing.
The payload editor
This feature will load CodeMirror editor in the Payload raw input instead of the standard textarea. The editor reconfigures itself according to your Content-type selection, selecting the most appropriate editing engine for your content.
Currently supported engines are: HTML + CSS + JavaScript (combined or splitted), XML, JSON, SQL.
If you have feature request use Google Code Issue Tracker and submit a request.
Happy RESTing!
Subscribe to:
Posts (Atom)