Axel Uhl 7a5c00609a fixing bug 896 by providing Timer.isInitialized() and not loading the leaderboard for an uninitialized timer; ...

the duplicate loading for the null time point in the Leaderboard.html entry point still persists; we would need
a smarter way of identifying that the offset adjustment which is causing the second load during the callback
wouldn't really required another load with null at basically the same time point, but the difficulty is that
then the timer's notion of live time and the leaderboard contents would deviate. Assuming that the null time
point is handled efficiently by the live leaderboard DTO cache, I think we can live with this.

2014-04-23 16:38:58 +02:00

..

.settings

updated classpath to use JDK 7

2014-03-12 18:41:09 +01:00

META-INF

moved some timer and player related base classes to com.sap.see.gwt bundle

2014-03-27 18:25:56 +01:00

src/com/sap/sse/gwt

fixing bug 896 by providing Timer.isInitialized() and not loading the leaderboard for an uninitialized timer;

2014-04-23 16:38:58 +02:00

.classpath

fixed some little classpath issues with gwt bundles and JDK version

2014-03-27 11:07:33 +01:00

.project

Renamed com.sap.sse.gwt.shared to com.sap.sse.gwt

2014-01-16 14:11:11 +01:00

build.properties

removed resources/ from classpath and build.properties of sse.gwt bundle; there was nothing in there

2014-03-22 15:03:29 +01:00

pom.xml

Finished integration of com.sap.sse.gwt

2014-01-16 17:38:43 +01:00