Get all your questions answered about our latest Photosynth Technical Preview.
Yes Anne, it accepts text and url's, but no line or paragraph breaks and so on, i.e. it is as lousy as the other Ps2 text boxes. Why not use a proper, standard text box control.(?)
It may have more to do with their database not correctly storing (or intentionally stripping out) whitespace characters like carriage returns than anything to do with the textbox (whether that's HTML as in the Photosynth 2 Tech Preview site, Silverlight as in the Photosynth 1 synth/pano editor, or Windows Forms - as in the original synther).
That is to say, perhaps we should be asking if there is a design reason why the Photosynth team explicitly does not allow paragraph separation in synth descriptions, comments, or highlight descriptions in Photosynth 2.
Maybe the team would be so kind as participating on their forum, then there would have been an answer to the question for some time already.
The reason to many of the design decisions you're raising here and elsewhere in the forums is simplicity. My philosophy is to start with the so-called "minimal viable product" and then tweak or add new features when there is a demonstrated need for them. This ensures both that we use our resources wisely (there is a cost to each of these smaller decisions) and that we don't get bloated software.
These forums are an opportunity for users to give us feedback and let us know what works or doesn't work for them. We love reading your comments - but don't always feel a need to respond to each of them. It doesn't mean we're not paying attention.
On the specific issue of whether we may support rich text in our text box controls in the future -- let's see if there are more users who feel this way to help us prioritize this request against the many more we receive.
Thanks again for all the feedback and all the enthusiasm!
Anne (Photosynth team)
Well Anne, at least I appreciate team members to participate in the discussions. It makes them more worthwhile and avoids the frustrating feeling of wasting time. Especially if matters have been raised more often over the years, like this one.
I hope your "minimal viable product" philosophy is not synonymous to "hack something together quickly". What I have seen of the latter has always shown to be difficult to clean up and get to the state of an extensible product, if possible at all.
Although "wideangle" is a nice username, you might want to follow David's example and change it.
A url in the Highlight Caption/Notes does not have color according Photosynth design language.
Concerning the highlight text box, "caption" and "Add your note" does not seem consistent to me.
This is what I would call waste of resource time. ~ If there is no time or professionalism to do it right the first time, then how will there ever be time to improve and extend.
If not a full featured rich-text control, then could we have at least a url insert feature to insert short text with underlying url. I am not talking about a url shortener.
To allow for bold text would be nice too.
I am definitely for allowing line breaks in the synth description (and maybe hightlight notes), it would make longer descriptions with multiple paragraphs easier to read.
More advanced formatting (rich-text) would be overkill, though, IMHO.
If it is about priorities, then I go with line breaks too.
I too would like the ability to at least insert a link within a word or phrase, even if I have to manually type the anchor and hyperlink reference tag/attribute.
I've been wanting that feature for ages.
Putting in the Highlight text box a name, a description/note, a Wikipedia url and a jump url.... results in a puzzle to read for the audience.
Refer the Highlight on the Queen Emma Bridge
When it comes to naming a synth or a highlight, I miss multi language support.
If a Highlight can be connected to a Bing Maps feature, then the Highlight should inherit the multi-lingual names of the Bing Maps feature.