This is Interesting: Free Magazines for Graphics designers and webmasters
Home > Archive > Dreamweaver > September 2005 > DW8, TXT Files, Bug?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
DW8, TXT Files, Bug?
|
|
|
| Okay, first of all, I'm having trouble understanding the preference for Open
in Code View (Edit > Preferences). What seems to happen is that if you add
an extension to the list, it not only defaults to Code View, but you have
not access at all to Design and Split Views.
But the thing that really has me puzzled is TXT files. I had a TXT file
that I wanted to view as HTML. Frankly, it was HTML, but with a .txt
extension. By default, .TXT was in that list. I wanted to see the file in
Design View (image map). But if I took it out of the list, and double
clicked in the DW Files pane, it opened in Notepad!. If I right click on it
and choose Open With > Dreamweaver, it opens in DW, but I still don't have
access to Design/Split Views.
What's up?
-Jeremy
| |
|
|
"yirm" <yirm.nospam@antispam.tiferet.com> wrote in message
news:dga18m$82j$1@forums.macromedia.com...
> Okay, first of all, I'm having trouble understanding the preference for
> Open
> in Code View (Edit > Preferences). What seems to happen is that if you
> add
> an extension to the list, it not only defaults to Code View, but you have
> not access at all to Design and Split Views.
>
> But the thing that really has me puzzled is TXT files. I had a TXT file
> that I wanted to view as HTML. Frankly, it was HTML, but with a .txt
> extension. By default, .TXT was in that list. I wanted to see the file
> in
> Design View (image map). But if I took it out of the list, and double
> clicked in the DW Files pane, it opened in Notepad!. If I right click on
> it
> and choose Open With > Dreamweaver, it opens in DW, but I still don't have
> access to Design/Split Views.
>
> What's up?
I really don't know what else you can expect if it's a .txt extension....
tim
| |
| Sir_Brizz 2005-09-14, 7:35 pm |
| it would be a nice feature to have TXT files displayed as HTML files if you would like.
| |
|
|
"Sir_Brizz" <webforumsuser@macromedia.com> wrote in message
news:dga3hh$bd7$1@forums.macromedia.com...
> it would be a nice feature to have TXT files displayed as HTML files if
> you would like.
Makes no sense to me. A browser is not going to open a .txt file as an html
file, so why should DW?
tim
--
Tim Gallant
Pactum Web Services: http://www.pactumgroup.com
Tutorials: http://www.pactumgroup.com/tutorials/
| |
|
|
|
| No, it's a text file with JavaScript that's supposed to be placed on an ad
server.
The point is, what should DW care what file extension it is? Can we define
whether or not we get to open files for any given extension or not? I mean,
what's that the "Open in Code View" option there for?
Furthermore, aren't filetypes defined in the extensions.txt file? I tried
Removing the Text line, and adding .txt to the HTML line. Didn't make a
difference. (the change was reflected in the Open File dialog, so I was
editing the correct file.
-jeremy
"Murray *TMM*" <forums@HAHAgreat-web-sights.com> wrote in message
news:dga5on$eje$1@forums.macromedia.com...
> I don't really get it either - is this an INCLUDE file?
| |
| Massimo Foti 2005-09-14, 7:36 pm |
| "yirm" <yirm.nospam@antispam.tiferet.com> wrote in message
news:dga6be$fec$1@forums.macromedia.com...
> The point is, what should DW care what file extension it is? Can we
define
> whether or not we get to open files for any given extension or not?
Yes:
http://www.macromedia.com/cfusion/k...cfm?id=tn_16410
----------------------------
Massimo Foti
Tools for ColdFusion and Dreamweaver developers:
http://www.massimocorner.com
----------------------------
| |
| Michael Fesser 2005-09-14, 11:17 pm |
| ..oO(yirm)
>No, it's a text file with JavaScript that's supposed to be placed on an ad
>server.
Then why does it have a .txt extension? Usually .txt means just that --
simple plain text. For JS files a .js extension is quite common.
>The point is, what should DW care what file extension it is?
How is DW supposed to know how to handle a file if it wouldn't care
about the file extension? If you open a text file then it will be seen
as just that -- simple plain text.
If you want a different behaviour then use a more appropriate extension.
>Can we define
>whether or not we get to open files for any given extension or not?
You want to open .txt files with DW? Makes no sense.
Micha
| |
|
| > Then why does it have a .txt extension? Usually .txt means just that --
> simple plain text. For JS files a .js extension is quite common.
I don't know. That's the way the ad people send it to me, and that's the
way I send it back.
[color=darkred]
> How is DW supposed to know how to handle a file if it wouldn't care
> about the file extension? If you open a text file then it will be seen
> as just that -- simple plain text.
Because what if for whatever reason I want to do it? There is no reason I
can think of why it should not allow me to view any extension I want with
Design View -- usual practice or not.
> If you want a different behaviour then use a more appropriate extension.
Man, I'm glad you're not a programmer for Macromedia. One of the best
things about DW is its flexibility. Software shouldn't force you to do
things a certain way just because it thinks it knows what's best for all
situations.
[color=darkred]
> You want to open .txt files with DW? Makes no sense.
To you it doesn't make sense, but for me, with my workflow, it does.
Otherwise I wouldn't have bothered posting.
-Jeremy
| |
|
| Thank you, Massimo!
I needed to go into MMDocumentTypes.xml.
I *knew* DW had this flexibility.
-Jeremy
"Massimo Foti" <massimo@massimocorner.com> wrote in message
news:dga7jq$h5g$1@forums.macromedia.com...
> "yirm" <yirm.nospam@antispam.tiferet.com> wrote in message
> news:dga6be$fec$1@forums.macromedia.com...
> define
>
> Yes:
> http://www.macromedia.com/cfusion/k...cfm?id=tn_16410
| |
| Massimo Foti 2005-09-15, 4:16 am |
| "yirm" <yirm.nospam@antispam.tiferet.com> wrote in message
news:dgagvc$sfh$1@forums.macromedia.com...
> I needed to go into MMDocumentTypes.xml.
>
> I *knew* DW had this flexibility.
Yes, it does. I just wish MM would provide a GUI on top of it. It would be
much better than hacking around configuration files...
--
----------------------------
Massimo Foti
Tools for ColdFusion and Dreamweaver developers:
http://www.massimocorner.com
----------------------------
| |
| Sir_Brizz 2005-09-15, 7:19 pm |
| I know the conversation's pretty much over, but for me I code alot of php.
Company policy is that all "include" files are named with a .txt extension.
Having a setting in the Preferences to display txt as html would have been
great (did use the MM hack).
| |
| Michael Fesser 2005-09-15, 7:19 pm |
| ..oO(yirm)
>Because what if for whatever reason I want to do it? There is no reason I
>can think of why it should not allow me to view any extension I want with
>Design View -- usual practice or not.
Of course you can do whatever you want. But a lot of standard extensions
serve a particular purpose, it's rather silly to entirely change that if
there are better solutions.
>Man, I'm glad you're not a programmer for Macromedia. One of the best
>things about DW is its flexibility. Software shouldn't force you to do
>things a certain way just because it thinks it knows what's best for all
>situations.
A .txt file is best for plain text. That's nothing a software has to
know, it's common sense.
>
>To you it doesn't make sense, but for me, with my workflow, it does.
>Otherwise I wouldn't have bothered posting.
Then I consider your workflow somewhat flawed. Do you expect .doc files
being spread sheets, .html being executables? Then why the hell should a
..txt file contain scripting code? If you download some text or program
documentation or just want to have a look at a README.txt -- do you want
DW to open them and interpret them as code?
Micha
|
|
|
| | Copyright 2003 - 2008 forum4designers.com Software forum Computer Hardware reviews |
|