css-rules.bfinc improvements

[Úr Balázs]

Hi!

From the css-rules.bfinc file are missing some new css properties and

values. I would like to add them. And i have an idea: add some extra
entry to the reference element as in the W3C spec is it + an URL to
point at the spec.

Original reference element (background-color):
<reference>Sets the background color of an element
<b>Values:</b> <color> | currentColor | transparent | inherit
<b>Initial value:</b> transparent
<b>Media group:</b> visual</reference>

Improved reference element (background-color): <reference>Sets the background color of an element. <b>Values:</b> &lt;color&gt; | currentColor | transparent | inherit
<b>Initial:</b> transparent
<b>Applies to:</b> all elements
<b>Inherited:</b> no
<b>Percentages:</b> N/A
<b>Animatable:</b> yes
<b>Media:</b> visual
<b>W3C spec:</b> <a
href="http://www.w3.org/TR/css3-background/#background-color">URL</a></reference>

I tested it in Bluefish, the URL is clickable and points to the
correct location, open it in the browser.

Can I make it for all CSS properties?
Can I add the missing properties?

Regards
--
Balázs Úr

[Olivier Sessink]

Post by Úr Balázs
Hi!

From the css-rules.bfinc file are missing some new css properties and

values. I would like to add them. And i have an idea: add some extra
entry to the reference element as in the W3C spec is it + an URL to
point at the spec.
<reference>Sets the background color of an element
<b>Values:</b> <color> | currentColor | transparent | inherit
<b>Initial value:</b> transparent
<b>Media group:</b> visual</reference>
<b>Initial:</b> transparent
<b>Applies to:</b> all elements
<b>Inherited:</b> no
<b>Percentages:</b> N/A
<b>Animatable:</b> yes
<b>Media:</b> visual
<b>W3C spec:</b> <a
href="http://www.w3.org/TR/css3-background/#background-color">URL</a></reference>
I tested it in Bluefish, the URL is clickable and points to the
correct location, open it in the browser.
Can I make it for all CSS properties?
Can I add the missing properties?

yes, this is very welcome! this is a very good improvement for the
language file.

Olivier

[Úr Balázs]

Post by Olivier Sessink
yes, this is very welcome! this is a very good improvement for the
language file.

OK, i will start it soon.
Is it possible to make these references translatable? Most of my
students do not speak English, it would be a huge help to read it in
Hungarian. It is very strange to read English references in a
localized program.

--
Balázs Úr

[Úr Balázs]

Post by Olivier Sessink
yes, this is very welcome! this is a very good improvement for the
language file.

Hi!

I finished the CSS language file improvement, I attached the result.
There are some missing CSS rules too, I will add them later.
I will do the same for HTML too, but first read my 2. quetions below.

I have 2 quetions:

1.) There are several times in this file a list of css colors:
<group highlight="css-value" >
<autocomplete append=";" />
<element pattern="aliceblue"/>
<element pattern="antiquewhite"/>
<element pattern="aqua"/>
<element pattern="aquamarine"/>
<element pattern="azure"/>
....
<element pattern="transparent"/>
<element pattern="inherit"/>
</group>

Is it possible to replace all occurance of this list with <element
idref="e.css.color"/> ? Where is the definition of this element?

2.) Why are 2 rules for html?
bluefish/data/bflang/all-html.bfinc
bluefish/data/bflang/all-html5.bfinc

I think we can merge both into one file, because CSS has only one
file, too. There isn't separated files for CSS2 and CSS3. In the
merged all-html.bfinc we can show a warning in the reference for
elements removed form HTML5, like:
<strike>frame</strike> DEPRECATED: removed from HTML5

Regards,
Balázs Úr

[clansco]

On Sat, 7 Dec 2013 15:10:25 +0100

Post by Úr Balázs

Post by Olivier Sessink
yes, this is very welcome! this is a very good improvement for the
language file.

Hi!
I finished the CSS language file improvement, I attached the result.
There are some missing CSS rules too, I will add them later.

