[Pro] Problem with Footer?

… unfortunately there is no automatic balancing here in Coda world.

Maybe I’m not following what “balancing” is, but Coda 2 does close open
tags for me. If there is an unclosed tag and I type the < or </ keys, Coda
auto-fills the necessary tag ending.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

And I should add, as with style brackets, when closing any tag Coda 2
briefly hi-lites the tag pairs.


Ernie Simpson

On Tue, May 14, 2013 at 3:43 PM, Ernie Simpson email@hidden wrote:

… unfortunately there is no automatic balancing here in Coda world.

Maybe I’m not following what “balancing” is, but Coda 2 does close open
tags for me. If there is an unclosed tag and I type the < or </ keys, Coda
auto-fills the necessary tag ending.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

That’s true, but in Kelly’s case he needs to find the missing closing tags in a preexisting doc.

Todd

Maybe I’m not following what “balancing” is, but Coda 2 does close open
tags for me. If there is an unclosed tag and I type the < or </ keys, Coda
auto-fills the necessary tag ending.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

In that case, what about using the “PHP & Web Toolkit” plugin, with the
Tidy HTML or CSS feature… will that close up his malformed tags?


Ernie Simpson

On Tue, May 14, 2013 at 3:48 PM, Todd email@hidden wrote:

That’s true, but in Kelly’s case he needs to find the missing closing tags
in a preexisting doc.

Todd
http://xiiro.com

Maybe I’m not following what “balancing” is, but Coda 2 does close open
tags for me. If there is an unclosed tag and I type the < or </ keys,
Coda
auto-fills the necessary tag ending.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

The Coda plugin, I meant to say.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Technically yes. But (at least in my experience, though I have been wrong before) it will also insert a doc type etc. which would break Kelly’s Perch template which is just a partial, no need for the default page structure in his case.

Todd

In that case, what about using the “PHP & Web Toolkit” plugin, with the
Tidy HTML or CSS feature… will that close up his malformed tags?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Hey guys, thanks agin for your help.

Yes, part of the problem was I was coding with Text Wrangle,r so as Ernie pointed out it should keep me from doing stupid stuff, like the mess I created earlier. :slight_smile:


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Todd, the
tag is what I’m using, but I don’t think you have to have the forward slash in HTML 5.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Class styles always start with a period (.) e.g., .classStyle ID > styles start with a hash/pound (#) e.g., #idStyle

In FW, if it’s just a class then add the name (e.g., classStyle) > in the Name field and FW will add the leading period (.) for
you. If it’s an ID style then put name (e.g., #idStyle) in the
Tag field and make sure the Name field is empty.

Thanks Todd. I need to start writing some of this stuff down.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Todd, the
tag is what I’m using, but I don’t think you have to have the forward slash in HTML 5.

The forward slash is only required when coding in XHTML.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Okay, next problem. How do I line my input fields up? Should I put these in a table or is there a better coding solution?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Yes, that’s true, but I didn’t know what doc type you’re using. Besides,
validates as HTML5 (the last time I checked the W3C validator).

Todd

Todd, the
tag is what I’m using, but I don’t think you have to have the forward slash in HTML 5.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Well I can use either. Is it better practice to use
?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I would stick with
for HTML5.

Todd

Well I can use either. Is it better practice to use
?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

If you’re hand-coding, you can use any structural element you like. In Freeway, the easiest thing of all is the table. But if you want a good semantic structure, not just a physical one with limited semantic relevance, try an ordered list or an unordered list. And use the label tag! Here’s a hand-coded example of a form that uses both to great effect:

http://scripty.walterdavisstudio.com/form-styling.html

All the CSS is inline for ease of dissection.

The point of the ordered list is that it reinforces the tab order of the elements. Note also how I’m using the :first-child pseudo-class to set the size and text alignment on the first label in each row, or any input without a preceding label, so there’s a strong visual “spine” to the form.

Walter

On May 14, 2013, at 4:45 PM, RavenManiac wrote:

Okay, next problem. How do I line my input fields up? Should I put these in a table or is there a better coding solution?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 15 May 2013, 1:04 pm, waltd wrote:

If you’re hand-coding, you can use any structural element you like. In Freeway, the easiest thing of all is the table. But if you want a good semantic structure, not just a physical one with limited semantic relevance, try an ordered list or an unordered list. And use the label tag! Here’s a hand-coded example of a form that uses both to great effect:

Form Example

All the CSS is inline for ease of dissection.

The point of the ordered list is that it reinforces the tab order of the elements. Note also how I’m using the :first-child pseudo-class to set the size and text alignment on the first label in each row, or any input without a preceding label, so there’s a strong visual “spine” to the form.

Walter

I’m not sure if I can use the label tag since Perch uses it’s on proprietary tag.


<perch:label for="email">Email Address:</perch:label>
                    <perch:input type="text" value="" id="email" required="true" label="Email" maxlength="50" tabindex="3" class="field" chars="200" />
					<perch:error for="email" type="required">
					<span class="error">Please add your email address.</span>
					</perch:error>

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It’s important to realize that Perch’s “proprietary” tags are converted into normal HTML on output. These extended tags are processed by the PHP interpreter before the page is served. If you are curious, you can view source in your browser while viewing the page as it is served from your Web server. But this template language is fairly consistent and one of the nice features of Perch from an “integration with other tools” standpoint.

Walter

On May 16, 2013, at 2:39 AM, RavenManiac wrote:

On 15 May 2013, 1:04 pm, waltd wrote:

If you’re hand-coding, you can use any structural element you like. In Freeway, the easiest thing of all is the table. But if you want a good semantic structure, not just a physical one with limited semantic relevance, try an ordered list or an unordered list. And use the label tag! Here’s a hand-coded example of a form that uses both to great effect:

Form Example

All the CSS is inline for ease of dissection.

The point of the ordered list is that it reinforces the tab order of the elements. Note also how I’m using the :first-child pseudo-class to set the size and text alignment on the first label in each row, or any input without a preceding label, so there’s a strong visual “spine” to the form.

Walter

I’m not sure if I can use the label tag since Perch uses it’s on proprietary tag.


<perch:label for="email">Email Address:</perch:label>
                   <perch:input type="text" value="" id="email" required="true" label="Email" maxlength="50" tabindex="3" class="field" chars="200" />
					<perch:error for="email" type="required">
					<span class="error">Please add your email address.</span>
					</perch:error>

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

So, I can still use the label tag as you described?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Yes. The “label” text you see in the Perch template will be rendered as an HTML tag in the webpage which you can then target with CSS.

Todd

So, I can still use the label tag as you described?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 16 May 2013, 12:30 pm, waltd wrote:

It’s important to realize that Perch’s “proprietary” tags are converted into normal HTML on output. These extended tags are processed by the PHP interpreter before the page is served. If you are curious, you can view source in your browser while viewing the page as it is served from your Web server. But this template language is fairly consistent and one of the nice features of Perch from an “integration with other tools” standpoint.

Walter

Walter, this worked great on the form. However, because my CSS Menu is also a list it negative impacted that. How can I fix the menu?

http://rcb.idealynx.com/contact-form.php


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options