![]() From there, several iterations are made on the prototype – as much as necessary. We simply share our comments by email most of the time, in a Basecamp project (their new version is great) or if necessary, in a Google Doc. We don’t use the commenting feature of Axure Share – it’s not convenient at all. I prefer Axure over other wireframing tools because it’s so easy to create a working prototype in minutes, with on-mouse events, keyboard validation and multiples states on each page.Īs soon as we have a working prototype, wireframes are uploaded on, letting teamates review the prototype and make comments. Wireframes usually start as hand-drawn scribbles and end up as a full wireframe done with the fantastic Axure app. WireframesĮvery feature we add starts with a wireframe, or a mockup depending on the situation. They just know that every week or so we make changes to the platform, and every two months, big new features are available. We don’t want to commit to a date, and we don’t want to over-excite our customers. We try to stay agile as much as possible. We know where we are going in terms of product strategy – but the priority for developing new features can change at any time. Contrary to most companies, this roadmap is not set in stone for a given period of time. ![]() Of course, we also have a product roadmap. Even though we happen to say no often (as you should – saying no is a powerful thing), if the idea is often requested, it might have a good chance of being put into the product. We also listen to our customers as much as possible. Anyone can come up with a good idea – and if it’s a good one, it will be implemented in the product. ![]() I also recommend using a text editor that has the option to show whitespace characters.In traditional workplaces, ideas that don’t come from the product manager are not typically taken into account. The easiest way I've found to work with non-printable character hacks like this is to save the sequence in a text file as hex, then whenever I need to use them I can quickly open a new tab, google 'hex to ascii', then copy/paste via any converter. If it automatically converts it to a space, or something similar refer below to an alternate method: Vertical Tab (between quotes): ""Īnd in a sentence as you would use it on Slack, where I've tested it successfully, regardless of how it works here (just copy/paste into Slack): There is *no* spoon. Here is the character info, though I am unsure how StackExchange and/or your individual web browser will display this. So instead if you were to use the Vertical Tab (VT) it would be enough to separate out the asterisk, without adding the additional space between the asterisks and the word(s) they surround. This in my opinion was the best answer given already, but it still adds the unsightly spaces. Solution: Use the Vertical Tab character.Īs mentioned above you can use a space to sort of detach the asterisks from the word or phrase they're around, like so: These * spaces * will keep it from becoming bold. And since none of the hacks provided so far are acceptable I grabbed a hotpocket and some Xena tapes and set out to prove my kung-fu was strong. Though they're all correct in one sense, there is no intentionally built method to handle this use case, it would require a hack of some sort. I had to agree with Richard Simões above, none of these answers actually provided a real solution. TL DR: You now have TWO working solutions for the price of one! ![]() The primary different between the two is my solution uses characters that will remain hidden if copy/pasted to a simple text-editor, whereas the soft-hyphen solution in my testing converts to a standard looking hyphen in common simple text-editors. HOWEVER, as far as usability is concerned leclercdumombasin's answer is elegant in that you can simply copy and paste the soft-hyphen and tag any words you want to remain unformatted with only a single hidden character. Personally I find it's always easiest and more compatible to use an ASCII range solution as opposed to tempting fate with a Unicode solution like in leclercdumombasin's answer. Or use any hex to ascii converter (ie: ASCII to Hex) to convert this: 2a 0c 68 61 78 0c 2a Solution: Copy the below fixed text to Slack and Edit: There is once again *no* spoon Not to fear, there is a simple Fix!įIX: Instead of using a Vertical Tab (hex character 0x0B), NOW use a Form Feed character (hex character 0x0C)! It seems Google has updated the Chrome web browser controls (and possibly others) to show placeholders for many common ASCII control characters, INCLUDING the Vertical Tab character! This change has caused my original Solution below to break, now showing "unknown character" squares or in some cases whitespace breaks, where before it was non-breaking in most use cases (notably Slack!).
0 Comments
Leave a Reply. |