5 ms·

Would it really hurt to include a screenshot of what it's like to use? Sorry for the grouchy comment but we're all busy people, there has to be a modicum of con

Would it really hurt to include a screenshot of what it's like to use? Sorry for the grouchy comment but we're all busy people, there has to be a modicum of convincing on a programmers part to encourage us to divert us attention to their project.

bdcravens 9y ago
"I've setup an instance on Heroku of Timestrap that resets every 10 minutes if you want to play with it."
- deleted 9y ago
  [deleted]
- jlgosse 9y ago
  I mean, did you expect better from a user named 'drcross'? Also, if you took the time to click through the link you quote yourself, you would see the following, mostly useless message: "If you don't have a user yet create one via the CLI. If you need more users add them via the admin panel."
  - bdcravens 9y ago
    The next line after what I quoted: "The username and password are set to the same as the Quickstart ones." (admin/changeme123)
largehotcoffee 9y ago
Agreed. That should be the bare minimum to show something like this off.
overshard 9y ago
Some screenshots would be useful but I'm still rapidly developing Timestrap and the interface is getting stuff added to it every few hours so I feel like it'd be a wasted effort on my part right now. EDIT: Added some screenshots to the bottom of the readme
- keehun 9y ago
  You could show off mock-ups you've done in Photoshop (and perhaps add a disclaimer) if you don't have a stable UI right now!
  - overshard 9y ago
    I don't have any mock-ups. I'm literally just creating the UI as I go since I just started making this on Friday and wanted to get something working.
- jaggederest 9y ago
  Automate it! Set up a browser test that screencaps the important pages for the documentation (and checks them for basic errors like 500 status or no text). In the long run you can diff the images and assert that they haven't changed more than N% from the reference, but for now, it makes evergreen documentation.
  - overshard 9y ago
    Good idea, I've already automated most everything else for testing and pushing to Heroku. I may as well!
    - sycora 9y ago
      Nightmare is great for this: https://github.com/segmentio/nightmare https://github.com/segmentio/nightmare
  - nodejsbangalore 9y ago
    http://trinityradar.com/ http://trinityradar.com/ can do this. Full disclosure: I work on this project.
pbreit 9y ago
Full functioning demo seems more than sufficient.
- tedmiston 9y ago
  Yeah but a video is always nice on mobile where some of the functionality is a little rough around the edges right now.

bdcravens 9y ago

"I've setup an instance on Heroku of Timestrap that resets every 10 minutes if you want to play with it."

deleted 9y ago
[deleted]
jlgosse 9y ago
I mean, did you expect better from a user named 'drcross'? Also, if you took the time to click through the link you quote yourself, you would see the following, mostly useless message: "If you don't have a user yet create one via the CLI. If you need more users add them via the admin panel."
- bdcravens 9y ago
  The next line after what I quoted: "The username and password are set to the same as the Quickstart ones." (admin/changeme123)

largehotcoffee 9y ago

Agreed. That should be the bare minimum to show something like this off.

overshard 9y ago

Some screenshots would be useful but I'm still rapidly developing Timestrap and the interface is getting stuff added to it every few hours so I feel like it'd be a wasted effort on my part right now. EDIT: Added some screenshots to the bottom of the readme

keehun 9y ago
You could show off mock-ups you've done in Photoshop (and perhaps add a disclaimer) if you don't have a stable UI right now!
- overshard 9y ago
  I don't have any mock-ups. I'm literally just creating the UI as I go since I just started making this on Friday and wanted to get something working.
jaggederest 9y ago
Automate it! Set up a browser test that screencaps the important pages for the documentation (and checks them for basic errors like 500 status or no text). In the long run you can diff the images and assert that they haven't changed more than N% from the reference, but for now, it makes evergreen documentation.
- overshard 9y ago
  Good idea, I've already automated most everything else for testing and pushing to Heroku. I may as well!
  - sycora 9y ago
    Nightmare is great for this: https://github.com/segmentio/nightmare https://github.com/segmentio/nightmare
- nodejsbangalore 9y ago
  http://trinityradar.com/ http://trinityradar.com/ can do this. Full disclosure: I work on this project.

pbreit 9y ago

Full functioning demo seems more than sufficient.

tedmiston 9y ago
Yeah but a video is always nice on mobile where some of the functionality is a little rough around the edges right now.