Skip to main content

Google PageCreator (beta)

Really. Honestly. Truly. I feel blessed! After all, The God of All Things (Big and Small), the great Google allowed me to access its service! And I was 'invited' to do so!

So ladies and gentlemen, I was given an 'invitation' (after I requested one by signing up on their site) from Google to try another new offering from Google stable, Google PageCreator.
PageCreator is a WYSIWYG ('What You See Is What You Get') tool that enables you to create a web page, using available templates and FrontPage like controls (e.g. inserting image or formatting text). Your pages are saved automatically and you can publish them on a 100 MB server space provided by Google, accessible by domain name: <\your-gmail-domain'>.googlepages.com(e.g. my homepage URL is http://iabhishek.googlepages.com).

What is so special about PageCreator? The controls are very elementary in nature. You can't access or edit the source-code of the page being generated. There are a number of page templates available but almost all seemed to me minor variations of each other, some color added here, some gif changed there. You can't create any new layouts or templates. So it is quite stifling if you want to express your creativity.

But this simplicity can be good for the beginners and newbees. If you are an HTML illiterate and have no idea (or don't want to have any hassles) of finding free servers and want to have a website of your own the Google PageCreator and Google Pages form the ideal combination for you.

The page even shows placeholders for putting in your text and headings. Uploading images is fast and easy, however you can place any image in only four sizes (one is the original size and three are decided by Google). Similarly creating any link has also been simplified beyond the limits! The page is saved automatically at certain intervals of time. And you can see the preview in new window any time. A page is available on your domain URL only after you have published it.

I don't expect this new offering from Google to create any ripples. No falling head over heals to sign up for it, no begging of invites! I am rating this service as page designer for beginners and hence simplicity and speed are the only deciding criteria. However obviously some points have to be deducted for lacking in some very basic features. My rating 6/10.

Was that the reason, my invite came so soon?

Comments

Popular posts from this blog

File upload problem: UTF-8 encoding not honored when form has multipart/form-data

The problem that I was facing was something like this. I was using Apache Commons File Upload library to upload and download some file.

I had a form in which user can upload a file and another field 'name' in which she can give any name to the file being loaded.


When I submitted the form, the file was uploaded fine but the value in name field was garbled. I followed all the possible suggestions I found:

<%@page pageEncoding="UTF-8"%> set. <%@page contentType="text/html;charset=UTF-8"%gt; set after the first directive. <meta equiv="Content-Type" content="text/html;charset=UTF-8"> in the head. enctype="multipart/form-data" attribute in the form. accept-charset="UTF-8" attribute in the form.
in the Servlet:
before doing any operations on request object: request.setCharacterEncoding("UTF-8"); For accessing the value

FileItem item = (FileItem) iter.next();

if (item.isFormField()) {

//For regular…

java.lang.IllegalArgumentException: Malformed \uxxxx encoding

I was getting this exception during build while running ant. Googling didn't help much and I was flummoxed because the same code was running fine till now.

My code reads a text file and does some operations on the basis of values read. It was only when I saw the text files I understood the error. I had copied the text in wordpad and saved it as .txt file. Wordpad had put lot of formatting information before and after the content. Also there was "\par" after every line, which was giving this error.

So moral of the story: if you get this exception check your properties file (or any other file that your code might be reading.)

How to upload to Google Cloud Storage buckets using CURL

Signed URLs are pretty nifty feature given by Google Cloud Platform to let anyone access your cloud storage (bucket or any file in the bucket) without need to sign in.

Official documentation gives step by step details as to how to read/write to the bucket using gsutil or through a program. This article will tell you how to upload a file to the bucket using curl so that any client which doesn't have cloud SDK installed can do this using a simple script. This command creates a signed PUT URL for your bucket. gsutil signurl -c 'text/plain' -m PUT serviceAccount.json gs://test_bucket_location
Here is my URL:
https://storage.googleapis.com/test_sl?GoogleAccessId=my-project-id@appspot.gserviceaccount.com&Expires=1490266627&Signature=UfKBNHWtjLKSBEcUQUKDeQtSQV6YCleE9hGG%2BCxVEjDOmkDxwkC%2BPtEg63pjDBHyKhVOnhspP1%2FAVSr%2B%2Fty8Ps7MSQ0lM2YHkbPeqjTiUcAfsbdcuXUMbe3p8FysRUFMe2dSikehBJWtbYtjb%2BNCw3L09c7fLFyAoJafIcnoIz7iJGP%2Br6gAUkSnZXgbVjr6wjN%2FIaudXIqAxyz4O6VU%2FIob8RHmf…