Sublime Forum

(osx|windows|linux) Color Scheme Editor (BETA)

#8

Can you give me some more info? How are you launching the program? If you click the program and try to run the program outside of Sublime Text, does it do anything differently?

0 Likes

#9

I am trying to launch app inside ST and from outside ST. Inside ST from Command Palette “Edit Color…”. There is no questions, messages, etc. icon appearing and disappearing in the dock. That’s all. Outside ST from Finder or Path Finder. App asking me for theme file. If I chose it icon in the dock disappearing and thats all. Nothing happen more.

0 Likes

#10

It sounds like when run outside of ST3, the program runs, but fails for some reason. Can you post the theme file you are trying to load when it asks you to select it? Maybe I am not handeling something proper…I need to add some kind of debugging to the app.

Also, what is the file path to the file? Maybe I am not handling some non-ascii path stuff?

When run from Sublime, do you see any errors in the console window in Sublime?

0 Likes

#11

Hi. I did some tests. I have downloaded “Monokai Blue.tmTheme” from your git and your app works fine!!! Personally I’m using customised “Solarized (Dark).tmTheme” but I see even original one is crashing app. It must be something with handling xml.

0 Likes

#12

Great! I just need to make the scheme parsing a bit more robust. I have a version 0.0.2 coming hopefully by the end of the day, I will try to resolve this issue in that.

0 Likes

#13

Solaris had some essentially empty items (no scope, colors, or font styles). The editor wasn’t prepared for the scope not being there. You can see “PHP: Class Function” has no members, but you can also see I got it working.


This will work in 0.0.2 which should drop tonight. In the future I will add a lot more checks and make sure to exit out clean if the plist is malformed.

0 Likes

#14

Great! I mean you have found where problem is :smile: I look forward for 0.0.2. Thanks!

0 Likes

#15

0.0.2 for OSX only (found some other stuff that needed work and didn’t have time to update windows)

-All events now update the theme file proper
-Fix color picker related issues
-Allow removal of a background or foreground color
-Fix issue where missing scope would cause the editor to fail
-Fix app title
-logging added
-debug mode added
-included settings file
-some internal changes

Replace all your files with the new 0.0.2

If you have the editor crash, there should be a subclrschm log file in you user folder.

I will update windows tomorrow.

0 Likes

#16

Thank you very much for this tool!! It works perfectly now!

0 Likes

#17

This is awesome! Thanks for building this.

0 Likes

#18

@n00ge @FaFiNoS, glad you like it. I had this floating in my head for a while.

0 Likes

#19

Windows version 0.0.2 is now available.

Linux is still coming along, mainly, I am trying to get my linux setup using wxgtk2.9…linux…sigh. Either that, or I need to make the editor work also with wxgtk2.8. The good news is that it half works…the bad news is that it half doesn’t. Once I get this working on Ubuntu, I have no idea if it will work on the latest Ubuntu. Oh linux…you frustrate me so. And I used linux exclusively for like 5 years; I just finally got tired of having to compile all my crap when it just wasn’t there, or to fix some new issue or driver on a simple update…it wears on you after a while. Don’t even know if the 32bit version can run on the 64bit version of linux either…

Anyways, I believe the Color Scheme Editor is 100% functional now, and relatively bug free…but report them if you find them (include the log). I do have some additional features I want to add when I have time, but for now, just let me know what you think and let me know if find issues.

0 Likes

#20

Ideas for future enhancements:

  • Run as standalone program and prompt for color-scheme file

  • Run as a package from non-User directory

This is an excellent complement to ST. Well done.
Have some confidence; skip the 0.0.x versions and jump to 1.0.0!

0 Likes

#21

@grant, it should already do the first, try it.

As for the second, I plan on it. It is pretty easy to do, I am just in development mode and will make it a package as soon as it is stable.

0 Likes

#22

Great minds think alike (and I should also try things before opening my big mouth).

0 Likes

#23

Moving forward, I plan on making it more robust. When just opened normal, I plan on asking if the user wants to open a theme file, or create a new one. I want to change the open file dialog to accept “tmTheme.JSON” files as well (it already supports them via the -j command line option; probably just change it to look at the extension instead of requiring the user to specify open mode). Maybe add a search option. Maybe add a way to “save as”.

From a plugin standpoint, I plan on allowing you to open a theme via the open dialog (it will still be direct edit, which is why a “save as” option would be nice), and possibly create a new theme also from sublime.

…oh and try and get linux running :frowning:.

Probably need an icon for the editor…

Haven’t decided how to distribute it yet. I know the Mac binary is 30MB and the windows is only 10MB, not sure about linux yet. Because I may not want to require a user to update 40+MB every time the plugin updates, I may provide the plugin without binaries, and you install or download the editor somewhere and point the plugin at it. The plugin could check the version to tell if you need to update it (after initial development is done, I hope not to be updating it a bunch).

Chime in if you have any ideas.

0 Likes

#24

Let me know if I can help with testing. I have one of each running Ubuntu 12.04. Sublime 3 only, I’m afraid.

I’m just about fed up with linux, as well – at least, that’s what I say under my breath in between cursing when I can’t get things to work. But it only takes me a few minutes on another OS before I have to ask: “What do you mean I can’t change this?” But then, customization is a sign of immaturity, I’m almost certain. Sigh.

Alex

Edit: slightly less crappy sentence.

0 Likes

#25

0.0.3 for OSX and Windows is now available.

Please read opening page for more details and for links as things have changed. Delete color_scheme_editor.py from you user folder. Install plugin from github, and then select your platform and download the binary to your user folder (if you wish to put it elsewhere, that can be configured in the plugin).

Changes:
Plugin
-Can now create a new theme via the command palette
-Can access the filepicker for the editor via the command palette
-Interlock check for version between plugin and binary

Binary
-Fix a bug were the tables weren’t getting updated when the global background and foreground settings got changed
-If launched standalone, asks if you want to open an existing theme or create a new one
-If given a .tmtheme file or json file, the editor will now take appropriate action on its own.

Note:
OSX seems to hate the wildcards for the filepicker. The wildcards work fine in windows, but weird in OSX…I will have to resolve that at a later date.

0 Likes

#26

I should have OSX wildcard stuff in filepicker dialogs sorted out in next update. Turns out “.JSON" works, but ".tmTheme.JSON” does not. It seems to only respect the very end. This is fine though, in OSX I will simply let the user pick a JSON, and if it is not a “*.tmTheme.JSON” I will make them pick again until they get it right :smile:.

0 Likes

#27

I’d love to have a way to load undefined scopes into the theme editor when editing a theme for a particular language. Sometimes I hop into a different language and see elements that would nice to have some different highlighting. This would be a great way to get into that. Feel free to mark this down as a feature request for down the line if it’s a pain in the ass.

Or… if there’s a way to place your cursor somewhere, get the scope and either jump to that scope in your current color scheme or add it if it doesn’t exist might be better.

0 Likes