Hi Úr,
my two cents:
The CSS Flexible Box Layout, is Candidate Recommendation since 18
September 2012, but actually it is not supported by browers, except
Opera 12.

CSS Animations are Working Draft... etc.

I have a question: is it useful to add properties that one can't use in
real life ? This seems to me very confusing.
For props that are not rec but well supported we have
highlight="css-draft-property"
For non supported props have we to add an highlight="css-not-supported"?

;)

[Olivier Sessink]

Post by clansco
On Sat, 7 Dec 2013 15:10:25 +0100

Post by Úr Balázs

Post by Olivier Sessink
yes, this is very welcome! this is a very good improvement for the
language file.

Hi!
I finished the CSS language file improvement, I attached the result.
There are some missing CSS rules too, I will add them later.

Hi Úr,
The CSS Flexible Box Layout, is Candidate Recommendation since 18
September 2012, but actually it is not supported by browers, except
Opera 12.
CSS Animations are Working Draft... etc.
I have a question: is it useful to add properties that one can't use in
real life ? This seems to me very confusing.
For props that are not rec but well supported we have
highlight="css-draft-property"
For non supported props have we to add an highlight="css-not-supported"?

that might be a good solution. Another possibility is if we create a
language option "Enable not-supported CSS elements", and add a <group
class="not-supported-css"> around these elements.

Olivier

[Olivier Sessink]

Post by Úr Balázs

Post by Olivier Sessink
yes, this is very welcome! this is a very good improvement for the
language file.

Hi!
I finished the CSS language file improvement, I attached the result.
There are some missing CSS rules too, I will add them later.
I will do the same for HTML too, but first read my 2. quetions below.

thanks, great work!

Post by Úr Balázs
<group highlight="css-value" >
<autocomplete append=";" />
<element pattern="aliceblue"/>
<element pattern="antiquewhite"/>
<element pattern="aqua"/>
<element pattern="aquamarine"/>
<element pattern="azure"/>
....
<element pattern="transparent"/>
<element pattern="inherit"/>
</group>
Is it possible to replace all occurance of this list with <element
idref="e.css.color"/> ? Where is the definition of this element?

There are two possibilities:
1) if the complete context is the same, you can add an id to the first
context, and the second time you use it you can refer to that context
with idref. This will save quite some memory.

2) if the context is not the same, you can only refer to each individual
element by adding an id to the first occurence, and referring with idref
later in the file. That will save a little memory.

Post by Úr Balázs
2.) Why are 2 rules for html?
bluefish/data/bflang/all-html.bfinc
bluefish/data/bflang/all-html5.bfinc
I think we can merge both into one file, because CSS has only one
file, too. There isn't separated files for CSS2 and CSS3. In the
merged all-html.bfinc we can show a warning in the reference for
<strike>frame</strike> DEPRECATED: removed from HTML5

yes that is historical: when html5 was very new it was a good thing to
have a separate file. Nowadays it's so standard that it doesn't make
sense anymore. Perhaps we should postpone that merge to 2.2.6 so we have
more time to test the changes.

Olivier

[Úr Balázs]

Post by Olivier Sessink
1) if the complete context is the same, you can add an id to the first
context, and the second time you use it you can refer to that context with
idref. This will save quite some memory.

Yes, the context is the same, all of the css colors. I replaced the
occurances with <context idref="c.css.color"/>, and the reference is
at line 424 (I attached the modified file). Is it OK?
But I didn't find the reference of <element idref="e.css.lcomment"/>
in the file. I think it is not OK.

Post by Olivier Sessink
I have a question: is it useful to add properties that one can't use in
real life ? This seems to me very confusing.
For props that are not rec but well supported we have
highlight="css-draft-property"
For non supported props have we to add an highlight="css-not-supported"?

I think it is useful to add the css properties that supports at least
one famous browser. I am teaching web-programming and i can use any
css properties supporting at least one browser to demostrate how it
works.
The highlight="css-not-supported" can be a solution, but I added the
<b>WARNING:</b> this property is only supported by ... string to the
reference for these properties. If it is OK, I will do the same for
the other non-supported css properties too. What is your opinion?

