dsmall
Posts: 5
|
| Posted: 04/15/2004, 5:23 PM |
|
Hi I have been using Codecharge 2.0 for over 2 years with great success. I am trying to move my projects to CCS. However I find CCS does not seem to update the files on the server. I am having to shutdown the project, delete the server files, clear the internet cache startup the project publish the project and determine if the changes worked. Is this a newbie problem? Am I missing something here?
Windows 2000 IIS
MySQL
ASP 3.0
CCS 2.2.3.60
Another strange thing happened I lost all the records in a table. This has never happened to me. I was experimenting with the query builder. I cant figure out what I did to delete all the records.
Any thoughts most appreciated.
|
 |
 |
peterr
Posts: 5971
|
| Posted: 04/15/2004, 5:59 PM |
|
I'm not familair with such problem except one case when the IIS server had some problems but the user who reported this issue resolved it without letting us know how.
Please describe why you have to shutdown the project, delete the server files and clear Internet cache? What happens if you simply publish your project to the server without performing all those actions?
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
dsmall
Posts: 5
|
| Posted: 04/15/2004, 9:25 PM |
|
This is so frustrating. I change the project theme I save the project I publish the project and would expect all the pages to change to the new theme. The body of the page changes but not much else. Navigation images don't update.
|
|
|
|
DonB
|
| Posted: 04/16/2004, 7:28 AM |
|
Have you checked the files on the server to see if their dates are being
updated - and that the new theme and image references are there? If they
are then maybe it's a caching issue in your browser and you are just not
retrieving the newer page data from the server. I"m not sure how the dates
are compared by browsers as to whether thye need to refetch, but perhaps
it's tied in with the server date/time vs. your browser date/time?
--
DonB
http://www.gotodon.com/ccbth
"dsmall" <dsmall@forum.codecharge> wrote in message
news:2407f60294d497@news.codecharge.com...
> This is so frustrating. I change the project theme I save the project I
publish
> the project and would expect all the pages to change to the new theme. The
body
> of the page changes but not much else. Navigation images don't update.
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
kangus
Posts: 47
|
| Posted: 04/22/2004, 1:06 PM |
|
 Two years ago I had a fight with CCS about the way they had mangled style changing; they code the name of the style into each class instead of using a style name as a selector. With the CCS method you have to hand change any code that you modify to change the style. With a selector method the current stylesheet storage system is used to select the style as in
$stylesheet = $home . $osfile . $ccspath . $osfile . $cssstyle . $osfile
which would be something like ./themes/Salad/
I have yet to figure out way they handled the style sheet issue the way they did.
_________________
PHP 4/5 mySQL 4.1/5 CCS 3.x |
|
|
|
peterr
Posts: 5971
|
| Posted: 04/22/2004, 1:26 PM |
|
kangus,
I'm not sure if you are asking why CCS doesn't provide the control of the CCS usage on the server (vs. the client/HTML like currently) ?
Generally I think that:
1. You can do what you described. Just ask how. If something cannot be done then we will take a closer look and possibly improve what's needed.
2. Certain decisions were made based on long and complex analysis of various possible situations. For example we utilize Theme names in CCS Tags to allow multiple themes to be used on the same page but with different forms. Most decisions are not made in 5 minutes by determining "let's use some selector method". Every decision involves long discussions and there is always someone who finds potential issues with almost any approach. We try to cover as many situations as possible while understanding that we may not satisfy everyone.
Though of course it is very helpful for us to know what are the users' goals and therefore we're looking for feedback about such goals, rather than ready-made solutions.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
DonB
|
| Posted: 04/22/2004, 2:49 PM |
|
I have never been able to see the value of "multiple themes to be used on
the same page but different forms" or how that ever became a deciding
factor. Changing themes over time? Yes. Having several themes on one
page? No.
I don't know when (if ever) I've seen a page with different parts having
different themes - at least no site that was pleasing to look at. And I
really would not want to have 2, 3, or 4 times the CSS baggage by specifying
multiple themes on a page (or even one each across several pages).
My opinion of the way CodeCharge implements CSS:
a. Requiring the IDE to parse and replace text throughout the project file
to change from one theme to another is very bad
b. It complicates the CSS making the files much larger than necessary.
c. It precludes taking advantage of the "cascading" aspect of style
sheets - themse are "flat", not "hierarchical"
d. It provides an overly-complicated and difficult to use theme editor that
makes style building as much work as building model ships in bottles
e. Run-time "skin" effects are out of the question because it's just too
much trouble to mess with getting it to work.
f. It is way too easy to screw up/overwrite theme changes because they all
have "style.css" for the file name
g. Each time you add a form to a page, the theme files get re-copied into
the project area, not following the code file concept of user changes are
marked and left untouched, which is bad because it runs contradictory to the
rest of CodeCharge behavior.
If you look at any well-designed web site (and the majority of those are run
by, and devoted to, those who truly understand the effective use of CSS) you
will see that elegant and visually-appealing sites are generally implemented
with "tiny" CSS definitions. In fact, the CodeCharge usage of CSS does not
lend itself well to one of the most fundamental tenets of CSS: separating
layout from formatting. And (a big issue), is the mixing of CSS elements
with embedded html attributes (look at your <body> tag!)
Just a couple of the many examples of the "right way" to do css:
http://www.meyerweb.com/eric/css/edge/ and http://www.bluerobot.com/.
CodeCharge encourages messy html. And I think that is the only real "bad
thing" I can say about the product: It's "99 and 44/100 percent pure", but
that other 66/100 of a percent is really is annoying at times.
Peter, please take this as constructive criticism and not a "rant". My
above comments (in various forms) have all previously been submitted to your
organization, through the official support channels and over the past couple
of years. It just seemed like a good time to revisit it.
--
DonB
http://www.gotodon.com/ccbth
"peterr" <peterr@forum.codecharge> wrote in message
news:240882a8366272@news.codecharge.com...
> I'm not sure if you are asking why CCS doesn't provide the control of the
CCS
> usage on the server (vs. the client/HTML like currently) ?
> Generally I think that:
> 1. You can do what you described. Just ask how. If something cannot be
done
> then we will take a closer look and possibly improve what's needed.
> 2. Certain decisions were made based on long and complex analysis of
various
> possible situations. For example we utilize Theme names in CCS Tags to
allow
> multiple themes to be used on the same page but different forms. Generally
it
> is not as simple as "let's use some selector method". Every decision
involves
> long discssions and there is always someone who finds potential issues
with
> almost any approach.
> _________________
> Peter R.
> YesSoftware Support Representative
> http://support.codecharge.com
> Warning: I use Google
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
|
