[
https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887076#comment-13887076 ]
Jacques Le Roux commented on OFBIZ-5522:
----------------------------------------
>That's a rather odd graph since it unifies all the Chromes and all the Firefoxes but not the IEs. I guess its because of the feature disparities between the versions of IE
Yes I made this choice in options to clarify the graph (you might uncheck it but then the graph is hard to understand). Because now Chrome is automatically updating on Windows and Mac (not Linux). And Firefox though, not forcing automated updates, has it by default also. So indeed statistically there are more similarities.
Their explanation:
{quote}
This statistic groups together browser versions which are on a "Rapid Release" cycle, whereby the browser gets updated from one version to the next automatically without the user taking any action.
All versions of Google Chrome, as well as versions of Firefox 5 and greater have this behavior.
{quote}
I tend to agree about not considering IE8 and below. XP will soon no longer be supported, so their extinction should grow.
My wondering was more about the dot-line and what it could hide (I guess mostly IE7-6-5... ?), 8% is not neglectable (weird it's 16 % with lines). But yes this should evolve with the end of XP (though world wide a lot of not professional users will not change quickly...)
BTW, though it misses the dynamic aspect, it's easier to read like that
http://gs.statcounter.com/#all-browser_version_partially_combined-ww-monthly-201212-201312-bar,
And finally it's great to see where we are now when you know where we come from ;)
> Introduce websocket usage
> -------------------------
>
> Key: OFBIZ-5522
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5522> Project: OFBiz
> Issue Type: Task
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Jacques Le Roux
> Priority: Minor
>
> After a discussion with Ean, was suggested (draft here):
> You need a service that lets you "subscribe" a widget to an entity and
> then propagate change events to the widget as the entity is modified.
> A generic mechanism like that could eventually expand to be a general
> purpose "data bound widgets" system that mostly looks like the existing
> system but magically reflects updates.
> Could be used with/for
> * The entity cache and webforms to automatically update views when data changes.
> * Replaces the current system notes
> * Create a dashboard type pages (to be discussed futher)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Locked
