Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: open
Want to be able to add
elements without hand coding? Do this...
When working with FrontPage and CSS, you have to be very specific with your stylesheets. If you want inline elements to appear in your formatting menu (as inline elements), you need to precede your classes with
. For example, let's say you want to make a word blue. You would need something like this in your stylesheet...
Once you append the
to the class, that will now appear in FP's styling menu with an a (with underscore) symbol to the left of it. This means that it is an inline element. Block level elements have a ¶ to the left of them which means they are block level.
If your style sheets have generic classes that start with a dot (.), they will appear in the menu without the a or ¶ symbols and will be treated as if they were block level elements.
FP's styling menu is sorted in a specific way. All of your predefined block level elements will appear at the top of the list. Then your generic classes will appear (in alphabetical order). And then your specific block and inline classes will appear at the bottom, in alphabetical order.
Any idea how to make it so when copying text from a website, dropping it in to html in FP, it doesn't try to add the style also?
I need to clarify what you are doing. When you say dropping it in to html, are you doing that through the FP HTML View? Actually pasting directly into the HTML code?
From my experience, you can paste from HTML to HTML with no problems. But, what you cannot do is paste from HTML into WYSIWYG or vice versa. I'm not sure if that applies in your case.
Right now, I copy from our website to notepad to strip the style, then drop in html.
I do this quite a bit myself, Notepad (and other similar products) are also a great companion to FrontPage.
I should point out at this point that you've probably run into a bug with the WYSIWYG view of FP when using external style sheets. Every now and then, the page styles appear to be missing. I'm not exactly sure what causes this, but it is easy to fix.
Make sure you have the page selected (just click anywhere in the page) and click your Refresh button or F5 to refresh the page. This will cause the styles to come back into the page and everything will be hunky dory.
Note: The Refresh button is in your Standard Toolbar and has two green opposing arrows (just like IE). You can also F5 (a standard command for refreshing a page in IE).
Anyone else ever run into this? It has been an issue for me as far back as I can remember. I think it has something to do with the style sheets and absolute positioning, not sure though.
Note: I edit at the browser level through IE live on the server. This may also be a part of the issue. The style sheets sometimes don't connect with the page. Those of you working locally and then publishing may not experience this.
Important Note: Close all pages you have open in your FrontPage Editor before renaming files and/or folders.
In the Folder List, right-click the file or folder that you want to rename. If the Folder List is hidden, on the View menu, click Folder List. On the shortcut menu, click Rename. Type a new name for the file or folder. When renaming a file, do not change or omit the file extension. For example, if you rename a file named index.asp to index.htm it might render the file as unusable. You should always rename a file or folder in a Web site by using this procedure. Microsoft FrontPage automatically repairs any hyperlinks to or from the renamed file (or files in the renamed folder).
Okay, I cheated on this tip. The above is from the FrontPage help menu and best describes the process of renaming files and/or folders. What they don't tell you is...
Important Note: Close all pages you have open in your FrontPage Editor before renaming files and/or folders.
I've run into issues where hyperlinks in open documents did not get updated properly when renaming a file and/or folder. I've noticed that if all pages are closed when performing the renaming procedure, all goes well.
Quick Naming Tip
You should go through your webs and perform a find and replace routine for this...
Find: /index.htm or /index.asp or any other index page links.
Replace with: /
I learned years ago that if you are linking to a root level index page, there is no need to use the index file name. This will save you heartache in the future if you ever decide to change the underlying technology of your website. Unfortunately this only applies to root level index pages. All your other files will have page names and extensions unless you are doing Content Negotiation which is a totally different topic.
This also helps in controlling the inbound linking practices of partners and scrapers. Many people will browse to a page and copy the address from their address bar. Don't give em' any links that have /index.asp on them or whatever technology you are using (index.htm, index.html, index.php, index.jsp, etc.)
If you are using FP 2003, look down in the lower right hand corner of your editing window. You'll most likely see these dimensions preceded with a page size icon...
760 x 420
The default setting out of the box is for 800 x 600 targeted screen resolution which equates to the above 760 x 420 maximized viewing pleasure.
Single click that number and bring up the menu for more options. Select one of the other resolution options and watch what happens to your layout canvas. It will grow or shrink depending on the resolution you choose.
This is a great feature for visual development. If you are working in a pixel perfect environment like I do using absolute positioning and fixed widths, having your working canvas set to show what a maximized browser window will show is a big plus!
And now that Rulers and Grids have been added to the WYSIWYG environment, my development process just became that much more efficient. I've been using a Screen Caliper Tool from Iconico [iconico.com] for years to measure on-screen distances in FrontPage. Now I don't need it as much but I still use it because it has a lot more features. If you don't have one, go grab the free version now, it's a great little app to have in your toolbox.
The Windows version of the Screen Calipers can be opened directly from Microsoft FrontPage® making designing webpages much seamless and straightforward. You may also find us on the Microsoft Office Marketplace.
Version 3.2 (and later) of the Screen Calipers for Windows adds the ability to fully control the Calipers from any other application. Using Microsoft's COM Automation you can open the Calipers from your application and set and get the current measurement and many more properties of the Calipers.
No, I am not affiliated with Iconico. I just think this measurement tool is a great app to have when designing in WYSIWYG mode.
I had no idea.
[ bookmarking this thread ]
Generally, I only use FrontPage when I have to troubleshoot some poor sucker's FrontPage site. :-) I'm still doing markup by hand in (eek!) vi, but this thread has made me interested in looking at FrontPage again.
Thanks to everyone who contributed/is contributing here: I'm learning a lot.
That funny dotted grey line that runs horizontly across the page indicates "the fold." Its position changes with the page size you've chosen and is a neat tool to help you position items above the fold, that is, in the visitor's viewport without them having to scroll down.
There are things I can't do in DW that were a breeze in FP, admittedly it may just be the learning curve but the net result is I'm not updating my site while I'm learning. For instance, I don't use SSI on my site so found FP's dynamic include really useful. Also, what's the easy way of highlighting just the recently modified files and PUTting them on the live site? I dunno, but it's so obvious in FP.
Those people that turned their noses up at FP mostly, either:
a) Hadn't actually used it (at least not as much as I had), or
b) Were anti-Microsoft snobs. You know the type, they have those stupid furry penguins on their desks...
My site's still a hobby and has earned me a few thousand dollars, which I'm happy with. With the momentum I have from this site and my familiarity with FP I'm sure I can earn a lot more.
I'll stick with FP for now.
I had hoped there could be more threads about FP without anyone feeling compelled to swoop in with a negative opinion.
I hate to ask any FP questions because I know it is very likely I will be insulted. And this has been going on for years. It is so old and so boring.
If I ask a question and you can help, thank you. But chiming in with "I don't know, I hate FP." is just incredibly rude. And many people say much worse. If I ask a FP question, and you hate FP, it is a safe bet the question was not asked of you. It is acceptable to leave the thread without posting.
A lot of us poor suckers are making good money from sites made with FP, and isn't that what it's all about? And, of course, a lot of us are having great fun, and it's about that, too.
I always wonder: why do so many people care what wysiwyg I use? Why do they feel this need to state their negative opinions when they have nothing to say that we haven't all heard a thousand times before?
I hate to ask any FP questions because I know it is very likely I will be insulted. And this has been going on for years. It is so old and so boring...
I have to agree. It seems like every post with a question about FP gets a few on-topic replies before someone feels compelled to post something like "FP Sucks".
Well, that's fine - that is their opinion. But it has no place in the thread. If people want to bash FP rather than contributing to the questions, then start your own thread about how you hate FP and MS etc.
And quite frankly, I don't CARE if you think FP sucks. If I wanted to know if you think FP sucked, I would post a message titled "Does FP Suck?".
If people want to bash FP rather than contributing to the questions, then start your own thread about how you hate FP and MS etc.
I have to agree with Wlauzon and Lilliabeth. I also get tired of the lame, single-line responses that can only suggest "dump FP" as an answer. With that kind of response, it's not only obvious the responder hasn't used FP in years, but it makes me also suspect their knowledge about ANY subject in these forums is either blatantly biased or badly misinformed, or both. If they are unable to advance the discussion by adding something meaningful, they should save the bandwidth and move on.
Just my opinion...
Should I upgrade to v2003, or are we expecting a new version this year?
I would do the upgrade now so you can get accustomed to the interface changes as many of them are prevalent in what I've seen from FrontPage 12 which is the code name for the next version due out this year sometime. I remember reading somewhere that it may eventually be named SharePoint Designer as everything now revolves around SharePoint Team Services. You'll want to start reading up on that. ;)
FrontPage 12 will make it easier to integrate data from external sources into your Web applications. It will also provide the ability to build custom application workflows, Web forms, and data views.
I know that I for one would not buy it if it was primarily aimed at that.