Groups > comp.sys.mac.apps > #28976 > unrolled thread

How do mac users create a blank text file where you want it?

Started by	"Adam H. Kerman" <ahk@chinet.com>
First post	2015-04-20 00:40 +0000
Last post	2015-04-22 09:45 -0400
Articles	20 on this page of 393 — 26 participants

Back to article view | Back to comp.sys.mac.apps

Page 13 of 20 — ← Prev page 1 … 11 12 [13] 14 15 … 20 Next page →

#29413

From	jamiekg@wizardling.geek.nz (Jamie Kahn Genet)
Date	2015-04-23 12:50 +1200
Message-ID	<1m3c0uq.odgdvqyf2a1mN%jamiekg@wizardling.geek.nz>
In reply to	#29409

Jolly Roger <jollyroger@pobox.com> wrote:

> On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
> > Alan Baker <email@domain.com> wrote:
> >
> >> Please...
> >> 
> >> "Adam", not "Alan"
> >> 
> >> :-)
> >
> > Was it? Sorry mate. His stupidity is already fading into the mists of
> > the past :-)
> 
> I knew who you meant, if it's any consolation. : D

Maybe I could just start calling all trolls 'Fuckface'? The last troll
who differentiated himself was that fundamentalist fanatic - John
someone or other. The rest just blend into... one big Fuckface.
-- 
If you're not part of the solution, you're part of the precipitate.

[toc] | [prev] | [next] | [standalone]

#29411

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-22 23:33 +0000
Message-ID	<cpqpeiF3ijcU4@mid.individual.net>
In reply to	#29403

On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
>
> So in order to be as clueless as Alan, one must:
> a) Not look through the menus and preferences, of which there are only a
> few.
> b) Not try anything to see what happens, and there is very little to
> try.
> c) Not read the help file available right there from the Help menu.
>
> I also note Alan seemed to think in several posts that changing the file
> extension would change the file type. This makes it even harder for me
> to believe he's even an experienced Unix user, as he claims.

He also claims to be a teacher.

I doubt every single word of it.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#29399

From	dorayme <do_ray_me@bigpond.com>
Date	2015-04-23 07:36 +1000
Message-ID	<do_ray_me-F8F360.07364923042015@aioe.org>
In reply to	#29377

In article <1m3bkop.q7q7rrfsa7fxN%jamiekg@wizardling.geek.nz>,
 jamiekg@wizardling.geek.nz (Jamie Kahn Genet) wrote:

> I've always though a Save As option that radically alters formatting and

...

I think of Save AS... mostly as a good way of saving a copy, albeit 
modified to some extent in its content, under a different name or to 
another folder. But there is no harm, and plenty of good in various 
apps, to add extra functionalities when this is chosen, such as 
formatting or type of file. In QT7, for example, if you Save AS..., 
you get options to save as a self-contained movie, a reference one, 
and there is the standard button for a new folder. In Illustrator for 
Mac, not Apple admittedly, they change some things in this regard from 
version to version, I used to have to 'export' to get some things done 
which I now just use Save As. 

Different apps do slightly different things, there is probably a lot 
of inconsistency and you have to just learn the options. That's how it 
is. No use insisting there is always a right set of options.

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#29400

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-22 22:00 +0000
Message-ID	<cpqjv2F3ijcU1@mid.individual.net>
In reply to	#29377

On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
>
>> On 15-04-22 13:11, Jamie Kahn Genet wrote:
>> 
>> > Plus given the switch between RTF and plain text changes formatting
>> > options available, as well as save options, it only makes sense to have
>> > it be a menu option, instead of a 'Save As…' dialog option.
>> 
>> 
>> But Save_As should give you the option to save as text (stripping all
>> formatting). I think earlier versions of textedit had that option.
>
> I've always though a Save As option that radically alters formatting and
> content (in the case of plain text - completely stripping it and any
> other embedded media out) is worthy of some kind of distinction, and
> TextEdit handles that well IMO.

I like the way that some applications put that kind of functionality in
the Export command.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#29405

