CSSDOC Google Group

Sorry for the SPAM mails lately

2009-09-17T07:21:13Z

Sorry for the SPAM mails lately, I was not aware of the fact that for
about the last 30 days this group was quite effectivly spammed. Nearly
any of those mails was caught by my own Spam folder therefore I did
not see them.
I removed those messages from the archive now and enabled a mechanism
that should protect the group better.

Re: tags

2009-08-09T21:55:16Z

Instead of diving down into ever-lengthening prefixes (sections,
subsections, subsubsections, and the logically necessary subsubsub-
and subsubsubsubsections), I'd suggest defining a generic way of
expressing hierarchy. "Packages" or "Sections" or "Components" or
"Widgets", the name is unimportant, but the concept is valuable.

Re: tags

2009-08-08T08:32:45Z

okay, section is not a secion of a hypertext document, it's a section
of the CSS file. so maybe that is the point of view that makes a
change.
the thought is good because for me I'm not so shure about having
subsections. we already had a discussion about that subsection /
subsubsection topic here in the list but not a real clue on it. maybe

Re: tags

2009-08-08T08:22:29Z

Well, it think it depends on the point of view... it is subjective.
Section is more like header or body to me, then subsection is f.e. left
panel. Each section can contain multiple elements, however component
should be css style for one separate component.

As I said, it is subjective, so never mind. I was just a thought :)

Re: tags

2009-08-08T08:04:44Z

Hi Martin,

thanks for you feedback. The examples you give look like sections for
me, I often put breadcrumb and other "widgets" or "boxes" etc. areas /
parts into sections or subsections. I have not run into any problems
with that until today.

Tom

Re: css_doc: Documentation Extraction Tool written in Ruby

2009-07-24T10:45:45Z

wir können auch deutsch schreiben wie ich dann gelesen habe :D

bin nicht so in C drin aber muss mal gucken ob wir libroco nach PHP
kriegen. vielleicht geht da was. die bisherigen parser an den ich dran
bin ist mehr selbstschreiben, aber libroco hat eh einige gute ideen.

was ich mich gefragt habe ist wie das da mit den kommentaren läuft.

Re: css_doc: Documentation Extraction Tool written in Ruby

2009-07-21T20:44:45Z

There are several CSS parsers around - perl has at least one, as does
java, python. But the first thing they all do is throw away comments,
so it takes hacking at the grammar to get them to be cssdoc-aware, by
which point you are more than half-way to making your own parser it
seems.
/Sam

Re: css_doc: Documentation Extraction Tool written in Ruby

2009-07-21T12:04:02Z

Hey tom,

Yeah, I wasn't either before I found csspool. I was about to write my
own CSS parser, which looking at it now would have been a stupid idea.
It really made things easy. After I figured out how to fix the
libcroco bug, it took me about an hour to get a first prototype
working, and another four hours to get it where it is right now.

Re: css_doc: Documentation Extraction Tool written in Ruby

2009-07-21T08:40:17Z

Heya Thomas!
That's really great news, and it looks just great!
I started a CSSDOC Implementations page in the Wiki and linked your
project there:
[link]
And put it on the front page.
I was not aware of such a library, need to take a look.
Regards,
Tom

css_doc: Documentation Extraction Tool written in Ruby

2009-07-20T21:48:32Z

Hey everyone,

As there is no tool to extract documentation from CSS files that I
know of, I got my hands dirty and wrote one myself. It is written in
the Ruby language as a Rubygem, and makes use of the wonderful csspool
library, which in turn depends on Gnome's powerful libcroco to do its
parsing. Therefore, the parser is as correct and stable as any CSS

Re: section / grouping concept using @section, @subsection, @subsubsection (or @group)

2009-05-07T08:05:36Z

yes, i would like to have some more ideas there as well because it
does not feel like this is having it in full.
i must say that subsection works quite well in practice. it is easy to
use even when i look conceptually at it it looks like having the said
flaws.
so it might be adviseable that current cssdoc users just give feedback

Re: section / grouping concept using @section, @subsection, @subsubsection (or @group)

2009-05-04T23:37:23Z

my concern also, the subsection thing just doesnt scale well, as
there's not really a useful "typical" section depth, and making a
arbitrary maximum depth in the specification is... arbitrary. Plus, if
you move code around, you may have to go through and correct all the
section levels. While best practices might dictate that a depth of

section / grouping concept using @section, @subsection, @subsubsection (or @group)

2009-05-02T11:35:45Z

Hi there,

I just read the Second Public Draft and get wondered about the section/
grouping concept.

As mentioned in the document itself, CSSEdit ([link]
cssedit/) uses @group with @end to group styles.
The first thing I was wondering while reading the draft was "How do I
close a section?" (without opening a new one).

updated textmate bundle

2009-02-11T10:05:56Z

hi list,
dirk dropped me some lines last night that an updated textmate bundle
for the cssdoc second public draft is available. some folks from
cologne/germany were so kind to provide it:
article (de): [link]
if you are unfamilar with the german language but you want to know