perl-css-devel — For Perl CSS developers

[css] Text::Balanced test cases

[Bjoern H. <der...@gm...>]

Hi,

   CSS::SAC needs some addtitional test cases to fail some tests if the
required Text::Balanced version is not installed. I don't remember what
made the difference (probably multiline strings, Robin probably knows
better), therfore I cannot recommend some...

regards,
-- 
Björn Höhrmann { mailto:bj...@ho... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

[css] CSS::SAC live on SourceForge

[Bjoern H. <der...@gm...>]

Hi,

   Never looked into SourceForge's homepage features. I like to install
a little CGI script that takes some style sheets and returns some
text/plain document (a Notation3 document, the script is supposed to be
an implementation of my meta data proposal for CSS Level 3). Would this
be possible in general, i.e. does Sourceforge allow us to run CGI
scripts? Are latest CSS::SAC, Text::Balanced, etc.pp. installed in this
web space? If not, what about some cron'd script that installs those
modules on a regular base? At least, can I get someone to install those
modules in a local module space? I don't trust my PREFIX=...
capabilities anymore :-)

regards,
-- 
Björn Höhrmann { mailto:bj...@ho... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

Re: [css] Teaching CSS::SAC new at-rules

[Robin B. <ro...@kn...>]

On Sunday 21 October 2001 18:31, Bjoern Hoehrmann wrote:
>    CSS::SAC currently completly ignores unknown at-rules, applications
> don't even get the data if it is stored in a block (this should be
> changed, really).

That was really a bug in the code, it wanted to report the entire ignored 
at-rule, but didn't. Thanks for noting this, the patch is already in CVS 
(should work this way, at least it does here).

> What could be done to let applications add additional
> parsing steps for unknown at-rules? For the moment, I let CSS::SAC call
>
>   $sac->[_dh_]->ignorable_at_rule($at_rule => $data)
>
> i.e. the extracted block gets stored in $data in place of undef and gets
> reported to the application, where happens additional parsing.

There are several solutions. Right now, with the latest patch, the 
application gets the _text_ of the entire ignored @rule. This is the simplest 
approach, the app can do its own parsing (and use CSS::SAC's helpers for 
that).

Otherwise, we need to add another API to register @rules which could be 
cumbersome, but could be a good idea. If you jump to lines around 395, you'll 
see that @rules are dispatched on their names. If it is an unknown @rule, 
what could be done would be to have a hash mapping @rule name (the name being 
the IDENT following the @) to a callback. The callback would get the name, 
full text, and the sac object. From there it ought to be able to parse the 
rule correctly using parse_rule and parse_selector_list, or any scheme of its 
own device. Feel free to patch in support for that, to add it to the TODO, or 
to describe what it is you want in greater detail so that I can add it myself.

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
Immature poets imitate, mature poets steal. -- T.S. Eliot

Re: [css] uri vs. url

[Robin B. <ro...@kn...>]

On Sunday 21 October 2001 18:31, Bjoern Hoehrmann wrote:
>    CSS::SAC search for uri() functions (for the namespace declaration),
> those don't exist in CSS, it's a historical "misnomer", i.e. it's url().
> Is this intended? Should I go and fix it in CVS?

I can find three possible occurences of the problem in the current cvs 
CSS-SAC, on lines 103, 565, and 570. It isn't intended and a previous scan 
actually eliminated a number of these problems.

Note that LexicalUnit.pm has a URI constant. This may or may not be a 
misnomer as well. If it is, then the best thing would probably be to add a 
URL constant, but not to delete the current one (for back-compat). 
TestWriter.pm, Writer.pm may also exhibit similar problems.

Finally, the test file probably has the same problem and should be changed 
accordingly with the code.

Go ahead and patch Bjoern !

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
Change is inevitable except from a vending machine.

[css] Teaching CSS::SAC new at-rules

[Bjoern H. <der...@gm...>]

Hi,

   CSS::SAC currently completly ignores unknown at-rules, applications
