Last 7 days

• Dec 17, 2009

  r928 (Upgrade exporter version ) committed by cromwellian   -   Upgrade exporter version

  Upgrade exporter version

Last 30 days

• Dec 08, 2009

  issue 126 (Doclet error during build) reported by walshms   -   What steps will reproduce the problem? 1. svn checkout http://gwt-chronoscope.googlecode.com/svn/trunk/ chronoscope 2. cd chronoscope 3. mvn install What is the expected output? What do you see instead? Instead of building, it errors out saying "chronoscope/chronoscope-api/src/main/java/org/timepedia/chronoscope/doclet/ChronoscopeDoclet.java:[3,22] package com.sun.javadoc does not exist" What version of the product are you using? On what operating system? trunk, Linux Please provide any additional information below. There's a workaround to provide the tools.jar by editing the chronoscop-api/pom.xml by adding the dependency, <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.6.0</version> <scope>system</scope> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency>

  What steps will reproduce the problem? 1. svn checkout http://gwt-chronoscope.googlecode.com/svn/trunk/ chronoscope 2. cd chronoscope 3. mvn install What is the expected output? What do you see instead? Instead of building, it errors out saying "chronoscope/chronoscope-api/src/main/java/org/timepedia/chronoscope/doclet/ChronoscopeDoclet.java:[3,22] package com.sun.javadoc does not exist" What version of the product are you using? On what operating system? trunk, Linux Please provide any additional information below. There's a workaround to provide the tools.jar by editing the chronoscop-api/pom.xml by adding the dependency, <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.6.0</version> <scope>system</scope> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency>
• Dec 07, 2009

  r927 ([No log message]) committed by socon...@gmail.com   -   [No log message]

  [No log message]
• Dec 04, 2009

  r926 (Switch pom to 2.0.0-rc2 temporarily. ) committed by cromwellian   -   Switch pom to 2.0.0-rc2 temporarily.

  Switch pom to 2.0.0-rc2 temporarily.
• Dec 04, 2009

  r925 (Fixed GWT versiond dependency ) committed by cromwellian   -   Fixed GWT versiond dependency

  Fixed GWT versiond dependency
• Dec 04, 2009

  r924 ( Moved to Gwt Exporter 2.07, added GSS style sheet import.) committed by cromwellian   -   Moved to Gwt Exporter 2.07, added GSS style sheet import.

  Moved to Gwt Exporter 2.07, added GSS style sheet import.
• Nov 23, 2009

  issue 124 (Failed to run chronoscope built with GWT 1.7.0 in IE6,7,8) commented on by cloudsketcher   -   Hi there, Did it work for you A.A.Vasiljev? I am also having this issue. Including the jars (incubator etc) allowed me to compile, however when i then run in hosted mode I see "org.timepedia.chronoscope.client.overlays.Marker' Rebinding org.timepedia.chronoscope.client.overlays.Marker Invoking <generate-with class='org.timepedia.exporter.rebind.ExporterGenerator'/> [ERROR] Return type of method org.timepedia.chronoscope.client.event.PlotHoverEvent.getDomainPoints() is not Exportable." as you've originally reported. Thanks.

  Hi there, Did it work for you A.A.Vasiljev? I am also having this issue. Including the jars (incubator etc) allowed me to compile, however when i then run in hosted mode I see "org.timepedia.chronoscope.client.overlays.Marker' Rebinding org.timepedia.chronoscope.client.overlays.Marker Invoking <generate-with class='org.timepedia.exporter.rebind.ExporterGenerator'/> [ERROR] Return type of method org.timepedia.chronoscope.client.event.PlotHoverEvent.getDomainPoints() is not Exportable." as you've originally reported. Thanks.

Earlier this year

