4 ms·

Thanks for this, it's a wonderfully detailed explanation of what you went through - mind putting it into a bug report for me? We have a ton of user testing to d

by ibdknox 14y ago

Thanks for this, it's a wonderfully detailed explanation of what you went through - mind putting it into a bug report for me? We have a ton of user testing to do and this is the first breath of air this particularly set up has seen (it didn't even really exist two weeks ago!) Some of these are things that just completely slipped my mind (e.g. clicking on the helpers), some are things that are just that the platform is so new it doesn't have any documentation, and some are just flat out busted assumptions on our part.

justinhj 14y ago
I hit the same issues as above. Once I found a project created with the last version of LightTable that loaded I was up and running. One thing I've noticed is evaluating an expression with Cmd-Enter seemed buggy until I realized it automatically evaluates the outermost expression rather than the previous expression which I expected due to my emacs C-x e experience. Finally, I love the color theme and feel of this in general, great stuff!
deleted 14y ago
[deleted]
spullara 14y ago
If someone goes to that much trouble to explain a bug, I generally expect the developer to file it. It is really a let down when someone has gone to that much trouble and is asked to do more work.
- hellweaver666 14y ago
  Absolutely... how difficult is it to copy and paste?
  - hisyam 14y ago
    The problem is the developer might want to get feedback from the user (eg: some bugs can't be reproduced). If the developer just copy & paste into the bugtracker then he/she will have a hard time communicating with the user.
    - spullara 14y ago
      Then you should reply with the bug ID and a URL to the bug that you filed and then the reporter can add themselves if they feel like they want to keep track of it.
  - Gigablah 14y ago
    For the developer, or the bug reporter?
- ibdknox 14y ago
  It wasn't a matter of the work involved, it's a matter of wanting to keep in touch with the person.

by ibdknox 14y ago

justinhj 14y ago

I hit the same issues as above. Once I found a project created with the last version of LightTable that loaded I was up and running. One thing I've noticed is evaluating an expression with Cmd-Enter seemed buggy until I realized it automatically evaluates the outermost expression rather than the previous expression which I expected due to my emacs C-x e experience. Finally, I love the color theme and feel of this in general, great stuff!

deleted 14y ago

[deleted]

spullara 14y ago

If someone goes to that much trouble to explain a bug, I generally expect the developer to file it. It is really a let down when someone has gone to that much trouble and is asked to do more work.

hellweaver666 14y ago
Absolutely... how difficult is it to copy and paste?
- hisyam 14y ago
  The problem is the developer might want to get feedback from the user (eg: some bugs can't be reproduced). If the developer just copy & paste into the bugtracker then he/she will have a hard time communicating with the user.
  - spullara 14y ago
    Then you should reply with the bug ID and a URL to the bug that you filed and then the reporter can add themselves if they feel like they want to keep track of it.
- Gigablah 14y ago
  For the developer, or the bug reporter?
ibdknox 14y ago
It wasn't a matter of the work involved, it's a matter of wanting to keep in touch with the person.