cameron
fluid transitions from squirt to page content and back again
Allow for Original Page being read to be seen or accessed without having to close squirt tab
It is not an application change I am asking for. It is a file/application handling and command issue. When squirt is on, it is maximized on the screen, making it impossible to see the article, blocking the ability to refer to charts, photos etc. in the article/text. It is also impossible to click back and forth between the regular original text and the squirt screen. I think that allowing easy transition between the squirt screen, and the original underlying text/images, and the ability to resize the squirt screen will make this application much more useful and useable.
-----Original Message----- From: Cameron Boehmer [email protected] To: cameron/squirt [email protected] Cc: Petersonan [email protected] Sent: Sun, Mar 16, 2014 1:15 am Subject: Re: [squirt] Allow for Original Page being read to be seen or accessed without having to close squirt tab (#88)
This is not a multitasking application. What is the use case you imagine? — Reply to this email directly or view it on GitHub.
Okay, I understand better and agree that Squirt having a more fluid relationship with the content it reads is desirable, but this is, to my mind, absolutely an application change.
Obviously its entirely up to you, but for me not being able to refer to charts etc. while reading is reducing the usability of the application. Too bad, looked promising
-----Original Message----- From: Cameron Boehmer [email protected] To: cameron/squirt [email protected] Cc: Petersonan [email protected] Sent: Sun, Mar 16, 2014 7:54 pm Subject: Re: [squirt] Allow for Original Page being read to be seen or accessed without having to close squirt tab (#88)
Okay, I understand better and agree that Squirt having a more fluid relationship with the content it reads is desirable, but this is, to my mind, absolutely an application change. — Reply to this email directly or view it on GitHub.
Too bad
Didn't mean to imply I'm against this! I would have closed it otherwise.
I think it's a great idea that would enhance the product dramatically for a certain subset of users. I'm totally into it, but there are more important issues on my plate at the moment (like SSL support).
Cant say I know what your development and enhancement priorities are, however: while security issues are important, product usability and functionality certainly should not take a back seat. In a product where there are few security concerns (after all it is not a product that generates/transfers new data, (but rather "reads" existing data streams which in one way or another have used an SSL or TLS protocol before reaching the current user of the data. Nor is the passage being "read" transmitted elsewhere. There is the danger of the passage being read to carry hidden malware of course.
Please let me know if/when you chose to allow for the "fluid transition from squirt to page content and back (#88), so that I could use squirt more fully. Maybe a side-by-side design (half window using the "source" content page, while the other half of the window uses the Squirt screen displaying the word being read...
Good luck
-----Original Message----- From: Cameron Boehmer [email protected] To: cameron/squirt [email protected] Cc: Petersonan [email protected] Sent: Mon, Mar 17, 2014 12:04 am Subject: Re: [squirt] fluid transitions from squirt to page content and back again (#88)
Too bad
Didn't mean to imply I'm against this! I would have closed it otherwise. I think it's a great idea that would enhance the product dramatically for a certain subset of users. I'm totally into it, but there are more important issues on my plate at the moment (like SSL support). — Reply to this email directly or view it on GitHub.
while security issues are important, product usability and functionality certainly should not take a back seat
My priorities stem from Squirt being unusable on sites served over https, like https://medium.com and gmail. Almost 10% of the bugs filed on the first day stemmed from this issue.
Good luck!
-----Original Message----- From: Cameron Boehmer [email protected] To: cameron/squirt [email protected] Cc: Petersonan [email protected] Sent: Mon, Mar 17, 2014 9:13 am Subject: Re: [squirt] fluid transitions from squirt to page content and back again (#88)
while security issues are important, product usability and functionality certainly should not take a back seat
My priorities stem from Squirt being unusable on sites served over https, like https://medium.com and gmail. Almost 10% of the bugs filed on the first day stemmed from this issue. — Reply to this email directly or view it on GitHub.
Thank you :)
I'm looking forward to spending some time on the interface and incorporating your feedback!