• Nov 18, 2009

  issue 125 (chronoscope + gwt 1.7?) reported by bobby.richards   -   What steps will reproduce the problem? 1. gwt 1.7 via eclipse on fedora 11 2. add latest gwt-chronoscope to buildpath 3. compile/run as web app Please provide any additional information below. Seems like others have had this issue. Problem is I am just not advanced enough to recompile (?) the library using diffs (if that is even the solution)

  What steps will reproduce the problem? 1. gwt 1.7 via eclipse on fedora 11 2. add latest gwt-chronoscope to buildpath 3. compile/run as web app Please provide any additional information below. Seems like others have had this issue. Problem is I am just not advanced enough to recompile (?) the library using diffs (if that is even the solution)
• Nov 13, 2009

  issue 122 (Error in DomTextLayer.java) commented on by piemmm20   -   Have the same issue here in GWT 1.7.1 with chronoscope-0.85, but the error is on line 291: Element elem = ci.createStructure(rfm.url, (int) b.x, (int) (b.y + 1), (int) b.width, (int) b.height); in DomTextLayer.class Looks like a mismatch with: com.google.gwt.dom.client.Element; in ClippedImageImpl.class and com.google.gwt.user.client.Element; in DomTextLayer.class Haven't tried the snapshot jar yet.

  Have the same issue here in GWT 1.7.1 with chronoscope-0.85, but the error is on line 291: Element elem = ci.createStructure(rfm.url, (int) b.x, (int) (b.y + 1), (int) b.width, (int) b.height); in DomTextLayer.class Looks like a mismatch with: com.google.gwt.dom.client.Element; in ClippedImageImpl.class and com.google.gwt.user.client.Element; in DomTextLayer.class Haven't tried the snapshot jar yet.
• Nov 09, 2009

  issue 122 (Error in DomTextLayer.java) commented on by shunichi.kanade   -   I have this same issue (running the demo for chronoscope) on GWT 1.7.1 and would be very interested in the solution/workaround to this problem. I am trying to run this within Eclipse on windows. Regards.

  I have this same issue (running the demo for chronoscope) on GWT 1.7.1 and would be very interested in the solution/workaround to this problem. I am trying to run this within Eclipse on windows. Regards.
• Nov 06, 2009

  r923 (Pom fixes, move to 2.0 client bundle) committed by cromwellian   -   Pom fixes, move to 2.0 client bundle

  Pom fixes, move to 2.0 client bundle
• Nov 06, 2009

  r922 (Remove incubator ) committed by cromwellian   -   Remove incubator

  Remove incubator
• Nov 05, 2009

  r921 (Pom fixes) committed by cromwellian   -   Pom fixes

  Pom fixes
• Nov 04, 2009

  r920 (Switch to 2.0.ms2, new maven plugin) committed by cromwellian   -   Switch to 2.0.ms2, new maven plugin

  Switch to 2.0.ms2, new maven plugin
• Nov 03, 2009

  issue 124 (Failed to run chronoscope built with GWT 1.7.0 in IE6,7,8) commented on by A.A.Vasiljev   -   Great news. Thank you for info.

  Great news. Thank you for info.
• Nov 03, 2009

  issue 124 (Failed to run chronoscope built with GWT 1.7.0 in IE6,7,8) commented on by j.brosens   -   I can compile Chronoscope r919 just fine with GWT 1.7.0, just had to add the dependencies to gwt-incubator july-14-2009, gin 1.0-SNAPSHOT and guice 2.0 to my pom.xml. I have no build failures on the @Export items you mentioned.

  I can compile Chronoscope r919 just fine with GWT 1.7.0, just had to add the dependencies to gwt-incubator july-14-2009, gin 1.0-SNAPSHOT and guice 2.0 to my pom.xml. I have no build failures on the @Export items you mentioned.
• Nov 03, 2009

  issue 124 (Failed to run chronoscope built with GWT 1.7.0 in IE6,7,8) commented on by A.A.Vasiljev   -   Thanks. This still does not resolve Chronoscope port to GWT 1.7.0+

  Thanks. This still does not resolve Chronoscope port to GWT 1.7.0+
