Thank you Tudor, thats looks definitely very useful .��I am downloading it now and studying it :)��On Wed, May 21, 2014 at 3:10 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
The first suggestion is to not invest in the PluggableTextMorph :)Ideally, we should get the new text widget soon, but in the meantime, you would be better with using Rubric. It is a pragmatic solution developed by Alain Plantec and that works now. This is where we are going with the Glamorous Toolkit at the moment. You find it already in the Moose image, or you can download it from here:Cheers,Doru--On Wed, May 21, 2014 at 12:44 PM, kilon alios <kilon.alios@gmail.com> wrote:
Hello guys, I have started a new experiment of mine, a tool I call "Talos". I want Talos to become workspace on steroids.The first thing I want to implement is emacs like navigation. With that I mean keyboard shortcuts for moving inside the text like you can do with arrow keys already and the ability to move to the next word , the first character of next word, the last character of next word , previous world, quickly rename variables and all the great things one can do with emacs and vim.��Of course I don't want to do all that at once, one step at a time.��Now I have take a look at Workspace and it seems that it uses PlaggableTextMorph , it also looks like I can get the contents via PluggableTextMorph>>text instance side. The source code returned is also send to RBParser using the parseBlock method , I think for syntax highlighting.��However because the PluggableTextMorph is very big and it does not even have a class comment, though quite a lot of methods are commented, I am really open to advice and suggestions on to how to parse the contents and manipulate the cursor position.��I know I could use PettitParser but I dont know if there are better options out there, or maybe I am doing the whole thing wrong.��So any advice and suggestion is more than welcomed.��"Every thing has its own flow"