none
Behaviours RRS feed

  • Question

  • I was going to start of by asking why  onmouseout="FP_changePropRestore()" wasn't doing what i wanted it to do on IE 9 but i see from here that there is an issue with behaviours. Presuming that what has went before me is known to the powers to be and will be modified in a later flavour of Expression Web if i skipped this 'tutorial' and finished the book would i be disadvantaged if i knew what it was supposed to do instead of what it did not do.... Understand?! lol


    Philip
    Tuesday, January 17, 2012 7:45 PM

Answers

  • No disadvantage at all. As illustrated in that thread, EW's Behaviors are but one of a multitude of ways to accomplish an end, any one of which may be equally valid or appropriate, but Behaviors have the character of being bloated, obsolete, obtrusive junk code. Skip it. Learn the rest of the stuff (except "Layers ;-), and you're good to go.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.
    • Edited by paladyn Tuesday, January 17, 2012 8:03 PM
    • Marked as answer by paxmas.eu Tuesday, January 17, 2012 8:08 PM
    Tuesday, January 17, 2012 8:02 PM
  • fp-style means nothing to HTML or CSS.  Ditto for fp-title.  You are mistaking javascript defined by behaviors for something that anything else would understand.

    What you show above is not using CSS to create interactive buttons.

    • Marked as answer by paxmas.eu Tuesday, January 17, 2012 11:29 PM
    Tuesday, January 17, 2012 9:01 PM
  • HTML5 friendly and use CSS to create interactive buttons:

    Nah, baby, nah! As Kathy pointed out, those Interactive Buttons are not CSS, but javascript, and were created for FrontPage contemporaneously with the Behaviors code, using exactly the same kind of bloated, obsolete, obtrusive junk javascript code. It is no more recommended for use than is the Behaviors code.

    Also, unless you are knowledgeable enough, and prepared to implement shim code, it's still a bit early to be concerning yourself with HTML5. Frankly, at your stage of development in this process, I would concern myself more with "getting it right" using current standards than with playing with a future standard. There are still enough gotachas and inconsistencies in the not-ready-for-prime-time HTML5 and CSS3 "standards" that you really to need to know what you're doing to account for them.

    Whatever... in any event, anything that you see that was carried over from FP, like FP Behaviors and Interactive Buttons, can safely be ignored.  ;-)

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.
    • Marked as answer by paxmas.eu Tuesday, January 17, 2012 11:35 PM
    Tuesday, January 17, 2012 9:22 PM
  • Scott I always wanted to run before i could walk:) From the Page Editor Options > Authoring tab what settings do you recommend for a white belt in web creation?

    What do you say I just tell you what I use?   ;-)

    Doctype: XHTML 1.0 Transitional

    Secondary Schema: XHTML 1.0 Transitional

    CSS Schema: CSS 2.1

    This will enable EW to use syntax highlighting and compatibility checking to notify you of issues in your markup, enforcing a degree of rigor that will serve you well while learning the fundamentals of the technology.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.
    • Marked as answer by paxmas.eu Thursday, January 19, 2012 12:03 PM
    Wednesday, January 18, 2012 3:20 PM

