Chip Cotton
|
| Posted: 07/03/2002, 5:12 PM |
|
I'm talking style sheets.
I'm trying to figure this style thing out but Code Charge is
overwriting my style sheet files and I can't figure out from WHERE.
I'd LIKE to add my own styles but it seems that styles are maintained
in at least three places, and a mysterious FOURTH place..
1) In the c:\program files\Codechargestudip\Components\Themes\
directory there are '.cct' files which seem to contain redundant
information contained in the:
2) '.css' files which are under their corresponding subdirectory under
Themes/
....then in the published directory there contains a
3) '.css' file which is being constantly overwritten using the source
from... WHERE?
I've tried making changes to all three of these sources, but I've
found styles reverting, or styles appearing one way in the preview and
another way in the published web.
OK, trying to start all over, I try the Tools/Themes menu option to
change the styles through CodeCharge Studio's style editor, even
though I paid for the vastly superior TopStyle Pro, but why would I
want to edit style sheets when I'm programming server side code? HUH?
Of COURSE I'd want to code my own style sheets, but....
I can make changes in the CSS file under the given \Themes directory,
but somehow, those changes get over-written with the defaults.
Likewise the published css file.
Hell, I've even edited the mysterious proprietory format "CCT" file,
but THE CCT FILE IS BEING EDITED FROM SOMEWHERE *ELSE* which is
shielded from our direct manipulation! (and this last one really threw
me for a loop)
OK, I had a cup of coffee, and start over.
I go to add a new theme, I'm told that whatever file name I use is
Read Only. Checking this has confirmed that the file's attributes are
NOT read only, nor is there any other application which has the target
file open (actually, this does this when trying to create a brand new
file.) So how is one suppose to Add a new theme?
This is really screwed up. I suppose it would be JUST TOO FREAKING
MUCH to have either a style tool that worked or the ability to simply
edit the style sheet and HAVE THE CHANGES STICK?
I'm really at a loss as to the mentality which is making this so
difficult.
I though that the direction of CodeCharge Studio from CodeCharge is
not to isolate us from the programming layer, not to have this 'menu
driven front end' but to give us hands on ability to work directly
with the code and the HTML, yet at basic every turn CCS frustrates me.
The tutorials have us directly write code and HTML, great! Yet we are
prevented from doing basic coding tasks (like embedding PHP code in
with HTML, directly editing style sheets, etc).
There is so much GOOD here, but boy-o-boy, this basic stuff is KILLING
me...
|
|
|
 |
DonB
|
| Posted: 07/03/2002, 7:04 PM |
|
Well, I think the "cct" files are nothing more than an assist to the IDE
where we see the style info appear in dialog boxes (I'm assuming the name
means these are CC "theme" files). Possibly these even come into play with
the "previews".
Anyway, from my vast experience  - 4 weeks - I can say pretty definitely
that the contents of your project's theme/whatever/style.css is what
controls your app and nothing else. Unless you've done something really
wierd like point to the "master" copy in the Components folder. I'm sure
that all it does is copy that folder to your project.
It sounds like you've tried to modify an existing theme and save it. I
would feel much safer having copied the cct and corresponding folder
contents to new names before I started editing them.
Be aware that all the classnames of the style elements are prefixed with the
style name and you're going to have to change the prefix to match. This may
be your downfall. Possibly the prefix names are causing things you change
to revert?
|
|
|
|
Chip Cotton
|
| Posted: 07/03/2002, 7:25 PM |
|
On Wed, 3 Jul 2002 21:04:37 -0500, "DonB"
<7432D63DBB01D03A196B1EDD80E8@comcast.net> wrote:
>Well, I think the "cct" files are nothing more than an assist to the IDE
>where we see the style info appear in dialog boxes (I'm assuming the name
>means these are CC "theme" files). Possibly these even come into play with
>the "previews".
>Anyway, from my vast experience - 4 weeks - I can say pretty definitely
>that the contents of your project's theme/whatever/style.css is what
>controls your app and nothing else. Unless you've done something really
>wierd like point to the "master" copy in the Components folder. I'm sure
>that all it does is copy that folder to your project.
You got it! I was COMPLETELY IGNORING the "project" files, and AHA!
Found out just before you wrote this. Thanks for the reply.
>It sounds like you've tried to modify an existing theme and save it. I
>would feel much safer having copied the cct and corresponding folder
>contents to new names before I started editing them.
Good advice, which I followed, but the missing link was the 'project'
directory. I somehow got it in my head that was just where the
codecharge file was being saved...
>Be aware that all the classnames of the style elements are prefixed with the
>style name and you're going to have to change the prefix to match. This may
>be your downfall. Possibly the prefix names are causing things you change
>to revert?
I believe you are right. They are 'reserved' and from now on I will
create new classes as I need them.
To further explain, I run a local webserver, and map the server's
'publishing' point to a local drive, to which I save the files
directly do to see what they'd look with PHP, etc. I use the same
server as a file server to which I save the codecharge files. Oh boy!
Silly me, I was thinking that I was editing the files *directly*!
Thanks again for the help.
|
|
|
|
|