don't even get the data if it is stored in a block (this should be
changed, really). What could be done to let applications add additional
parsing steps for unknown at-rules? For the moment, I let CSS::SAC call

  $sac->[_dh_]->ignorable_at_rule($at_rule => $data)

i.e. the extracted block gets stored in $data in place of undef and gets
reported to the application, where happens additional parsing.
-- 
Björn Höhrmann { mailto:bj...@ho... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

[css] uri vs. url

[Bjoern H. <der...@gm...>]

Hi,

   CSS::SAC search for uri() functions (for the namespace declaration),
those don't exist in CSS, it's a historical "misnomer", i.e. it's url().
Is this intended? Should I go and fix it in CVS?

regards,
-- 
Björn Höhrmann { mailto:bj...@ho... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

[css] CSS::Properties

[Bjoern H. <der...@gm...>]

Hi,

   CSS::SAC and CSS::DOM need some CSS::Properties module, SAC to adhere
to the forwared compatibility rules (i.e. ignore unknown properties,
ignore invalid values, etc.) if the user wants to parse some stylesheet
according to some specified CSS version, DOM to resolve shorthand
properties to the real properties. Requirements for this module are

  * it must distinguish between CSS levels (1, 2, 3)
  * it must provide explicite information on valid values
  * it must enable applications to resolve shorthand properties
  * it must consider CSS modules
  * it should be easily extensible for new CSS levels
  * it should consider CSS profiles
  * it should consider SVG 1.0

We can make a deal, someone provides a template for the data and I will
fill that template with data from CSS 1.0, CSS 2.0, SVG 1.0 and
occasionally CSS Level 3.

The CSS property value notation is quite complex. Think of property
values as XML DTD content models, thus order, occurences, alternates,
etc. shall be considered.

This module, in combination with CSS::SAC would enable us to write some
CSS::Validator module. If I get any time, I'll write that module as
contribution to the W3C HTML Validator (http://validator.w3.org/).

regards,
-- 
Björn Höhrmann { mailto:bj...@ho... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

[css] CSS DOM woes

[Bjoern H. <der...@gm...>]

Hi,

   The more I try to implement the current DOM Level 2 Style
recommendation in Perl, the more I dislike it. I asked a lot of
questions in mid April 2001, but I didn't get any answer, so I ask them
again and new ones, this time bugging www-dom, www-style *and* the
editors (with exception of Vidur Apparao, the recommendation doesn't
list any of the editors email addresses and I don't know his... :-( ).

Genericalism:

  The CSS DOM is very focussed on CSS Level 2 thus making it hard or
  nearly impossible to implement it in a generic fashion. This is
  allowed at least implicitly by the CSSStyleDeclaration definition in
  the specification. So, my questions assume, that the implementation
  doesn't know anything about things specific to a certain level of CSS.

The cascade:

  Some methods provide access to properties by their name, this implies
  that the cascade has to apply somewhere, but it isn't specified where.
  What rules apply to a CSS DOM implementation? Is it

    * only the last declaration counts
    * !important declarations override non-!important declarations?

  If this is the case, a call like

    CSSStyleDeclaration::setProperty('coolness', 'root', '')

  doesn't do anything if there was already a
  'coolness: kiddie !important'?

Typing:

  What constitutes a CSSValueList? It can't be the property's definition
  (since generic implementations don't know nothing about them), so this
  information must lie in the CSS tokens, but how is this supposed to
  work in a case like

    font-family: Arial Unicode MS, Trebuchet MS, sans-serif

  We have 6 CSS_IDENT values here, there are no other CSS types, that
  could be used to represent the comma but CSS_UNKNOWN, however, the
  comma is not specified as CSS value in the normative reference CSS
  Level 2. The comma will be lost in the DOM, an application is unable
  to know about what values make a singe font family name, the cssText
  attribute is useless, since the DOM application is supposed to
  re-stringify the property, in fact, the original text isn't available
  if the DOM builder used SAC to parse the style sheet. The
  specification could have said commas to create new CSSValueLists, but
  CSSValueList::item returns only CSSValue object, so this is no
  possible implementation.

Constructors:

  Where are create* methods? Why is there no interface to create
  CSSValues, CSSValueLists, etc. Actually this question should be,
  where are the objects in this object model? I/O via strings may be
  ok for values and selectors, but certainly not for rules and
  declarations, this just complicates implementations. Stringifycation
  is a job for serializers, but not for a DOM.

Error Treatment:

  It is not specified, how implementations are supposed to treat errors
  in string input, raising a DOMException with SYNTAX_ERR is not
  compatible with the forwared compatibility rules of the normative
  reference CSS Level 2. Consider some application tries to set
  CSSStyleDeclaration.cssText to

    "font-size: 2em; font-family: 'sans-serif'"

  A CSS parser will ignore the infalid font-family declaration, the DOM
  Interface would probably raise the mentioned DOMException and ignore
  the whole declaration. Or would it set font-size? But how should the 
  application then catch the error?

Selector API:

  Why is there no API for W3C Selectors? How should applications find
  out about what rules they want to manipulate, if they can't find out
  if the selector matches their needs, or how are simple modifications
  to some selectors to be done? The XPath DOM3 module also lacks of a
  feature to access XPath expressions. I think some task force should
  try to give them both a shareable API; this should be possible, since
  they share functionality and have similar syntax. Of course they need
  also specialised APIs to access their full potential, but if they'd
  have something in common, the learning curve of both and
  implementations of possible translators between W3C selectors and
  XPath expressions could be built more easily.

CSSStyleDeclaration:
 
  attribute item: "Used to retrieve the properties that have been 
  explicitly set in this declaration block. The order of the properties
  retrieved using this method does not have to be the order in which
  they were set." How does this interact with setProperty()?  If I add a
  new property via setProperty(), which index number does it get? length
  i.e. it is inserted at the end of the 'list'? Or doesn't that matter,
  i.e. the order may be changed through calling setProperty() or
  removeProperty()? In general, it doesn't make much sense to make
  CSSStyleDeclaration some type of list if this list is only accessed by
  property names, but this is a general DOM disease.

Font Descriptors and more typing:

  Given ist the following style sheet:

    @font-face {
      font-style: normal, italic;
    }

  How to present this in the DOM? I _very_ dislike the current
  situation, that font descriptors are treated as properties, however,
  according to the CSS grammar we have here [IDENT, DELIM, IDENT] in the
  property value. In the DOM is a CSSFontFaceRule for the 
  @font-face-rule created and CSSStyleDeclaration for it's content. Ok,
  but what about the value? I thought individual tokens make individual
  CSSValues, then we have a CSSValueList with

    [CSS_PRIMITIVE_VALUE, CSS_UNKNOWN, CSS_PRIMITIVE_VALUE]

  Is that the way to go, or is it

    [CSS_PRIMITIVE_VALUE, CSS_PRIMITIVE_VALUE]

  only for the 'normal' and 'italic' IDENTs? Which DELIM tokens would
  then not go into the DOM? How to present something like

    elem { twinkle: 6 > 7 }

Value Unit Conversion:

  The units [cm, mm, in, pt, pc], [hz, khz], [s, ms], [deg, rad, grad]
  allow mutual conversion, are other conversions possible? Can a CSS_URI
  be a CSS_STRING? Can CSS_DIMENSION and CSS_NUMBER be converted into
  something else?

Unicode Ranges:

  The specification does not provide any way to access Unicode Ranges.
  Why this omission? Representing them as CSS_UNKNOWN types doesn't
  really make sense.

Actual Values:

  The current CSS DOM doesn't provide any means to access the actual
  value for properties, why?

I'm sure I've missed a lot of issues (maybe others post ), but I'd be
very happy to get some clarifications on the mentioned points. The CSS
DOM will become more important since SVG users are likely to use it, but
that's IMO impossible, with a CSS DOM specification like the one
provided.

regards,
-- 
Björn Höhrmann { mailto:bj...@ho... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

[css] CSS::SAC::Writer::HTML

[Steffen G. <s.g...@eu...>]

This is a simple SAC handler that generates HTML.
Please note: This is not an attempt to transform
HTML4+CSS into HTML3+FONT!
This module helps to generate a syntax highlighted
representation of a stylesheet.


Steffen Goeldner

Re: [css] Re: [css-cvs] CVS: Parse - Imported sources

[Allen D. <da...@cs...>]

Yes, I've decided to put my module under the Parse namespace.  This seems
to make sense as I'm using a Parse::RecDescent grammar in one of the
modules.  Is it possible for you to purge my old cvs directory?

No Robin, I haven't really looked at your code.  I did skim the summary
and wasn't sure if it was really what I needed, so I made something of my
own.  

I don't think anyone will have a problem finding my module under Parse...
Maybe the functionality will be harder to guess though.  Where would you
recommend placing it?

-Allen

On Mon, 27 Aug 2001, Robin Berjon wrote:

> Allen,
> 
> is Parse::CSS the new name of CSS.pm ? Would you mind discussing all of this 
> on the list ? It seems to me that your module does much more than just parse 
> CSS which would make it harder to find for people looking for the rest of its 
> functionality. Also, I'm afraid of seeing good coding effort be duplicated by 
> having several CSS parsers. Have you taken a look at CSS::SAC ? If so, I'd be 
> interested in knowing your objections against it.
> 
> Thanks,
> 
> On Monday 27 August 2001 18:18, Allen Day wrote:
> > Update of /cvsroot/perl-css/Parse
> > In directory usw-pr-cvs1:/tmp/cvs-serv31580
> >
> > Log Message:
> > nothing yet
> >
> > Status:
> >
> > Vendor Tag:	allenday
> > Release Tags:	initial-import
> >
> > N Parse/CSS.pm
> > N Parse/Makefile.PL
> > N Parse/Makefile
> > N Parse/pm_to_blib
> > N Parse/test.pl
> > N Parse/CSS/CSS.xs
> > N Parse/CSS/Style.pm
> > N Parse/CSS/MANIFEST
> > N Parse/CSS/Adaptor.pm
> > N Parse/CSS/Adaptor/Default.pm
> > N Parse/CSS/Adaptor/Test.pm
> > N Parse/blib/lib/Parse/.exists
> > N Parse/blib/lib/Parse/CSS.pm
> > N Parse/blib/lib/Parse/CSS/test.pl
> > N Parse/blib/lib/Parse/CSS/CSS.xs
> > N Parse/blib/lib/Parse/CSS/Style.pm
> > N Parse/blib/lib/Parse/CSS/MANIFEST
> > N Parse/blib/lib/Parse/CSS/Adaptor.pm
> > N Parse/blib/lib/Parse/CSS/Adaptor/Default.pm
> > N Parse/blib/lib/Parse/CSS/Adaptor/Test.pm
> > N Parse/blib/lib/auto/Parse/CSS/.exists
> > N Parse/blib/arch/auto/Parse/CSS/.exists
> > N Parse/blib/man3/.exists
> > N Parse/blib/man3/Parse::CSS.3
> > N Parse/t/test1.pl
> > N Parse/t/t.css
> > N Parse/t/t
> > N Parse/t/wormbase.css
> >
> > No conflicts created by this import
> >
> >
> > ***** Bogus filespec: - Imported sources
> >
> > _______________________________________________
> > perl-css-commits mailing list
> > per...@li...
> > http://lists.sourceforge.net/lists/listinfo/perl-css-commits
> 
> -- 
> _______________________________________________________________________
> Robin Berjon <ro...@kn...> -- CTO
> k n o w s c a p e : // venture knowledge agency www.knowscape.com
> -----------------------------------------------------------------------
> The only sensible way to estimate the stability of a Windows server 
> is to power it down and try it out as a step ladder. 
> -- Robert Crawford, in the Monastery
> 
> 
> _______________________________________________
> per...@li...
> http://lists.sourceforge.net/lists/listinfo/perl-css-devel
> 

__________________
Allen Day
all...@cs...
1.516.367.6904

[css] Re: [css-cvs] CVS: Parse - Imported sources

[Robin B. <ro...@kn...>]

Allen,

is Parse::CSS the new name of CSS.pm ? Would you mind discussing all of this 
on the list ? It seems to me that your module does much more than just parse 
CSS which would make it harder to find for people looking for the rest of its 
functionality. Also, I'm afraid of seeing good coding effort be duplicated by 
having several CSS parsers. Have you taken a look at CSS::SAC ? If so, I'd be 
interested in knowing your objections against it.

Thanks,

On Monday 27 August 2001 18:18, Allen Day wrote:
> Update of /cvsroot/perl-css/Parse
> In directory usw-pr-cvs1:/tmp/cvs-serv31580
>
> Log Message:
> nothing yet
>
> Status:
>
> Vendor Tag:	allenday
> Release Tags:	initial-import
>
> N Parse/CSS.pm
> N Parse/Makefile.PL
> N Parse/Makefile
> N Parse/pm_to_blib
> N Parse/test.pl
> N Parse/CSS/CSS.xs
> N Parse/CSS/Style.pm
> N Parse/CSS/MANIFEST
> N Parse/CSS/Adaptor.pm
> N Parse/CSS/Adaptor/Default.pm
> N Parse/CSS/Adaptor/Test.pm
> N Parse/blib/lib/Parse/.exists
> N Parse/blib/lib/Parse/CSS.pm
> N Parse/blib/lib/Parse/CSS/test.pl
> N Parse/blib/lib/Parse/CSS/CSS.xs
> N Parse/blib/lib/Parse/CSS/Style.pm
> N Parse/blib/lib/Parse/CSS/MANIFEST
> N Parse/blib/lib/Parse/CSS/Adaptor.pm
> N Parse/blib/lib/Parse/CSS/Adaptor/Default.pm
> N Parse/blib/lib/Parse/CSS/Adaptor/Test.pm
> N Parse/blib/lib/auto/Parse/CSS/.exists
> N Parse/blib/arch/auto/Parse/CSS/.exists
> N Parse/blib/man3/.exists
> N Parse/blib/man3/Parse::CSS.3
> N Parse/t/test1.pl
> N Parse/t/t.css
> N Parse/t/t
> N Parse/t/wormbase.css
>
> No conflicts created by this import
>
>
> ***** Bogus filespec: - Imported sources
>
> _______________________________________________
> perl-css-commits mailing list
> per...@li...
> http://lists.sourceforge.net/lists/listinfo/perl-css-commits

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
The only sensible way to estimate the stability of a Windows server 
is to power it down and try it out as a step ladder. 
-- Robert Crawford, in the Monastery

Re: [css] CVS updates

[Robin B. <ro...@kn...>]

On Friday 17 August 2001 22:03, Robin Berjon wrote:
> thanks to many bug reports (especially *lots* by Bjoern Hoehrmann and
> Steffen Goeldner) I've now produced a number of patches. All of the current
> progress on CSS::SAC has been entered into CVS, making the current bundle
> an 0.04 candidate (until someone comes up with more bugs).
>
> 0.04 should be mostly a bugfix release, the features that are in the TODO
> will come later.

And to make life easier for the lazy I've made a release of the current CVS 
:-) It should appear on the project page soonish.

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
The computer can't tell you the emotional story.  It can give you the
exact mathematical design, but what's missing is the eyebrows. 
-- Frank Zappa

[css] CVS updates

[Robin B. <ro...@kn...>]

Hi,

thanks to many bug reports (especially *lots* by Bjoern Hoehrmann and Steffen 
Goeldner) I've now produced a number of patches. All of the current progress 
on CSS::SAC has been entered into CVS, making the current bundle an 0.04 
candidate (until someone comes up with more bugs).

0.04 should be mostly a bugfix release, the features that are in the TODO 
will come later.

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
"Chance is irrelevant. We will succeed." 
-- 7o9

[css] CVS list added

[Robin B. <ro...@kn...>]

Hi,

the perl-css-commits list has been created. It is not meant to be a 
discussion list (except for the very occasional post) but rather the list 
that receives CVS noitification of commits. You probably don't want to be 
there unless you're interested directly in the development of the modules 
that we have in CVS.

  http://lists.sourceforge.net/lists/listinfo/perl-css-commits

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
"My girlfriend always laughs during sex, no matter what she's reading"
-- Steve Jobs

Re: [css] CSS.pm added

[Allen D. <da...@cs...>]

> The single suggestion I have for the moment would be to change the namespace. 
> CSS.pm would normally be reserved for the base class, or all encompassing 
> system, or something like that, relating to CSS. That's why there is no 
> XML.pm for instace, because none of the modules there are generic enough 
> (though there may be one at some point).

I'll see if I can come up with something more appropriate.

> Sorry for being thick, but I'm still not sure I understand what it does 
> correctly. Could you provide an example ?

Say you have an array of text that represents a 1-dimensional series, and
you want some of that series to be highlighted yellow.  You can just
put <SPAN> tags around the text, and get your yellow highlighting by
defining the class (or id) of the tag.

             ----------------                        <-- highlight section
ATCGTTAACTAGACCTAACTTGGGCCTAAACGATACCCCCTTGGAACAAAAA <-- whole series

Now say you have a GD image, and you want to draw a line that represents
this same series, with the same part in yellow, and the rest black.
Calculating which part of the line should be a different color is just
arithmetic.  To make the yellow section yellow, you have to do something
like:

   $fg = GD->color(255,255,0);
   GD->line($x1,$y1,$x2,$y2,$fg);

What my module allows you to do is configure this in my.css as:

   .highlight { background-color: yellow; }

and then do something more flexible, like:

   $css = CSS->new(-source=>'my.css');
   $fg  = GD->color($css->style('.highlight');
   GD->line($x1,$y1,$x2,$y2,$fg);

and still obtain the same result.

-Allen

__________________
Allen Day
all...@cs...
1.516.367.6904

Re: [css] Hello!

[Chris C. <ch...@we...>]

Hi List

On Fri 17-Aug-2001 at 03:55:11 +0200, Robin Berjon wrote:
> 
> Any discussion related to CSS and Perl is welcome here.

I'm not very good with Perl but I know CSS, I've joined this list in
case there is anything I can do to help.

Chris 

-- 
Chris Croome 
http://www.webarchitects.co.uk/

Re: [css] CSS.pm added

[Robin B. <ro...@kn...>]

On Friday 17 August 2001 15:58, Allen Day wrote:
> I intend to use it hand-in-hand with CGI.pm.  In my work, I am often
> making dynamic HTML and image documents that need to be styled.  I thought
> it would be nice to put all the style configuration into one CSS file, and
> do the HTML and images from there.
>
> Right now I think this is all it's useful for.  It can be used to manage
> PerlMagick and GD images easily.

Sorry for being thick, but I'm still not sure I understand what it does 
correctly. Could you provide an example ?

> I haven't really thought about what else it should do.  Any
> ideas/suggestions would be welcome.

The single suggestion I have for the moment would be to change the namespace. 
CSS.pm would normally be reserved for the base class, or all encompassing 
system, or something like that, relating to CSS. That's why there is no 
XML.pm for instace, because none of the modules there are generic enough 
(though there may be one at some point).

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
Heisenberg may have been here.

Re: [css] Project Idea: EnCSS

[Robin B. <ro...@kn...>]

On Thursday 09 August 2001 11:27, Shlomi Fish wrote:
> My problem is that Netscape 4.7 has some CSS bugs, so I hoped I could
> write them with CSS and then EnCSS them. Well, guess it would not work.

Such an effort was started a year or two ago, and produced a few results.=
=20
While not totally useless it is true that it is not the way forward as in=
=20
many ways it is better to wait for nn4 to die the atrociously horrible de=
ath=20
that it deserves ten times over. Also, it is a lot harder than it seems. =
The=20
trivial parts are trivial (eg adding font tags) but the interesting parts=
=20
(positioning for instance) are very very hard to get right.

I agree with Bj=F6rn that something that worked the other way round would=
 be=20
very cool (I thought Tidy could do this partially).

On the CSS cleanup front there are also cool things to do with SVG. A lot=
 of=20
the SVG editors out there will produce stupid code where you have hundred=
s of=20
path elements in a row all of them with the exact same style attribute. W=
hile=20
gzip takes care of the size problem, it'd still be easier to hand edit if=
 and=20
to read (not to mention that it would produce a much lighter client-side =
DOM)=20
if those would be factored out into a CSS class.

--=20
_______________________________________________________________________=0D
Robin Berjon <ro...@kn...> -- CTO=0D
k n o w s c a p e : // venture knowledge agency www.knowscape.com=0D
-----------------------------------------------------------------------=0D
"What I like about deadlines is the lovely whooshing sound they make =0D
as they rush past." =0D
--Douglas Adams=0D
=0D

Re: [css] CSS.pm added

[Allen D. <da...@cs...>]

I intend to use it hand-in-hand with CGI.pm.  In my work, I am often
making dynamic HTML and image documents that need to be styled.  I thought
it would be nice to put all the style configuration into one CSS file, and
do the HTML and images from there.

Right now I think this is all it's useful for.  It can be used to manage
PerlMagick and GD images easily.

I haven't really thought about what else it should do.  Any
ideas/suggestions would be welcome.

-Allen

On Fri, 17 Aug 2001, Robin Berjon wrote:

> On Monday 13 August 2001 22:04, Allen Day wrote:
> > I'm using sourceforge to manage my CSS modules now.  Hopefully I've
> > succesfully added myself to the list, or I'm typing this in vain...
> 
> Hi Allen,
> 
> you are succesfully subscribed :-) Could you please expand on what your goals 
> are for CSS.pm, how it works, what it does, etc... ?
> 
> -- 
> _______________________________________________________________________
> Robin Berjon <ro...@kn...> -- CTO
> k n o w s c a p e : // venture knowledge agency www.knowscape.com
> -----------------------------------------------------------------------
> "Science is like sex: sometimes something useful comes out, but that 
> is not the reason we are doing it." -- R. Feynman
> 
> 
> _______________________________________________
> per...@li...
> http://lists.sourceforge.net/lists/listinfo/perl-css-devel
> 

__________________
Allen Day
all...@cs...
1.516.367.6904

Re: [css] Hello!

[Robin B. <ro...@kn...>]

On Tuesday 07 August 2001 09:22, gp...@ma... wrote:
> What's going on?  Just joined the list, read the archives.  What's this all
> about?  I love CSS and I love Perl, so I thought I'd join ;)

The idea is to coordinate people CSS development efforts in Perl and provide 
support to users of CSS modules. And also to provide a place when people can 
publicly shame overworked CSS module authors that do not follow the schedule 
they'd like to, while still being on topic.

Any discussion related to CSS and Perl is welcome here.

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
The computer can't tell you the emotional story.  It can give you the
exact mathematical design, but what's missing is the eyebrows. 
-- Frank Zappa

[css] CSS::SAC added

[Robin B. <ro...@kn...>]

Hi,

I've added CSS::SAC v0.03 (ie current CPAN) to SF's CVS. The idea is to now 
commit my current version so that the diffs are more apparent. I've requested 
a new list (perl-css-cvs) for those who wish to receive CVS commit 
information and am right now configuring our repository to mail that list 
when needed. I'll announce it when it's there.

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
"Many people would sooner die than think. In fact, they do." 
-- Bertrand Russell

Re: [css] CSS.pm added

[Robin B. <ro...@kn...>]

On Monday 13 August 2001 22:04, Allen Day wrote:
> I'm using sourceforge to manage my CSS modules now.  Hopefully I've
> succesfully added myself to the list, or I'm typing this in vain...

Hi Allen,

you are succesfully subscribed :-) Could you please expand on what your goals 
are for CSS.pm, how it works, what it does, etc... ?

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
"Science is like sex: sometimes something useful comes out, but that 
is not the reason we are doing it." -- R. Feynman

[css] CSS.pm added

[Allen D. <da...@cs...>]

Hi guys,

I'm using sourceforge to manage my CSS modules now.  Hopefully I've
succesfully added myself to the list, or I'm typing this in vain...

-Allen

__________________
Allen Day
all...@cs...
1.516.367.6904

Re: [css] A CSS module

[Robin B. <ro...@kn...>]

On Thursday 09 August 2001 02:08, Bjoern Hoehrmann wrote:
> * Robin Berjon wrote:
> >those of you not receiving CPAN daily updates might want to check this out
> > (I haven't had time, gotta rush to a wedding):
> >
> >http://theoryx5.uwinnipeg.ca/mod_perl/cpan-search?request=searchsearch?dis
> >t=CSS-0.02
>
> Oh my dear, CSS::Parser did better CSS parsing than this module, the
> documentation uses weired words (like "tags" for selectors or
> "attributes" for properties), `make test` isn't compatible with
> Test::Harness, the script doesn't even do testing, the POD for CSS.pm is
> equivalent with the POD for CSS::Selector, I have no idea what
> CSS::Adaptor is used for, etc.pp.

I was afraid that's what would happen if people started spawning lots of CSS 
projects...

> >I've prepared the latest CSS::SAC (with a fair number of patches to fix
> > the bugs, but no new features for now) for cvs, and will commit it monday
> > when I go back to work.
>
> I don't have to comment on this, do I? ;-)

heh. Actually I got sent to work in Provence at the last minute, with no 
cvs/ssh access. Not that I'm complaining mind you ;-), but I'm a few cvs 
add/commit aways... when I come back, which will be soon.

> >Is CSS::DOM already part/fully coded or is it just a plan ?
>
> The interface should be complete, but it lacks of CSS::SAC bindings to
> build a tree, I'm waiting for a current versin of CSS::SAC... :-)

Cool, then we'll have it soon.

Do you think CSS::SAC should move to spec-based event names or keep the 
current ones wrt CSS::DOM ? The trend in the Perl world seems to have 
changed...

> PS: the list server should modify the Reply-to: header to send all
>     replies to the list by default

Yup, change should be effective now.

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
All programmers are playwrights and all computers are lousy actors.

Re: [css] Project Idea: EnCSS

[Shlomi F. <sh...@te...>]

On Thu, 9 Aug 2001, Bjoern Hoehrmann wrote:

> * Shlomi Fish wrote:
> >Do you mean that those standards rely that such things be specified in t=
he
> >Cascading Style Sheets of the HTML page?
>
> Yes.
>
> >My problem is that Netscape 4.7 has some CSS bugs, so I hoped I could
> >write them with CSS and then EnCSS them. Well, guess it would not work.
>
> Not really, no. Better upgrade to NN 6.1 :-)

Hey, I have Mozilla 0.9.2 at home. However, go tell the Technion people to
install Navigator 6.1 on all of the Technion's computers. At one point
Netscape did not work at all on the EE NT Farm and I was told that I
should use IE 5 instead...

But then they fixed it...

Regards,

=09Shlomi Fish

 > --
> Bj=F6rn H=F6hrmann { mailto:bj...@ho... } http://www.bjoernsworld=
=2Ede
> am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
> 25899 Dageb=FCll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote=
/
>



----------------------------------------------------------------------
Shlomi Fish        sh...@t2...
Home Page:         http://t2.technion.ac.il/~shlomif/
Home E-mail:       sh...@te...

A more experienced programmer does not make less bugs. He just realizes
what went wrong more quickly.