Good day,
I am interested in assisting with TextMate development. I really like the editor, and want to contribute to make it better! I want to help add newer and more modern actions to it similar to Sublime Text. I was wondering if you had any links for getting started? I’ve downloaded the source code and set up a dev environment and can compile it successfully. I’m reading through the source code and testing things; I was just wondering if you have any information on the Oak framework and the general layout of the application structure. Thank you for your help!
-- Josh Bernitt Sent with Airmail
On 2016-04-09 15:22, Josh Bernitt wrote:
Good day,
I am interested in assisting with TextMate development. I really like the editor, and want to contribute to make it better! I want to help add newer and more modern actions to it similar to Sublime Text.
This sounds great :). Any particular ideas or features you're thinking of implementing?
I was wondering if you had any links for getting started? I’ve downloaded the source code and set up a dev environment and can compile it successfully. I’m reading through the source code and testing things; I was just wondering if you have any information on the Oak framework and the general layout of the application structure. Thank you for your help!
As far as I know there's no getting started documentation. This is what I've figured out so far hacking on the source code:
* The application is a Cocoa application which uses Objective-C++ for the interface related code and C++ for the rest of the code
* The application is divided in a bunch of frameworks, the Frameworks directory
* It doesn't use nib files like a traditional Cocoa application
* The OakTextView framework contains the document view, gutter, status bar and the view for the actual source code. The OakTextView class is responsible for responding to keyboard input when editing the source code
* The rendering of the source code is not performed in OakTextView but delegated to the "layout" framework. This framework uses Core Text to render the source code
Yes, I have a few simple ideas to start off on while I learn all the ins and outs. 1) Highlighted text in the editor will auto populate the Find field when searching, rather than having to type in the text to find. I’ve personally grown accustomed to that in all the other editors I use.
2) Code comments should autocomplete. So if I use /** [tab]—> I would get an auto completed /** * */ and upon every return inside of a multiline comment, a new asterisk would prepend the new line so it would keep proper formatting and such. I want to apply that logic to all code comments.
I have some other ideas too, but I figure I should focus on doing those first since they seem easier to get my feet wet.
Thanks for the response of the file structure layout! That helps me understand it a bit more.
-- Josh Bernitt Sent with Airmail
On April 10, 2016 at 7:08:14 AM, Jacob Carlborg (doob@me.com) wrote:
On 2016-04-09 15:22, Josh Bernitt wrote:
Good day, I am interested in assisting with TextMate development. I really like the editor, and want to contribute to make it better! I want to help add newer and more modern actions to it similar to Sublime Text.
This sounds great :). Any particular ideas or features you're thinking of implementing?
I was wondering if you had any links for getting started? I’ve downloaded the source code and set up a dev environment and can compile it successfully. I’m reading through the source code and testing things; I was just wondering if you have any information on the Oak framework and the general layout of the application structure. Thank you for your help!
As far as I know there's no getting started documentation. This is what I've figured out so far hacking on the source code:
* The application is a Cocoa application which uses Objective-C++ for the interface related code and C++ for the rest of the code
* The application is divided in a bunch of frameworks, the Frameworks directory
* It doesn't use nib files like a traditional Cocoa application
* The OakTextView framework contains the document view, gutter, status bar and the view for the actual source code. The OakTextView class is responsible for responding to keyboard input when editing the source code
* The rendering of the source code is not performed in OakTextView but delegated to the "layout" framework. This framework uses Core Text to render the source code
-- /Jacob Carlborg
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Hi Josh,
Maybe a 3rd idea: ability to choose block cursor instead of line cursor. ;)
Kind regards,
Peter
On 10 Apr 2016, at 13:25 pm, Josh Bernitt jjbernitt@gmail.com wrote:
Yes, I have a few simple ideas to start off on while I learn all the ins and outs.
Highlighted text in the editor will auto populate the Find field when searching, rather than having to type in the text to find. I’ve personally grown accustomed to that in all the other editors I use.
Code comments should autocomplete. So if I use /** [tab]—> I would get an auto completed /** * */
and upon every return inside of a multiline comment, a new asterisk would prepend the new line so it would keep proper formatting and such. I want to apply that logic to all code comments.
I have some other ideas too, but I figure I should focus on doing those first since they seem easier to get my feet wet.
Thanks for the response of the file structure layout! That helps me understand it a bit more.
-- Josh Bernitt Sent with Airmail
On April 10, 2016 at 7:08:14 AM, Jacob Carlborg (doob@me.com) wrote:
On 2016-04-09 15:22, Josh Bernitt wrote:
Good day,
I am interested in assisting with TextMate development. I really like the editor, and want to contribute to make it better! I want to help add newer and more modern actions to it similar to Sublime Text.
This sounds great :). Any particular ideas or features you're thinking of implementing?
I was wondering if you had any links for getting started? I’ve downloaded the source code and set up a dev environment and can compile it successfully. I’m reading through the source code and testing things; I was just wondering if you have any information on the Oak framework and the general layout of the application structure. Thank you for your help!
As far as I know there's no getting started documentation. This is what I've figured out so far hacking on the source code:
- The application is a Cocoa application which uses Objective-C++ for
the interface related code and C++ for the rest of the code
- The application is divided in a bunch of frameworks, the Frameworks
directory
It doesn't use nib files like a traditional Cocoa application
The OakTextView framework contains the document view, gutter, status
bar and the view for the actual source code. The OakTextView class is responsible for responding to keyboard input when editing the source code
- The rendering of the source code is not performed in OakTextView but
delegated to the "layout" framework. This framework uses Core Text to render the source code
-- /Jacob Carlborg
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
That is definitely a good idea! Thanks!
-- Josh Bernitt Sent with Airmail
On April 10, 2016 at 8:37:53 AM, Novitzky Peter (pnovitzky@gmail.com) wrote:
Hi Josh,
Maybe a 3rd idea: ability to choose block cursor instead of line cursor. ;)
Kind regards,
Peter
On 10 Apr 2016, at 13:25 pm, Josh Bernitt jjbernitt@gmail.com wrote:
Yes, I have a few simple ideas to start off on while I learn all the ins and outs.
- Highlighted text in the editor will auto populate the Find field when searching, rather than having to type in the text to find. I’ve personally grown accustomed to that in all the other editors I use.
2) Code comments should autocomplete. So if I use /** [tab]—> I would get an auto completed /**
*/ and upon every return inside of a multiline comment, a new asterisk would prepend the new line so it would keep proper formatting and such. I want to apply that logic to all code comments. I have some other ideas too, but I figure I should focus on doing those first since they seem easier to get my feet wet. Thanks for the response of the file structure layout! That helps me understand it a bit more. -- Josh Bernitt Sent with Airmail On April 10, 2016 at 7:08:14 AM, Jacob Carlborg (doob@me.com) wrote:
On 2016-04-09 15:22, Josh Bernitt wrote:
Good day, I am interested in assisting with TextMate development. I really like the editor, and want to contribute to make it better! I want to help add newer and more modern actions to it similar to Sublime Text.
This sounds great :). Any particular ideas or features you're thinking of implementing?
I was wondering if you had any links for getting started? I’ve downloaded the source code and set up a dev environment and can compile it successfully. I’m reading through the source code and testing things; I was just wondering if you have any information on the Oak framework and the general layout of the application structure. Thank you for your help!
As far as I know there's no getting started documentation. This is what I've figured out so far hacking on the source code:
- The application is a Cocoa application which uses Objective-C++ for
the interface related code and C++ for the rest of the code
- The application is divided in a bunch of frameworks, the Frameworks
directory
- It doesn't use nib files like a traditional Cocoa application
- The OakTextView framework contains the document view, gutter, status
bar and the view for the actual source code. The OakTextView class is responsible for responding to keyboard input when editing the source code
- The rendering of the source code is not performed in OakTextView but
delegated to the "layout" framework. This framework uses Core Text to render the source code -- /Jacob Carlborg _______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 2016-04-10 14:25, Josh Bernitt wrote:
- Code comments should autocomplete. So if I use /** [tab]—> I would
get an auto completed /**
*/ and upon every return inside of a multiline comment, a new asterisk would prepend the new line so it would keep proper formatting and such. I want to apply that logic to all code comments.
This seems to be possible with a bundle action.
Perhaps a bundle would be better suited for this then. I had considered it, but then I also thought that having it natively handled might be a better for immediate functionality straight out of the box.
-- Josh Bernitt Sent with Airmail
On April 10, 2016 at 8:38:24 AM, Jacob Carlborg (doob@me.com) wrote:
On 2016-04-10 14:25, Josh Bernitt wrote:
- Code comments should autocomplete. So if I use /** [tab]—> I would
get an auto completed /**
*/ and upon every return inside of a multiline comment, a new asterisk would prepend the new line so it would keep proper formatting and such. I want to apply that logic to all code comments.
This seems to be possible with a bundle action.
-- /Jacob Carlborg
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 10 Apr 2016, at 14:25, Josh Bernitt jjbernitt@gmail.com wrote:
- Highlighted text in the editor will auto populate the Find field when searching, rather than having to type in the text to find. I’ve personally grown accustomed to that in all the other editors I use.
I do this via pressing ⌘E (the normal Mac behaviour) [Menu > Edit > Find > Use selection for Find].
-Hans
Is that in addition to hitting ⌘F? I can do ⌘E ⌘F and that uses my selection for Find. I was thinking of bypassing the manual choice entirely and always using the highlighted portion of text as the Find value. It’s how Sublime Text, Atom, and IntelliJ all work, but perhaps that’s not the best then? All those other editors are not native Mac apps, so maybe if I try to bypass the ⌘E, that will detract from the native experience and choice. I had not considered that at all. Thoughts?
-- Josh Bernitt Sent with Airmail
On April 10, 2016 at 8:44:36 AM, Hans-Jörg Bibiko (bibiko@shh.mpg.de) wrote:
On 10 Apr 2016, at 14:25, Josh Bernitt jjbernitt@gmail.com wrote:
- Highlighted text in the editor will auto populate the Find field when searching, rather than having to type in the text to find. I’ve personally grown accustomed to that in all the other editors I use.
I do this via pressing ⌘E (the normal Mac behaviour) [Menu > Edit > Find > Use selection for Find].
-Hans
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 10 Apr 2016, at 14:58, Josh Bernitt jjbernitt@gmail.com wrote:
Is that in addition to hitting ⌘F? I can do ⌘E ⌘F and that uses my selection for Find. I was thinking of bypassing the manual choice entirely and always using the highlighted portion of text as the Find value. It’s how Sublime Text, Atom, and IntelliJ all work, but perhaps that’s not the best then? All those other editors are not native Mac apps, so maybe if I try to bypass the ⌘E, that will detract from the native experience and choice. I had not considered that at all. Thoughts?
By myself I'm using ⌘E followed by ⌘G [find next]. But your workflow can be implemented by using a macro à la
( { command = 'copySelectionToFindPboard:'; }, { argument = { action = 'findNext'; wrapAround = :true; }; command = 'findWithOptions:'; }, )
bound to any key equivalent.
-H
On Sun, Apr 10, 2016 at 7:58 AM, Josh Bernitt jjbernitt@gmail.com wrote:
Is that in addition to hitting ⌘F? I can do ⌘E ⌘F and that uses my selection for Find. I was thinking of bypassing the manual choice entirely and always using the highlighted portion of text as the Find value. It’s how Sublime Text, Atom, and IntelliJ all work, but perhaps that’s not the best then? All those other editors are not native Mac apps, so maybe if I try to bypass the ⌘E, that will detract from the native experience and choice. I had not considered that at all. Thoughts?
I would prefer to keep it as is. This change would also be awkward with the "Find in Selection" feature which I find is quite useful.
Am 10.04.16 um 18:51 schrieb Curt Sellmer:
On Sun, Apr 10, 2016 at 7:58 AM, Josh Bernitt <jjbernitt@gmail.com mailto:jjbernitt@gmail.com> wrote:
Is that in addition to hitting ⌘F? I can do ⌘E ⌘F and that uses my selection for Find. I was thinking of bypassing the manual choice entirely and always using the highlighted portion of text as the Find value. It’s how Sublime Text, Atom, and IntelliJ all work, but perhaps that’s not the best then? All those other editors are not native Mac apps, so maybe if I try to bypass the ⌘E, that will detract from the native experience and choice. I had not considered that at all. Thoughts?I would prefer to keep it as is. This change would also be awkward with the "Find in Selection" feature which I find is quite useful.
+1 to keep the current behaviour (at least as an option).
One of things I do really often:
1) Select a string I want to replace and press ⌘E to make it the current search string. 2) Select a part of my document. 3) Press ⌘⌥F to do a “Find All” restricted to the current selection. 4) Start typing to replace each occurance at once (multiple carets are such a great feature, btw!)
(I omit step 1 if the thing I want to replace is already the current search string.)
Stefan
"Find and replace text" is where TM is already ahead of all the other code editors. I think there's no need to mess with it.
Maybe Allan has a todo list posted somewhere so anyone can pick a thing that is waiting to be implemented.
One thing that I'm really waiting for are the indent guides. Working with indent-based languages using spaces for indents is uncomfortable at the moment.
Ok, good call then on the text search abilities, and leaving them as is. Thanks for clarifying. @AllenOdgaard, thanks for the link. This is the first open source project I’ve gotten involved in, so I’m excited to help as much as I can. @IgorK, I agree that indent guides would be awesome. That’s definitely something I would love to see as well, and sounds like a good idea for me to research.
-- Josh Bernitt Sent with Airmail
On April 10, 2016 at 1:23:44 PM, Igor K (me@igorkozlov.me) wrote:
"Find and replace text" is where TM is already ahead of all the other code editors. I think there's no need to mess with it.
Maybe Allan has a todo list posted somewhere so anyone can pick a thing that is waiting to be implemented.
One thing that I'm really waiting for are the indent guides. Working with indent-based languages using spaces for indents is uncomfortable at the moment.
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 10 Apr 2016, at 8:58, Josh Bernitt wrote:
All those other editors are not native Mac apps, so maybe if I try to bypass the ⌘E, that will detract from the native experience and choice. I had not considered that at all. Thoughts?
Another thing I haven’t seen anyone bring up is that the search string is shared across all [correctly written] applications system-wide, so replacing it without some explicit user action (like ⌘E) seems too “destructive” to me.
On 10 Apr 2016, at 18:08, Jacob Carlborg wrote:
As far as I know there's no getting started documentation. This is what I've figured out so far hacking on the source code: […]
Also, there is this document (but it’s no “Getting Started”):
https://github.com/textmate/textmate/blob/master/INTERNALS.md
On 2016-04-09 15:22, Josh Bernitt wrote:
Good day,
I am interested in assisting with TextMate development. I really like the editor, and want to contribute to make it better! I want to help add newer and more modern actions to it similar to Sublime Text. I was wondering if you had any links for getting started? I’ve downloaded the source code and set up a dev environment and can compile it successfully. I’m reading through the source code and testing things; I was just wondering if you have any information on the Oak framework and the general layout of the application structure. Thank you for your help!
There's a minimap plugin for TextMate 1 [1]. I think it would be really nice if that was ported to TextMate 2 and contributed to be a proper part of TextMate and not a separate plugin.
[1] https://github.com/JulianEberius/Textmate-Minimap
Yes! I did see that as well, and you’re right, that would be really nice to be fully incorporated. I’ll take a look at that too. Thanks!
-- Josh Bernitt Sent with Airmail
On April 10, 2016 at 2:15:04 PM, Jacob Carlborg (doob@me.com) wrote:
On 2016-04-09 15:22, Josh Bernitt wrote:
Good day, I am interested in assisting with TextMate development. I really like the editor, and want to contribute to make it better! I want to help add newer and more modern actions to it similar to Sublime Text. I was wondering if you had any links for getting started? I’ve downloaded the source code and set up a dev environment and can compile it successfully. I’m reading through the source code and testing things; I was just wondering if you have any information on the Oak framework and the general layout of the application structure. Thank you for your help!
There's a minimap plugin for TextMate 1 [1]. I think it would be really nice if that was ported to TextMate 2 and contributed to be a proper part of TextMate and not a separate plugin.
[1] https://github.com/JulianEberius/Textmate-Minimap
-- /Jacob Carlborg
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-
Allan Odgaard -
Curt Sellmer -
Hans-Jörg Bibiko -
Igor K -
Jacob Carlborg -
Josh Bernitt -
Novitzky Peter -
Rob McBroom -
Stefan Daschek