From	jamiekg@wizardling.geek.nz (Jamie Kahn Genet)
Date	2015-04-23 10:55 +1200
Message-ID	<1m3bv38.18wnolllz4mu6N%jamiekg@wizardling.geek.nz>
In reply to	#29400

Jolly Roger <jollyroger@pobox.com> wrote:

> On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
> > JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> >
> >> On 15-04-22 13:11, Jamie Kahn Genet wrote:
> >> 
> >> > Plus given the switch between RTF and plain text changes formatting
> >> > options available, as well as save options, it only makes sense to have
> >> > it be a menu option, instead of a 'Save As…' dialog option.
> >> 
> >> 
> >> But Save_As should give you the option to save as text (stripping all
> >> formatting). I think earlier versions of textedit had that option.
> >
> > I've always though a Save As option that radically alters formatting and
> > content (in the case of plain text - completely stripping it and any
> > other embedded media out) is worthy of some kind of distinction, and
> > TextEdit handles that well IMO.
> 
> I like the way that some applications put that kind of functionality in
> the Export command.

I'm indifferent to breaking out exporting into it's own dialog. I guess
there's no harm, but I was fine with Save As and then picking a file
type :-) Maybe that's just what I'm used to.

Still, TextEdit is a special case as it makes little sense within it's
context of a simple plain text editor/rich text word processor, to make
the user save to swap between plain text and RTF, or to force the user
to pick one type when creating a new document. It's just easier,
simpler, and more useful to be able to swap on the fly.
-- 
If you're not part of the solution, you're part of the precipitate.

[toc] | [prev] | [next] | [standalone]

#29410

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-22 23:36 +0000
Message-ID	<cpqpklF3ijcU6@mid.individual.net>
In reply to	#29405

On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
>
> Still, TextEdit is a special case as it makes little sense within it's
> context of a simple plain text editor/rich text word processor, to make
> the user save to swap between plain text and RTF, or to force the user
> to pick one type when creating a new document. It's just easier,
> simpler, and more useful to be able to swap on the fly.

Yep, if you treat the application like an application rather than your
mommy. : D

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#29418

From	Crosby Livingston <crosbylivingston44584@verizon.net>
Date	2015-04-22 22:52 -0500
Message-ID	<ae97e$55386c8f$43da7656$10393@nntpswitch.blueworldhosting.com>
In reply to	#29400

On Wed, 22 Apr 2015 22:00:02 +0000, Jolly Roger wrote:

> I like the way that some applications put that kind of functionality in
> the Export command.

Gimp has an export to another format which then asks, when you kill Gimp
if you wanted to save the original format also.

[toc] | [prev] | [next] | [standalone]

#29398

From	Your Name <YourName@YourISP.com>
Date	2015-04-23 09:18 +1200
Message-ID	<230420150918589098%YourName@YourISP.com>
In reply to	#29365

In article <5537d993$0$64023$b1db1813$2411a48f@news.astraweb.com>, JF
Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 15-04-22 13:11, Jamie Kahn Genet wrote:
> >
> > Plus given the switch between RTF and plain text changes formatting
> > options available, as well as save options, it only makes sense to have
> > it be a menu option, instead of a 'Save AsŠ' dialog option.
> 
> But Save_As should give you the option to save as text (stripping all
> formatting). I think earlier versions of textedit had that option.

TextEdit 1.2 under Mac OS X 10.2.8 doesn't have any options in the Save
As dialog when using a Rich Text document. When using a Plain Text
document you do get various encoding options.

[toc] | [prev] | [next] | [standalone]

#29368

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-22 17:32 +0000
Message-ID	<cpq4aaFt5tjU5@mid.individual.net>
In reply to	#29361

On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
> Tim Streater <timstreater@greenbee.net> wrote:
>
>> In article <alpine.OSX.2.20.1504221037270.31550@mako.ath.cx>, David
>> Ritz <dritz@mindspring.com> wrote:
>> 
>> >As it happens, I agree with Adam, that the way TextEdit works isn't as
>> >intuitive as having the option of saving a file, in whatever format 
>> >one desires, directly from the Save dialog.
>> 
>> A trivially unimportant difference. Most people would either figure it
>> out for themselves, or have understood it in short order after a few
>> posts. As it was "Adam" is either terminally thick, or was being
>> deliberately obtuse with a view to trolling, or is Harry Worth.
>
> Plus given the switch between RTF and plain text changes formatting
> options available, as well as save options, it only makes sense to have
> it be a menu option, instead of a 'Save As…' dialog option.