All replies

  • No disadvantage at all. As illustrated in that thread, EW's Behaviors are but one of a multitude of ways to accomplish an end, any one of which may be equally valid or appropriate, but Behaviors have the character of being bloated, obsolete, obtrusive junk code. Skip it. Learn the rest of the stuff (except "Layers ;-), and you're good to go.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.
    • Edited by paladyn Tuesday, January 17, 2012 8:03 PM
    • Marked as answer by paxmas.eu Tuesday, January 17, 2012 8:08 PM
    Tuesday, January 17, 2012 8:02 PM
  • Thanks Scott.

     

    From that information then should i not be worried about the fact that when change DOC to HTML5 friendly and use CSS to create interactive buttons:

     

    <p><a href="buttons.html">
    <img id="img1" alt="Interactive button " fp-style="fp-btn: Glass Rectangle 1; fp-font-color-normal: #808080; fp-font-color-press: #C0C0C0" fp-title="Interactive button " height="25" onmousedown="FP_swapImg(1,0,/*id*/'img1',/*url*/'buttons/button46.jpg')" onmouseout="FP_swapImg(0,0,/*id*/'img1',/*url*/'buttons/button44.jpg')" onmouseover="FP_swapImg(1,0,/*id*/'img1',/*url*/'buttons/button45.jpg')" onmouseup="FP_swapImg(0,0,/*id*/'img1',/*url*/'buttons/button45.jpg')" src="buttons/button44.jpg" style="border: 0" width="125"></a></p>

    The attribute above, which i have highlighted, in HTML 5 is not permitted for the <img> tag: the dislike, the red underline, is displayed under what i have put in italics.


    Philip
    Tuesday, January 17, 2012 8:19 PM
  • fp-style means nothing to HTML or CSS.  Ditto for fp-title.  You are mistaking javascript defined by behaviors for something that anything else would understand.

    What you show above is not using CSS to create interactive buttons.

    • Marked as answer by paxmas.eu Tuesday, January 17, 2012 11:29 PM
    Tuesday, January 17, 2012 9:01 PM
  • HTML5 friendly and use CSS to create interactive buttons:

    Nah, baby, nah! As Kathy pointed out, those Interactive Buttons are not CSS, but javascript, and were created for FrontPage contemporaneously with the Behaviors code, using exactly the same kind of bloated, obsolete, obtrusive junk javascript code. It is no more recommended for use than is the Behaviors code.

    Also, unless you are knowledgeable enough, and prepared to implement shim code, it's still a bit early to be concerning yourself with HTML5. Frankly, at your stage of development in this process, I would concern myself more with "getting it right" using current standards than with playing with a future standard. There are still enough gotachas and inconsistencies in the not-ready-for-prime-time HTML5 and CSS3 "standards" that you really to need to know what you're doing to account for them.

    Whatever... in any event, anything that you see that was carried over from FP, like FP Behaviors and Interactive Buttons, can safely be ignored.  ;-)

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.
    • Marked as answer by paxmas.eu Tuesday, January 17, 2012 11:35 PM
    Tuesday, January 17, 2012 9:22 PM
  • I'm not sure if this *.PNG image can be enlarged but: mea culpa Kathy, I was thinking of the CSS generated button and writing about the EW4 automatic generator.

    Scott I always wanted to run before i could walk:) From the Page Editor Options > Authoring tab what settings do you recommend for a white belt in web creation?


    Philip
    Tuesday, January 17, 2012 11:35 PM
  • From what I can see (which may be completely wrong since I can hardly make out anything in that image) you are showing the FrongPage "Interactive Button".

    There is no "CSS generated button".  If you want to style a link to change when hovered, etc., that's up to you to do yourself.  If you mean something else, I you'll have to clarify.

    Tuesday, January 17, 2012 11:53 PM
  • From what I can see (which may be completely wrong since I can hardly make out anything in that image) you are showing the FrongPage "Interactive Button".

    There is no "CSS generated button".  If you want to style a link to change when hovered, etc., that's up to you to do yourself.  If you mean something else, I you'll have to clarify.


    As you may have guess I am just reading a book and doing its lessons:

    <h2>CSS Buttons</h2>
    <p><a class="basicBox" href="buttons.html">Basic Box Buttons</a>

    .basicBox {
     font-family: Arial, Helvetica, sans-serif;
     font-size: .8em;
     font-weight: bold;
     text-transform: uppercase;
     color: #FFFFFF;
     text-decoration: none;
     background-color: #99CCFF;
     border-style: solid;
     border-width: 2px;
     border-color: #0F87FF #004F9D #004F9D #0F87FF;
    }
    .basicBox:hover {
     font-family: Arial, Helvetica, sans-serif;
     font-size: .8em;
     font-weight: bold;
     text-transform: uppercase;
     color: #000000;
     text-decoration: none;
     background-color: #99CCFF;
     border-style: solid;
     border-width: 2px;
     border-color: #004F9D #0F87FF #0F87FF #004F9D;
    }


    Philip
    Wednesday, January 18, 2012 1:26 PM
  • You've completely lost me.  What has that to do with the image you posted?  (Which, again, I'm having to guess what is.  How about just telling us?)
    Wednesday, January 18, 2012 2:03 PM
  • Scott I always wanted to run before i could walk:) From the Page Editor Options > Authoring tab what settings do you recommend for a white belt in web creation?

    What do you say I just tell you what I use?   ;-)

    Doctype: XHTML 1.0 Transitional

    Secondary Schema: XHTML 1.0 Transitional

    CSS Schema: CSS 2.1

    This will enable EW to use syntax highlighting and compatibility checking to notify you of issues in your markup, enforcing a degree of rigor that will serve you well while learning the fundamentals of the technology.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.
    • Marked as answer by paxmas.eu Thursday, January 19, 2012 12:03 PM
    Wednesday, January 18, 2012 3:20 PM
  • You've completely lost me.  What has that to do with the image you posted?  (Which, again, I'm having to guess what is.  How about just telling us?)

    If the book tells me that that code is CSS and it produces the button (see above) then who am I to contradict the author - i was refering to that when i made the mistake: i.e. in the design view of the PNG image the CSS button is below the interactive one.
    Philip
    • Edited by paxmas.eu Thursday, January 19, 2012 12:04 PM Spelling mistake - author
    Thursday, January 19, 2012 12:00 PM
  • Scott I always wanted to run before i could walk:) From the Page Editor Options > Authoring tab what settings do you recommend for a white belt in web creation?

    What do you say I just tell you what I use?   ;-)

    Doctype: XHTML 1.0 Transitional

    Secondary Schema: XHTML 1.0 Transitional

    CSS Schema: CSS 2.1

    This will enable EW to use syntax highlighting and compatibility checking to notify you of issues in your markup, enforcing a degree of rigor that will serve you well while learning the fundamentals of the technology.

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.


    OK Scott i shall bite my lip until i can walk competently;) After all whats the point of giving advise if its not taken.

    Thanks.


    Philip


    Got a question to ask of you Scott; and thank god for the light of Wikipedia! Why did you not use XHTML 1.0T and not its upgrade; 1.1 - is transitional a key word and if so what the omission of it for 1.1. mean on 1.1?

    • Edited by paxmas.eu Thursday, January 19, 2012 12:16 PM
    Thursday, January 19, 2012 12:03 PM
  • Phil, I've said it more than once: I can't make out that image and had to guess.  Unless you tell me, I have no idea what you are referring to.
    Thursday, January 19, 2012 3:14 PM
  • Phil, I've said it more than once: I can't make out that image and had to guess.  Unless you tell me, I have no idea what you are referring to.

    I am used to saving PNG images using the right click of the mouse, save as, and the viewing said image (where it automatically enlarges) in Windows Photo Viewer.  
    Philip
    Thursday, January 19, 2012 4:51 PM
  • Got a question to ask of you Scott; and thank god for the light of Wikipedia! Why did you not use XHTML 1.0T and not its upgrade; 1.1 - is transitional a key word and if so what the omission of it for 1.1. mean on 1.1?

    Transitional is a qualifier to distinguish it from Strict and Frameset, the other two flavors of XHTML 1.0. XHTML 1.0T is basically a reformulation of HTML 4.x using XML rules for validity and well-formedness, but still containing the same elements, etc., as HTML 4.01. XHTML 1.0S goes further and eliminates a number of elements and attributes which, to me, make little sense unless the primary objective is to limit the developer while providing little to nothing in the way of advantage. XHTML1.0 Frameset we don't even want to talk about, nor, indeed, anything with "Frameset" in its name, as framed sites have long ago gone out of favor among experienced developers.  ;-)

    XHTML 1.1 is not a "next version of XHTML 1.0" as the unfortunate naming would imply. It is an entirely different formulation meant to be used in pure XML environments, along with other XML variants such as MathML and SVG. It is useless for general-purpose Web development, and should never have been named as it was. Stick with XHTML 1.0T while you are learning. Most current training materials are written with it in mind, and, of course, EW has excellent markup proofing tools built around using it. It's your best bet.  ;-)

    cheers,
    scott


    Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.
    • Edited by paladyn Thursday, January 19, 2012 5:31 PM
    Thursday, January 19, 2012 5:03 PM
  • Well Philip, I have no idea why you introduced that to this thread.  Nevermind that entire topic.
    Thursday, January 19, 2012 5:08 PM
  • Well Philip, I have no idea why you introduced that to this thread.  Nevermind that entire topic.

    Thank you your help Kathy, as the above is a way of viewing images that are blown up I thought ity may be of help. This thread has been answered. 
    Philip
    Thursday, January 19, 2012 5:26 PM