• Nov 03, 2009

  issue 48 (Currently-selected zoom link should not be hyperlinked) commented on by j.brosens   -   I would like to see some onHover() behaviour on the zoom links, like underlining and displaying the hyperlink mouse cursor (hand). Is this possible with GSS already?

  I would like to see some onHover() behaviour on the zoom links, like underlining and displaying the hyperlink mouse cursor (hand). Is this possible with GSS already?
• Nov 03, 2009

  issue 124 (Failed to run chronoscope built with GWT 1.7.0 in IE6,7,8) commented on by j.brosens   -   Chronoscope uses Flash to render in IE, so you shouldn't disable it while running in IE. All other major browsers support the native <canvas> tag for VML rendering. Chronoscope uses deferred binding to take the FlashView implementation instead of BrowserView when it detects IE as configured in Chronoscope.gwt.xml with the hasflash property.

  Chronoscope uses Flash to render in IE, so you shouldn't disable it while running in IE. All other major browsers support the native <canvas> tag for VML rendering. Chronoscope uses deferred binding to take the FlashView implementation instead of BrowserView when it detects IE as configured in Chronoscope.gwt.xml with the hasflash property.
• Oct 06, 2009

  r919 (Doclet update) committed by cromwellian   -   Doclet update

  Doclet update
• Sep 18, 2009

  issue 124 (Failed to run chronoscope built with GWT 1.7.0 in IE6,7,8) commented on by A.A.Vasiljev   -   here is a diff

  here is a diff
• Sep 18, 2009

  issue 124 (Failed to run chronoscope built with GWT 1.7.0 in IE6,7,8) reported by A.A.Vasiljev   -   Hello. I use trunk version of chronoscope (r918). GWT 1.7.0. I saw you reverted to 1.6.4 recently, but nevetherless tried 1.7.0 Diff is attached. As you see, changes are simply in GWT and incubator versions, plus removing @Export from PlotHoverEvent. Having @Export there results in Computing all possible rebind results for 'org.timepedia.chronoscope.client.overlays.Marker' Rebinding org.timepedia.chronoscope.client.overlays.Marker Invoking <generate-with class='org.timepedia.exporter.rebind.ExporterGenerator'/> [ERROR] Return type of method org.timepedia.chronoscope.client.event.PlotHoverEvent.getDomainPoints() is not Exportable. compiling the project. Without @Export all is compiling OK, however I got 'too much recursion' error running my project in FF, IE7,8, as you could see at http://chronoscope-r.latest.away-from-you.appspot.com/ script is compiled in pretty mode. If I disable export and flash in my project: <set-property name="export" value="no"/> <set-property name="hasflash" value="no"/> Then project compiles and runs OK in FF: http://chronoscope.latest.away-from-you.appspot.com/ but not in IE7,8: 'object does not support this property or method'. Again script is compiled in pretty mode and the reason of error is line: this$static.ctx = this$static.canvas.getContext('2d'); in constructor of BrowserLayer May you please provide hints how to make Chronoscope-based project works in IEs with mainstream GWT?

  Hello. I use trunk version of chronoscope (r918). GWT 1.7.0. I saw you reverted to 1.6.4 recently, but nevetherless tried 1.7.0 Diff is attached. As you see, changes are simply in GWT and incubator versions, plus removing @Export from PlotHoverEvent. Having @Export there results in Computing all possible rebind results for 'org.timepedia.chronoscope.client.overlays.Marker' Rebinding org.timepedia.chronoscope.client.overlays.Marker Invoking <generate-with class='org.timepedia.exporter.rebind.ExporterGenerator'/> [ERROR] Return type of method org.timepedia.chronoscope.client.event.PlotHoverEvent.getDomainPoints() is not Exportable. compiling the project. Without @Export all is compiling OK, however I got 'too much recursion' error running my project in FF, IE7,8, as you could see at http://chronoscope-r.latest.away-from-you.appspot.com/ script is compiled in pretty mode. If I disable export and flash in my project: <set-property name="export" value="no"/> <set-property name="hasflash" value="no"/> Then project compiles and runs OK in FF: http://chronoscope.latest.away-from-you.appspot.com/ but not in IE7,8: 'object does not support this property or method'. Again script is compiled in pretty mode and the reason of error is line: this$static.ctx = this$static.canvas.getContext('2d'); in constructor of BrowserLayer May you please provide hints how to make Chronoscope-based project works in IEs with mainstream GWT?
