Default classes for form input tags?
Locked
Default classes for form input tags?
 
|
Why is it that form fields get their class initialized by default to match
their type in WAFormInputTag>>with: aBlock self type isNil ifFalse: [ self attributes at: 'type' ifAbsentPut: [ self type ]. self class: self type ]. super with: aBlock. I find it very odd that Seaside would try to impose any classes onto the developer, same applies to WAListTag>>with: and these are the only two cases I could find. Thanks! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 [hidden email] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
smime.p7s (4K)
Re: Default classes for form input tags?
|
|
RE: Default classes for form input tags?
|
|
Good point, thanks. I walked into this as I was integrating a new round of
changes from our designer and had a bit of a head-scratcher when things were out of whack. I guess I'll just ask him not to use any of the types as selectors: text, submit, radio, password, image, hidden, file, checkbox, button. Speaking of silly things like that, any chance we could get an FAQ (or just Q&A) page over at seaside.st? If yes, I don't mind updating it with stuff as I stumble upon the more interesting bits hoping to attract others to join in. There are a few Seaside FAQ's out there, but they seem to be maintained separately and honestly some of them are just a tad obsolete. Cheers, -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 [hidden email] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Avi Bryant Sent: Wednesday, August 09, 2006 1:28 PM To: The Squeak Enterprise Aubergines Server - general discussion. Subject: Re: [Seaside] Default classes for form input tags? On Aug 9, 2006, at 1:24 PM, Boris Popov wrote: > Why is it that form fields get their class initialized by default > to match > their type in > > WAFormInputTag>>with: aBlock > self type isNil ifFalse: [ > self attributes at: 'type' ifAbsentPut: [ self type ]. > self class: self type ]. > super with: aBlock. > > I find it very odd that Seaside would try to impose any classes > onto the > developer, same applies to WAListTag>>with: and these are the only > two cases > I could find. reason for it was. I can say, however, that it's a pretty useful thing to have, in that it lets you use selectors like input.text or input.password in your CSS... Avi _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Re: Default classes for form input tags?
|
|
Re: Default classes for form input tags?
|
|
RE: Default classes for form input tags?
|
|
Stephane,
That's kind of what I was hinting at, but I'm not sure who maintains seaside.st at the moment. If I could get access to the wiki, I'd put some time into pulling various FAQs together in the next couple of weeks before leaving on vacation. Thanks! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 [hidden email] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of stephane ducasse Sent: Thursday, August 10, 2006 10:48 AM To: The Squeak Enterprise Aubergines Server - general discussion. Subject: Re: [Seaside] Default classes for form input tags? On 9 août 06, at 22:39, Boris Popov wrote: > Good point, thanks. I walked into this as I was integrating a new > round of > changes from our designer and had a bit of a head-scratcher when > things were > out of whack. I guess I'll just ask him not to use any of the types as > selectors: text, submit, radio, password, image, hidden, file, > checkbox, > button. > > Speaking of silly things like that, any chance we could get an FAQ > (or just > Q&A) page over at seaside.st? If yes, I don't mind updating it with > stuff as > I stumble upon the more interesting bits hoping to attract others > to join > in. There are a few Seaside FAQ's out there, but they seem to be > maintained > separately and honestly some of them are just a tad obsolete. Indeed we need a FAQ!!!! As a community we should learn to record knowledge other than in email. May be we could use a wiki part of the seaside.st wiki :) Stef_______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Default classes for form input tags?
|
|
Re: Default classes for form input tags?
|
|
| Free forum by Nabble | Edit this page |