Absolutely. Loss of data is something that should be respected in the
design. Converting a rich text document containing images, styling, and
so on to a plain text document removes those things which may be
important to users. Doing that *while* saving the document isn't a good
user experience.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#29375

From	jamiekg@wizardling.geek.nz (Jamie Kahn Genet)
Date	2015-04-23 07:10 +1200
Message-ID	<1m3bl37.1wclsf11kd5jmdN%jamiekg@wizardling.geek.nz>
In reply to	#29368

Jolly Roger <jollyroger@pobox.com> wrote:

> On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
> > Tim Streater <timstreater@greenbee.net> wrote:
> >
> >> In article <alpine.OSX.2.20.1504221037270.31550@mako.ath.cx>, David
> >> Ritz <dritz@mindspring.com> wrote:
> >> 
> >> >As it happens, I agree with Adam, that the way TextEdit works isn't as
> >> >intuitive as having the option of saving a file, in whatever format
> >> >one desires, directly from the Save dialog.
> >> 
> >> A trivially unimportant difference. Most people would either figure it
> >> out for themselves, or have understood it in short order after a few
> >> posts. As it was "Adam" is either terminally thick, or was being
> >> deliberately obtuse with a view to trolling, or is Harry Worth.
> >
> > Plus given the switch between RTF and plain text changes formatting
> > options available, as well as save options, it only makes sense to have
> > it be a menu option, instead of a 'Save As…' dialog option.
> 
> Absolutely. Loss of data is something that should be respected in the
> design. Converting a rich text document containing images, styling, and
> so on to a plain text document removes those things which may be
> important to users. Doing that *while* saving the document isn't a good
> user experience.

Aye. Plus it makes no sense to me in a text editor/lightweight word
processor to have to Save As in order to switch between plain text and
RTF editing modes.
-- 
If you're not part of the solution, you're part of the precipitate.

[toc] | [prev] | [next] | [standalone]

#29395

From	JF Mezei <jfmezei.spamnot@vaxination.ca>
Date	2015-04-22 17:00 -0400
Message-ID	<55380be6$0$19479$c3e8da3$b1356c67@news.astraweb.com>
In reply to	#29375

On 15-04-22 15:10, Jamie Kahn Genet wrote:

> Aye. Plus it makes no sense to me in a text editor/lightweight word
> processor to have to Save As in order to switch between plain text and
> RTF editing modes.

You don't have to use SAVE AS to change your editor mode. There is a
menu option to do that.

But this doesn't mean that you shouldn't be able to use your rich text
doc as a source to do a SAVE AS to plain text without first having to
conver the doc to plain text.

The big UI question is whether a SAVE AS operation should change the
context of the current window to that of the newly created copy, or
whether the original document should remain the context of the window.

(say I have A.RTF in rich text, and do a SAVE AS  B.txt in plain text,
should the window still have A.RTF in rich text or  B.txt in plain text
?). There are arguments for both scenarios.

Photoshop has "SAVE AS" and "SAVE A COPY" to distinguich between the two.

[toc] | [prev] | [next] | [standalone]

#29406

From	jamiekg@wizardling.geek.nz (Jamie Kahn Genet)
Date	2015-04-23 10:55 +1200
Message-ID	<1m3bvj9.1fkz67913n9q4bN%jamiekg@wizardling.geek.nz>
In reply to	#29395

JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:

> On 15-04-22 15:10, Jamie Kahn Genet wrote:
> 
> > Aye. Plus it makes no sense to me in a text editor/lightweight word
> > processor to have to Save As in order to switch between plain text and
> > RTF editing modes.
> 
> You don't have to use SAVE AS to change your editor mode. There is a
> menu option to do that.

Yes, I know :-) But Alan didn't.

> But this doesn't mean that you shouldn't be able to use your rich text
> doc as a source to do a SAVE AS to plain text without first having to
> conver the doc to plain text.