• Sep 10, 2009

  r918 (Fix static factory reference issue) committed by cromwellian   -   Fix static factory reference issue

  Fix static factory reference issue
• Sep 04, 2009

  r917 (Back to 1.6.4 ) committed by cromwellian   -   Back to 1.6.4

  Back to 1.6.4
• Sep 04, 2009

  r916 (Revert to FastDate) committed by cromwellian   -   Revert to FastDate

  Revert to FastDate
• Sep 03, 2009

  r915 (Decade fix, DataTableParser fix.) committed by cromwellian   -   Decade fix, DataTableParser fix.

  Decade fix, DataTableParser fix.
• Sep 03, 2009

  r914 (continued refactoring for GIN ) committed by cromwellian   -   continued refactoring for GIN

  continued refactoring for GIN
• Aug 20, 2009

  r913 (Move all GWT code to chronoscope module, leaving pure chart ...) committed by cromwellian   -   Move all GWT code to chronoscope module, leaving pure chart code in chronoscope-api

  Move all GWT code to chronoscope module, leaving pure chart code in chronoscope-api
• Aug 20, 2009

  r912 ([No log message]) committed by cromwellian   -   [No log message]

  [No log message]
• Aug 20, 2009

  r911 (Refactor GWT specific code to separate module ) committed by cromwellian   -   Refactor GWT specific code to separate module

  Refactor GWT specific code to separate module
• Aug 17, 2009

  r910 (Fix poms ) committed by cromwellian   -   Fix poms

  Fix poms
