there is no plan to introduce a plugin system or scripting capability. I want to keep Code Browser as simple as possible to keep it fast, with small footprint, and easy to port to another platform. I thought of several alternatives:
* Use lua: it is a lightweight programming language easy to embed.
* Provide a library for ruby: a script loads the editor library, registers ruby commands, then starts the editor.
* Better integration with external tools:
- more variables
- auto-reload files (allow external tools to modify text)
- accept folding and link directives in tool output
I'm currently prefering the last choice but I have no plan to implement any of it in the near future.
Marc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was thinking, since code-browser displays comments in a different mode than code, why not introduce markups and embeded graphics. For example, markups to emphasis keywords with italics, bold fonts, foreground and background colour or underlining.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would be great to have some kind of rich text in comments. But it should be restricted to simple tags (bold, italic, color) without graphics in order to be rendered in a (future) console version. And developing a rich text editor is a huge task even a simple one and I won't have time to do it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Are there any plans to introduce plugins or scripting into code-browser ? There's only so much you can do with the tools option.
mark
Hi,
there is no plan to introduce a plugin system or scripting capability. I want to keep Code Browser as simple as possible to keep it fast, with small footprint, and easy to port to another platform. I thought of several alternatives:
* Use lua: it is a lightweight programming language easy to embed.
* Provide a library for ruby: a script loads the editor library, registers ruby commands, then starts the editor.
* Better integration with external tools:
- more variables
- auto-reload files (allow external tools to modify text)
- accept folding and link directives in tool output
I'm currently prefering the last choice but I have no plan to implement any of it in the near future.
Marc
The second option sounds interesting.
I was thinking, since code-browser displays comments in a different mode than code, why not introduce markups and embeded graphics. For example, markups to emphasis keywords with italics, bold fonts, foreground and background colour or underlining.
It would be great to have some kind of rich text in comments. But it should be restricted to simple tags (bold, italic, color) without graphics in order to be rendered in a (future) console version. And developing a rich text editor is a huge task even a simple one and I won't have time to do it.
Any changes for it way?
ps: pls can you make option: tabbar in top/bottom.
No change here, but suggestions on scripting / plugins are welcome.
An option for the notebook tab positon will be added in the next release.
Cheers,
Marc