Join forces? about decent-swift-syntax HOT 19 OPEN

Haha glad you dig the name - I was frustrated with the other swift packages at the time.

I found another one recently that is an improvement, best yet I think. Search for "Swift tmLanguage".

I'd definitely like to work on something cooperatively, but I'd like to take a stab at using the new sublime-syntax syntax. I'm not very proficient at the tmLanguage format. What do you use to convert it from YAML?

I'm struggling to find much time for open source projects these days, but I'm going to check out SourceKitten, I've never heard of it! I'll try to chip in where I can. 😄

On Apr 12, 2015, at 5:42 PM, bryn austin bellomy [email protected] wrote:

Before anything, the tone of this repo is hilarious and reminds me of some similarly aggressive READMEs I've written

I've been working on a similar revamp of the Swift syntax that quiqueg put out a while back. It's a complete rewrite at this point, and I sort of used the C# syntax as a jumping-off point (and took an occasional look at the Java syntax for inspiration as well).

I've been checking out your syntax and I was wondering if you might want to take a look at the one I've been working on and maybe merge our efforts.

More generally, I'm sort of aiming at making a suite of Sublime plugins for Swift so that I can eventually avoid Xcode altogether. If you have any interest in getting something like that going, let me know. I have a working (but unpublished) plugin that replaces the built-in Sublime Goto functionality (it matches a few regexes against the source file and then opens a navigation popup similar to the Goto popup). I'm also starting to work on new approach that leverages jpsim/SourceKitten to tap into information from SourceKitService. If SourceKitten pans out, it could be the basis of a full IDE in Sublime (in the style of the incredible Phaiax/ArcticTypescript plugin).

Anyway, here's the YAML-.tmLanguage file: https://github.com/brynbellomy/SublimeSwiftIDE/blob/master/New%20Swift.YAML-tmLanguage

... and the .tmLanguage file: https://github.com/brynbellomy/SublimeSwiftIDE/blob/master/New%20Swift.tmLanguage

Thanks!

—
Reply to this email directly or view it on GitHub.

from decent-swift-syntax.

Hey dude, I got a bunch of work done on the conversion to .sublime-syntax! https://github.com/colinta/Swift-for-f-ing-sublime/tree/sublime-syntax

from decent-swift-syntax.

Nice! I haven't dug into that new file format yet; it's basically just a YAML-ized version of the original tmLanguage format, right? If so, we'd have a much easier time merging some of the declarations from our two syntax files.

For YAML conversion I've been using the "convert yaml/json/plist" functionality in AAAPackageDev.

I'll give this a spin today.

from decent-swift-syntax.

It’s actually a new syntax, which makes it (for bettor or worse) incompatible with the tried-and-not-so-great tmLanguage format. I find it to be much easier; this syntax file is barely over 200 lines.

On Apr 14, 2015, at 1:13 PM, bryn austin bellomy [email protected] wrote:

Nice! I haven't dug into that new file format yet; it's basically just a YAML-ized version of the original tmLanguage format, right? If so, we'd have a much easier time merging some of the declarations from our two syntax files.

For YAML conversion I've been using the "convert yaml/json/plist" functionality in AAAPackageDev.

I'll give this a spin today.

—
Reply to this email directly or view it on GitHub https://github.com/colinta/Swift-for-f-ing-sublime/issues/1#issuecomment-93024320.

from decent-swift-syntax.

Hey, @colinta, just a note that I couldn't get AAAPackageDev conversion to work in the latest HEAD. Getting:

Input type not specified, auto-detecting...
Unable to detect file type.

despite all my attempts. (And I even got the YAML to parse using yaml2json, which required removal of you #######...###### separators. But that didn't help AAAPackageDev detect it.)

from decent-swift-syntax.

Does AAAPackageDev already support the new 'sublime-syntax' file format?

On Apr 21, 2015, at 5:54 AM, Andrey Tarantsov [email protected] wrote:

Hey, @colinta, just a note that I couldn't get AAAPackageDev conversion to work in the latest HEAD. Getting:

Input type not specified, auto-detecting...
Unable to detect file type.
despite all my attempts. (And I even got the YAML to parse using yaml2json, which required removal of you #######...###### separators. But that didn't help AAAPackageDev detect it.)

―
Reply to this email directly or view it on GitHub.

from decent-swift-syntax.

@colinta I assumed that AAAPackageDev has invented .sublime-syntax. No? I've only installed it today for the specific purpose of trying to compile your syntax file. Ended up using @brynbellomy's precompiled file for now.

Btw, FYI, when your plugin is installed via Package Control, it does not come with a compiled file and thus doesn't work. I spent a lot of time troubleshooting before I figured out that .sublime-syntax is not a natively supported format. :-)

from decent-swift-syntax.

Are you using ST2? This is a ST3 feature. I can create an st2 branch to
support the old .tmLanguage format.

On Tue, Apr 21, 2015 at 8:58 AM, Andrey Tarantsov [email protected]
wrote:

@colinta https://github.com/colinta I assumed that AAAPackageDev has
invented .sublime-syntax. No? I've only installed it today for the
specific purpose of trying to compile your syntax file. Ended up using
@brynbellomy https://github.com/brynbellomy's precompiled file for now.

Btw, FYI, when your plugin is installed via Package Control, it does not
come with a compiled file and thus doesn't work. I spent a lot of time
troubleshooting before I figured out that .sublime-syntax is not a
natively supported format. :-)

—
Reply to this email directly or view it on GitHub
https://github.com/colinta/Swift-for-f-ing-sublime/issues/1#issuecomment-94830693
.

from decent-swift-syntax.

@colinta No, I've long switched to ST3. Are you saying that it is a native feature?

from decent-swift-syntax.

Hmm, weird that it doesn't work, then. Yes, native feature, one of the most recent builds included it. https://www.sublimetext.com/docs/3/syntax.html

from decent-swift-syntax.

@andreyvit if you still have trouble, please open a new issue. We kind of hijacked the conversation about new Swift packages! 😃

from decent-swift-syntax.

@colinta Yes, I'm sorry about that. I made a lot of wrong assumptions and thought I was continuing an ongoing discussion about converting to sublime-syntax.

On the topic of this issue, I'm very interested in what you guys can do, and would love to help occasionally (I used to make IDEs for a living). I've looked at SourceKitten, but it seems to re-parse the files on every invocation, which is not a very good foundation for code completion. :-)

from decent-swift-syntax.

Hi guys, is this package supposed to be better than the more popular https://packagecontrol.io/packages/Swift ?

In which ways?

Thanks!

from decent-swift-syntax.

from decent-swift-syntax.

I'm just starting to learn Swift, I wouldn't know. Just using it for a small project. Would be happy to compare it it was a language I use consistently.

from decent-swift-syntax.

from decent-swift-syntax.

It was not clear which one came first because package control only shows the number of installs in the search results. It would be a good improvment.

Which other packages would recommend from that list? SwiftKitten and the linter?

from decent-swift-syntax.

from decent-swift-syntax.

Thanks colinta, sorry for abusing this thread. Anything else to enhance to improve the experience with / without xcode?
@andreyvit what about you, any experience on this?

from decent-swift-syntax.