As I'm sure you are aware, we and many of you have had a long and tiresome battle with Java when trying to use our streaming services. We have therefore been working on a solution to remove this problem.

We are pleased to announce that we have a new stockwatch available for use which no longer uses Java. We are currently making this available as a technical beta version, which means we are interested in your feedback regarding performance, bugs and browser/operating system/device compatibility issues (note: design and styling will be addressed in later beta releases).

For the purpose of allowing the old and new stockwatch versions to run concurrently, the technical functionality of the new stockwatch mimics the old one for now (not style, fonts or look). Editing and managing watchlists uses the same process as the current java stockwatch but is now at the top of the page. This will allow you to switch between the versions should you have any problems. All technical features of the current stockwatch are available in the new version except for the ability to drag resize columns. In the near future and as we migrate away from the java version of stockwatch, we will add new usability features as well as design it up to make the whole stockwatch experience smoother than it has ever been.

As this new version does not require java, you should expect it to work on your android devices and ipad/iphones. For now the display has not been optimised for smaller screens, but this will come in future development.

NOTE: Due to javascript performance in Internet Explorer 8, this new stockwatch can cause high CPU load. We recommend you use a current version of a modern browser such as Google Chrome or Mozilla Firefox for best results.

The new version can be found on the following link:

http://www.moneyam.com/stockwatch/beta.php

NOTE: Non java versions of streaming trades, streaming news and level 2 will be released over the coming weeks.

Please do not worry about design/style at the moment as this version has not been styled it is purely a technical beta test environment it will be styled before it is released. We have put this here purely for feedback on its technical functionality i.e does it work in your browser and on your PC/Laptop/Tablet/Mobile

Please post your technical feedback in this discussion thread

Thank you for your feedback and we hope you enjoy it

Presumably, a non Java version of Level 2 would be possible.

Stockwatch is excellent on a tablet where Java is not possible? I only use a tablet these days. I haven't booted up my PC for at least four months.

haystack,

yes it is on the cards, we are working on trades and news at the moment and then will be looking at level 2,

Ian

its the way forward as java was rubbish

Absolutely brilliant, I imagine there are plenty out there who are fed up to the back teeth with java related problems. The beta works a treat so well done guys and I hope you get a good return from the platform...

Looks great to me. Quicker to load than with Java. Nicely laid out, and very clear. As a bonus, it will go to a print preview first time, whereas with the Java edition, it takes me 9 or 10 attempts to get a print preview before I can print me tables! VERY promising. I like the look of it, and eagerly await the finalised format!

It's fine, all I want are the figures as quick as possible and it delivers. Java has become a pain in many areas. If you can do without it do without it.

Just a couple of points that may have been covered already.

1) I cannot see any of my information I've stored in the 'notes' columns.

2) A minor nag, but I find the 'all upper case' stock name difficult to read c/f standard text.

Actually, stocks in upper case is the norm everywhere. so
I imagine that ia a personal preference rather than a
contentious issue.

Apple mac, massive improvement on Java version. Can I disable Java version loading first?

Seems far more stable than Java, on my PC anyway. I'm all in favour of the change. Roll on the final version with full functionality.

George:

Firefox 27.0.1
IE 8.0.6001.18702

Both on Windows XP SP3

Firefox goes to "Status: not connected"
IE8 gives "Status: Not connected -EventSource's response has a Content-Type specifying an unsupported type: . Aborting the connection."

Jave stockwatch on Firefox cycles between "Connecting to stream" and "connection lost. Attempting to reconnect". Very occasionally will connect, but 99% of the time doesn't.

Current HTML stockwatch works flawlessly, all the time.

Great for I pad thanks

No style comments, as requested.
It's a great improvement functionality speaking.
BUT
The live Trades windows are not streaming trades. I'm in Chrome, up to date.
Have to select, 'largest first' to see trades.
Thanks again.

Well done

Can we have the news flag in its own column please, so I can place the column where I want it, rather than having it stuck wherever is easiest for the techies?

Also are there any plans to have the news flag update to indicate that further news items have appeared on the same stock, as the current system fails to highlight if multiple news items appear?

Yes, an update news flag would be great, when you get the chance.

New system has many advantages. Streaming , however, is troubled by paralysis & requiring very frequent refreshing.

what is "pubads.g.doubleclick ..... " as I have to wait for this to respond and it sometimes does not ?? Always when I am trying to get into Stockwatch streaming prices.
Alan - please advise why I am delayed many times with this

biohazard: Regarding your Notes issue, can you describe what you see? Can you see the title to your Notes? If you click the Note, do you not see it's content in an overlay window? What Browser/OS are you using?

zzaxx99: Ok, so it sounds like you're unable to connect to the data source for whatever reason either via Java or the new html version.

The message "EventSource's response has a Content-Type specifying an unsupported type" probably means it's just received a junk response. Is there a proxy on your side that is breaking the direct connection and interfering with the response? The current static html stockwatch is generated in a single request so is immune to any of these problems.