cssparser-developers Mailing List for CSS Parser (Page 3)

Hi Alan,

Thanks for your response,

I'm using the 0.9.5 version, as in
http://sourceforge.net/projects/cssparser/files/cssparser/ that one is the
latest released version.

Here is an example code:



package pruebitas;

import org.w3c.dom.css.CSSStyleDeclaration;

import com.steadystate.css.dom.CSSRuleListImpl;
import com.steadystate.css.dom.CSSStyleDeclarationImpl;
import com.steadystate.css.dom.CSSStyleRuleImpl;
import com.steadystate.css.dom.CSSStyleSheetImpl;

public class MyParser {
 public static void main(String[] args){
CSSStyleSheetImpl _styleSheet = null;
_styleSheet = new CSSStyleSheetImpl();
_styleSheet.setCssRules(new CSSRuleListImpl());

// Create a new rule
CSSStyleRuleImpl foundRule = new CSSStyleRuleImpl();
foundRule.setParentStyleSheet(_styleSheet);
foundRule.setSelectorText("#an-id-for-this");
 ((CSSRuleListImpl)_styleSheet.getCssRules()).add(foundRule);
 // set the rule's attribute value
CSSStyleDeclaration declaration = foundRule.getStyle();
// If declaration is null, add a new declaration to the above rule.
if (declaration == null)
{
// Create a new Declaration
declaration = new CSSStyleDeclarationImpl(foundRule);
// Add the declaration to the rule
((CSSStyleRuleImpl)foundRule).setStyle((CSSStyleDeclarationImpl)declaration);
}

declaration.setProperty("font-family", "arial, verdana, sans-serif", null);
 System.out.println("<<<<<<<<START>>>>>>>>");
System.out.println(_styleSheet.toString());
System.out.println("<<<<<<<<END>>>>>>>>");
 }
}


On Thu, Sep 29, 2011 at 11:22 AM, Alan Krueger <al...@tr...> wrote:

