Issue 6893 in pharo: SourceCode styler should use RBParser

Status: Accepted
Owner: ----
Labels: Milestone-2.0 Type-Feature

New issue 6893 by [hidden email]: SourceCode styler should use  
RBParser
http://code.google.com/p/pharo/issues/detail?id=6893

ST80 currently features it's own parser, superfluous!

Solution:
- use RB to parse sources
- use a visitor to color nodes
- properly mark selector keywords


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 6893 by [hidden email]: SourceCode styler should  
use RBParser
http://code.google.com/p/pharo/issues/detail?id=6893

work started in the inbox


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Blockedon: pharo:6894

Comment #2 on issue 6893 by [hidden email]: SourceCode styler should  
use RBParser
http://code.google.com/p/pharo/issues/detail?id=6893

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 6893 by [hidden email]: SourceCode styler should  
use RBParser
http://code.google.com/p/pharo/issues/detail?id=6893

As a note: Do not forget:
PluggableTextMorph stylingClass: SHRBTextStyler


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Issue 6893: SourceCode styler should use RBParser
http://code.google.com/p/pharo/issues/detail?id=6893

This issue is no longer blocking issue pharo:6945.
See http://code.google.com/p/pharo/issues/detail?id=6945
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #6 on issue 6893 by [hidden email]: SourceCode styler should  
use RBParser
http://code.google.com/p/pharo/issues/detail?id=6893

Should we add this as a preview?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: WorkNeeded
        Owner: [hidden email]

Comment #7 on issue 6893 by [hidden email]: SourceCode styler should  
use RBParser
http://code.google.com/p/pharo/issues/detail?id=6893

I am almost done (I won't have much time to work on it until the 6.Dec).
I will definitely finish it in December, the current version has something  
like 90%:

- needs some changes in Nautilus since the Class Definition should be  
styled as in a Workspace (currently the shout parser does some magic to  
figure that out)
- some additional coloring tests are needed (as usual no tests for the  
shout parser / highlighter)
- the stylers cannot be switched that easily (so it's an either-or choice)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: -Milestone-2.0 Milestone-3.0

Comment #8 on issue 6893 by [hidden email]: SourceCode styler should  
use RBParser
http://code.google.com/p/pharo/issues/detail?id=6893

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker