ST3: Adding a "Working with ST3 list" ?

[mariozaizar]

I think we should provide a list of the current supported packages on ST3.
Maybe a wiki page? This is an small list that I made today.

Updated 07/02/2013

Not working:

• Advance New File
• Alignment
• Change Quotes
• Gist
• Git
• Github Tools
• Highlight Duplicates
• Markdown Preview
• Themr

Working:

• Case Convertion
• Loremipsum
• Rails Migration List
• RailsCasts Colour Scheme

With issues:

• Trailing spaces.
• Theme: Nexus

[zchrykng]

Here are the ones that I have run into so far.

Working:
Color Scheme - Phix
Theme - Nil

Not working:
SublimeCodeIntel
SublimeLinter

[charlesmudy]

WORKING:
CodeIgniter Snippets
ColorPicker

NOT WORKING:
AutoFileName
BracketHighlighter

[LeonB]

Working:
SASS
Theme - Soda

Not working:
emmet

[zchrykng]

@LeonB emmet has partial support. You have to pull the st3 branch of the plugin and be running Linux or OSX at the moment. Windows support should be in a few days.

[LeonB]

@zchrykng nice. I'm using Linux so that should work. Do you know if I install it via git package control will keep it up to date?

[zchrykng]

@LeonB I am not sure. I think package control will do that.

[Jreen]

@charlesmudy BracketHighlighter(pull the BHST3 branch)

[Jreen]

Working:
SublimeInsertDatetime
SublimeTmpl
ConvertToUTF8
google-search
BracketHighlighter(pull the BHST3 branch) has partial support
DocBlockr（has partial support，https://github.com/spadgos/sublime-jsdocs/pulls)
HexViewer(pull the ST3 branch)
HighlightWords
Tradsim

Not working:
KeymapManager
Tortoise
Github
Tag

[zchrykng]

Hi everyone. I have created a gist to track this. Please let me know what need to added, changed, or removed.

https://gist.github.com/zchrykng/4945704

[wbond]

I just enabled the Wiki, is someone cares to port the current list there.

[zchrykng]

@wbond I can do that, but it is not allowing me to open the wiki tab.

[wbond]

Maybe try now? I just visited he wiki page and it says something at the bottom about how I just created the initial version now.

[zchrykng]

@wbond Looks like it worked! Please let me know if you think the formatting should be different, I would be fine with 'curating' the list while it is useful. List

[wbond]

https://github.com/wbond/sublime_package_control/wiki/Sublime-Text-3-Compatible-Packages is now the definitive list. Please update it if you have changes.

[francodacosta]

@wbond I've updated a package and now it works with st2 and st3, the new website (https://sublime.wbond.net.) still says it is only compatible with st2. What can I do to change it ?

thanks

nuno

[wbond]

The crawler has been hitting a JSON bug in one of the package files that has been stopping it from picking up the new info for some of the packages.

[francodacosta]

@wbond is this solved? I see no updates on my packages

https://sublime.wbond.net/packages/PHP%20Getters%20and%20Setters

Maybe I'm doing something wrong, can you help me out ?

[FichteFoll]

Doesn't seem like it. Even though your file https://raw.github.com/francodacosta/sublime-php-getters-setters/master/packages.json shows two packages (for whatever reason) it seems to be cached in the channel.

FYI, do you know that you can have multiple releases per package? This was specifically designed to provide different versions of a package for different OSes or ST versions. Also, using the details key would make 4 of your keys obsolete.

[francodacosta]

@FichteFoll this was my attempt to provide st2 and st3 versions of the same package

I have an hard time finding documention on this, I only found the example .json.

What would be the best way to have st2 and st3 versions of the same package ?

thanks

Nuno

[FichteFoll]

A combination of the two examples here.

There should also be some real world examples in the main repository already: https://github.com/wbond/package_control_channel/

[FichteFoll]

Okay, here's an update: Your repository is invalid.

It lacks date, which must be provided when using explicit versioning and instead provides last_modified which is unused.

Thank you, my tests ❤️.

[FichteFoll]

Ah no, this doesn't work either. Please take a close look at the example repositories file I linked above (the whole thing).

You either provide details OR version, url and date for a release. This is because Package Control knows how to fetch the latter 3 from github if you provide the tags page or a branch url as details.

And the date key does not belong to the package but to a release.

Since it kinda hard to explain everything, here is what it should look like: http://hastebin.com/gaqafoceki.json.

[francodacosta]

Thanks!!

I hope it works now!

cheers

Nuno

On 06/09/2013 15:43, FichteFoll wrote:

Ah no, this doesn't work either. Please take a close look at the
example repositories file I linked above (the whole thing).

You either provide |details| OR |version|, |url| and |date| for a
release. This is because Package Control knows how to fetch the latter
3 from github if you provide the tags page or a branch url as |details|.

And the |date| key does not belong to the package but to a release.

Since it kinda hard to explain everything, here is what it should look
like: http://hastebin.com/gaqafoceki.json.

—
Reply to this email directly or view it on GitHub
#330 (comment).

[francodacosta]

@FichteFoll thanks for your help, it is working now