Suntower
Posts: 225
|
| Posted: 12/16/2004, 11:50 AM |
|
It appears that when one changes a Theme using CCS not all the things I would expect get updated (background page, table properties, etc.)
I read some other posts which mention this so I'm looking for a strategy for the future.
1. Do you recommend using CCS styles or HTML styles? Is there a way to tell the appgen to use one or the other?
2. Can I simply change the them source in some way to use html style tags ( <p> <td> etc. ) so that if I can a particular colour I will -know- the change propagates to all relevant pages?
3. Any plans in CCS to make this more comprehensive?
TIA,
---JC
_________________
---On a campaign for more examples and better docs! |
 |
 |
peterr
Posts: 5971
|
| Posted: 12/16/2004, 2:02 PM |
|
Hi JC,
When modifying a Theme you're modifying the source of that Theme, not the styles already included in your pages. That's just like modifying a MS Word template document - it won't change your existing documents until you reuse that template to create new documents in the future.
However, if you create a new form on a page using that newly modified Theme then the new Theme will get copied to your project and will modify your other pages & forms at that time.
#1. I'd recommend CSS. You can specify this on the Sep 8 of 9 of the App Builder.
#2. Probably you don't need to use Themes for this. Just include your own .css file into your pages.
#3. Yes.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
Benjamin Krajmalnik
|
| Posted: 12/17/2004, 11:16 AM |
|
This is what I have done:
I have gone in and modified all of the themes so that, for example, the word
"Cobalt" is removed from all of the identifiers in the theme.
In my source, I use a label to hold the theme , and dynamically replace it
based on a config setting.
That way, my application can be used with many configurable themes without
having to change any settings at all.
|
|
|
|
Mike Bavistock
|
| Posted: 01/30/2005, 7:15 PM |
|
I have found the same problems when using CCS as JC (Suntower). In point 2. JC talks about using native HTML tags, instead of custom CCS theme styles.
Besides the fact that the Theme's make the product look like something from the 90's, the prolific use of class= in the source code demonstrates that the product developers are not up to speed with HTML/CSS standards.
For example:
<font class="Mailbox_copyFormHeaderFont">Add/Edit Agency</font>
should be:
<h1>Add/Edit Agency</h1>
, with h1 defined just like .Mailbox_copyFormHeaderFont in the CSS.
Reasons:
1. The <font> tag is deprecated, and
2. <h1> tells us more about the page structure.
|
|
|
|
|
