IIRC, there was an error in the error CSS that some of us ran into,
with a margin being set at -20px instead of 20px. I overrode that
style to fix the problem. I believe it is this:
div.t-error li {
list-style-type: disc;
margin-left: 20px;
}
I agree CSS for layout and positioning is not the answer for all of us
-- I've switched back and forth a few times already (with tables). I
think the only decent answer is to not pick a side, and let there be
an implementation for both.
Is there room for a chapter on extending the BeanEditForm (thereby
changing the markup that gets output, so at least you have a specific
CSS tag for everything?)
On 8/22/07, Kolesnikov, Alexander GNI
<[EMAIL PROTECTED]> wrote:
> Thanks, guys,
>
> You see, if it was just for myself I would certainly do as you suggest.
> The problem is that I am writing a book on T5 and the idea is to keep
> the book as simple as possible. So far I have managed to do this, and I
> am already in chapter 6.
>
> What can be easier than BeanEditForm? Just insert a short line of code
> into the page template, and here you have a lot of stuff in one moment,
> including a fully blown validation! Do you want to change which
> properties are displayed and how they are edited? That's easy (two ways:
> changing the edited object or using BeanModel)... Do you want to change
> the look of the form? Just override the default CSS styles... Blah,
> blah..
>
> Everything goes on easily. But finally we see a form with error messages
> going awry in major browsers (displayed across the left border of the
> component) and submit button that cannot be positioned without creating
> a custom component or doing some tricks...
>
> As a result, there is an impression that BeanEditForm is good only for
> quick prototyping where you do not care about the appearance. Although
> it would be so easy to make it both powerful AND looking nice.
>
> I.m.o. the problem of BeanEditForm is that its layout was created by a
> CSS purist who cannot bear using tables even when they make things
> tremendously easier. If a table was used as a skeleton, the error
> messages would never go across the border, whichever browser you use.
> And if a row or, well, DIV for the submit button had a special style,
> the component as a whole would become much more useful.
>
> Tapestry 5 is in active development, and I am simply trying to provide
> some feedback to its developers. I would say that making things easier
> and more reliable would assist in wider acceptance of the framework.
>
> Cheers,
>
> Alexander
>
> -----Original Message-----
> From: Chris Lewis [mailto:[EMAIL PROTECTED]
> Sent: 20 August 2007 17:19
> To: Tapestry users
> Subject: Re: [T5] BeanEditForm CSS suggestion
>
>
> You can extend the BeadEditForm instead of copying it can't you? That
> would be a pain...
>
> Daniel Jue wrote:
> > In general, Tapestry's defaults are good -- they get you up and
> > running. But for people who want to add more pieces of flair to the
> > components, we'll probably end up needing to copy the component and
> > make changes as needed. For example, rewriting the Grid component's
> > template to make changes to the DOM that gets output. Or adding more
> > CSS tags to the elements of the bean form, so we can make more
> > specific CSS changes if we want to.
> >
> > As for the colon. it's plausible that you may want a question mark
> > after a field label, or perhaps in some locales you may not want a
> > prompt character at all.
> >
> > For an immediate fix, without affecting your other submit buttons,
> > maybe you can wrap your bean edit form inside a div, and use that
> > div's class as a way to help target the submit button.
> >
> > On 8/20/07, Kolesnikov, Alexander GNI
> > <[EMAIL PROTECTED]> wrote:
> >
> >> Thank you, Chris,
> >>
> >> CSS2 has a lot of wonderful stuff in it, but the problem is that it
> >> doesn't work consistently in different browsers. For example, your
> >> solution works in Firefox, but not in IE6, the most popular Web
> >> browser these days.
> >>
> >> On the other hand, having a different style for the button area would
>
> >> work in every browser, and it would allow someone to use a different
> >> background for the button area too - why not?
> >>
> >> Another style used for BeanEditForm I am not happy with is this:
> >>
> >> FORM.t-beaneditor LABEL:after {
> >> content: ":";
> >> }
> >>
> >> Looks like a clever use of CSS2, but again, this doesn't work in both
>
> >> IE6 and IE7. Also, in some other browsers (don't remember now,
> >> probably Opera), the colon seems to be lower than the label, not
> >> properly aligned. And, if you think about it, why not to have this
> >> colon hard-coded? What else one would wish to place after the label
> >> instead of a colon? A semicolon? :/
> >>
> >> Alexander
> >>
> >> -----Original Message-----
> >> From: Chris Lewis [mailto:[EMAIL PROTECTED]
> >> Sent: 17 August 2007 18:07
> >> To: Tapestry users
> >> Subject: Re: [T5] BeanEditForm CSS suggestion
> >>
> >>
> >> Alexander,
> >>
> >> You can use CSS2 attribute selectors to match only submit input
> >> types. Try this:
> >>
> >> div.t-beaneditor-row input[type="submit"] { font-size: 20px; }
> >>
> >> This will match only input elements of type submit.
> >>
> >> chris
> >>
> >> Kolesnikov, Alexander GNI wrote:
> >>
> >>> I wonder if it would make sense to use a different CSS class for the
>
> >>> DIV that contains the Submit button in BeanEditForm (not
> >>> t-beaneditor-row)? I am trying to tweak the button using
> >>> div.t-beaneditor-row input style, but whatever I do with it, the
> >>> same applies to all the other <input> elements in the form...
> >>>
> >>> Alexander
> >>>
> >>> --------------------------------------------------------------------
> >>> --
> >>> --------
> >>> CONFIDENTIALITY NOTICE: If you have received this email in error,
> >>>
> >> please immediately notify the sender by e-mail at the address shown.
> >> This email transmission may contain confidential information. This
> >> information is intended only for the use of the individual(s) or
> >> entity to whom it is intended even if addressed incorrectly. Please
> >> delete it from your files if you are not the intended recipient.
> >> Thank you for your compliance. Copyright 2007 CIGNA
> >>
> >> =====================================================================
> >> ===
> >> ======
> >>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> ---------
> >> CONFIDENTIALITY NOTICE: If you have received this email in error,
> please immediately notify the sender by e-mail at the address shown.
> This email transmission may contain confidential information. This
> information is intended only for the use of the individual(s) or entity
> to whom it is intended even if addressed incorrectly. Please delete it
> from your files if you are not the intended recipient. Thank you for
> your compliance. Copyright 2007 CIGNA
> >>
> ========================================================================
> ======
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ------------------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: If you have received this email in error, please
> immediately notify the sender by e-mail at the address shown. This email
> transmission may contain confidential information. This information is
> intended only for the use of the individual(s) or entity to whom it is
> intended even if addressed incorrectly. Please delete it from your files if
> you are not the intended recipient. Thank you for your compliance.
> Copyright 2007 CIGNA
> ==============================================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