Just change format, then Save As.

> The big UI question is whether a SAVE AS operation should change the
> context of the current window to that of the newly created copy, or
> whether the original document should remain the context of the window.
> 
> (say I have A.RTF in rich text, and do a SAVE AS  B.txt in plain text,
> should the window still have A.RTF in rich text or  B.txt in plain text
> ?). There are arguments for both scenarios.
> 
> Photoshop has "SAVE AS" and "SAVE A COPY" to distinguich between the two.

Save As, so far as I recall, always left one with the new document in
it's new form on screen, if the app could handle the document type
exported to.
-- 
If you're not part of the solution, you're part of the precipitate.

[toc] | [prev] | [next] | [standalone]

#29407

From	Alan Baker <email@domain.com>
Date	2015-04-22 15:56 -0700
Message-ID	<mh98vn$hr$1@news.datemas.de>
In reply to	#29406

On 2015-04-22 22:55:28 +0000, Jamie Kahn Genet said:

> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> 
>> On 15-04-22 15:10, Jamie Kahn Genet wrote:
>> 
>>> Aye. Plus it makes no sense to me in a text editor/lightweight word
>>> processor to have to Save As in order to switch between plain text and
>>> RTF editing modes.
>> 
>> You don't have to use SAVE AS to change your editor mode. There is a
>> menu option to do that.
> 
> Yes, I know :-) But Alan didn't.

Again: "Adam didn't", not "Alan didn't"

Alan must certainly did know.

:-)

[toc] | [prev] | [next] | [standalone]

#29412

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-22 23:57 +0000
Message-ID	<cpqqruF3ijcU7@mid.individual.net>
In reply to	#29407

On 2015-04-22, Alan Baker <email@domain.com> wrote:
> On 2015-04-22 22:55:28 +0000, Jamie Kahn Genet said:
>
>> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
>> 
>>> On 15-04-22 15:10, Jamie Kahn Genet wrote:
>>> 
>>>> Aye. Plus it makes no sense to me in a text editor/lightweight word
>>>> processor to have to Save As in order to switch between plain text and
>>>> RTF editing modes.
>>> 
>>> You don't have to use SAVE AS to change your editor mode. There is a
>>> menu option to do that.
>> 
>> Yes, I know :-) But Alan didn't.
>
> Again: "Adam didn't", not "Alan didn't"
>
> Alan must certainly did know.
>
>:-)

I would expect Alan to know, yes. : D

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#29414

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-23 00:57 +0000
Message-ID	<cpquc4F3ijcU8@mid.individual.net>
In reply to	#29395

On 2015-04-22, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 15-04-22 15:10, Jamie Kahn Genet wrote:
>
>> Aye. Plus it makes no sense to me in a text editor/lightweight word
>> processor to have to Save As in order to switch between plain text and
>> RTF editing modes.
>
> You don't have to use SAVE AS to change your editor mode. There is a
> menu option to do that.
>
> But this doesn't mean that you shouldn't be able to use your rich text
> doc as a source to do a SAVE AS to plain text without first having to
> conver the doc to plain text.

I don't have a problem with that as long as the user is fully aware of
what is happening.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#29415

From	Your Name <YourName@YourISP.com>
Date	2015-04-23 13:09 +1200
Message-ID	<230420151309345357%YourName@YourISP.com>
In reply to	#29395

In article <55380be6$0$19479$c3e8da3$b1356c67@news.astraweb.com>, JF
Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 15-04-22 15:10, Jamie Kahn Genet wrote:
> > 
> > Aye. Plus it makes no sense to me in a text editor/lightweight word
> > processor to have to Save As in order to switch between plain text and
> > RTF editing modes.
> 
> You don't have to use SAVE AS to change your editor mode. There is a
> menu option to do that.
> 
> But this doesn't mean that you shouldn't be able to use your rich text
> doc as a source to do a SAVE AS to plain text without first having to
> conver the doc to plain text.
> 
> The big UI question is whether a SAVE AS operation should change the
> context of the current window to that of the newly created copy, or
> whether the original document should remain the context of the window.
> 
> (say I have A.RTF in rich text, and do a SAVE AS  B.txt in plain text,
> should the window still have A.RTF in rich text or  B.txt in plain text
> ?). There are arguments for both scenarios.
> 
> Photoshop has "SAVE AS" and "SAVE A COPY" to distinguich between the two.

