Whoops, sent the previous message before finishing it:
> That is definitely a nice idea. I wonder if we might take it a step > further and just drop the last word (which may be incomplete). This is > untested: <$text text={{{ > [<display-title>length[]compare:number:lt[40]then<display-title>] > ~[<display-title>split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]] > }}}/> > What do you think? I did consider this, but I'm actually not sure which way looks better. I don't think that cutting off an incomplete word half way through looks bad, and I might even prefer it, though I couldn't say why. Possibly just because that's what windows explorer does so I'm just used to it. On Sun, 27 Jun 2021 at 20:59, Si Si <si4314...@gmail.com> wrote: > Saq, > > I've also been considering asking for volunteers for a small group of >> regular users of Streams for testing new features.. > > > I'm happy to test stuff out as required. > > >> from my perspective however how, much effort I put into adding new >> features to Streams is highly dependent on how many people regularly use it >> and find that it imparts value. Call it a personal quirk but wanting to >> impart the most value possible is something that often drives my decision >> making in terms of what I dedicate my time to. > > > It says a lot of positive things about your character if that is what > motivates you! > > That is definitely a nice idea. I wonder if we might take it a step >> further and just drop the last word (which may be incomplete). This is >> untested: > > <$text text={{{ >> [<display-title>length[]compare:number:lt[40]then<display-title>] >> ~[<display-title>split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]] >> }}}/> >> What do you think? > > > On Sat, 26 Jun 2021 at 14:21, Saq Imtiaz <saq.imt...@gmail.com> wrote: > >> @Walt hopefully you are getting some helpful feedback here. Apologies for >> the slight digression caused by my replying to Streams specific comments >> and feedback. >> >> @fred you can also export using a filter from the Filter tab in Advanced >> Search >> >> @Si, >> >> >>> On the topic of how many people use it, maybe you could consider >>> creating a Google Form and linking to it from the download page, asking >>> users if they would take a second to answer some brief questions? >>> >> >> I've been considering it for some time actually. Apart from feedback on >> workflow, just knowing whether the number of people regularly using Streams >> is < 10, 10-20, or 20+ would be very helpful. >> >> >>> I was also wondering if you had considered setting up a way for users to >>> donate? Not necessarily to fund development, just to show appreciation for >>> great free software! I am not currently in a position to contribute much, >>> but in the future I would certainly be happy to subscribe to a patreon or >>> whatever. >>> >> >> I think the most value for myself would be in just getting regular, >> precise and on-topic feedback. Implementing new features in the absence of >> user feedback is just driving blind from my perspective. I also find it >> very frustrating and motivation sapping when I post ideas or demos and at >> times get feedback that is far off topic or just so poorly written that it >> is more frustrating than helpful. Mind you, I try to be very understanding >> of users for whom English is not their first language. It is actually very >> pleasing how constructive and helpful this thread has been thus far in >> comparison. >> >> I've also been considering asking for volunteers for a small group of >> regular users of Streams for testing new features.. from my perspective >> however how, much effort I put into adding new features to Streams is >> highly dependent on how many people regularly use it and find that it >> imparts value. Call it a personal quirk but wanting to impart the most >> value possible is something that often drives my decision making in terms >> of what I dedicate my time to. Otherwise the motivation for work on Streams >> is just whatever seems interesting for me personally from a technical >> perspective. >> >> >>> I would add that like Mario I am very happy with the current features of >>> streams, though I have made the following tweak to the text display for the >>> breadcrumbs. It's a very minor thing, but in my opinion looks nicer than >>> just cutting off the title mid-word: >>> >>> <$text text={{{ >>> [<display-title>length[]compare:number:lt[40]then<display-title>] >>> ~[<display-title>split[]first[40]join[]trim[]addsuffix[...]] }}}/> >>> >> >> That is definitely a nice idea. I wonder if we might take it a step >> further and just drop the last word (which may be incomplete). This is >> untested: >> >> <$text text={{{ >> [<display-title>length[]compare:number:lt[40]then<display-title>] >> ~[<display-title>split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]] >> }}}/> >> >> What do you think? >> Cheers, >> Saq >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "TiddlyWiki" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> tiddlywiki+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/0b65a408-28d6-4709-8e16-feb01355858en%40googlegroups.com >> <https://groups.google.com/d/msgid/tiddlywiki/0b65a408-28d6-4709-8e16-feb01355858en%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAKKx7WaGddJx5BvUiPuJDU1mS-xix5K2pUTvjfC_w0Lfoe8juQ%40mail.gmail.com.