Encoding drop down removal from the app

Hi developers!

Update April 4, 2016
As of release 6 of the app the dropdown for content type header back to the app. Read more in this blog post.

I received a lot of questions about missing drop-down with predefined encoding values. I feel I owe you an explanation.

Lets begin of what it was. Encoding for payload is nothing more than value for Content-Type header. So when you selected one of predefined encodings (or rather mime types) the app added Content-Type header to the headers list before submission.

Earlier, the drop down list contained a list of predefined values for the Content-Type header. In fact this was only a shortcut for adding a header to the headers list. We all love shortcuts but..

Let's test the prototype!

As you may know lately I have worked on new version of the Advanced Rest Client application. It will change... well, pretty all!

Minor changes will cover:

• storage - change from deprecated WebSQL to IndexedDb
• projects to become "requests groups" - old projects are to much complex and unnecessary. In nev version you will have an option to group requests and easily switch between endpoints
• responses history - it is a new feature, the app will store responses so you can check how your server's response change over time. It also implicate that the app will be useful offline as well.
• better Google Drive integration - it will use different API to connect to +Google Drive. Thanks to a new Identity API in +Google Chrome you will authorize the app in more user friendly way
• upgrade to Chrome App! - instead of opening the app in new tab it will open as native-like application. You may even add the application to the task bar or desktop
• new way hows the requests are made - using new Google Chrome Sockets API the app is able to make a request without a limitations of XmlHttpRequest. You'll be able to set every type of HTTP header. Also I'm planning a raw socket testing implementation.
• change the +GWT framework to +AngularJS - it is more flexible for HTML5 apps than GWT. And it takes much less time to add new functionality or change existing ones
• completely new UI

How about new version?

Hi all,

What do you say for new version of Rest Client for Google Chrome? :)

This is a snapshot of dev version of the app:

It will be faster than current version and it will be totally redesigned. I've added some new features that should help you with your work.

The new version is witted in pure javascript this time. I left GWT behind because for HTML5 features it was a pain in an ass. Now I'm using Bootstrap framework. Mostly for pretty nice styles, out of the box.

I hope you'll enjoy new UI and new set of functionality. I think I've done a lot of good job regarding UX.

It's still under development and there is a lot of work to do. RC version should be available in the end of September. I'm hoping that final version will be ready in middle October.

Give me a feedback what you think about this proposition. I know that it is only one screenshot and only small part of the app but you can see a direction of changes.

P.S.
I'm not planning to maintain server side of the application anymore.  It means that the only way to save and share your data is either save it to file (locally) or save and share it on Google Drive.
If you have any data on application's server you should restore it on your app and save it on Google Drive.

Happy RESTing!

Google Drive integration

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.

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!

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 ;)

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.

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!