Home Download Buy Blog Forum Support

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

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

Postby iamntz on Wed Apr 10, 2013 5:07 am

Code: Select all
4. What do you mean a dropdown for selecting other themes? What other themes? The editor simply gets pointed at the theme files via a file picker or command line. It isn't tied to sublime in anyway, so it doesn't know where to find themes without help. Do you mean the plugin side should scan sublime for theme files? Please elaborate.

this should also be visible somewhere in the editor. Right now, to edit multiple themes i had to:
1) switch theme
2) launch „edit current theme”

I guess it would be nicer to have a dropdown in the editor itself (don't forget to add a confirmation if the current theme is not saved! :D )
iamntz
 
Posts: 917
Joined: Fri Apr 29, 2011 8:52 am
Location: Romania

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

Postby facelessuser on Wed Apr 10, 2013 6:50 am

Keep in mind, the editor is designed to be a standalone app, and then I tap into it via a plugin.

My current plan is:
- make sure ESC is working properly in all platforms for closing dialogs.
- Probably adjust insert workflow, but again not critical on my list.
- Maybe add an "open theme" option in the menu to open a theme via the file picker
- Look into getting linux working
- Maybe add a menu in the sublime plugin to list available themes that can be picked to load in the editor

Conditional:
- If someone provides a list of common scopes, I will look into adding the ability to select them via a dropdown or something.

Maybe in the future:
- I may allow for the editor to be fed the path to a config file. In that config file, a user could specify folders to scan for theme files, and those theme files could appear in some kind of menu or dropdown list. This may happen sometime in the future, but not right now. I would have to add the ability for the editor to scan the folders, search sublime-plugin zip files, give logic to unpack from said zip files to a temp location. This isn't even including live edits that show in Sublime. To do that, I need to communicate back to the plugin to switch the theme for live updates (maybe to a settings file that is being watched, maybe sockets, maybe named pipes; I don't know). At this point, I view it as a nice to have. I want to avoid making the editor dependent on the sublime environment, but allow it to be an independent tool as it was designed to be.

The other thing to keep in mind is that right now I am ready to take a break from this tool, so more ambitious features are going to get stuffed in the wish list for the possible future.
facelessuser
 
Posts: 1576
Joined: Tue Apr 05, 2011 7:38 pm

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

Postby rgidney on Wed Apr 10, 2013 12:08 pm

Tried 0.0.6 this morning in OSX (10.7) and Win7x64. Everything worked really nice when called from within Sublime. When called as a standalone editing functionality did not change but when I tried to close the application it would not close. In both OSX and Win 7 I had to kill it because it would not respond to closing the window or Quitting the application.
rgidney
 
Posts: 26
Joined: Wed Feb 29, 2012 11:58 am

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

Postby facelessuser on Wed Apr 10, 2013 1:03 pm

@rgidney It should have created a log file. Can you post it?
facelessuser
 
Posts: 1576
Joined: Tue Apr 05, 2011 7:38 pm

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

Postby rgidney on Wed Apr 10, 2013 1:05 pm

Here you go:

Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
Traceback (most recent call last):
File "<string>", line 1488, in on_close
AttributeError: 'Editor' object has no attribute 'update_thread'
rgidney
 
Posts: 26
Joined: Wed Feb 29, 2012 11:58 am

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

Postby facelessuser on Wed Apr 10, 2013 1:17 pm

@rgidney, thanks, I know what the problem is. I will try and get a fix out later today.
facelessuser
 
Posts: 1576
Joined: Tue Apr 05, 2011 7:38 pm

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

Postby FaFiNoS on Wed Apr 10, 2013 8:58 pm

@facelessuser. 0.0.6 is great! It works very well. No problem at all on my Mac. I would like suggest to implement maybe in future version(s) more keyboard support. I.e. if cursor is in Font Style column key "i" make the font style Italic, "b" Bold, "u" Underline, press again to remove style (keys just for example). I think it will be more handy for user and less burdensome for mouse :). Also I would like possibility to use keyboard for copy/paste function for colours, styles, maybe scope from one selection to the other especially if we need to create duplicate selection with slightly different colour. These are some my ideas. Anyway thank you very much for this app. It saved me a lot of time. Good Job!
FaFiNoS
 
Posts: 6
Joined: Mon Apr 01, 2013 3:38 pm

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

Postby facelessuser on Wed Apr 10, 2013 9:13 pm

I like the keyboard ideas for fontstyle, and I like the idea of copying and pasting between like columns. Could maybe even create a "duplicate" command to duplicate a row (style settings only; global can't have rows with the same name). I like the keyboard idea enough I might look into some of this in the next couple of days. Maybe I can get it into the next release and hopefully it will finally be bug free...we shall see :).
facelessuser
 
Posts: 1576
Joined: Tue Apr 05, 2011 7:38 pm

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

Postby facelessuser on Thu Apr 11, 2013 5:12 am

0.0.7 is posted. You should up install both halves to get all of the features and fixes:

Binary:
-Fix live save thread issue when live save is disabled
-Add "Open" menu option to open a different theme from the editor when a theme is already loaded
-ESC now closes settings dialogs in windows
-disallow column selecting
-Small fix for font stye updating
-Shortcuts "B", "I", and "U" can be used on a style settings row to change the the font style


Plugin:
-Direct edit is now a global setting instead of a command setting
-Scan for themes to allow for opening and editing any installed theme (take into consideration of packages overriding other packages)
-Scan for themes to allow for simply setting any installed theme without opening the editor (take into consideration of packages overriding other packages)
-Update command palette commands

Hopefully the major bugs are fixed and I can focus on getting Linux going. I will probably add a couple more things after Linux is working...assuming I get Linux working :).
facelessuser
 
Posts: 1576
Joined: Tue Apr 05, 2011 7:38 pm

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

Postby quodlibet on Thu Apr 11, 2013 8:03 am

facelessuser wrote:3. I can understand the desire of having a list of commonly used scopes...who's going to compile this list :)? I am building the editor, if someone wants to do some legwork to compile a list of common scopes, I may add a way to import the list; probably as an external settings file.


A file with a big pile of scopes is simple to put together, but I can only half see how this would work. First off, what format would you like this in?

Also:

- Do you have any thoughts on how to handle the common pattern "X, punctuation.definition.X" (as in "comment, punctuation.definition.comment")? Do you want these listed as one or two scopes?

- Do you want generic scopes ("entity"), to be separated from syntax-specific ("entity.name.section.markdown ") or sublime-specific ("entity.name.filename.find-in-files")?

Or do you want a flat file with everything* in it?

* By everything I don't mean every scope for every syntax. That would be madness :)

Let me know what would make sense for you and I'll take a stab at it.

Cheers,
Alex
quodlibet
 
Posts: 554
Joined: Sat Jun 18, 2011 5:53 pm

PreviousNext

Return to Plugin Announcements

Who is online

Users browsing this forum: No registered users and 13 guests