DonB
|
| Posted: 02/28/2003, 2:13 PM |
|
Here's another bug (beta 3). Stylesheets are overwritten with the "master"
copy anytime you create a new page (and at other times, too).
Really, if the stylesheet is put into the project, CCS ought to leave it
alone until you say "OK, go back to the unmodified style". I know the
"supported" way is to create a new folder, create a new style and change all
the names - bleaghh.
So, I elected to create an "override" sheet rather than mangle the standard
one. No good either, because the <LINK> tag to my sheet gets ripped out
when I flip from design to code or rebuild the page. Arrggghhh! After all
these are "cascading" style sheets.
I already voiced opposition (to Yes) about the way they rename all the style
"classes" to be prefixed with the style name. The "right way" to use CSS is
to keep the classe names always the same, but point the <LINK> to the
desired CSS file (which ought to be named "Noise.CSS", "DeepWater.CSS", etc.
The way it is, trying to implement a "skins" feature is impractical. Yes
feels I am wrong. Bzzzzt! Wrong answer.
DonB (just ranting, not mad).
|
|
|
 |
Brian Bermingham
|
| Posted: 03/01/2003, 4:07 AM |
|
Don
I agree with you, keeping the style names the same with different CCS file
names would make it much easier to change the styles of a page in code.
BrianB
"DonB" <dbweb2@premiersi.com> wrote in message
news:b3omtd$104$1@news.codecharge.com...
> Here's another bug (beta 3). Stylesheets are overwritten with the
"master"
> copy anytime you create a new page (and at other times, too).
>
> Really, if the stylesheet is put into the project, CCS ought to leave it
> alone until you say "OK, go back to the unmodified style". I know the
> "supported" way is to create a new folder, create a new style and change
all
> the names - bleaghh.
>
> So, I elected to create an "override" sheet rather than mangle the
standard
> one. No good either, because the <LINK> tag to my sheet gets ripped out
> when I flip from design to code or rebuild the page. Arrggghhh! After
all
> these are "cascading" style sheets.
>
> I already voiced opposition (to Yes) about the way they rename all the
style
> "classes" to be prefixed with the style name. The "right way" to use CSS
is
> to keep the classe names always the same, but point the <LINK> to the
> desired CSS file (which ought to be named "Noise.CSS", "DeepWater.CSS",
etc.
> The way it is, trying to implement a "skins" feature is impractical. Yes
> feels I am wrong. Bzzzzt! Wrong answer.
>
>
> DonB (just ranting, not mad).
>
>
|
|
|
|
Kevin
|
| Posted: 03/01/2003, 7:31 PM |
|
You have another YES VOTE:
YES/CCS - Please tell us how you plan to address changing skins with your
current naming convention????
Kangus A
"DonB" <dbweb2@premiersi.com> wrote in message
news:b3omtd$104$1@news.codecharge.com...
> Here's another bug (beta 3). Stylesheets are overwritten with the
"master"
> copy anytime you create a new page (and at other times, too).
>
> Really, if the stylesheet is put into the project, CCS ought to leave it
> alone until you say "OK, go back to the unmodified style". I know the
> "supported" way is to create a new folder, create a new style and change
all
> the names - bleaghh.
>
> So, I elected to create an "override" sheet rather than mangle the
standard
> one. No good either, because the <LINK> tag to my sheet gets ripped out
> when I flip from design to code or rebuild the page. Arrggghhh! After
all
> these are "cascading" style sheets.
>
> I already voiced opposition (to Yes) about the way they rename all the
style
> "classes" to be prefixed with the style name. The "right way" to use CSS
is
> to keep the classe names always the same, but point the <LINK> to the
> desired CSS file (which ought to be named "Noise.CSS", "DeepWater.CSS",
etc.
> The way it is, trying to implement a "skins" feature is impractical. Yes
> feels I am wrong. Bzzzzt! Wrong answer.
>
>
> DonB (just ranting, not mad).
>
>
|
|
|
|
Robert Rodgers
|
| Posted: 03/02/2003, 6:52 AM |
|
Yes, I agree also.
rob
"Kevin" <ka@acats.com> wrote in message
news:b3rtv2$pr0$1@news.codecharge.com...
> You have another YES VOTE:
>
> YES/CCS - Please tell us how you plan to address changing skins with your
> current naming convention????
> Kangus A
> "DonB" <dbweb2@premiersi.com> wrote in message
>news:b3omtd$104$1@news.codecharge.com...
> > Here's another bug (beta 3). Stylesheets are overwritten with the
> "master"
> > copy anytime you create a new page (and at other times, too).
> >
> > Really, if the stylesheet is put into the project, CCS ought to leave it
> > alone until you say "OK, go back to the unmodified style". I know the
> > "supported" way is to create a new folder, create a new style and change
> all
> > the names - bleaghh.
> >
> > So, I elected to create an "override" sheet rather than mangle the
> standard
> > one. No good either, because the <LINK> tag to my sheet gets ripped out
> > when I flip from design to code or rebuild the page. Arrggghhh! After
> all
> > these are "cascading" style sheets.
> >
> > I already voiced opposition (to Yes) about the way they rename all the
> style
> > "classes" to be prefixed with the style name. The "right way" to use
CSS
> is
> > to keep the classe names always the same, but point the <LINK> to the
> > desired CSS file (which ought to be named "Noise.CSS", "DeepWater.CSS",
> etc.
> > The way it is, trying to implement a "skins" feature is impractical.
Yes
> > feels I am wrong. Bzzzzt! Wrong answer.
> >
> >
> > DonB (just ranting, not mad).
> >
> >
>
>
|
|
|
|
charisse
|
| Posted: 03/02/2003, 8:04 AM |
|
I also agree...it is a major pain.
Char
"Robert Rodgers" <rrodgers@sylvancomputing.com> wrote in message
news:b3t5ql$gup$1@news.codecharge.com...
> Yes, I agree also.
>
> rob
>
> "Kevin" <ka@acats.com> wrote in message
>news:b3rtv2$pr0$1@news.codecharge.com...
> > You have another YES VOTE:
> >
> > YES/CCS - Please tell us how you plan to address changing
skins with your
> > current naming convention????
> > Kangus A
> > "DonB" <dbweb2@premiersi.com> wrote in message
> >news:b3omtd$104$1@news.codecharge.com...
> > > Here's another bug (beta 3). Stylesheets are overwritten
with the
> > "master"
> > > copy anytime you create a new page (and at other times,
too).
> > >
> > > Really, if the stylesheet is put into the project, CCS
ought to leave it
> > > alone until you say "OK, go back to the unmodified style".
I know the
> > > "supported" way is to create a new folder, create a new
style and change
> > all
> > > the names - bleaghh.
> > >
> > > So, I elected to create an "override" sheet rather than
mangle the
> > standard
> > > one. No good either, because the <LINK> tag to my sheet
gets ripped out
> > > when I flip from design to code or rebuild the page.
Arrggghhh! After
> > all
> > > these are "cascading" style sheets.
> > >
> > > I already voiced opposition (to Yes) about the way they
rename all the
> > style
> > > "classes" to be prefixed with the style name. The "right
way" to use
> CSS
> > is
> > > to keep the classe names always the same, but point the
<LINK> to the
> > > desired CSS file (which ought to be named "Noise.CSS",
"DeepWater.CSS",
> > etc.
> > > The way it is, trying to implement a "skins" feature is
impractical.
> Yes
> > > feels I am wrong. Bzzzzt! Wrong answer.
> > >
> > >
> > > DonB (just ranting, not mad).
> > >
> > >
> >
> >
>
>
|
|
|
|
DAVID
|
| Posted: 03/10/2003, 5:31 AM |
|
I agree, but I have a workarround. When i deliver files to the server, I
remove style names from everywhere in html files (batched procedure). Upon
login the skinname is saved into session. every page has stylesheet call
dynamically built with skin being read from the session. All skins have skin
names removed from element names:
i.e:
<head>
<link rel="stylesheet" type="text/css" href="Themes/Mailbox/Style.css">
...
</head>
<html><td nowrap class="MailboxColumnTD">...</html>
becomes
<link rel="stylesheet" type="text/css"
href="Themes/{session_skin}/Style.css">
<html><td nowrap class="ColumnTD"></html>
"Kevin" <ka@acats.com> wrote in message
news:b3rtv2$pr0$1@news.codecharge.com...
> You have another YES VOTE:
>
> YES/CCS - Please tell us how you plan to address changing skins with your
> current naming convention????
> Kangus A
> "DonB" <dbweb2@premiersi.com> wrote in message
>news:b3omtd$104$1@news.codecharge.com...
> > Here's another bug (beta 3). Stylesheets are overwritten with the
> "master"
> > copy anytime you create a new page (and at other times, too).
> >
> > Really, if the stylesheet is put into the project, CCS ought to leave it
> > alone until you say "OK, go back to the unmodified style". I know the
> > "supported" way is to create a new folder, create a new style and change
> all
> > the names - bleaghh.
> >
> > So, I elected to create an "override" sheet rather than mangle the
> standard
> > one. No good either, because the <LINK> tag to my sheet gets ripped out
> > when I flip from design to code or rebuild the page. Arrggghhh! After
> all
> > these are "cascading" style sheets.
> >
> > I already voiced opposition (to Yes) about the way they rename all the
> style
> > "classes" to be prefixed with the style name. The "right way" to use
CSS
> is
> > to keep the classe names always the same, but point the <LINK> to the
> > desired CSS file (which ought to be named "Noise.CSS", "DeepWater.CSS",
> etc.
> > The way it is, trying to implement a "skins" feature is impractical.
Yes
> > feels I am wrong. Bzzzzt! Wrong answer.
> >
> >
> > DonB (just ranting, not mad).
> >
> >
>
>
|
|
|
|
Kevin
|
| Posted: 03/10/2003, 9:13 AM |
|
-- Something so simple yet powerful!!
Kevin A
"DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
news:b4i432$s1g$1@news.codecharge.com...
> I agree, but I have a workarround. When i deliver files to the server, I
> remove style names from everywhere in html files (batched procedure). Upon
> login the skinname is saved into session. every page has stylesheet call
> dynamically built with skin being read from the session. All skins have
skin
> names removed from element names:
> i.e:
> <head>
> <link rel="stylesheet" type="text/css" href="Themes/Mailbox/Style.css">
> ...
> </head>
> <html><td nowrap class="MailboxColumnTD">...</html>
> becomes
> <link rel="stylesheet" type="text/css"
> href="Themes/{session_skin}/Style.css">
> <html><td nowrap class="ColumnTD"></html>
>
> "Kevin" <ka@acats.com> wrote in message
>news:b3rtv2$pr0$1@news.codecharge.com...
> > You have another YES VOTE:
> >
> > YES/CCS - Please tell us how you plan to address changing skins with
your
> > current naming convention????
> > Kangus A
> > "DonB" <dbweb2@premiersi.com> wrote in message
> >news:b3omtd$104$1@news.codecharge.com...
> > > Here's another bug (beta 3). Stylesheets are overwritten with the
> > "master"
> > > copy anytime you create a new page (and at other times, too).
> > >
> > > Really, if the stylesheet is put into the project, CCS ought to leave
it
> > > alone until you say "OK, go back to the unmodified style". I know the
> > > "supported" way is to create a new folder, create a new style and
change
> > all
> > > the names - bleaghh.
> > >
> > > So, I elected to create an "override" sheet rather than mangle the
> > standard
> > > one. No good either, because the <LINK> tag to my sheet gets ripped
out
> > > when I flip from design to code or rebuild the page. Arrggghhh!
After
> > all
> > > these are "cascading" style sheets.
> > >
> > > I already voiced opposition (to Yes) about the way they rename all the
> > style
> > > "classes" to be prefixed with the style name. The "right way" to use
> CSS
> > is
> > > to keep the classe names always the same, but point the <LINK> to the
> > > desired CSS file (which ought to be named "Noise.CSS",
"DeepWater.CSS",
> > etc.
> > > The way it is, trying to implement a "skins" feature is impractical.
> Yes
> > > feels I am wrong. Bzzzzt! Wrong answer.
> > >
> > >
> > > DonB (just ranting, not mad).
> > >
> > >
> >
> >
>
>
|
|
|
|
DAVID
|
| Posted: 03/10/2003, 11:54 AM |
|
:) not so fast - the real pain is Theme images (next_rec,last_rec etc.) I
have to have a parsed block for every damn grid box on this planet ...
I think Yes ought to fix the situation somehow.
"Kevin" <ka@acats.com> wrote in message
news:b4ih48$pj5$1@news.codecharge.com...
> -- Something so simple yet powerful!!
> Kevin A
>
> "DAVID" <codecharge_newsfeed@stridetech.com> wrote in message
>news:b4i432$s1g$1@news.codecharge.com...
> > I agree, but I have a workarround. When i deliver files to the server, I
> > remove style names from everywhere in html files (batched procedure).
Upon
> > login the skinname is saved into session. every page has stylesheet call
> > dynamically built with skin being read from the session. All skins have
> skin
> > names removed from element names:
> > i.e:
> > <head>
> > <link rel="stylesheet" type="text/css" href="Themes/Mailbox/Style.css">
> > ...
> > </head>
> > <html><td nowrap class="MailboxColumnTD">...</html>
> > becomes
> > <link rel="stylesheet" type="text/css"
> > href="Themes/{session_skin}/Style.css">
> > <html><td nowrap class="ColumnTD"></html>
> >
> > "Kevin" <ka@acats.com> wrote in message
> >news:b3rtv2$pr0$1@news.codecharge.com...
> > > You have another YES VOTE:
> > >
> > > YES/CCS - Please tell us how you plan to address changing skins with
> your
> > > current naming convention????
> > > Kangus A
> > > "DonB" <dbweb2@premiersi.com> wrote in message
> > >news:b3omtd$104$1@news.codecharge.com...
> > > > Here's another bug (beta 3). Stylesheets are overwritten with the
> > > "master"
> > > > copy anytime you create a new page (and at other times, too).
> > > >
> > > > Really, if the stylesheet is put into the project, CCS ought to
leave
> it
> > > > alone until you say "OK, go back to the unmodified style". I know
the
> > > > "supported" way is to create a new folder, create a new style and
> change
> > > all
> > > > the names - bleaghh.
> > > >
> > > > So, I elected to create an "override" sheet rather than mangle the
> > > standard
> > > > one. No good either, because the <LINK> tag to my sheet gets ripped
> out
> > > > when I flip from design to code or rebuild the page. Arrggghhh!
> After
> > > all
> > > > these are "cascading" style sheets.
> > > >
> > > > I already voiced opposition (to Yes) about the way they rename all
the
> > > style
> > > > "classes" to be prefixed with the style name. The "right way" to
use
> > CSS
> > > is
> > > > to keep the classe names always the same, but point the <LINK> to
the
> > > > desired CSS file (which ought to be named "Noise.CSS",
> "DeepWater.CSS",
> > > etc.
> > > > The way it is, trying to implement a "skins" feature is impractical.
> > Yes
> > > > feels I am wrong. Bzzzzt! Wrong answer.
> > > >
> > > >
> > > > DonB (just ranting, not mad).
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
|
|
