(Migrated) "Blog" from reading and trying the 2.0 tutorial

(This message has been automatically imported from the retired mailing list)

This isn’t along “blog”, but I installed Zato and had to learn and the
best way was of course to read the tutorial.

So, while going through the tutorial, I wrote down some points that may
be useful for making the Zato experience even better.

It’s not much, and it’s basically nit picking, but since I wrote it I
can just as well post it here.

Feel free to ignore :=)

Thomas.

On 25/01/15 12:51, Thomas Lundquist wrote:

  • I presume that the JSON I got will be replaced with the nice GUI box
    pictured in the documentation. (And maybe I’ve set some dev-environment?)

Hi Thomas,

these are some nice usability suggestions you post, thanks for your
input, in particular - auto-completing service names and picking a
cluster automatically if there is only a single one sound very good.

However, on that point I quoted above - this warrants inspection.

Are you sure you have JavaScript enabled for the host your Zato
installation is on?

Can you please repeat the operation with Firebug turned on and confirm
that everything is fine on JS end?

It sounds as though it was related to JS in some way but if you could
use Firebug it would be easier to pinpoint it.

What browser + OS is it?

thanks,

On 25/01/15 12:51, Thomas Lundquist wrote:

  • I presume that the JSON I got will be replaced with the nice GUI box
    pictured in the documentation. (And maybe I’ve set some dev-environment?)

Hi Thomas,

these are some nice usability suggestions you post, thanks for your
input, in particular - auto-completing service names and picking a
cluster automatically if there is only a single one sound very good.

However, on that point I quoted above - this warrants inspection.

Are you sure you have JavaScript enabled for the host your Zato
installation is on?

Can you please repeat the operation with Firebug turned on and confirm
that everything is fine on JS end?

It sounds as though it was related to JS in some way but if you could
use Firebug it would be easier to pinpoint it.

What browser + OS is it?

thanks,