LW Irving
|
| Posted: 06/09/2002, 3:36 AM |
|
I was getting very frustrated with CCS everytime I'd get to the end of my
project I'd do something small like change a font all hell would break
loose. First it couldn't find components, then weird errors would compound
as I tired to fix it.
I found the cause of most of my blues and will share it as this is a really
good product just a few teehing problems.
when you change the font of a field or in component like a navigator from
the design page it is really easy to apply the format tags in the wrong
place, but everything still looks good on the design page ie the html should
say <B>{mydbfieldname}</B> if you do not select the tags on the design page
you can get something like this {my<B>dbfieldname}</B>. Now code charge
can't find the variable.
I found this and was busily fixing the html in html view, I was marvelling
at how you could virtually see the links restablishing when the whole thing
just silently failed and I Lost all the work. So remember to save ofetn and
use different names to ensure you have more than one good copy.
I was ready to give up on CCS but since I found the format problem I have
been forging ahead, I'm really starting to like it.
Wayne
|
|
|
 |
DonB
|
| Posted: 06/09/2002, 9:00 AM |
|
I think you would do well to stick with "the program", that is, stay with
the concept of controlling the appearance by "class=xxx" attributes. You
could augment the standard CSS files or even (probably better, too) include
your own, separate, CSS with these classnames your tweaks require.
I'm concerned that in future versions, some embedded stuff like this might
fail. Following their "style" of development should minimize any chance of
that.
This means a small amount of extra work initially, sure. But the long term
benefits surely outweight that.
don
"LW Irving" <lirving@coffs.com.au> wrote in message
news:advb3r$k44$1@news.codecharge.com...
> I was getting very frustrated with CCS everytime I'd get to the end of my
> project I'd do something small like change a font all hell would break
> loose. First it couldn't find components, then weird errors would compound
> as I tired to fix it.
>
> I found the cause of most of my blues and will share it as this is a
really
> good product just a few teehing problems.
>
> when you change the font of a field or in component like a navigator from
> the design page it is really easy to apply the format tags in the wrong
> place, but everything still looks good on the design page ie the html
should
> say <B>{mydbfieldname}</B> if you do not select the tags on the design
page
> you can get something like this {my<B>dbfieldname}</B>. Now code charge
> can't find the variable.
>
> I found this and was busily fixing the html in html view, I was marvelling
> at how you could virtually see the links restablishing when the whole
thing
> just silently failed and I Lost all the work. So remember to save ofetn
and
> use different names to ensure you have more than one good copy.
>
> I was ready to give up on CCS but since I found the format problem I have
> been forging ahead, I'm really starting to like it.
>
>
> Wayne
>
>
|
|
|
|
LW Irving
|
| Posted: 06/10/2002, 1:30 AM |
|
Some times you need to be able to do things that are not in the program,
particularly when a number of functions do not work or are so different that
the method of use is no longer apparent. So the correct answer to the
original problem is use style sheets to control appearance.
My point was that the design screen should not enable you to apply
formatting (all I was doing was bolding a couple of fields) in a position
that can corrupt the html.
Secondly I have found no other way to do fine formating ie two tables next
to each other without going to the html and deleting the </P> that is
automaticly put there by the editor. However several times when I have been
doing this the program has just silently quit.
I mean the idea of puting the html page there is to take care of things that
can't be automated, so it should work correctly.
look at http://coffs.com.au/cdcbdb/cl.asp?name=coffsdotcom for the list or
for the record http://coffs.com.au/cdcbdb/cvr.asp?memberID=1105 the
welcome text has a bold for the word coffsdotcom. I had to type in the
since then i have found it on the html controls toolbox. My point
here is that it was a small formatting change, one of the last things I
noticed.
Wayne
"DonB" <7432D63DBB01D03A196B1EDD80E8@comcast.net> wrote in message
news:advu2m$njp$1@news.codecharge.com...
> I think you would do well to stick with "the program", that is, stay with
> the concept of controlling the appearance by "class=xxx" attributes. You
> could augment the standard CSS files or even (probably better, too)
include
> your own, separate, CSS with these classnames your tweaks require.
>
> I'm concerned that in future versions, some embedded stuff like this might
> fail. Following their "style" of development should minimize any chance
of
> that.
>
> This means a small amount of extra work initially, sure. But the long
term
> benefits surely outweight that.
>
> don
>
>
> "LW Irving" <lirving@coffs.com.au> wrote in message
>news:advb3r$k44$1@news.codecharge.com...
> > I was getting very frustrated with CCS everytime I'd get to the end of
my
> > project I'd do something small like change a font all hell would break
> > loose. First it couldn't find components, then weird errors would
compound
> > as I tired to fix it.
> >
> > I found the cause of most of my blues and will share it as this is a
> really
> > good product just a few teehing problems.
> >
> > when you change the font of a field or in component like a navigator
from
> > the design page it is really easy to apply the format tags in the wrong
> > place, but everything still looks good on the design page ie the html
> should
> > say <B>{mydbfieldname}</B> if you do not select the tags on the design
> page
> > you can get something like this {my<B>dbfieldname}</B>. Now code charge
> > can't find the variable.
> >
> > I found this and was busily fixing the html in html view, I was
marvelling
> > at how you could virtually see the links restablishing when the whole
> thing
> > just silently failed and I Lost all the work. So remember to save ofetn
> and
> > use different names to ensure you have more than one good copy.
> >
> > I was ready to give up on CCS but since I found the format problem I
have
> > been forging ahead, I'm really starting to like it.
> >
> >
> > Wayne
> >
> >
>
>
|
|
|
|
DonBevis
|
| Posted: 06/10/2002, 3:42 PM |
|
Yes, I can see your situation now. Originally, you described "field'
changes, which I took to mean a textbox,etc. So my suggestion won't work in
your case.
|
|
|
|
Dave Rexel
|
| Posted: 06/10/2002, 5:54 PM |
|
Hello Wayne
In the light of your experience:
To keep it simple, one should never be in danger of losing the page just by
applying a few hasty Bolds or Colors. This is surprisngly poor design from
this high-octane team.
I would like to suggest to CCS-team an omnipresent GUI Option for locking
the components in Design View and just exposing the names/text for editing
and formatting until the option is unlocked.
The main components to be locked/invisible would be the tag-badges for
sorters and navigators etc, resulting in an editable display resembling the
Preview.
Exposing one *solid* draggable tag-badge per form in this mode should get us
back to the beautiful and extremely functional reshuffling of forms on pages
as per CC2x. Components and forms should not be delete-enabled in this mode.
Tag-Variable names already have uniqueness checking so there is already much
of this functionality apparent in the execution of the IDE. Also in this
mode one would possibly dim/disable the Properties Panel or better yet
replace it with a CSS tag selector reading from the Themes loaded into
project.
Why?
I sincerely dislike having to redo/reload my page just because my hand
slipped even more than I detest restarting CCS *every* time I want to
rewrite one of my plug-ins.
A simple tag-badge locking mechanism would elegantly allow us to go wild on
the page display in relative safety, unleashing the presently under-used
designer aspect of this cool program.
Regards,
Dave
"LW Irving" <lirving@coffs.com.au> wrote in message
news:advb3r$k44$1@news.codecharge.com...
> I was getting very frustrated with CCS everytime I'd get to the end of my
> project I'd do something small like change a font all hell would break
> loose. First it couldn't find components, then weird errors would compound
> as I tired to fix it.
>
> I found the cause of most of my blues and will share it as this is a
really
> good product just a few teehing problems.
>
> when you change the font of a field or in component like a navigator from
> the design page it is really easy to apply the format tags in the wrong
> place, but everything still looks good on the design page ie the html
should
> say <B>{mydbfieldname}</B> if you do not select the tags on the design
page
> you can get something like this {my<B>dbfieldname}</B>. Now code charge
> can't find the variable.
>
> I found this and was busily fixing the html in html view, I was marvelling
> at how you could virtually see the links restablishing when the whole
thing
> just silently failed and I Lost all the work. So remember to save ofetn
and
> use different names to ensure you have more than one good copy.
>
> I was ready to give up on CCS but since I found the format problem I have
> been forging ahead, I'm really starting to like it.
>
>
> Wayne
>
>
|
|
|
|
LW Irving
|
| Posted: 06/13/2002, 9:59 PM |
|
exactly!
I wish I had said that
Wayne
ps I have come to terms with the things mentioned and have to say that this
already a great program and with daves suggestions would be truly EXCELLANT
"Dave Rexel" <therex_spamenot@hotmail.com> wrote in message
news:ae3hnn$fet$1@news.codecharge.com...
> Hello Wayne
> In the light of your experience:
>
> To keep it simple, one should never be in danger of losing the page just
by
> applying a few hasty Bolds or Colors. This is surprisngly poor design from
> this high-octane team.
>
> I would like to suggest to CCS-team an omnipresent GUI Option for locking
> the components in Design View and just exposing the names/text for editing
> and formatting until the option is unlocked.
>
> The main components to be locked/invisible would be the tag-badges for
> sorters and navigators etc, resulting in an editable display resembling
the
> Preview.
>
> Exposing one *solid* draggable tag-badge per form in this mode should get
us
> back to the beautiful and extremely functional reshuffling of forms on
pages
> as per CC2x. Components and forms should not be delete-enabled in this
mode.
> Tag-Variable names already have uniqueness checking so there is already
much
> of this functionality apparent in the execution of the IDE. Also in this
> mode one would possibly dim/disable the Properties Panel or better yet
> replace it with a CSS tag selector reading from the Themes loaded into
> project.
>
> Why?
> I sincerely dislike having to redo/reload my page just because my hand
> slipped even more than I detest restarting CCS *every* time I want to
> rewrite one of my plug-ins.
>
> A simple tag-badge locking mechanism would elegantly allow us to go wild
on
> the page display in relative safety, unleashing the presently under-used
> designer aspect of this cool program.
>
> Regards,
> Dave
>
> "LW Irving" <lirving@coffs.com.au> wrote in message
>news:advb3r$k44$1@news.codecharge.com...
> > I was getting very frustrated with CCS everytime I'd get to the end of
my
> > project I'd do something small like change a font all hell would break
> > loose. First it couldn't find components, then weird errors would
compound
> > as I tired to fix it.
> >
> > I found the cause of most of my blues and will share it as this is a
> really
> > good product just a few teehing problems.
> >
> > when you change the font of a field or in component like a navigator
from
> > the design page it is really easy to apply the format tags in the wrong
> > place, but everything still looks good on the design page ie the html
> should
> > say <B>{mydbfieldname}</B> if you do not select the tags on the design
> page
> > you can get something like this {my<B>dbfieldname}</B>. Now code charge
> > can't find the variable.
> >
> > I found this and was busily fixing the html in html view, I was
marvelling
> > at how you could virtually see the links restablishing when the whole
> thing
> > just silently failed and I Lost all the work. So remember to save ofetn
> and
> > use different names to ensure you have more than one good copy.
> >
> > I was ready to give up on CCS but since I found the format problem I
have
> > been forging ahead, I'm really starting to like it.
> >
> >
> > Wayne
> >
> >
>
>
|
|
|
|
|