>  On 9/22/2011 12:33 PM, Martin Fox wrote:
>
> I just changed the version to the latest one, and when I run
> the getCssText() of a style sheet, the *font-family* value is coming
> without the comas that separate the different families in a same rule.
>
>  That was not happening in the previous version :(
>
>  Do you know how can I fix it?
> I replaced the version because the last one was giving me error when I
> parse an @import(), but now I'm having this issue.
>
>  Could you attach some sample code—maybe even a JUnit test—that
> demonstrates the problem?
>
> Specifically which version are you seeing this on?  We're in the middle of
> wrapping up 0.9.6 and I'm unsure if you're using one of the snapshot builds
> of that, or if you meant that you moved up to 0.9.5 from something else.
>
> You might want to try one of the snapshots of 0.9.6, as there were a number
> of bugfixes applied to that.
>
> Thanks,
> Alan Krueger
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>
>

On 9/22/2011 12:33 PM, Martin Fox wrote:
> I just changed the version to the latest one, and when I run 
> the getCssText() of a style sheet, the *font-family* value is coming 
> without the comas that separate the different families in a same rule.
>
> That was not happening in the previous version :(
>
> Do you know how can I fix it?
> I replaced the version because the last one was giving me error when I 
> parse an @import(), but now I'm having this issue.
>
Could you attach some sample code---maybe even a JUnit test---that 
demonstrates the problem?

Specifically which version are you seeing this on?  We're in the middle 
of wrapping up 0.9.6 and I'm unsure if you're using one of the snapshot 
builds of that, or if you meant that you moved up to 0.9.5 from 
something else.

You might want to try one of the snapshots of 0.9.6, as there were a 
number of bugfixes applied to that.

Thanks,
Alan Krueger

Hi,

I just changed the version to the latest one, and when I run
the getCssText() of a style sheet, the *font-family* value is coming without
the comas that separate the different families in a same rule.

That was not happening in the previous version :(

Do you know how can I fix it?
I replaced the version because the last one was giving me error when I parse
an @import(), but now I'm having this issue.

Thanks in advance.
Martin Fox.-

>Any idea when CSS3 support will be available?
>
Hi Kevin,

at the moment i have no idea.
I'm nearly done with my list of todo's for the next version. A new snapshot build will be available in some days.
The next step is to make a real release.

An than i will spend some time on setting up an initial css3 parser support. So there is hope to have something ready before chrismas...


    RBRi
    --------------------------
    Wetator
    Smart web application testing
    http://www.wetator.org

Any idea when CSS3 support will be available?

Congrats, Ronald!


On Tue, Jul 26, 2011 at 1:21 PM, Alan Krueger <al...@tr...> wrote:

> Just added Ronald Brill as a developer to the project.  He's been
> contributing patches in his role as developer on HtmlUnit, perhaps the
> largest client module of the CSS Parser project.  With HtmlUnit's
> profile in the Java community, I thought it made sense to plug Ronald
> into the project directly to meet their needs more quickly.
>
>
>
> ------------------------------------------------------------------------------
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

Just added Ronald Brill as a developer to the project.  He's been 
contributing patches in his role as developer on HtmlUnit, perhaps the 
largest client module of the CSS Parser project.  With HtmlUnit's 
profile in the Java community, I thought it made sense to plug Ronald 
into the project directly to meet their needs more quickly.

On 7/8/2011 4:31 PM, Ronald Brill wrote:
> Any progress?
>
I've been fairly swamped with a combination of my own and other 
developer's (day job) vacations.  I'll try to get to it shortly.

Would it make sense to bring you in as a developer on the cssparser 
project? If you don't want/need another commitment, I would completely 
understand.

Thanks,
Alan Krueger

Any progress?

    RBRi
    --------------------------
    Wetator
    Smart web application testing
    http://www.wetator.org

I don't have any notes, but I think there's a web interface to release on
SF:

http://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download#FileManagerWebInterface

The process for releasing to the central Maven repo has also changed since I
last messed with it:

http://maven.apache.org/guides/mini/guide-central-repository-upload.html

I think you're supposed to deploy to the Sonatype repo, which will
automatically send things to the central Maven repo:

https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide


On Mon, Jun 27, 2011 at 10:34 AM, Alan Krueger <al...@tr...> wrote:

> On 3/27/2008 5:08 PM, D&J Gredler wrote:
> > I've uploaded it to SF and deployed it to our Maven repo, which I'll
> > soon request be sync'ed with the central repo.
> Can you share instructions for what SF requires to get a release
> published?  I've never done that before in SF and I'm trying to be
> responsive to the HtmlUtil team's request for another release.  I could
> try to puzzle it out myself, but if you have some quick notes or
> pointers that would be very helpful.
>
> Thanks,
> Alan Krueger
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

On 3/27/2008 5:08 PM, D&J Gredler wrote:
> I've uploaded it to SF and deployed it to our Maven repo, which I'll 
> soon request be sync'ed with the central repo.
Can you share instructions for what SF requires to get a release 
published?  I've never done that before in SF and I'm trying to be 
responsive to the HtmlUtil team's request for another release.  I could 
try to puzzle it out myself, but if you have some quick notes or 
pointers that would be very helpful.

Thanks,
Alan Krueger

On Thu, 23 Jun 2011 10:44:07 -0500 Alan Krueger wrote:
>I agree.  Would it be possible to break up the large patch into discrete 
>functional patches, or are they irretrievably combined?

Hi Alan,

nice to finally get some response.
Breaking the patch up is not really possible. It contains too many different things. And CSSParser has not so many classes to realy work on different parts.
The patch is available at
http://www.wetator.org/repo/cssparser_2.txt
Please have a look. I tried to respect the rules of the project.

>
>I've not performed releases myself for this project, but I'd be willing 
>to help get things moving.
>

Thanks a lot for your help.
I'm not at home for the next days; will be back at Monday.


    RBRi
    --------------------------
    Wetator
    Smart web application testing
    http://www.wetator.org

On 6/13/2011 6:53 AM, Ronald Brill wrote:
> So i checked out the thing and have tried to build it and fix some issue.
> At first i have noticed, that some of the problems are already fixed because of the chanes waldbaer did; but nerver relased.
> Additionaly we need some more fixes and imporvements. So i have started some coding.
>
> Finally i contaced Daniel to submit that patch. But i think he has no time at the moment.
> Is it possible that i send you the (monster) patche and you commit the stuff (of course after carefully checking). And second, is it possible for you to make at least snapshot builds available?
> We have some plans to make a new release but it will be really helpfull too have have an improved version of cssparser also.
I agree.  Would it be possible to break up the large patch into discrete 
functional patches, or are they irretrievably combined?

I've not performed releases myself for this project, but I'd be willing 
to help get things moving.

Hi CSSParser Developers,

I'm one of the HtmlUnit developers. At the moment, we have some issues open related to problems with cssparser.

So i checked out the thing and have tried to build it and fix some issue.
At first i have noticed, that some of the problems are already fixed because of the chanes waldbaer did; but nerver relased.
Additionaly we need some more fixes and imporvements. So i have started some coding.

Finally i contaced Daniel to submit that patch. But i think he has no time at the moment.
Is it possible that i send you the (monster) patche and you commit the stuff (of course after carefully checking). And second, is it possible for you to make at least snapshot builds available?
We have some plans to make a new release but it will be really helpfull too have have an improved version of cssparser also.

Thanks for your time/support



    RBRi
    --------------------------
    Wetator
    Smart web application testing
    http://www.wetator.org

On 3/20/2008 1:15 PM, Alan Krueger wrote:
> (The question was asked earlier, but in the middle of another message.
> I'll restate the question to ensure it doesn't get missed.)
>
> Does anyone object to using Subversion for our source control?  We can't
> use both SVN and CVS at the same time.  We would have to enable SVN,
> convert our existing CVS repository into SVN, then import that into SF's
> SVN repository.
>
> It takes a bit of work, but it should be easy to back out if something
> went wrong in the conversion process.  I'm in favor of Subversion
> myself, I've found it quite a bit easier to use than CVS and more powerful.
I got only positive responses back then, but I didn't have time to look 
at it then.  I'd forgotten about this until recently.

I've converted over the CVS repo into SVN and imported it.  I haven't 
done any cleanup like adding svn:ignore properties anywhere or removing 
the CVSROOT from the trunk yet.

I disabled the CVS feature in the project, but we can get it back if 
someone rabidly objects at the last minute.  =)

Thanks,
Alan

Hello everyone,

I have a question about recompiling the parser's source with JavaCC and the .jj files found on the CVS. 

I have checked out the latest version (0.9.6-SNAPSHOT) and it works just fine. When I recompile the parser using the .jj files found in src/main/javacc and replace the files found in target/generate-sources/javacc, I always EmptyStackException errors with the same test code that was working just fine before.

The exact error I'm getting is:

Exception in thread "main" java.util.EmptyStackException
	at java.util.Stack.peek(Stack.java:85)
	at java.util.Stack.pop(Stack.java:67)
	at com.steadystate.css.parser.CSSOMParser$CSSOMHandler.endDocument(CSSOMParser.java:266)
	at com.steadystate.css.parser.AbstractSACParser.handleEndDocument(AbstractSACParser.java:488)
	at com.steadystate.css.parser.SACParserCSS2.styleSheet(SACParserCSS2.java:51)
	at com.steadystate.css.parser.AbstractSACParser.parseStyleSheet(AbstractSACParser.java:320)
	at com.steadystate.css.parser.CSSOMParser.parseStyleSheet(CSSOMParser.java:139)
	at CssTest.main(CssTest.java:24)

Is there anything that I'm doing wrong? Is there a special procedure to follow to recompile the parser?

Thanks a lot for the help,
Gabriel

Hi list,

can somebody experienced with javacc syntax please recheck the .jj 
files? To me it looks like there are some differences between the parser 
implementations and the CSS grammars, especially for CSS1.

-- 
Waldbaer

Daniel Gredler schrieb:
> Then standardizing on the first character sounds good to me!

I checked in some changes, so that the CSSOMObject's Locators point to 
the first character. This does not effect line/char numbers in exceptions.

-- 
Waldbaer

Then standardizing on the first character sounds good to me!


On Mon, Nov 24, 2008 at 3:43 AM, Waldbaer <wal...@us...>wrote:

> Daniel Gredler schrieb:
> > What's the current behavior?
>
> It's somehow mixed ...
>
> --
> Waldbaer
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

Waldbaer schrieb:
> Hi,
> 
> just recently I parsed a CSS resource containing something like the 
> following:
> 
>    .important {
> /* ... */
> }
> 
> using the CSS 2.1 SAC parser. There seems to be an issue with the class 
> selector '.important' because 'important' is a keyword in the grammar.
> 
> I'll try to look into this after the weekend.

I think, I fixed it. The (few) test run without failure.

Daniel Gredler schrieb:
> What's the current behavior?

It's somehow mixed ...

-- 
Waldbaer

On 22/11/2008, at 4:39 AM, Daniel Gredler wrote:

> Works for me, though I'd prefer we had some feedback from David  
> regarding the initial rationale for this code :-/

The plan for me is to go camping in a couple of hours, but looking at  
the wind and the rain outside I may have an opportunity to go through  
all this sooner than that.

David

What's the current behavior?


On Fri, Nov 21, 2008 at 5:26 AM, Waldbaer <wal...@us...>wrote:

> Hi,
>
> I plan to rewrtie the adding of Locators to CSSOM objects and
> LexicalValues. At the moment the following objects get a Locator:
>
> * CSSCharsetRuleImpl
> * CSSImportRuleImpl
> * CSSFontFaceRuleImpl
> * CSSMediaRuleImpl
> * CSSPageRuleImpl
> * CSSStyleRuleImpl
> * CSSUnknownRuleImpl
> * Property
> * LexicalUnitImpl
>
> Which location in the source code should the Locator point to?
>
> Should it always point to the first character?
>
> Example:
>
> @import "../../dojo/resources/dojo.css";
> ^                           Locator for CSSImportRuleImpl
>
> #testLayout {
> ^                           Locator for CSSStyleRuleImpl
>     height: 100%;
>     ^                       Locator for Property 'height'
>             ^               Locator for LexicalUnitImpl '100%'
>     border: 1px solid black;
>     ^                       Locator for Property 'border'
>             ^               Locator for LexicalUnitImpl '1px'
>                 ^           Locator for LexicalUnitImpl 'solid'
>                       ^     Locator for LexicalUnitImpl 'black'
> }
>
> --
> Waldbaer
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

Works for me, though I'd prefer we had some feedback from David regarding
the initial rationale for this code :-/


On Fri, Nov 21, 2008 at 11:12 AM, Alan Krueger <al...@tr...> wrote:

> Waldbaer wrote:
> > Well, I did some _changes_, but I did not write the original code. David?
> >
> If I'm reading the diff correctly, it claims those lines were added in
> that revision.
> > The problem that I see with this special treatment is that some viewing
> > applications may treat a TAB char as 8, some as 4, some as 2 characters
> > wide. In fact it's still only one character.
> >
> > I propose to remove the whole case block for '\t'
> I agree.  This is really presentation logic embedded in the parser.  The
> caller can expand the returned column based on how it treats tabs, but
> that's not something the parser itself needs to do.
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> cssparser-developers mailing list
> css...@li...
> https://lists.sourceforge.net/lists/listinfo/cssparser-developers
>



-- 
Daniel Gredler
http://daniel.gredler.net/

Waldbaer wrote:
> Which location in the source code should the Locator point to?
>
> Should it always point to the first character?
>
> Example:
>
> @import "../../dojo/resources/dojo.css";
> ^                           Locator for CSSImportRuleImpl
>
> #testLayout {
> ^                           Locator for CSSStyleRuleImpl
>   
That seems like a sensible approach to me.