Loading Profile...
Markdown support
Other than email integration, Markdown is the other thing I'd need to buy Sifter.
I capture screenshots using Skitch, and upload them to another server - I just want an easy way to display that uploaded image, rather than uploading images using the web interface.
Thanks!
I capture screenshots using Skitch, and upload them to another server - I just want an easy way to display that uploaded image, rather than uploading images using the web interface.
Thanks!
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has not planned to implement this.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Unfortunately, we have no plans to support Markdown (or Textile). While it is a popular request, it has an unfortunate side effect of confusing people who are not familiar with it and do not expect it.
We are however considering some options for basic formatting, but we're being very cautious about it. You can find a little more information in the following threads. One in particular specifically addresses using Skitch.
http://getsatisfaction.com/nextupdate...
http://getsatisfaction.com/nextupdate...
I’m confident we'll find a good solution
The company thinks
this is one of the best points
-
Inappropriate?Thanks for your response, Garrett.
Regarding your response to Robby's skitch idea, not all people upload Skitch to the skitch server - I upload it to my own domain, so the url is indistinguishable from other image urls.
Two questions..
1. Why not just make markup languages (Markdown, Textile, restricted html) a setting that is disabled by default?
2. I'm curious if you've actually seen/read evidence that a markup language like Markdown interferes with less-technical users? I'd think that if it's too technical for someone, they could just not use it. There are very few situations where Markdown syntax overlaps with normal writing in a way that would generate unexpected and confusing results.
Easy/quick screenshot uploads are the key feature for a bugtracking system, in my opinion. It's why we use FogBugz, even though we hate almost everything else about it. -
Inappropriate?1. Primarily because I am very passionate about avoiding preferences. While they are relatively easy to add, they're a very slippery slope that can significantly increase the number of scenarios that need to be tested in order to ensure everything works properly. I'm sure we'll eventually add some preferences, but in my experience, it's usually possible to solve problems without falling back on preferences. It just takes a little more thought and time to come up with the right solution.
2. Most of the evidence is personal working with clients and non-technical people. The problem is that text formatting languages like Markdown and Textile are only good if you are expecting that behavior, and there's enough people that don't expect the behavior such that it ends up being confusing.
Personally, I'm a huge proponent of Markdown and/or Textile, so this hasn't been an easy decision, but I've adapted and don't really miss it. We actually supported Textile in the very early days of the beta, but we decided to yank it pretty quickly after we realized that everybody wanted something different. We decided to go with nothing for the time being so that we didn't lock ourselves into needing to support something forever. Of course, I've also heard anecdotal evidence from others building web apps encountering similar issues.
One of the scenarios where text formatting can mess things up is when people copy and pasted a long error message. It's not at all uncommon for it to end up being parsed incorrectly and make the resulting text unreadable.
Ultimately, it just comes down to the fact that there are many different types of users who all want different things, and some of them are contradictory. (Markdown, Textile, Code Formatting/Syntax Highlighting, HTML, etc.) I'm confident I'll find or create a solution that balances everyone's needs, but it will take some time. Unfortunately, there are a handful of features that are higher priority right now.
As for easy/quick screenshot uploads, I couldn't agree more, and I've got some pretty cool ideas for making the process easier. I'd like to create a Dashboard widget that lets you capture screenshots and submit an issue without even having to open a web browser. That could evolve into actual desktop apps. It's way too early to know for sure, but rest assured that I'm right there with you about streamlining things.
We're just getting started, and I'm only about 10% satisfied with where we are at this point. Right now, we're just trying to slowly chip away at the mountain of ideas we have.
I’m excited about the future
1 Comment Add a comment
This is one of the best points
-
Cool - well it looks great - I'll definitely be keeping an eye on it as it develops!
EMPLOYEE
