Updated version of TimeYourCube

ricehigh

Member
Joined
Jul 18, 2011
Messages
20
Hi guys,

A couple of years ago, I created a speedsolve timer at timeyourcube.com and now I felt it was time for a major update.

The site is now faster than ever and should now support touch-based devices. There are now more visualization options and plots now work on mobile devices.

I encourage you to try the site out :)

I would also appreciate any feedback you have on the site. I don't have access to Apple products, so I would especially like your feedback on how the site runs on OS X and iOS.

I hope you like it :)

Changelog:
  • Initiatives to improve experience from mobile devices
    • Adaptive design
    • Speed optimization
    • New sound engine (sound still a bit experimental on mobile devices).
    • New plotting engine (old one was based on Flash)
  • Changed database access for faster response times from server. (less waiting)
  • Added option to change timezone (timezone will be fetched by geoip on first visit)
  • Added new plotting modes.
  • Added option to download log as a comma separated file (csv file), which can be loaded directly into other programs, such as Excel.
  • Added a "social bar", which makes it easy to share this site with family and friends.
  • Fixed a bug that could take the user to an non-existing page when signing up.
  • Added URL navigation.
  • Minor UI improvement, including a loading symbol that appears, when elements on screen are being updated.
 
Way too small on iOS.
You have to hit accurately into a box roughly 1cmx6cm, and it's easy to miss, or hit e.g. "changelog" by mistake.
For touch, I'd want to be able to touch almost anywhere on the screen.
It's not terrible on iPhone (although the problem above), but on iPad over 50% of the screen is blank space.
 
Last edited:
Thank you for your quick and great feedback, ellwd.

I will definitely look more into the adaptive design part of the site, so that it will adapt better to different screen sizes.
 
I looked at this originally and said mehh... Then I saw the login page. Like holy crap I have wanted this forever. Not to mention decent stat options

EDIT:When you have inspection set pressing space bar stops inspection changes the scramble but does not start the time... I very rarely use 15 seconds of inspection and don't want to wait when I don't
 
Last edited:
Thank you for reporting back, pdilla. I'm glad it works on OSX :)

I'm glad you find it useful, biscuit. However I'm not sure I understand the problem with the inspection and scramble. Could you try to explain it more clearly, so i could have a look at it?
 
So I have not sat down to actually do any solves but I tested the timer (aka start/ stopped it) and it worked fine then I set inspection time to 15 seconds. I pressed the space bar and inspection started like I would expect. When I pressed it again instead of starting the actual timing like I would expect and get on other timers. It treats the space bar as stopping the timer even though timing had not started. This resulted as the inspection time stopping the scramble changing but no time came up in the time box as the time had not started.

How I would fix this is in the statement where you check if the space bar has been pressed you use the Boolean used to check if the check box is ticked (if that is how you are doing it) then on the first space bar it runs a function to do inspection. In that function you say that when/if the space bar is pressed again to cut inspection (just stop it where it is) and run the function that runs the timer (this may need a lot of lines to be recoded to add the functions)

If you did not understand that I will try one more way to explain it. How I expected it to work is

space bar (I will denote space bar with _ from now on) _ - inspection start - _ - inspection stop && timer start - _ - timer stop && time displayed in time box. What I got

_ - inspection start - _ - inspection stop - no output. When the space bar is pressed to start the timer it breaks the whole function instead of starting a new one
 
Biscuit, now I get your point :)

However, I actually made it this way on purpose. See, to my mind, it makes more sense that pressing spacebar stops the countdown.

Would somebody else weigh in here: What is the expected behavior of pressing the spacebar when the countdown is running?
 
Would somebody else weigh in here: What is the expected behavior of pressing the spacebar when the countdown is running?

It would be natural to me if it started the timer when I pressed the spacebar. It is how I'm used to it being from other timers, and in competitions.
 
I have tried to implement the spacebar behavior requested by biscuit on the testing page of the site http://testing.timeyourcube.com/

biscuit and IllegalLaws, can you confirm that this is working as intended?

If it works as intended, I would like a few comments from a few more in here whether or not to move the feature to the main site :)
 
Yes, the inspection/timer on the testing page works as expected. Please make this work on main site.

PS - It makes no sense for the inspection time to stop when you press spacebar and not make the timer start. What's the point of that?

Edit: Also, right now the timer just starts after the inspection countdown is over. But it should note whether it merits +2 or DNF. So after the 15 second countdown is over, it should show as +2 for two more seconds. If spacebar is pressed then, two seconds are added to the time and it's marked on the right side with the times. After 17 seconds it will be DNF. Could you add this to the testing page so we can try it again?
 
Last edited:
Yea the inspection feature as it is now is really retarded, to be perfectly blunt. In my 30 seconds of experimentation I couldn't figure out how to get it to start timing the solve without counting all the way down.
 
Upon your popular request, I have updated the spacebar behavior on the main site.

Also, would someone else comment on sneaklyfox's request that the timer should not start after the countdown, but rather give DNF or +2 seconds? and also, it's a bit unclear to me if that should be +2 seconds on the timer or +2 seconds on the countdown? And if this is implemented, I suppose there should be a comment in timer log whether it's DNF or +2 seconds or neither? Lastly, should DNFs then just not be counted in statistics and plots?
 
tbh this looks very similar to cubetimer. just sayin'

I mean, that's on purpose. It even says so on the 'about'-page. I like cubetimer, but I just wanted a service, where i could also plot my progress and log in from different computers. So i made just that.
 
I have added a "WCA" inspection time option on the testing page (http://testing.timeyourcube.com/). When using this inspection mode, penalty and DNF are automatically added to the solve. Please tell me if this was the behavior you wanted :)

By the way. The stats in the upper right corner uses data with penalty, but discards data with DNF. Is that the behavior you want? I mean, if I include DNF data, then the Avg 5, Avg 10, 3 of 5 and 10 of 12 will have to be DNF if these solves contains any DNF...
 
Back
Top