IanT(MoneyAM)
- 29 Jan 2014 07:42
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
biohazard
- 20 Feb 2014 09:08
- 302 of 734
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.
midknight
- 20 Feb 2014 12:24
- 303 of 734
Actually, stocks in upper case is the norm everywhere. so
I imagine that ia a personal preference rather than a
contentious issue.
Sea
- 20 Feb 2014 13:40
- 304 of 734
Apple mac, massive improvement on Java version. Can I disable Java version loading first?
Caldox
- 20 Feb 2014 16:31
- 305 of 734
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.
zzaxx99
- 20 Feb 2014 16:44
- 306 of 734
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.
leedslad
- 20 Feb 2014 18:00
- 307 of 734
Great for I pad thanks
Escovido
- 21 Feb 2014 08:36
- 308 of 734
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.
williags
- 21 Feb 2014 08:39
- 309 of 734
Well done
dell314
- 21 Feb 2014 10:24
- 310 of 734
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?
greekman
- 21 Feb 2014 11:07
- 311 of 734
Yes, an update news flag would be great, when you get the chance.
Belvoir
- 23 Feb 2014 14:32
- 312 of 734
New system has many advantages. Streaming , however, is troubled by paralysis & requiring very frequent refreshing.
rekirkham
- 24 Feb 2014 08:21
- 313 of 734
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
George (ex MoneyAM)
- 24 Feb 2014 11:21
- 314 of 734
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?
George (ex MoneyAM)
- 24 Feb 2014 11:58
- 315 of 734
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.
George (ex MoneyAM)
- 24 Feb 2014 11:59
- 316 of 734
Escovido: We are working on a replacement Trades page because it still suffers Java problems.
George (ex MoneyAM)
- 24 Feb 2014 12:13
- 317 of 734
dell314, greekman: In order to have a news flag that flagged only if you had unread news, we would have to track all the news that each user has read, or at least the last time a user looked at a list of news items for a stock code. We would have to validate against this list each time a stock list was loaded so we could decide to show the N or not, so it would have some performance impact. We currently don't do this. It's not impossible but it's not a simple task to achieve without potential downsides.
dell314: Regarding News having it's own column, it's never been requested before so I expect more people would have to ask for it, and for it to be decided there was tangible benefit. What we don't really want to do is make the stockwatch wider.
A potential solution to both suggestions would be to have a 'last news time' column which could check periodically for news updates. That way you could know if there is new news.
George (ex MoneyAM)
- 24 Feb 2014 12:21
- 318 of 734
Belvoir: What browser are you using?
greekman
- 24 Feb 2014 15:49
- 319 of 734
Afternoon George,
Re your post 317 regarding unread news, I appreciate what you say but it was actually a request that if there are more than 1 news items per day, could something be done to show that, it was not a case of unread news as I accept this would be very complicated to show.
A competitor shows news item by number per day next to the epic, IE 1, 2 etc, just wondering if MoneyAm could do the same.
No prob if they can't.
Regards Greek
cowshapedfish
- 25 Feb 2014 08:54
- 320 of 734
George
Is it not possible to clear the 'T.time' column at the end of each trading day? And even the cum/vol. column?
Just a thought
Thanks
George (ex MoneyAM)
- 25 Feb 2014 09:38
- 321 of 734
greekman: OK, I understand. I (and Bullshare) thought you only wanted the N to show if you had not read stories about that stock. Actually, I thought of a way we could potentially do this by just storing the last time you clicked the N next to a stock. We could then potentially check if the last news story was after that time to decide to show the N or a different icon. We will see what new features could be added around the news area. We are discussing other possibilities anyway.