Post by Olivier Sessink

Post by Úr Balázs
2.) Why are 2 rules for html?
bluefish/data/bflang/all-html.bfinc
bluefish/data/bflang/all-html5.bfinc

yes that is historical: when html5 was very new it was a good thing to have
a separate file. Nowadays it's so standard that it doesn't make sense
anymore. Perhaps we should postpone that merge to 2.2.6 so we have more time
to test the changes.

OK, I will merge both file to 2.2.6.

Can you commit my CSS language file improvement to 2.2.5 or it will be
only the part of 2.2.6 too?

Regards,
Balázs

[Olivier Sessink]

Post by Úr Balázs

Post by Olivier Sessink
1) if the complete context is the same, you can add an id to the first
context, and the second time you use it you can refer to that context with
idref. This will save quite some memory.

Yes, the context is the same, all of the css colors. I replaced the
occurances with <context idref="c.css.color"/>, and the reference is
at line 424 (I attached the modified file). Is it OK?
But I didn't find the reference of <element idref="e.css.lcomment"/>
in the file. I think it is not OK.

Post by Olivier Sessink
I have a question: is it useful to add properties that one can't use in
real life ? This seems to me very confusing.
For props that are not rec but well supported we have
highlight="css-draft-property"
For non supported props have we to add an highlight="css-not-supported"?

I think it is useful to add the css properties that supports at least
one famous browser. I am teaching web-programming and i can use any
css properties supporting at least one browser to demostrate how it
works.
The highlight="css-not-supported" can be a solution, but I added the
<b>WARNING:</b> this property is only supported by ... string to the
reference for these properties. If it is OK, I will do the same for
the other non-supported css properties too. What is your opinion?

sounds good.

Post by Úr Balázs
OK, I will merge both file to 2.2.6.
Can you commit my CSS language file improvement to 2.2.5 or it will be
only the part of 2.2.6 too?

I would propose to commit the CSS for 2.2.5, but merging html and html5
in 2.2.6

Olivier

[Olivier Sessink]

Post by Úr Balázs
Yes, the context is the same, all of the css colors. I replaced the
occurances with <context idref="c.css.color"/>, and the reference is
at line 424 (I attached the modified file). Is it OK?
But I didn't find the reference of <element idref="e.css.lcomment"/>
in the file. I think it is not OK.

possibly this is defined in one of the html and php language files where
css is included?

Olivier

[Olivier Sessink]

Post by Úr Balázs
Yes, the context is the same, all of the css colors. I replaced the
occurances with <context idref="c.css.color"/>, and the reference is
at line 424 (I attached the modified file). Is it OK?
But I didn't find the reference of <element idref="e.css.lcomment"/>
in the file. I think it is not OK.

If I test this file I get many errors in the console:

Error in language file, element with id e.css.length does not exist
Error in language file, context id c.css.border already exists
Error in language file, element with id e.css.length does not exist
Error in language file, element with id e.css.percent does not exist
Error in language file, context id c.css.uri already exists
Error in language file, element with id e.css.length does not exist
Error in language file, element with id e.css.percent does not exist
Error in language file, context id c.css.border already exists
Error in language file, element with id e.css.length does not exist
Error in language file, context id c.css.border_style already exists
Error in language file, context id c.css.border_width already exists
Error in language file, context id c.css.border already exists

it seems that the same ID is used multiple times, and some idref's refer
to an ID that does not exist.

Do you know how to fix these errors or do you need some help with that?

Olivier

[Úr Balázs]

Post by Olivier Sessink
it seems that the same ID is used multiple times, and some idref's refer
to an ID that does not exist.
Do you know how to fix these errors or do you need some help with that?

Hi!

I try to fix the errors, in my opinion the process is the following:
- at the first occurance: <element id="e.css.end" ... >
- at the other occurances: <element idref="e.css.end"/>

