I don't know if this is the right place to post a Subject like this.
First of all a piece of advice: this is a funny experiment (unreliable source). At the same time I've learned some about java and processing (thanks BEN/CASEY and all the people of this forum).

Some time ago I wrote up some about posting messages and the YaBB tags. Some people seems to have the same problem (is it a general problem?).
I had an simple idea: use processing IDE to solve it (interaction IDE-webBoard).

Originally I thought about a library, but I couldn't find out a way to read the sketchcode from a library without import or creating a new sketch (any idea, please?). That's the reason why I tried to hack PDE's source (may be it's a sin...).

This source creates a new menu option on the mouse's (right-button) popup menu called "Format for discourse".
And the new menu option lets you to format the sketchcode from the actual tab of the editor, according to the YaBB Bulletin Board Code (YaBBC color and b).
It uses mouse only (right click, Select All and copy). No editable.
No macs or keyboard support (I've tested only with windowsXP and Processing 0091).
Another features can be added: formatting selected text with a determined tag (|url|selected text|/url|).

I hope you enjoy this.
One Saludo.

Using CODE (you know...)
***********************
Code:

// This is a comment line
int a = 12;

void setup()
{
  println(a);
}

void draw() {
}

class example
{
  this.nothing = 0;
}

 

Using hacking-discourse (quote
instead because code tag cancels other YaBB tags)
***************************************************
Quote:

YaBB Tags (broken for read)
**************************
[color=#777755]// This is a comment line [/color[color=#993300][b]draw[/b [color


And the source (Eclipse workspace):
Discourse.zip

That sounds funny (teeny jar)!
Inside the Discourse.zip there is a readme.txt with the points you're refering to (if I've understood you correctly). Sorry: it's a bit hidden (ProcessingStyle/readme.txt).


� "were there things that you had to make public and whatnot that had not been previously":
It was necessary to read from outside (Discourse.java > String codeFormated() )

package processing.app.syntax
1.-- TextAreaPainter.java

 // package-private members
 // Changed to public <<<<
 public int currentLineIndex;
 public Token currentLineTokens;
 public Segment currentLine;


� "what sort of things did you have to change in the editor object":
Mouse button: a bridge to read and define (parent) Editor's textarea

package processing.app
2.-- Editor.java

----- At public TextAreaPopup() added:

this.addSeparator();

item = new JMenuItem("Format for discourse");
item.addActionListener(new ActionListener() {
  public void actionPerformed(ActionEvent e) {
    Discourse.formatDiscourse(textarea);
  }
});
this.add(item);


� And "what sort of methods do you need from the Editor object":

Uf! Well... this is more complicated.
May be I got the hardest way for Proccesing runtime, but the easiest for me and my limits. It can be changed for best running. Anyway...
The objective is SyntaxStyle[] styles (getFontMetrics and getColor). I've used the same Processing method, that is, first read code, put it into segment, get the Editor.textarea TextAreaPainter, the TokenMarker etc...
Then it creates a new window and paint the formated code.

Methods?
- To create a button (and may be a submenu) in the "Tools" as you say using that "teeny jar".
- To "get" the Editor object and its textarea.
- And your opinion about those private members in the TextAreaPainter.

Any other idea or suggestion are welcome.

Sure!
Feel free to do what you want.
I have another version without hack TextAreaPainter creating a new DiscourseTextAreaPainter (paralel TextAreaPainter) thinking about tools... But actually I have not much time.
Thank you for your hard work (and all the people who keep on helping-teaching!).

Keep on !

Nach.