"Save A Copy" is a completely redundant and silly option. You simply
"Save As" without changing the file format ... or duplicate the file in
the Finder.

[toc] | [prev] | [next] | [standalone]

#29416

From	Savageduck <savageduck1@{REMOVESPAM}me.com>
Date	2015-04-22 20:19 -0700
Message-ID	<2015042220195338205-savageduck1@REMOVESPAMme.com>
In reply to	#29415

On 2015-04-23 01:09:34 +0000, Your Name said:

> In article <55380be6$0$19479$c3e8da3$b1356c67@news.astraweb.com>, JF
> Mezei <jfmezei.spamnot@vaxination.ca> wrote:
>> On 15-04-22 15:10, Jamie Kahn Genet wrote:
>>> 
>>> Aye. Plus it makes no sense to me in a text editor/lightweight word
>>> processor to have to Save As in order to switch between plain text and
>>> RTF editing modes.
>> 
>> You don't have to use SAVE AS to change your editor mode. There is a
>> menu option to do that.
>> 
>> But this doesn't mean that you shouldn't be able to use your rich text
>> doc as a source to do a SAVE AS to plain text without first having to
>> conver the doc to plain text.
>> 
>> The big UI question is whether a SAVE AS operation should change the
>> context of the current window to that of the newly created copy, or
>> whether the original document should remain the context of the window.
>> 
>> (say I have A.RTF in rich text, and do a SAVE AS  B.txt in plain text,
>> should the window still have A.RTF in rich text or  B.txt in plain text
>> ?). There are arguments for both scenarios.
>> 
>> Photoshop has "SAVE AS" and "SAVE A COPY" to distinguich between the two.
> 
> "Save A Copy" is a completely redundant and silly option. You simply
> "Save As" without changing the file format ... or duplicate the file in
> the Finder.

In Photoshop *Save as a Copy* in the *Save as* dialog serves a purpose, 
paricularly if you are working on a 16-bit TIFF or PSD and want to save 
a JPEG.
JPEGs a 8-bit, so you have two options, convert the TIFF/PSD you are 
working on to 8-bit, and then *Save as*, or when in the *Save as* 
dialog, check the Format as JPEG and the *Save As a Copy* check box. 
That way an 8-bit JPEG copy of the 16-bit TIFF/PSD is saved without 
degrading the source file.

-- 
Regards,

Savageduck

[toc] | [prev] | [next] | [standalone]

#29417

From	Savageduck <savageduck1@{REMOVESPAM}me.com>
Date	2015-04-22 20:21 -0700
Message-ID	<2015042220215694985-savageduck1@REMOVESPAMme.com>
In reply to	#29416

On 2015-04-23 03:19:53 +0000, Savageduck said:

> On 2015-04-23 01:09:34 +0000, Your Name said:
>> In article <55380be6$0$19479$c3e8da3$b1356c67@news.astraweb.com>, JF
>> Mezei <jfmezei.spamnot@vaxination.ca> wrote:
>>> On 15-04-22 15:10, Jamie Kahn Genet wrote:
>>>> 
>>>> Aye. Plus it makes no sense to me in a text editor/lightweight word
>>>> processor to have to Save As in order to switch between plain text and
>>>> RTF editing modes.
>>> 
>>> You don't have to use SAVE AS to change your editor mode. There is a
>>> menu option to do that.
>>> 
>>> But this doesn't mean that you shouldn't be able to use your rich text
>>> doc as a source to do a SAVE AS to plain text without first having to
>>> conver the doc to plain text.
>>> 
>>> The big UI question is whether a SAVE AS operation should change the
>>> context of the current window to that of the newly created copy, or
>>> whether the original document should remain the context of the window.
>>> 
>>> (say I have A.RTF in rich text, and do a SAVE AS  B.txt in plain text,
>>> should the window still have A.RTF in rich text or  B.txt in plain text
>>> ?). There are arguments for both scenarios.
>>> 
>>> Photoshop has "SAVE AS" and "SAVE A COPY" to distinguich between the two.
>> 
>> "Save A Copy" is a completely redundant and silly option. You simply
>> "Save As" without changing the file format ... or duplicate the file in
>> the Finder.

In Photoshop *Save as a Copy* in the *Save as* dialog serves a purpose, 
paricularly if you are working on a 16-bit TIFF or PSD and want to save 
a JPEG.
JPEGs a 8-bit, so you have two options, convert the TIFF/PSD you are 
working on to 8-bit, and then *Save as*, or when in the *Save as* 
dialog, check the Format as JPEG and the *Save As a Copy* check box. 
That way an 8-bit JPEG copy of the 16-bit TIFF/PSD is saved without 
degrading the source file.

-- 
Regards,

Savageduck

[toc] | [prev] | [next] | [standalone]

#29419

From	Tim Streater <timstreater@greenbee.net>
Date	2015-04-23 08:46 +0100
Message-ID	<230420150846444418%timstreater@greenbee.net>
In reply to	#29415

In article <230420151309345357%YourName@YourISP.com>, Your Name
<YourName@YourISP.com> wrote:

>In article <55380be6$0$19479$c3e8da3$b1356c67@news.astraweb.com>, JF
>Mezei <jfmezei.spamnot@vaxination.ca> wrote:

>> Photoshop has "SAVE AS" and "SAVE A COPY" to distinguich between the two.
>
>"Save A Copy" is a completely redundant and silly option. You simply
>"Save As" without changing the file format ... or duplicate the file in
>the Finder.

I don't know about PS, but I use TextWrangler's Save a Copy all the
time. If you use Save As in TW (and perhaps this is how it works in
other apps, too), then after Save As you're no longer editing the
original file, you're now editing the copy you made with Save As, under
its new name.

Save a Copy, by contrast, allows you to save somewhere else, while
leaving you editing the original file. When doing this, I really don't
want to be leaving the app I'm using (TW).

-- 
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf

[toc] | [prev] | [next] | [standalone]

#29401

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-22 22:01 +0000
Message-ID	<cpqk25F3ijcU2@mid.individual.net>
In reply to	#29375

On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
> Jolly Roger <jollyroger@pobox.com> wrote:
>
>> On 2015-04-22, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
>> > Tim Streater <timstreater@greenbee.net> wrote:
>> >
>> >> In article <alpine.OSX.2.20.1504221037270.31550@mako.ath.cx>, David
>> >> Ritz <dritz@mindspring.com> wrote:
>> >> 
>> >> >As it happens, I agree with Adam, that the way TextEdit works isn't as
>> >> >intuitive as having the option of saving a file, in whatever format
>> >> >one desires, directly from the Save dialog.
>> >> 
>> >> A trivially unimportant difference. Most people would either figure it
>> >> out for themselves, or have understood it in short order after a few
>> >> posts. As it was "Adam" is either terminally thick, or was being
>> >> deliberately obtuse with a view to trolling, or is Harry Worth.
>> >
>> > Plus given the switch between RTF and plain text changes formatting
>> > options available, as well as save options, it only makes sense to have
>> > it be a menu option, instead of a 'Save As…' dialog option.
>> 
>> Absolutely. Loss of data is something that should be respected in the
>> design. Converting a rich text document containing images, styling, and
>> so on to a plain text document removes those things which may be
>> important to users. Doing that *while* saving the document isn't a good
>> user experience.
>
> Aye. Plus it makes no sense to me in a text editor/lightweight word
> processor to have to Save As in order to switch between plain text and
> RTF editing modes.

Totally agree.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

Page 13 of 20 — ← Prev page 1 … 11 12 [13] 14 15 … 20 Next page →

csiph-web

How do mac users create a blank text file where you want it?

Contents

#29413

#29411

#29399

#29400

#29405

#29410

#29418

#29398

#29368

#29375

#29395

#29406

#29407

#29412

#29414

#29415

#29416

#29417

#29419

#29401