You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-user@incubator.apache.org by Chris Lowe <ch...@gmail.com> on 2007/02/13 15:47:01 UTC
Skinless
Hi,
Is it possible to switch off skinning altogether? If so, will turning off
the skinning prevent the wrapping of various components in SPANs and the
download of a ~140k CSS file?
Cheers,
Chris.
Re: Skinless
Posted by Chris Lowe <ch...@gmail.com>.
Thanks for the info. So, specifying HTTP cache control headers will work
since this that is an instruction to the browser. That should save some
hits to the server.
Cheers,
Chris.
On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
>
> On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> > Hi Adam,
> >
> > Thanks for the info on the minimal skin, I'll switch to that in the
> > meantime. An even more minimal skin would be great though - anything to
> > save bandwidth, server hits and browser parsing of CSS/JS will be
> greatly
> > appreciated.
> >
> > My main reasons for not using a skin are cited in my original post. I'm
> > using making minimal use of the Trinidad component set (using <10
> > components) and having the CSS download seems excessive, plus learning
> about
> > the skinning for my needs was overkill. So for my current project,
> regular
> > CSS suited my needs for positioning and setting simple attributes like
> > width.
> >
> > I completely get the point of skinning and it looks really useful, it's
> just
> > not necessary at the minute.
> >
> > I will be using a compression filter for resources like CSS, I've always
> > found that the following filter does everything I need:
> >
> > http://sourceforge.net/projects/pjl-comp-filter/
> >
> > Are there any better ones out there?
> >
> > Are the Trinidad generated CSS/JS files constant between pages? If so,
> do
> > you see any problem with setting the HTTP cache headers: "Expires" and
> > "Cache-Control" to prevent the browser from requesting these resources
> on
> > each page request?
>
> They're completely constant from page-to-page - though
> not from user-to-user, since we'll send different .css
> for different browsers.
>
> - Adam
>
> >
> > Cheers,
> >
> > Chris.
> >
> >
> >
> > On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
> > >
> > > Skinning is an integral feature, so there's no turning it
> > > off. You could switch to a simpler l+f - minimal, for instance,
> > > clocks in at <30K. We could provide an even more minimal l+f,
> > > perhaps. But, I wonder, why are you looking to completely disable
> > > skinning?
> > >
> > > If it's an issue of download size, you might consider getting
> > > a .gzip filter involved, which will majorly decrease the size
> > > of the .css file (~80% smaller). The minimal l+f .css comes
> > > in at about 5K once gzip'd.
> > >
> > > -- Adam
> > >
> > >
> > >
> > > On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > Is it possible to switch off skinning altogether? If so, will
> turning
> > > off
> > > > the skinning prevent the wrapping of various components in SPANs and
> the
> > > > download of a ~140k CSS file?
> > > >
> > > > Cheers,
> > > >
> > > > Chris.
> > > >
> > >
> >
>
Re: Skinless
Posted by Adam Winer <aw...@gmail.com>.
On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> Hi Adam,
>
> Thanks for the info on the minimal skin, I'll switch to that in the
> meantime. An even more minimal skin would be great though - anything to
> save bandwidth, server hits and browser parsing of CSS/JS will be greatly
> appreciated.
>
> My main reasons for not using a skin are cited in my original post. I'm
> using making minimal use of the Trinidad component set (using <10
> components) and having the CSS download seems excessive, plus learning about
> the skinning for my needs was overkill. So for my current project, regular
> CSS suited my needs for positioning and setting simple attributes like
> width.
>
> I completely get the point of skinning and it looks really useful, it's just
> not necessary at the minute.
>
> I will be using a compression filter for resources like CSS, I've always
> found that the following filter does everything I need:
>
> http://sourceforge.net/projects/pjl-comp-filter/
>
> Are there any better ones out there?
>
> Are the Trinidad generated CSS/JS files constant between pages? If so, do
> you see any problem with setting the HTTP cache headers: "Expires" and
> "Cache-Control" to prevent the browser from requesting these resources on
> each page request?
They're completely constant from page-to-page - though
not from user-to-user, since we'll send different .css
for different browsers.
- Adam
>
> Cheers,
>
> Chris.
>
>
>
> On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
> >
> > Skinning is an integral feature, so there's no turning it
> > off. You could switch to a simpler l+f - minimal, for instance,
> > clocks in at <30K. We could provide an even more minimal l+f,
> > perhaps. But, I wonder, why are you looking to completely disable
> > skinning?
> >
> > If it's an issue of download size, you might consider getting
> > a .gzip filter involved, which will majorly decrease the size
> > of the .css file (~80% smaller). The minimal l+f .css comes
> > in at about 5K once gzip'd.
> >
> > -- Adam
> >
> >
> >
> > On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> > > Hi,
> > >
> > > Is it possible to switch off skinning altogether? If so, will turning
> > off
> > > the skinning prevent the wrapping of various components in SPANs and the
> > > download of a ~140k CSS file?
> > >
> > > Cheers,
> > >
> > > Chris.
> > >
> >
>
Re: Skinless
Posted by Chris Lowe <ch...@gmail.com>.
Thanks for the information Jeanne. I was able to define the following
veryMinimal skin (grep to the rescue!) and the generated CSS file is now
just 434 bytes. I'll need to reintroduce a couple of the styles for the
inputDate's popup calendar, but apart from that this skin suits my needs
perfectly.
Thanks again for you help,
Chris.
.AFAccessKeyStyle,
.AFAddressFieldText,
.AFAddressFieldTextDisabled,
.AFDataNumber,
.AFDataNumberDisabled,
.AFDataText,
.AFDataTextDisabled,
.AFErrorIconStyle,
.AFErrorText,
.AFFieldNumber,
.AFFieldNumberDisabled,
.AFFieldText,
.AFFieldTextDisabled,
.AFFieldTextLTR,
.AFFieldTextLTRDisabled,
.AFHeaderLevelOne,
.AFHeaderLevelThreePlus,
.AFHeaderLevelTwo,
.AFInfoIconStyle,
.AFInstructionText,
.AFInstructionTextDisabled,
.AFLabelCell,
.AFLabelText,
.AFLinkAccessKeyStyle,
.AFLogo,
.AFPhoneFieldText,
.AFPhoneFieldTextDisabled,
.AFPostalCodeFieldText,
.AFPostalCodeFieldTextDisabled,
.AFQuickSelectDisabledIconStyle,
.AFQuickSelectIconStyle,
.AFRequiredIconStyle,
.AFSortableHeaderSortIcon,
.AFWarningIconStyle,
.OraALinkText,
.OraBGAccentDark,
.OraBGAccentLight,
.OraBGAccentMedium,
.OraBGAccentVeryDark,
.OraBGColorDark,
.OraBGColorLight,
.OraBGColorMedium,
.OraBGColorVeryDark,
.OraBGGrayDark,
.OraBGGrayLight,
.OraBGGrayMedium,
.OraBGGrayVeryDark,
.OraBulletedList A,
.OraBulletedList UL,
.OraColorFieldSwatchOverlayIcon,
.OraErrorNameText,
.OraGlobalPageTitle,
.OraHGridLocatorHeader,
.OraHGridNavRowActiveLink,
.OraHGridNavRowInactiveLink,
.OraInlineErrorText,
.OraInlineInfoText,
.OraLink:active,
.OraLink:link,
.OraLink:visited,
.OraLinkDisabled,
.OraLinkText,
.OraMessageBoxErrorText,
.OraMessageBoxList,
.OraNav3,
.OraNav3Selected,
.OraNavBarActiveLink,
.OraNavBarInactiveLink,
.OraNavBarViewOnly,
.OraPageStampLabel,
.OraPageStampText,
.OraShuttleHeader,
.OraShuttleLinkText,
.OraSortableHeaderBorder,
.OraStyledList .OraStyledList,
.OraStyledList,
.OraTable,
.OraTableBorder0001,
.OraTableBorder0010,
.OraTableBorder0011,
.OraTableBorder0100,
.OraTableBorder0101,
.OraTableBorder0110,
.OraTableBorder0111,
.OraTableBorder1000,
.OraTableBorder1001,
.OraTableBorder1010,
.OraTableBorder1011,
.OraTableBorder1100,
.OraTableBorder1101,
.OraTableBorder1110,
.OraTableBorder1111,
.OraTableCellSelect,
.OraTableCellSelectBand,
.OraTableControlBarText,
.OraTableTitle,
.OraTableTotal,
.OraTextInline,
.OraVLinkText,
.PortletBodyColor,
.PortletHeaderColor,
.PortletHeaderLink,
.PortletHeaderStyle,
.PortletHeaderText,
.PortletHeading1,
.PortletHeading2,
.PortletHeading3,
.PortletHeading4,
.PortletSubHeaderColor,
.PortletSubHeaderLink,
.PortletSubHeaderText,
.PortletText1,
.PortletText2,
.PortletText3,
.PortletText4,
.p_InContextBrandingText,
.p_OraColorFieldSwatch,
.p_OraColorPalette,
.p_OraColorPaletteEmptyCell,
.p_OraContentFooterBottom,
.p_OraContentFooterChildren,
.p_OraContentFooterRule,
.p_OraContentFooterStart,
.p_OraDisabled,
.p_OraDisplayBlock,
.p_OraFooter,
.p_OraFooterBottom,
.p_OraGlobalQuick,
.p_OraHeaderImage,
.p_OraHeaderNest,
.p_OraHiddenLabel,
.p_OraHideShowDisclosedSymbol,
.p_OraHideSkipNaviText,
.p_OraMessageBoxMessage,
.p_OraNav2,
.p_OraOnePixelLine,
.p_OraProcessingStatus,
.p_OraProductBrandingCompactText,
.p_OraProductBrandingText,
.p_OraQuickSearchBox,
.p_OraSelected,
.p_OraSideBarMinWidth,
.p_OraTreeDisclosedSymbol A:active,
.p_OraTreeDisclosedSymbol A:link,
.p_OraTreeDisclosedSymbol A:visited,
.p_OraTreeDisclosedSymbol,
.p_OraTreeIcon,
.p_OraTreeNodeAdjust,
.p_OraTreeRow A:active,
.p_OraTreeRow A:link,
.p_OraTreeRow A:visited,
.p_OraTreeRow,
.p_OraTreeRowSelected A:active,
.p_OraTreeRowSelected A:link,
.p_OraTreeRowSelected A:visited,
.p_OraTreeRowSelected,
.panelCustomizableContainer,
.portlet-dlg-icon-label,
.portlet-font,
.portlet-font-dim,
.portlet-form-button,
.portlet-form-field,
.portlet-form-field-label,
.portlet-form-input-field,
.portlet-form-label,
.portlet-icon-label,
.portlet-msg-error,
.portlet-msg-info,
.portlet-section-alternate,
.portlet-section-body,
.portlet-section-footer,
.portlet-section-header,
.portlet-section-selected,
.portlet-section-subheader,
.portlet-section-text,
.portlet-table-alternate,
.portlet-table-body,
.portlet-table-footer,
.portlet-table-header,
.portlet-table-selected,
.portlet-table-subheader,
.portlet-table-text,
.sdfActionsImageSpacer,
.sdfChromeContainer,
.sdfChromeContainerNoTitleBar,
.sdfChromeContainerOnmouseoverSelected,
.sdfChromeContainerOnmouseoverUnselected,
.sdfContentAreaStyleClass,
.sdfDropdownMainMenugroup,
.sdfDropdownMenuitemSeparator,
.sdfDropdownSubMenugroup,
.sdfTitleBarStyleClassAlwaysDisplay,
A.sdfChromeTitleClickable,
A.sdfDropdownMenuitem,
A.sdfDropdownSubMenuitem,
A:hover.sdfDropdownMenuitem,
A:hover.sdfDropdownSubMenuitem,
BODY,
af|breadCrumbs,
af|chart,
af|chooseDate::content,
af|chooseDate::content-link,
af|chooseDate::header,
af|chooseDate::nav-link,
af|chooseDate::selected,
af|chooseDate::title,
af|column::cell-icon-format,
af|column::cell-icon-format-band,
af|column::cell-number,
af|column::cell-number-band,
af|column::cell-text,
af|column::cell-text-band,
af|column::header-icon-format,
af|column::header-number,
af|column::header-text,
af|column::row-header-text,
af|column::sortable-header-icon-format,
af|column::sortable-header-number,
af|column::sortable-header-text,
af|column::total-number,
af|column::total-text,
af|commandButton,
af|goButton,
af|inputChoice.AFAddressFieldTextMarker::content-input,
af|inputChoice.AFFieldNumberMarker::content-input,
af|inputChoice.AFFieldTextLTRMarker::content-input,
af|inputChoice.AFFieldTextMarker::content-input,
af|inputChoice.AFPhoneFieldTextMarker::content-input,
af|inputChoice.AFPostalCodeFieldTextMarker::content-input,
af|inputChoice::content,
af|inputChoice::content-input,
af|inputChoice::group-icon-style,
af|inputChoice::label,
af|inputChoice::required-icon-style,
af|inputChoice:disabled.AFAddressFieldTextMarker::content-input,
af|inputChoice:disabled.AFFieldNumberMarker::content-input,
af|inputChoice:disabled.AFFieldTextLTRMarker::content-input,
af|inputChoice:disabled.AFFieldTextMarker::content-input,
af|inputChoice:disabled.AFPhoneFieldTextMarker::content-input,
af|inputChoice:disabled.AFPostalCodeFieldTextMarker::content-input,
af|inputChoice:disabled::label,
af|inputColor::content,
af|inputColor::label,
af|inputColor::swatch-overlay,
af|inputColor:disabled::label,
af|inputColor:required::content,
af|inputColor:required::label,
af|inputDate::content,
af|inputDate::content-link,
af|inputDate::group-icon-style,
af|inputDate::header,
af|inputDate::label,
af|inputDate::nav-link,
af|inputDate::required-icon-style,
af|inputDate::selected,
af|inputDate::title,
af|inputDate:disabled::label,
af|inputDate:required::content,
af|inputDate:required::label,
af|inputFile::label,
af|inputFile:required::content,
af|inputFile:required::label,
af|inputListOfValues::content,
af|inputListOfValues::label,
af|inputListOfValues:disabled::label,
af|inputListOfValues:required::content,
af|inputListOfValues:required::label,
af|inputNumberSpinbox.AFFieldNumberMarker::content,
af|inputNumberSpinbox.AFFieldTextLTRMarker::content,
af|inputNumberSpinbox.AFFieldTextMarker::content,
af|inputNumberSpinbox::content,
af|inputNumberSpinbox::decrement-cell,
af|inputNumberSpinbox::group-icon-style,
af|inputNumberSpinbox::increment-cell,
af|inputNumberSpinbox::label,
af|inputNumberSpinbox::required-icon-style,
af|inputNumberSpinbox::spinbox-cell,
af|inputNumberSpinbox:disabled.AFFieldNumberMarker::content,
af|inputNumberSpinbox:disabled.AFFieldTextLTRMarker::content,
af|inputNumberSpinbox:disabled.AFFieldTextMarker::content,
af|inputNumberSpinbox:disabled::label,
af|inputNumberSpinbox:required::content,
af|inputNumberSpinbox:required::label,
af|inputText.AFAddressFieldTextMarker::content,
af|inputText.AFFieldNumberMarker::content,
af|inputText.AFFieldTextLTRMarker::content,
af|inputText.AFFieldTextMarker::content,
af|inputText.AFPhoneFieldTextMarker::content,
af|inputText.AFPostalCodeFieldTextMarker::content,
af|inputText::content,
af|inputText::group-icon-style,
af|inputText::label,
af|inputText::required-icon-style,
af|inputText:disabled.AFAddressFieldTextMarker::content,
af|inputText:disabled.AFFieldNumberMarker::content,
af|inputText:disabled.AFFieldTextLTRMarker::content,
af|inputText:disabled.AFFieldTextMarker::content,
af|inputText:disabled.AFPhoneFieldTextMarker::content,
af|inputText:disabled.AFPostalCodeFieldTextMarker::content,
af|inputText:disabled::label,
af|inputText:required::content,
af|inputText:required::label,
af|menuBar img,
af|menuBar,
af|menuBar::body,
af|menuBar::empty,
af|menuBar::enabled,
af|menuBar::enabled-link,
af|menuBar::selected,
af|menuBar::selected-link,
af|menuBar::separator,
af|menuBar::title,
af|menuButtons::icon-style,
af|menuButtons::text,
af|menuButtons::text-disabled,
af|menuButtons::text-selected,
af|menuChoice::label,
af|menuList,
af|menuList::selected,
af|menuPath,
af|menuPath::selected-step,
af|menuPath::step,
af|menuTabs img,
af|menuTabs,
af|menuTabs::disabled,
af|menuTabs::enabled,
af|menuTabs::enabled-link,
af|menuTabs::selected,
af|menuTabs::selected-link,
af|menuTabs::separator,
af|messages img,
af|messages,
af|messages::body,
af|messages::error,
af|messages::header,
af|messages::list,
af|messages::message-text,
af|navigationPane,
af|navigationPane::bar,
af|navigationPane::bar-active-disabled af|navigationPane::bar-content a,
af|navigationPane::bar-active-disabled af|navigationPane::bar-content,
af|navigationPane::bar-active-disabled,
af|navigationPane::bar-active-enabled af|navigationPane::bar-content a,
af|navigationPane::bar-active-enabled af|navigationPane::bar-content
a:hover,
af|navigationPane::bar-active-enabled af|navigationPane::bar-content,
af|navigationPane::bar-active-enabled,
af|navigationPane::bar-content a,
af|navigationPane::bar-content,
af|navigationPane::bar-inactive-disabled af|navigationPane::bar-content a,
af|navigationPane::bar-inactive-disabled af|navigationPane::bar-content,
af|navigationPane::bar-inactive-disabled,
af|navigationPane::bar-inactive-enabled af|navigationPane::bar-content a,
af|navigationPane::bar-inactive-enabled af|navigationPane::bar-content
a:hover,
af|navigationPane::bar-inactive-enabled af|navigationPane::bar-content,
af|navigationPane::bar-inactive-enabled,
af|navigationPane::bar-separator,
af|navigationPane::buttons-active-disabled
af|navigationPane::buttons-content a,
af|navigationPane::buttons-active-disabled
af|navigationPane::buttons-content,
af|navigationPane::buttons-active-disabled,
af|navigationPane::buttons-active-enabled af|navigationPane::buttons-content
a:hover,
af|navigationPane::buttons-active-enabled
af|navigationPane::buttons-content,
af|navigationPane::buttons-active-enabled,
af|navigationPane::buttons-content a,
af|navigationPane::buttons-content,
af|navigationPane::buttons-inactive-disabled
af|navigationPane::buttons-content a,
af|navigationPane::buttons-inactive-disabled
af|navigationPane::buttons-content,
af|navigationPane::buttons-inactive-disabled,
af|navigationPane::buttons-inactive-enabled
af|navigationPane::buttons-content a:hover,
af|navigationPane::buttons-inactive-enabled,
af|navigationPane::buttons-separator,
af|navigationPane::choice-button,
af|navigationPane::choice-label,
af|navigationPane::choice-options,
af|navigationPane::list-active-disabled af|navigationPane::list-content a,
af|navigationPane::list-active-disabled af|navigationPane::list-content,
af|navigationPane::list-active-disabled,
af|navigationPane::list-active-enabled af|navigationPane::list-content
a:hover,
af|navigationPane::list-active-enabled af|navigationPane::list-content,
af|navigationPane::list-active-enabled,
af|navigationPane::list-bullet,
af|navigationPane::list-content a,
af|navigationPane::list-content,
af|navigationPane::list-inactive-disabled af|navigationPane::list-content a,
af|navigationPane::list-inactive-disabled af|navigationPane::list-content,
af|navigationPane::list-inactive-disabled,
af|navigationPane::list-inactive-enabled af|navigationPane::list-content
a:hover,
af|navigationPane::list-inactive-enabled,
af|navigationPane::tabs,
af|navigationPane::tabs-active af|navigationPane::tabs-bottom-end,
af|navigationPane::tabs-active af|navigationPane::tabs-bottom-end-content,
af|navigationPane::tabs-active af|navigationPane::tabs-bottom-end-join,
af|navigationPane::tabs-active af|navigationPane::tabs-bottom-mid,
af|navigationPane::tabs-active af|navigationPane::tabs-bottom-start,
af|navigationPane::tabs-active af|navigationPane::tabs-bottom-start-content,
af|navigationPane::tabs-active af|navigationPane::tabs-end,
af|navigationPane::tabs-active af|navigationPane::tabs-end-join-to-inactive,
af|navigationPane::tabs-active af|navigationPane::tabs-mid A,
af|navigationPane::tabs-active af|navigationPane::tabs-mid,
af|navigationPane::tabs-active af|navigationPane::tabs-start,
af|navigationPane::tabs-active af|navigationPane::tabs-start-join,
af|navigationPane::tabs-active,
af|navigationPane::tabs-active:disabled af|navigationPane::tabs-mid,
af|navigationPane::tabs-active:disabled,
af|navigationPane::tabs-bottom-end,
af|navigationPane::tabs-bottom-end-content,
af|navigationPane::tabs-bottom-end-join,
af|navigationPane::tabs-bottom-mid,
af|navigationPane::tabs-bottom-mid-content,
af|navigationPane::tabs-bottom-start,
af|navigationPane::tabs-bottom-start-content,
af|navigationPane::tabs-end,
af|navigationPane::tabs-end-join-to-inactive,
af|navigationPane::tabs-inactive af|navigationPane::tabs-bottom-end,
af|navigationPane::tabs-inactive af|navigationPane::tabs-bottom-end-content,
af|navigationPane::tabs-inactive af|navigationPane::tabs-bottom-end-join,
af|navigationPane::tabs-inactive af|navigationPane::tabs-bottom-mid,
af|navigationPane::tabs-inactive af|navigationPane::tabs-bottom-start,
af|navigationPane::tabs-inactive
af|navigationPane::tabs-bottom-start-content,
af|navigationPane::tabs-inactive af|navigationPane::tabs-end,
af|navigationPane::tabs-inactive
af|navigationPane::tabs-end-join-to-inactive,
af|navigationPane::tabs-inactive af|navigationPane::tabs-mid A,
af|navigationPane::tabs-inactive af|navigationPane::tabs-mid,
af|navigationPane::tabs-inactive af|navigationPane::tabs-start,
af|navigationPane::tabs-inactive
af|navigationPane::tabs-start-join-from-active,
af|navigationPane::tabs-inactive
af|navigationPane::tabs-start-join-from-inactive,
af|navigationPane::tabs-inactive,
af|navigationPane::tabs-inactive:disabled af|navigationPane::tabs-mid,
af|navigationPane::tabs-inactive:disabled,
af|navigationPane::tabs-mid A,
af|navigationPane::tabs-mid,
af|navigationPane::tabs-start,
af|navigationPane::tabs-start-join,
af|navigationPane::tabs-start-join-from-active,
af|navigationPane::tabs-start-join-from-inactive,
af|outputDocument,
af|outputDocument::paragraph,
af|outputDocument::separator,
af|outputDocument::title,
af|outputFormatted,
af|outputLabel,
af|outputLabel::group-icon-style,
af|outputLabel::required-icon-style,
af|outputText,
af|panelBox::body,
af|panelBox::bottom,
af|panelBox::bottom-end,
af|panelBox::bottom-start,
af|panelBox::content,
af|panelBox::content-dark af|panelBox::body,
af|panelBox::content-dark img,
af|panelBox::content-dark,
af|panelBox::content-light af|panelBox::body,
af|panelBox::content-light img,
af|panelBox::content-light,
af|panelBox::content-medium af|panelBox::body,
af|panelBox::content-medium img,
af|panelBox::content-medium,
af|panelBox::content-transparent af|panelBox::body,
af|panelBox::content-transparent img,
af|panelBox::content-transparent,
af|panelBox::dark af|panelBox::body,
af|panelBox::dark img,
af|panelBox::dark,
af|panelBox::end,
af|panelBox::header,
af|panelBox::light af|panelBox::body
af|panelBox::light af|panelBox::body,
af|panelBox::light af|panelBox::header,
af|panelBox::light img,
af|panelBox::light,
af|panelBox::medium af|panelBox::body,
af|panelBox::medium img,
af|panelBox::medium,
af|panelBox::start,
af|panelBox::top,
af|panelBox::top-end,
af|panelBox::top-start,
af|panelBox::transparent af|panelBox::body,
af|panelBox::transparent img,
af|panelBox::transparent,
af|panelFormLayout::cell,
af|panelFormLayout::column,
af|panelFormLayout::content-cell,
af|panelFormLayout::label-cell,
af|panelFormLayout::label-stacked-cell,
af|panelFormLayout::message-cell,
af|panelFormLayout::separator,
af|panelHeader::error,
af|panelHeader::level-five,
af|panelHeader::level-four,
af|panelHeader::level-one,
af|panelHeader::level-six,
af|panelHeader::level-three,
af|panelHeader::level-two,
af|panelLabelAndMessage::label,
af|panelList::link,
af|panelList::unordered-list,
af|panelPage::about,
af|panelPage::about-link,
af|panelPage::copyright,
af|panelPage::copyright-link,
af|panelPage::privacy,
af|panelPage::privacy-link,
af|panelSideBar,
af|panelSideBar::body,
af|panelTabbed::cell-end,
af|panelTabbed::cell-start,
af|panelTabbed::orientation-bottom,
af|panelTabbed::orientation-top,
af|panelTabbed::tab .p_OraDisabled,
af|panelTabbed::tab,
af|panelTabbed::tab-link,
af|panelTabbed::tab-selected,
af|panelTabbed::tab-selected-link,
af|panelTip,
af|panelTip::content,
af|panelTip::label,
af|resetButton,
af|selectBooleanCheckbox::group-icon-style,
af|selectBooleanCheckbox::label,
af|selectBooleanCheckbox::required-icon-style,
af|selectBooleanCheckbox:disabled::label,
af|selectBooleanCheckbox:required::content,
af|selectBooleanCheckbox:required::label,
af|selectBooleanRadio::group-icon-style,
af|selectBooleanRadio::label,
af|selectBooleanRadio::required-icon-style,
af|selectBooleanRadio:disabled::label,
af|selectBooleanRadio:required::content,
af|selectBooleanRadio:required::label,
af|selectManyCheckbox::content,
af|selectManyCheckbox::group-icon-style,
af|selectManyCheckbox::item-text,
af|selectManyCheckbox::label,
af|selectManyCheckbox::required-icon-style,
af|selectManyCheckbox:disabled::label,
af|selectManyCheckbox:required::content,
af|selectManyCheckbox:required::label,
af|selectManyListbox::content,
af|selectManyListbox::group-icon-style,
af|selectManyListbox::label,
af|selectManyListbox::required-icon-style,
af|selectManyListbox:disabled::label,
af|selectManyListbox:required::content,
af|selectManyListbox:required::label,
af|selectManyShuttle::box-content af|selectManyShuttle::box-body,
af|selectManyShuttle::box-content img,
af|selectManyShuttle::box-content,
af|selectOneChoice::content,
af|selectOneChoice::group-icon-style,
af|selectOneChoice::label,
af|selectOneChoice::required-icon-style,
af|selectOneChoice:disabled::label,
af|selectOneChoice:required::content,
af|selectOneChoice:required::label,
af|selectOneListbox::content,
af|selectOneListbox::group-icon-style,
af|selectOneListbox::label,
af|selectOneListbox::required-icon-style,
af|selectOneListbox:disabled::label,
af|selectOneListbox:required::content,
af|selectOneListbox:required::label,
af|selectOneRadio::content,
af|selectOneRadio::group-icon-style,
af|selectOneRadio::item-text,
af|selectOneRadio::label,
af|selectOneRadio::required-icon-style,
af|selectOneRadio:disabled::label,
af|selectOneRadio:required::content,
af|selectOneRadio:required::label,
af|selectOrderShuttle::box-content af|selectOrderShuttle::box-body,
af|selectOrderShuttle::box-content img,
af|selectOrderShuttle::box-content,
af|selectinputDate::content,
af|showDetailHeader::level-five,
af|showDetailHeader::level-four,
af|showDetailHeader::level-one,
af|showDetailHeader::level-six,
af|showDetailHeader::level-three,
af|showDetailHeader::level-two,
af|showOnePanel::container,
af|showOnePanel::content,
af|showOnePanel::header-collapsed,
af|showOnePanel::header-disabled,
af|showOnePanel::header-expanded,
af|showOnePanel::title-disabled-link,
af|showOnePanel::title-link,
af|table::column-footer,
af|table::content,
af|table::control-bar-bottom,
af|table::control-bar-top,
af|table::detail,
af|table::sub-control-bar,
af|tableSelectMany::cell-icon-format,
af|tableSelectMany::cell-icon-format-band,
af|tableSelectOne::cell-icon-format,
af|tableSelectOne::cell-icon-format-band,
af|train,
af|train::join,
af|train::join-overflow,
af|train::join-parent,
af|train::link,
af|train::overflow-end,
af|train::overflow-end-content,
af|train::overflow-end-icon-cell,
af|train::overflow-start,
af|train::overflow-start-content,
af|train::overflow-start-icon-cell,
af|train::parent-end,
af|train::parent-end-content,
af|train::parent-end-icon-cell,
af|train::parent-start,
af|train::parent-start-content,
af|train::parent-start-icon-cell,
af|train::stop,
af|train::stop-content,
af|train::stop-icon-cell,
af|train::stop:disabled af|train::link,
af|train::stop:disabled,
af|train::stop:selected,
af|train::stop:unvisited,
af|train::stop:visited af|train::link,
af|train::stop:visited,
af|treeTable::content,
af|treeTable::control-bar-bottom,
af|treeTable::control-bar-top,
af|treeTable::expansion,
af|treeTable::focus,
af|treeTable::locator,
af|treeTable::path,
af|treeTable::path-selected-step,
af|treeTable::path-step,
af|treeTable::sub-control-bar,
body,
button {
-tr-inhibit: all;
}
On 16/02/07, Jeanne Waldman <je...@oracle.com> wrote:
>
> We need a lot more documentation on skinning, that is for sure.
>
> Let me try to explain the -tr-inhibit feature, which is relatively new.
>
> As you know in the default (aka base) skin there are a lot of skin style
> definitions.
> These get converted somewhat and generated into a css file that is
> included into the generated html file when you run
> a jspx page.
>
> Let's say the base skin has this definition (among all the other
> definitions):
>
> af|inputText::context {
> background-color: red;
> color: blue;
> }
>
> And when you run a page with the nputText component on it, you will get
> background-color: red
> and color: blue.
> The generated CSS file will have this (among all the other styles):
> .af_inputText_content {background-color: red; color: blue}
>
> But you don't want background-color red. You want to inhibit it.
> You think color blue is ok.
>
> So, you create a skin. (see trinidad-skins.xml for an example). In your
> css file you would do this:
>
> af|inputText:content {
> -tr-inhibit: background-color
> }
>
> Then when you run your page, you won't see a background-color.
>
> The generated css file will have this (among all the other styles):
> .af_inputText_content {color: blue}
>
>
> Let's say you wanted NO styles at all on af|inputText::content.
>
> You would do this:
>
> af|inputText {
> -tr-inhibit: all;
> }
>
> Then you won't see anything for .af_inputText_content in the generated
> css file.
>
> But, as you can see, if you want to inhibit everything, then whew...
> you'd need to open up base-desktop.xss and simple-desktop.xss (our base
> skins -- and they are in a different format than the css) to get the
> keys and then you'd have to type out all the keys
> .key1,
> .key2,
> etc {
> -tr-inhibit: all;
> }
> Not fun.
>
> Inhibiting all properties on the aliases will help a little bit. You can
> inhibit font-family everywhere, for example, by doing this:
>
> .AFDefaultFontFamily:alias {
> -tr-inhibit: all;
> }
>
> And since lots of our skinning keys include the AFDefaultFontFont:alias,
> your inhibiting it once will ripple through.
>
> I hope that makes sense. Let me know if you are confused.
>
> By the way, until recently we generated both full names and compressed
> names. like:
> .af_inputText_content, .x11 {background-color: red; color: blue}
> But now we generate one or the other.
> If you want to see full style names, then you need to add this to the
> web.xml:
>
> <context-param>
> <param-name>
> org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION
> </param-name>
> <param-value>true</param-value>
> </context-param>
>
>
>
> - Jeanne
>
>
> Chris Lowe wrote:
> > Matt,
> >
> > Thanks for the pointer, but to be honest all this skinning stuff sends
> me
> > into a dizzy state of confusion. I looked at the FAQ which has one
> > occurrance of "-tr-inhibit" - this directed me to the purpleSkin in the
> > demo. From there I can see a usage of "-tr-inhibit" but I don't really
> > understand how I'd apply this in my case.
> >
> > Cheers,
> >
> > C.
> >
> > On 13/02/07, Matt Cooper <ma...@gmail.com> wrote:
> >>
> >> You also can create a custom skin that inhibits styles from the style
> >> definitions using "-tr-inhibit". More details can be found at:
> >> http://wiki.apache.org/myfaces/Trinidad_Skinning_FAQ
> >>
> >> Regards,
> >> Matt
> >>
> >> On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> >> >
> >> > Hi Adam,
> >> >
> >> > Thanks for the info on the minimal skin, I'll switch to that in the
> >> > meantime. An even more minimal skin would be great though -
> >> anything to
> >> > save bandwidth, server hits and browser parsing of CSS/JS will be
> >> greatly
> >> > appreciated.
> >> >
> >> > My main reasons for not using a skin are cited in my original
> >> post. I'm
> >> > using making minimal use of the Trinidad component set (using <10
> >> > components) and having the CSS download seems excessive, plus
> learning
> >> > about
> >> > the skinning for my needs was overkill. So for my current project,
> >> regular
> >> > CSS suited my needs for positioning and setting simple attributes
> like
> >> > width.
> >> >
> >> > I completely get the point of skinning and it looks really useful,
> >> it's
> >> > just
> >> > not necessary at the minute.
> >> >
> >> > I will be using a compression filter for resources like CSS, I've
> >> always
> >> > found that the following filter does everything I need:
> >> >
> >> > http://sourceforge.net/projects/pjl-comp-filter/
> >> >
> >> > Are there any better ones out there?
> >> >
> >> > Are the Trinidad generated CSS/JS files constant between pages? If
> >> so,
> >> do
> >> > you see any problem with setting the HTTP cache headers: "Expires"
> and
> >> > "Cache-Control" to prevent the browser from requesting these
> resources
> >> on
> >> > each page request?
> >> >
> >> > Cheers,
> >> >
> >> > Chris.
> >> >
> >> >
> >> >
> >> > On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
> >> > >
> >> > > Skinning is an integral feature, so there's no turning it
> >> > > off. You could switch to a simpler l+f - minimal, for instance,
> >> > > clocks in at <30K. We could provide an even more minimal l+f,
> >> > > perhaps. But, I wonder, why are you looking to completely disable
> >> > > skinning?
> >> > >
> >> > > If it's an issue of download size, you might consider getting
> >> > > a .gzip filter involved, which will majorly decrease the size
> >> > > of the .css file (~80% smaller). The minimal l+f .css comes
> >> > > in at about 5K once gzip'd.
> >> > >
> >> > > -- Adam
> >> > >
> >> > >
> >> > >
> >> > > On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> >> > > > Hi,
> >> > > >
> >> > > > Is it possible to switch off skinning altogether? If so, will
> >> turning
> >> > > off
> >> > > > the skinning prevent the wrapping of various components in
> >> SPANs and
> >> > the
> >> > > > download of a ~140k CSS file?
> >> > > >
> >> > > > Cheers,
> >> > > >
> >> > > > Chris.
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: Skinless
Posted by Chris Lowe <ch...@gmail.com>.
Jeanne,
Thank you so much for your response - that made a lot of sense. I won't be
able to give this a try until this evening, so I'll let you know how I get
on...
Cheers,
Chris.
On 16/02/07, Jeanne Waldman <je...@oracle.com> wrote:
>
> We need a lot more documentation on skinning, that is for sure.
>
> Let me try to explain the -tr-inhibit feature, which is relatively new.
>
> As you know in the default (aka base) skin there are a lot of skin style
> definitions.
> These get converted somewhat and generated into a css file that is
> included into the generated html file when you run
> a jspx page.
>
> Let's say the base skin has this definition (among all the other
> definitions):
>
> af|inputText::context {
> background-color: red;
> color: blue;
> }
>
> And when you run a page with the nputText component on it, you will get
> background-color: red
> and color: blue.
> The generated CSS file will have this (among all the other styles):
> .af_inputText_content {background-color: red; color: blue}
>
> But you don't want background-color red. You want to inhibit it.
> You think color blue is ok.
>
> So, you create a skin. (see trinidad-skins.xml for an example). In your
> css file you would do this:
>
> af|inputText:content {
> -tr-inhibit: background-color
> }
>
> Then when you run your page, you won't see a background-color.
>
> The generated css file will have this (among all the other styles):
> .af_inputText_content {color: blue}
>
>
> Let's say you wanted NO styles at all on af|inputText::content.
>
> You would do this:
>
> af|inputText {
> -tr-inhibit: all;
> }
>
> Then you won't see anything for .af_inputText_content in the generated
> css file.
>
> But, as you can see, if you want to inhibit everything, then whew...
> you'd need to open up base-desktop.xss and simple-desktop.xss (our base
> skins -- and they are in a different format than the css) to get the
> keys and then you'd have to type out all the keys
> .key1,
> .key2,
> etc {
> -tr-inhibit: all;
> }
> Not fun.
>
> Inhibiting all properties on the aliases will help a little bit. You can
> inhibit font-family everywhere, for example, by doing this:
>
> .AFDefaultFontFamily:alias {
> -tr-inhibit: all;
> }
>
> And since lots of our skinning keys include the AFDefaultFontFont:alias,
> your inhibiting it once will ripple through.
>
> I hope that makes sense. Let me know if you are confused.
>
> By the way, until recently we generated both full names and compressed
> names. like:
> .af_inputText_content, .x11 {background-color: red; color: blue}
> But now we generate one or the other.
> If you want to see full style names, then you need to add this to the
> web.xml:
>
> <context-param>
> <param-name>
> org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION
> </param-name>
> <param-value>true</param-value>
> </context-param>
>
>
>
> - Jeanne
>
>
> Chris Lowe wrote:
> > Matt,
> >
> > Thanks for the pointer, but to be honest all this skinning stuff sends
> me
> > into a dizzy state of confusion. I looked at the FAQ which has one
> > occurrance of "-tr-inhibit" - this directed me to the purpleSkin in the
> > demo. From there I can see a usage of "-tr-inhibit" but I don't really
> > understand how I'd apply this in my case.
> >
> > Cheers,
> >
> > C.
> >
> > On 13/02/07, Matt Cooper <ma...@gmail.com> wrote:
> >>
> >> You also can create a custom skin that inhibits styles from the style
> >> definitions using "-tr-inhibit". More details can be found at:
> >> http://wiki.apache.org/myfaces/Trinidad_Skinning_FAQ
> >>
> >> Regards,
> >> Matt
> >>
> >> On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> >> >
> >> > Hi Adam,
> >> >
> >> > Thanks for the info on the minimal skin, I'll switch to that in the
> >> > meantime. An even more minimal skin would be great though -
> >> anything to
> >> > save bandwidth, server hits and browser parsing of CSS/JS will be
> >> greatly
> >> > appreciated.
> >> >
> >> > My main reasons for not using a skin are cited in my original
> >> post. I'm
> >> > using making minimal use of the Trinidad component set (using <10
> >> > components) and having the CSS download seems excessive, plus
> learning
> >> > about
> >> > the skinning for my needs was overkill. So for my current project,
> >> regular
> >> > CSS suited my needs for positioning and setting simple attributes
> like
> >> > width.
> >> >
> >> > I completely get the point of skinning and it looks really useful,
> >> it's
> >> > just
> >> > not necessary at the minute.
> >> >
> >> > I will be using a compression filter for resources like CSS, I've
> >> always
> >> > found that the following filter does everything I need:
> >> >
> >> > http://sourceforge.net/projects/pjl-comp-filter/
> >> >
> >> > Are there any better ones out there?
> >> >
> >> > Are the Trinidad generated CSS/JS files constant between pages? If
> >> so,
> >> do
> >> > you see any problem with setting the HTTP cache headers: "Expires"
> and
> >> > "Cache-Control" to prevent the browser from requesting these
> resources
> >> on
> >> > each page request?
> >> >
> >> > Cheers,
> >> >
> >> > Chris.
> >> >
> >> >
> >> >
> >> > On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
> >> > >
> >> > > Skinning is an integral feature, so there's no turning it
> >> > > off. You could switch to a simpler l+f - minimal, for instance,
> >> > > clocks in at <30K. We could provide an even more minimal l+f,
> >> > > perhaps. But, I wonder, why are you looking to completely disable
> >> > > skinning?
> >> > >
> >> > > If it's an issue of download size, you might consider getting
> >> > > a .gzip filter involved, which will majorly decrease the size
> >> > > of the .css file (~80% smaller). The minimal l+f .css comes
> >> > > in at about 5K once gzip'd.
> >> > >
> >> > > -- Adam
> >> > >
> >> > >
> >> > >
> >> > > On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> >> > > > Hi,
> >> > > >
> >> > > > Is it possible to switch off skinning altogether? If so, will
> >> turning
> >> > > off
> >> > > > the skinning prevent the wrapping of various components in
> >> SPANs and
> >> > the
> >> > > > download of a ~140k CSS file?
> >> > > >
> >> > > > Cheers,
> >> > > >
> >> > > > Chris.
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: Skinless
Posted by Jeanne Waldman <je...@oracle.com>.
We need a lot more documentation on skinning, that is for sure.
Let me try to explain the -tr-inhibit feature, which is relatively new.
As you know in the default (aka base) skin there are a lot of skin style
definitions.
These get converted somewhat and generated into a css file that is
included into the generated html file when you run
a jspx page.
Let's say the base skin has this definition (among all the other
definitions):
af|inputText::context {
background-color: red;
color: blue;
}
And when you run a page with the nputText component on it, you will get
background-color: red
and color: blue.
The generated CSS file will have this (among all the other styles):
.af_inputText_content {background-color: red; color: blue}
But you don't want background-color red. You want to inhibit it.
You think color blue is ok.
So, you create a skin. (see trinidad-skins.xml for an example). In your
css file you would do this:
af|inputText:content {
-tr-inhibit: background-color
}
Then when you run your page, you won't see a background-color.
The generated css file will have this (among all the other styles):
.af_inputText_content {color: blue}
Let's say you wanted NO styles at all on af|inputText::content.
You would do this:
af|inputText {
-tr-inhibit: all;
}
Then you won't see anything for .af_inputText_content in the generated
css file.
But, as you can see, if you want to inhibit everything, then whew...
you'd need to open up base-desktop.xss and simple-desktop.xss (our base
skins -- and they are in a different format than the css) to get the
keys and then you'd have to type out all the keys
.key1,
.key2,
etc {
-tr-inhibit: all;
}
Not fun.
Inhibiting all properties on the aliases will help a little bit. You can
inhibit font-family everywhere, for example, by doing this:
.AFDefaultFontFamily:alias {
-tr-inhibit: all;
}
And since lots of our skinning keys include the AFDefaultFontFont:alias,
your inhibiting it once will ripple through.
I hope that makes sense. Let me know if you are confused.
By the way, until recently we generated both full names and compressed
names. like:
.af_inputText_content, .x11 {background-color: red; color: blue}
But now we generate one or the other.
If you want to see full style names, then you need to add this to the
web.xml:
<context-param>
<param-name>org.apache.myfaces.trinidadinternal.DISABLE_CONTENT_COMPRESSION</param-name>
<param-value>true</param-value>
</context-param>
- Jeanne
Chris Lowe wrote:
> Matt,
>
> Thanks for the pointer, but to be honest all this skinning stuff sends me
> into a dizzy state of confusion. I looked at the FAQ which has one
> occurrance of "-tr-inhibit" - this directed me to the purpleSkin in the
> demo. From there I can see a usage of "-tr-inhibit" but I don't really
> understand how I'd apply this in my case.
>
> Cheers,
>
> C.
>
> On 13/02/07, Matt Cooper <ma...@gmail.com> wrote:
>>
>> You also can create a custom skin that inhibits styles from the style
>> definitions using "-tr-inhibit". More details can be found at:
>> http://wiki.apache.org/myfaces/Trinidad_Skinning_FAQ
>>
>> Regards,
>> Matt
>>
>> On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
>> >
>> > Hi Adam,
>> >
>> > Thanks for the info on the minimal skin, I'll switch to that in the
>> > meantime. An even more minimal skin would be great though -
>> anything to
>> > save bandwidth, server hits and browser parsing of CSS/JS will be
>> greatly
>> > appreciated.
>> >
>> > My main reasons for not using a skin are cited in my original
>> post. I'm
>> > using making minimal use of the Trinidad component set (using <10
>> > components) and having the CSS download seems excessive, plus learning
>> > about
>> > the skinning for my needs was overkill. So for my current project,
>> regular
>> > CSS suited my needs for positioning and setting simple attributes like
>> > width.
>> >
>> > I completely get the point of skinning and it looks really useful,
>> it's
>> > just
>> > not necessary at the minute.
>> >
>> > I will be using a compression filter for resources like CSS, I've
>> always
>> > found that the following filter does everything I need:
>> >
>> > http://sourceforge.net/projects/pjl-comp-filter/
>> >
>> > Are there any better ones out there?
>> >
>> > Are the Trinidad generated CSS/JS files constant between pages? If
>> so,
>> do
>> > you see any problem with setting the HTTP cache headers: "Expires" and
>> > "Cache-Control" to prevent the browser from requesting these resources
>> on
>> > each page request?
>> >
>> > Cheers,
>> >
>> > Chris.
>> >
>> >
>> >
>> > On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
>> > >
>> > > Skinning is an integral feature, so there's no turning it
>> > > off. You could switch to a simpler l+f - minimal, for instance,
>> > > clocks in at <30K. We could provide an even more minimal l+f,
>> > > perhaps. But, I wonder, why are you looking to completely disable
>> > > skinning?
>> > >
>> > > If it's an issue of download size, you might consider getting
>> > > a .gzip filter involved, which will majorly decrease the size
>> > > of the .css file (~80% smaller). The minimal l+f .css comes
>> > > in at about 5K once gzip'd.
>> > >
>> > > -- Adam
>> > >
>> > >
>> > >
>> > > On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
>> > > > Hi,
>> > > >
>> > > > Is it possible to switch off skinning altogether? If so, will
>> turning
>> > > off
>> > > > the skinning prevent the wrapping of various components in
>> SPANs and
>> > the
>> > > > download of a ~140k CSS file?
>> > > >
>> > > > Cheers,
>> > > >
>> > > > Chris.
>> > > >
>> > >
>> >
>>
>
Re: Skinless
Posted by Chris Lowe <ch...@gmail.com>.
Matt,
Thanks for the pointer, but to be honest all this skinning stuff sends me
into a dizzy state of confusion. I looked at the FAQ which has one
occurrance of "-tr-inhibit" - this directed me to the purpleSkin in the
demo. From there I can see a usage of "-tr-inhibit" but I don't really
understand how I'd apply this in my case.
Cheers,
C.
On 13/02/07, Matt Cooper <ma...@gmail.com> wrote:
>
> You also can create a custom skin that inhibits styles from the style
> definitions using "-tr-inhibit". More details can be found at:
> http://wiki.apache.org/myfaces/Trinidad_Skinning_FAQ
>
> Regards,
> Matt
>
> On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> >
> > Hi Adam,
> >
> > Thanks for the info on the minimal skin, I'll switch to that in the
> > meantime. An even more minimal skin would be great though - anything to
> > save bandwidth, server hits and browser parsing of CSS/JS will be
> greatly
> > appreciated.
> >
> > My main reasons for not using a skin are cited in my original post. I'm
> > using making minimal use of the Trinidad component set (using <10
> > components) and having the CSS download seems excessive, plus learning
> > about
> > the skinning for my needs was overkill. So for my current project,
> regular
> > CSS suited my needs for positioning and setting simple attributes like
> > width.
> >
> > I completely get the point of skinning and it looks really useful, it's
> > just
> > not necessary at the minute.
> >
> > I will be using a compression filter for resources like CSS, I've always
> > found that the following filter does everything I need:
> >
> > http://sourceforge.net/projects/pjl-comp-filter/
> >
> > Are there any better ones out there?
> >
> > Are the Trinidad generated CSS/JS files constant between pages? If so,
> do
> > you see any problem with setting the HTTP cache headers: "Expires" and
> > "Cache-Control" to prevent the browser from requesting these resources
> on
> > each page request?
> >
> > Cheers,
> >
> > Chris.
> >
> >
> >
> > On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
> > >
> > > Skinning is an integral feature, so there's no turning it
> > > off. You could switch to a simpler l+f - minimal, for instance,
> > > clocks in at <30K. We could provide an even more minimal l+f,
> > > perhaps. But, I wonder, why are you looking to completely disable
> > > skinning?
> > >
> > > If it's an issue of download size, you might consider getting
> > > a .gzip filter involved, which will majorly decrease the size
> > > of the .css file (~80% smaller). The minimal l+f .css comes
> > > in at about 5K once gzip'd.
> > >
> > > -- Adam
> > >
> > >
> > >
> > > On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > Is it possible to switch off skinning altogether? If so, will
> turning
> > > off
> > > > the skinning prevent the wrapping of various components in SPANs and
> > the
> > > > download of a ~140k CSS file?
> > > >
> > > > Cheers,
> > > >
> > > > Chris.
> > > >
> > >
> >
>
Re: Skinless
Posted by Matt Cooper <ma...@gmail.com>.
You also can create a custom skin that inhibits styles from the style
definitions using "-tr-inhibit". More details can be found at:
http://wiki.apache.org/myfaces/Trinidad_Skinning_FAQ
Regards,
Matt
On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
>
> Hi Adam,
>
> Thanks for the info on the minimal skin, I'll switch to that in the
> meantime. An even more minimal skin would be great though - anything to
> save bandwidth, server hits and browser parsing of CSS/JS will be greatly
> appreciated.
>
> My main reasons for not using a skin are cited in my original post. I'm
> using making minimal use of the Trinidad component set (using <10
> components) and having the CSS download seems excessive, plus learning
> about
> the skinning for my needs was overkill. So for my current project, regular
> CSS suited my needs for positioning and setting simple attributes like
> width.
>
> I completely get the point of skinning and it looks really useful, it's
> just
> not necessary at the minute.
>
> I will be using a compression filter for resources like CSS, I've always
> found that the following filter does everything I need:
>
> http://sourceforge.net/projects/pjl-comp-filter/
>
> Are there any better ones out there?
>
> Are the Trinidad generated CSS/JS files constant between pages? If so, do
> you see any problem with setting the HTTP cache headers: "Expires" and
> "Cache-Control" to prevent the browser from requesting these resources on
> each page request?
>
> Cheers,
>
> Chris.
>
>
>
> On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
> >
> > Skinning is an integral feature, so there's no turning it
> > off. You could switch to a simpler l+f - minimal, for instance,
> > clocks in at <30K. We could provide an even more minimal l+f,
> > perhaps. But, I wonder, why are you looking to completely disable
> > skinning?
> >
> > If it's an issue of download size, you might consider getting
> > a .gzip filter involved, which will majorly decrease the size
> > of the .css file (~80% smaller). The minimal l+f .css comes
> > in at about 5K once gzip'd.
> >
> > -- Adam
> >
> >
> >
> > On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> > > Hi,
> > >
> > > Is it possible to switch off skinning altogether? If so, will turning
> > off
> > > the skinning prevent the wrapping of various components in SPANs and
> the
> > > download of a ~140k CSS file?
> > >
> > > Cheers,
> > >
> > > Chris.
> > >
> >
>
Re: Skinless
Posted by Chris Lowe <ch...@gmail.com>.
Hi Adam,
Thanks for the info on the minimal skin, I'll switch to that in the
meantime. An even more minimal skin would be great though - anything to
save bandwidth, server hits and browser parsing of CSS/JS will be greatly
appreciated.
My main reasons for not using a skin are cited in my original post. I'm
using making minimal use of the Trinidad component set (using <10
components) and having the CSS download seems excessive, plus learning about
the skinning for my needs was overkill. So for my current project, regular
CSS suited my needs for positioning and setting simple attributes like
width.
I completely get the point of skinning and it looks really useful, it's just
not necessary at the minute.
I will be using a compression filter for resources like CSS, I've always
found that the following filter does everything I need:
http://sourceforge.net/projects/pjl-comp-filter/
Are there any better ones out there?
Are the Trinidad generated CSS/JS files constant between pages? If so, do
you see any problem with setting the HTTP cache headers: "Expires" and
"Cache-Control" to prevent the browser from requesting these resources on
each page request?
Cheers,
Chris.
On 13/02/07, Adam Winer <aw...@gmail.com> wrote:
>
> Skinning is an integral feature, so there's no turning it
> off. You could switch to a simpler l+f - minimal, for instance,
> clocks in at <30K. We could provide an even more minimal l+f,
> perhaps. But, I wonder, why are you looking to completely disable
> skinning?
>
> If it's an issue of download size, you might consider getting
> a .gzip filter involved, which will majorly decrease the size
> of the .css file (~80% smaller). The minimal l+f .css comes
> in at about 5K once gzip'd.
>
> -- Adam
>
>
>
> On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> > Hi,
> >
> > Is it possible to switch off skinning altogether? If so, will turning
> off
> > the skinning prevent the wrapping of various components in SPANs and the
> > download of a ~140k CSS file?
> >
> > Cheers,
> >
> > Chris.
> >
>
Re: Skinless
Posted by Adam Winer <aw...@gmail.com>.
Skinning is an integral feature, so there's no turning it
off. You could switch to a simpler l+f - minimal, for instance,
clocks in at <30K. We could provide an even more minimal l+f,
perhaps. But, I wonder, why are you looking to completely disable
skinning?
If it's an issue of download size, you might consider getting
a .gzip filter involved, which will majorly decrease the size
of the .css file (~80% smaller). The minimal l+f .css comes
in at about 5K once gzip'd.
-- Adam
On 2/13/07, Chris Lowe <ch...@gmail.com> wrote:
> Hi,
>
> Is it possible to switch off skinning altogether? If so, will turning off
> the skinning prevent the wrapping of various components in SPANs and the
> download of a ~140k CSS file?
>
> Cheers,
>
> Chris.
>