• Aug 06, 2009

  issue 99 (Chart can't deal with 0 datasets or a dataset having 0 point...) commented on by j.brosens   -   Came across this issue today but what I found was: Dataset containing exactly 1 point with a value -> browser hangs on an infinite script loop causing a memory leak. Occurs in IE as well as FF. GWT console mentions something like an ArrayIndexOutOfBoundsException while computing tick size, which seems logical while having only one point in the domain. Used chronoscope r844.

  Came across this issue today but what I found was: Dataset containing exactly 1 point with a value -> browser hangs on an infinite script loop causing a memory leak. Occurs in IE as well as FF. GWT console mentions something like an ArrayIndexOutOfBoundsException while computing tick size, which seems logical while having only one point in the domain. Used chronoscope r844.
• Jul 28, 2009

  r909 ([No log message]) committed by cromwellian   -   [No log message]

  [No log message]
• Jul 28, 2009

  r908 ([No log message]) committed by cromwellian   -   [No log message]

  [No log message]
• Jul 28, 2009

  r907 ([No log message]) committed by cromwellian   -   [No log message]

  [No log message]
• Jul 28, 2009

  r906 (Switch to version 1.0. Change poms to use new GWT Maven Plug...) committed by cromwellian   -   Switch to version 1.0. Change poms to use new GWT Maven Plugin. Refactored plugin config to top level pom. Upgrade to GWT 1.7.0

  Switch to version 1.0. Change poms to use new GWT Maven Plugin. Refactored plugin config to top level pom. Upgrade to GWT 1.7.0
• Jul 24, 2009

  r905 (Fix ready listener issue. ) committed by cromwellian   -   Fix ready listener issue.

  Fix ready listener issue.
• Jul 10, 2009

  issue 119 (Auto-resizing on multiple points differing in seconds) commented on by danshao   -   I also noticed that this occurred when the data points had time differences of seconds.

  I also noticed that this occurred when the data points had time differences of seconds.
• Jul 02, 2009

  r904 (Support for clickable domain axis panel links. ) committed by cromwellian   -   Support for clickable domain axis panel links.

  Support for clickable domain axis panel links.
• Jun 22, 2009

  issue 123 (Should not zoom beyond data resolution) commented on by j.brosens   -   I agree, I got a colleague who saw that it was still possible to zoom in to millisecond level when our dataset only had a resolution of hours. He expected to encounter more resolution while zooming, but never got there. I would vote for an option/switch to make zooming stop on the deepest level of resolution of a dataset.

  I agree, I got a colleague who saw that it was still possible to zoom in to millisecond level when our dataset only had a resolution of hours. He expected to encounter more resolution while zooming, but never got there. I would vote for an option/switch to make zooming stop on the deepest level of resolution of a dataset.
• Jun 21, 2009

  issue 123 (Should not zoom beyond data resolution) reported by frankg.fgleason   -   Zooming should stop when current data resolution is reached. Should not be able to zoom in to 100s second when the data has a resolution of one year.

  Zooming should stop when current data resolution is reached. Should not be able to zoom in to 100s second when the data has a resolution of one year.
• Jun 15, 2009

  issue 119 (Auto-resizing on multiple points differing in seconds) commented on by danshao   -   I'm really not sure how to reproduce this problem. Apparently when I load the library from <script src="http://api.timepedia.org/gviz/"></script> - and I have the chronoscope visualization displayed in a div of width 100% along with a scatterplot or table from the Google Viz, this causes the page to be re-sized automatically on the page - essentially moving the chronoscope viz out of the browser window - without allowing the ability to scroll horizontally.

  I'm really not sure how to reproduce this problem. Apparently when I load the library from <script src="http://api.timepedia.org/gviz/"></script> - and I have the chronoscope visualization displayed in a div of width 100% along with a scatterplot or table from the Google Viz, this causes the page to be re-sized automatically on the page - essentially moving the chronoscope viz out of the browser window - without allowing the ability to scroll horizontally.
• Jun 15, 2009

  issue 118 (Missing visualization on null value) commented on by danshao   -   Okay let's say here is my data set: DateTime | Product 1 | Product 2 xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx This will product a perfect chronoscope plot. However, let's say this is another set of data I am trying to plot: DateTime | Product 1 | Product 2 xxxx:xx:xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx Now, if you tried to draw this visualization, product 2 would not be displayed at all.

  Okay let's say here is my data set: DateTime | Product 1 | Product 2 xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx This will product a perfect chronoscope plot. However, let's say this is another set of data I am trying to plot: DateTime | Product 1 | Product 2 xxxx:xx:xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx xxxx:xx:xx xx xx Now, if you tried to draw this visualization, product 2 would not be displayed at all.
• Jun 13, 2009

  issue 118 (Missing visualization on null value) commented on by pkirklew...@gabaedevelopment.com   -   Can you describe step by step how you created the project please ? That would help in understanding what's going on.

  Can you describe step by step how you created the project please ? That would help in understanding what's going on.
• Jun 13, 2009

  issue 119 (Auto-resizing on multiple points differing in seconds) commented on by pkirklew...@gabaedevelopment.com   -   Can you describe step by step how you created the project please ? That would help in understanding what's going on.

  Can you describe step by step how you created the project please ? That would help in understanding what's going on.
• Jun 13, 2009

  issue 120 (Legend labels overlap when using VML rendering (non-IE brows...) commented on by pkirklew...@gabaedevelopment.com   -   Can you describe step by step how you created the project please ? That would help in understanding what's going on.

  Can you describe step by step how you created the project please ? That would help in understanding what's going on.
• Jun 13, 2009

  issue 121 (IE/Flash: Overview chart is offset to the left and top) commented on by pkirklew...@gabaedevelopment.com   -   Can you describe step by step how you created the project please ? That would help in understanding what's going on.

  Can you describe step by step how you created the project please ? That would help in understanding what's going on.
• Jun 12, 2009

  issue 122 (Error in DomTextLayer.java) reported by pkirklew...@gabaedevelopment.com   -   What steps will reproduce the problem? 1.Create application in GWT 1.6 or 1.5 2. Add ./lib dir and download chronoscope-0.7.jar and gwtexporter.jar 3.Follow these instructions: http://timepedia.org/chronoscope/docs/gwt/ What is the expected output? A webpage with a chart on it. What do you see instead? [ERROR] Errors in 'jar:file:/root/java/gwt/HelloChart/lib/chronoscope- 0.7.jar!/org/timepedia/chronoscope/client/browser/DomTextLayer.java' [ERROR] Line 289: Type mismatch: cannot convert from Element to Element What version of the product are you using? chronoscope-0.7.jar with gwt 1.6 and 1.5 On what operating system? Tested on Linux Ubuntu

  What steps will reproduce the problem? 1.Create application in GWT 1.6 or 1.5 2. Add ./lib dir and download chronoscope-0.7.jar and gwtexporter.jar 3.Follow these instructions: http://timepedia.org/chronoscope/docs/gwt/ What is the expected output? A webpage with a chart on it. What do you see instead? [ERROR] Errors in 'jar:file:/root/java/gwt/HelloChart/lib/chronoscope- 0.7.jar!/org/timepedia/chronoscope/client/browser/DomTextLayer.java' [ERROR] Line 289: Type mismatch: cannot convert from Element to Element What version of the product are you using? chronoscope-0.7.jar with gwt 1.6 and 1.5 On what operating system? Tested on Linux Ubuntu
• Jun 10, 2009

  issue 121 (IE/Flash: Overview chart is offset to the left and top) reported by j.brosens   -   What steps will reproduce the problem? 1. View a chart in IE/Flash 2. Look at the overview chart (small one at the bottom) 3. What is the expected output? What do you see instead? It should render normally, but instead the overview chart is positioned too high and slightly to the left. This leaves white space below the overview and the selected area of the overview chart doesn't match the visible domain in the main chart, since it is offset to the left. What version of the product are you using? On what operating system? Windows XP, IE6, GWT 1.5.3, Chronoscope 0.86-r844 Please provide any additional information below.

  What steps will reproduce the problem? 1. View a chart in IE/Flash 2. Look at the overview chart (small one at the bottom) 3. What is the expected output? What do you see instead? It should render normally, but instead the overview chart is positioned too high and slightly to the left. This leaves white space below the overview and the selected area of the overview chart doesn't match the visible domain in the main chart, since it is offset to the left. What version of the product are you using? On what operating system? Windows XP, IE6, GWT 1.5.3, Chronoscope 0.86-r844 Please provide any additional information below.
• Jun 09, 2009

  issue 120 (Legend labels overlap when using VML rendering (non-IE brows...) reported by j.brosens   -   What steps will reproduce the problem? 1. Add several datasets to a chart with 'long' legend labels 2. View the chart in a non-IE browser (VML rendering) 3. Hover over a point and see the labels overlap What is the expected output? What do you see instead? Expected: all labels are correctly laid out Instead: overlap occurs What version of the product are you using? On what operating system? Windows XP, FF3, Safari 4, GWT 1.5.3, Chronoscope r844. Please provide any additional information below.

  What steps will reproduce the problem? 1. Add several datasets to a chart with 'long' legend labels 2. View the chart in a non-IE browser (VML rendering) 3. Hover over a point and see the labels overlap What is the expected output? What do you see instead? Expected: all labels are correctly laid out Instead: overlap occurs What version of the product are you using? On what operating system? Windows XP, FF3, Safari 4, GWT 1.5.3, Chronoscope r844. Please provide any additional information below.