Is it correct? If it is, i will fix it.

Regards,
Balázs

[clansco]

On Tue, 10 Dec 2013 19:16:55 +0100

Post by Úr Balázs

Post by Olivier Sessink
it seems that the same ID is used multiple times, and some idref's refer
to an ID that does not exist.
Do you know how to fix these errors or do you need some help with that?

Hi!
- at the first occurance: <element id="e.css.end" ... >
- at the other occurances: <element idref="e.css.end"/>
Is it correct? If it is, i will fix it.

Yes, first you define the ref, then you can use it.
Regards,
ff

[Úr Balázs]

Post by Olivier Sessink
Do you know how to fix these errors or do you need some help with that?

Hi!

I fixed most of the errors, but I have still 2 errors:
Error in language file, blockstartelement e.css.lbrace does not exist
Error in language file, context id c.css.pseudo already exists

I don't know how to fix the first error.
The second error said that c.css.pseudo already exists but I don't
find it in the file.

Can you help to fix these errors?

Regards,
Balázs

[Andrius]

Could not help much with fixing, but c.css.pseudo is also defined in css-selectors.bfinc file.

________________________________
Sent: Thursday, December 19, 2013 12:10 AM
Subject: Re: css-rules.bfinc improvements

Post by Olivier Sessink
Do you know how to fix these errors or do you need some help with that?

Hi!
Error in language file, blockstartelement e.css.lbrace does not exist
Error in language file, context id c.css.pseudo already exists
I don't know how to fix the first error.
The second error said that c.css.pseudo already exists but I don't
find it in the file.
Can you help to fix these errors?
Regards,
Balázs

[Olivier Sessink]

Post by Úr Balázs

Post by Olivier Sessink
Do you know how to fix these errors or do you need some help with that?

Hi!
Error in language file, blockstartelement e.css.lbrace does not exist
Error in language file, context id c.css.pseudo already exists
I don't know how to fix the first error.
The second error said that c.css.pseudo already exists but I don't
find it in the file.
Can you help to fix these errors?

you found a design problem in the language file loading. The css-rulles
are included twice in the HTML language file. I'm currently changing the
code such that you can set both id and idref for a context (and possibly
also for a element and tag). The first time the context is found, it is
compiled, the second time idref is used.

I'll make the changes to fix the last errors.

Olivier

[clansco]

On Wed, 12 Jun 2013 23:29:46 +0200

Hi!
From the css-rules.bfinc file are missing some new css properties and
values. I would like to add them. And i have an idea: add some extra
entry to the reference element as in the W3C spec is it + an URL to
point at the spec.
<reference>Sets the background color of an element
<b>Values:</b> <color> | currentColor | transparent | inherit
<b>Initial value:</b> transparent
<b>Media group:</b> visual</reference>
<b>Initial:</b> transparent
<b>Applies to:</b> all elements
<b>Inherited:</b> no
<b>Percentages:</b> N/A
<b>Animatable:</b> yes
<b>Media:</b> visual
<b>W3C spec:</b> <a
href="http://www.w3.org/TR/css3-background/#background-color">URL</a></reference>
I tested it in Bluefish, the URL is clickable and points to the
correct location, open it in the browser.

I agree to take reference at W3C, http://www.w3.org/TR/#tr_CSS
css base reference is CSS 2.1,
we have to update properties that are in Candidate Recommendations,
but see for example box-decoration-break, that is only supported by
Opera, I think we don't add for now.
on the contrary background-size is well supported and have to be add.

We can also add as css-draft-property properties that are in Working Draft
but well supported.
http://www.w3.org/Style/CSS/current-work.en.html

we have list here for example :
http://realworldvalidator.com/css/properties
http://csscreator.com/properties

I think we don't add Vendor-prefixed CSS Properties in bflang2,
but only in snippets:
http://peter.sh/experiments/vendor-prefixed-css-property-overview/

It would be nice to have a xslt sheet to do this,
but I'm not able to work on it right now.