Yep it is costly. I have it only because my office stopped using it and I was not about to let them toss it. But even at the full cost I figure it's a lot less than having to hire someone. The prices they are quoting are out of this world. Catlady is the only person I know who is affordable that puts out a quality product.
Do you have anything on your site about web software, or would that be putting yourself out of a job?swirt said:
Referring to Namo
In your opinon Is this product a good product for a nice website without all the hidden codes that software like FP tacts on in the background?swirt said:
No I don't have anything on my site about specific software. Too many issues to deal with and not a fear of putting myself out of work. Most of the sites I do now are based on my content managment system so innkeepers can update content without needing me.Do you have anything on your site about web software, or would that be putting yourself out of a job?swirt said:
I'd be interested in what YOU think is a good replacement for FP, for folks like me & JBJ who are willing to try to figure stuff out and can't let go of control of the site!
.
To my knowledge there is only one other editor that has this kind of feature and it only runs on linux. (Disclaimer: I may be wrong, new releases come out too often for me to be 100% certain of this.)
I believe it produces reasonable code (not sure what it does with already mangled code). There are very few web editors in existence today that produce garbage code they way FP did. Microsoft tried to override html standards and thought they were big enough to create and force their own...they weren't. Most of the other companies learned from this.
I guess that why I think it is a good choice for people just starting to free themselves from the ongoing charges of having someone else do it. For $60 bucks, you just can't go wrong. I have a lot of work to do yet, but I barely scratched the surface of what Namo can do and I got a decent site that is easy to update. I am not so smart about what Swirt was saying, but Namo allows me to update Navigation bars and banners and stuff like that in one action that takes a minute or so. I can choose to update all the pages or just the one I have open. It is not Dreamweaver, but isn't too far off.
Hi knkbnb, please don't take this personally, but I can't put my vote behind any editor that can't manage to get the first mandatory line of code in place
oryour code said:
MsoNormal is Microsoft formatting clutter that doesn't belong there.
I don't take it personally at all. It is all an education for me. I would say it is very helpful. Nor should you be expected to put your vote behind Namo based on our Website. The making sure part falls on me and that is a risky bet.
I was able to get a Doc type on there without to much trouble thanks to you pointing me to that validator. I think we are talking operator error on my end.
Don't go beating yourself upI was able to get a Doc type on there without to much trouble thanks to you pointing me to that validator. I think we are talking operator error on my end.
.
It is more than operator error. If a webpage editor doesn't know to put a doctype in, it also won't know what flavor of code to use in creating the page. The doctype chooses the flavor of code. Though when you have the chance you ought to put the doctype on every page, not just your home page.
It has something called Global Find and Replace which can possibly do that. It does have the ability to do a site wide change in WYSIWYG, which works fine.Don't go beating yourself upI was able to get a Doc type on there without to much trouble thanks to you pointing me to that validator. I think we are talking operator error on my end.
.
This brings up a good question though. When you added the doctype to your home page, did Namo ask you if you wanted to add it to all pages? (This is the true power of a templating system.)
.
Did you actually mention a good brand of web editor for we soon to be without FP folks? What would you get if you were us? I don't mind learning something new. And, from what you said, the switch over may be painful. But, better now than when I have a million pages!Don't go beating yourself upI was able to get a Doc type on there without to much trouble thanks to you pointing me to that validator. I think we are talking operator error on my end.
.
This brings up a good question though. When you added the doctype to your home page, did Namo ask you if you wanted to add it to all pages? (This is the true power of a templating system.)
.
It has something called Global Find and Replace which can possibly do that. It does have the ability to do a site wide change in WYSIWYG, which works fine.Don't go beating yourself upI was able to get a Doc type on there without to much trouble thanks to you pointing me to that validator. I think we are talking operator error on my end.
.
This brings up a good question though. When you added the doctype to your home page, did Namo ask you if you wanted to add it to all pages? (This is the true power of a templating system.)
.
It also allows you to create a template, which could include that and then be worked across the site. That was a good way for me to launch a consistent page with the elements that were site wide.
.
I guess that is what I am wondering... if you placed the doctype declaration on your template now, would it add it to every page, or will it only use it on new pages your create from the template?knkbnb said:
HMMMM.. I don't know exactly. that is where the operator error comes in. I wish I knew half the stuff it does, but I am on a need to know basis. A wiz could get the program and have it figured out in days. In my case, the tail is wagging the dog- ALTHOUGH- I now know where the tail is!It has something called Global Find and Replace which can possibly do that. It does have the ability to do a site wide change in WYSIWYG, which works fine.Don't go beating yourself upI was able to get a Doc type on there without to much trouble thanks to you pointing me to that validator. I think we are talking operator error on my end.
.
This brings up a good question though. When you added the doctype to your home page, did Namo ask you if you wanted to add it to all pages? (This is the true power of a templating system.)
.
It also allows you to create a template, which could include that and then be worked across the site. That was a good way for me to launch a consistent page with the elements that were site wide.
.I guess that is what I am wondering... if you placed the doctype declaration on your template now, would it add it to every page, or will it only use it on new pages your create from the template?knkbnb said:
.
