Nice extension. The end result looks like crap on OS X because the default theme uses background images, and you get borders + background colors + background images + text color, which is a bit too much. I tried a few things but in the end the only decent solution I found was to just change the text color: dark blue for HTML, dark green for CSS, dark red for JS.
Of course one solution would be to get rid of the background images and create your own style. What I'd like to do instead: use border-radius, box-shadow and possibly text-shadow to get a nice, integrated, pure-CSS effect. This will have to wait for Komodo to use the next Gecko engine (in Komodo 6, I guess). :(
Oh, a few comments on the preferences UI:
- i wish extensions preferences would go in Preferences > Extensions > ExtensionName, rather than directly Preferences > ExtensionName;
- the set of buttons should contain an "edit" button as well, double-clicking an entry should be a shortcut, not the one way to do it;
- the set of buttons should be focusable using the keyboard (Tab key);
- maybe it's just on OS X, but you with the default colors you can't see when an item in the list has focus, because focus changes the item's background color to default color for selections, and the displayed styles override that... maybe the preview should only take a part of each item?
> The end result looks like crap on OS X
I have no Apple where to test, I hope a day (a far day) to buy a Mac with donations received for my extensions :D :D :D
> you get borders + background colors + background images + text color
Backgrounds images aren't mandatory, about borders I'm considering to make them optional from UI, do you agree?
> I tried a few things but in the end the only decent solution I found was to just change the text color: dark blue for HTML, dark green for CSS, dark red for JS.
May you post some screenshot? Please file a feature request on my ColorTab project
> Of course one solution would be to get rid of the background images and create your own style.
> ...
> This will have to wait for Komodo to use the next Gecko engine (in Komodo 6, I guess
Have you tried the styles posted by Nathan?
They use background images and -moz-border-radius
> i wish extensions preferences would go in Preferences > Extensions > ExtensionName, rather than directly Preferences > ExtensionName;
I don't like this layout but I want to be a good citizen so if it is a best practice I can use it, my other estensions MoreKomodo, TabSwitcher, ToolbarArranger and Klint must be changed, too.
> the set of buttons should contain an "edit" button as well, double-clicking an entry should be a shortcut, not the one way to do it;
You are right, next version will have the fix
> the set of buttons should be focusable using the keyboard (Tab key);
maybe a OSX issue, under WinXP and Linux Ubuntu I can focus and move using tab
> maybe it's just on OS X, but you with the default colors you can't see when an item in the list has focus
this problem is present on all platforms :(
> maybe the preview should only take a part of each item
Maybe a dedicated area with the preview, the list should contain only the patterns without colors, when use click on items the preview updates itself, do you agree?
Here's my feedback as per previous topic. Take this with a grain of salt as it's just my opinion and I'm sure many of you might disagree:
Replace the current JavaScript observers in the engine with a CSS file using CSS3 selectors
The ideal file format for saving the settings would be that very CSS file mentioned above
Give the User the option to freely edit the CSS (i.e. advanced mode)
Upon updating the settings, remove the CSS file from the DOM and add it again (append a timestamp to force a reload). This should update the UI immediately.
So what I have in mind in a parser that reads a CSS file, figures out what the User has specified for background-color, border, etc. Presents a nice Settings dialogue (what you have in there at the moment is fine). Upon Saving any changes the properties that were not supported (i.e. if I had a padding-left: 10px in there) are also persisted, but anything I've updated in the UI is reflected on the CSS file.
You existing engine works very well, don't get me wrong -- it's just that I think using 20KB of JS to get the job done could be avoided and replaced with a single CSS file (no hooks, observers, etc.)
I agree with your for 99%, I'm lazy, very lazy and I simply prefer a comfortable UI instead of editing directly files.
I've already a new interface for ColorTab (not yet released), based on scintilla you can modify the styles using syntax highlighted CSS code (this is the advanced mode).
I can add a "Standard" UI from with user can choose only a few attributes (background color, text color and image)
I don't know how many users prefer ColorTab to userChrome.css editing so actually I'm adding features useful only for me but any idea, criticism or hint is welcomed, we are a community at all (I hope)!
I like the UI as well, I think it gives user with no CSS or programming experience the right tools to customise Komodo's UI. However I was concerned about the engine (which is about 20KB of JavaScript). I think it would be much more appropriate if your settings dialogue generated a CSS file which is applied to the chrome, rather than listening for events (view_created, etc.) I noticed you save the settings in a JSON format, so it shouldn't be a big hassle to generate a CSS out of this. I hope this clarifies my feedback a bit.
And yes, deffo we are a community, though at time I feel alone :D
I've realized ColorTab is only a non-sense extension.
The better approach is yours or simply use Stylish under Komodo.
The only very very little advantage over CSS selectors is the glob routine, using ColorTab you can define patterns like /opt/project/*/css/* (notice two wildchars), AFAIK selectors allow only "begins with", "ends with" and "contains".
I use similar patterns for my projects but I think only a couple of users can find useful this feature.
No, no, no -- my opinion is not the ultimate one Lol. I reckon there are at least five more ways in which this extension could be implemented and neither one of these is, well, the best one. In my view a Stylish approach is good enough. But it has so many flaws and it's limited to the file name.
Your approach allows not only to look at the file name, but also to match directories (very useful when all files end with .php, but you want the distinction of M-V-C), to match the language set in Komodo and lots more. And let's not forget the cool UI which allows you to set all this up.
So don't drop it yet. Keep it current and help Users who run into problems.
This extension allows to color view tab based on pattern defined by user
Installed and configured in under 2 minutes.. awesome job dafi! :)
This is a great extension - I'd love to use it, but do not want to upgrade to IDE 5.0 only because of it.
Technically speaking it is easy to add backward compatibility but I'm not sure to add it.
I admit my Komodo IDE 4.4 at office now is so sadly without color tabs...
--
dafi
Enhance KomodoEdit with MoreKomodo
Great extension!
A feature that I would like is to be able to re-arrange the list, so that the first matching pattern is used.
I forgot to publish the patch containing the up/down button.
I've had the same need :D
Install the version 1.0.1
--
dafi
Enhance KomodoEdit with MoreKomodo
Nice extension. The end result looks like crap on OS X because the default theme uses background images, and you get borders + background colors + background images + text color, which is a bit too much. I tried a few things but in the end the only decent solution I found was to just change the text color: dark blue for HTML, dark green for CSS, dark red for JS.
Of course one solution would be to get rid of the background images and create your own style. What I'd like to do instead: use border-radius, box-shadow and possibly text-shadow to get a nice, integrated, pure-CSS effect. This will have to wait for Komodo to use the next Gecko engine (in Komodo 6, I guess). :(
Oh, a few comments on the preferences UI:
- i wish extensions preferences would go in Preferences > Extensions > ExtensionName, rather than directly Preferences > ExtensionName;
- the set of buttons should contain an "edit" button as well, double-clicking an entry should be a shortcut, not the one way to do it;
- the set of buttons should be focusable using the keyboard (Tab key);
- maybe it's just on OS X, but you with the default colors you can't see when an item in the list has focus, because focus changes the item's background color to default color for selections, and the displayed styles override that... maybe the preview should only take a part of each item?
> The end result looks like crap on OS X
I have no Apple where to test, I hope a day (a far day) to buy a Mac with donations received for my extensions :D :D :D
> you get borders + background colors + background images + text color
Backgrounds images aren't mandatory, about borders I'm considering to make them optional from UI, do you agree?
> I tried a few things but in the end the only decent solution I found was to just change the text color: dark blue for HTML, dark green for CSS, dark red for JS.
May you post some screenshot? Please file a feature request on my ColorTab project
> Of course one solution would be to get rid of the background images and create your own style.
> ...
> This will have to wait for Komodo to use the next Gecko engine (in Komodo 6, I guess
Have you tried the styles posted by Nathan?
They use background images and -moz-border-radius
color: rgb(0, 0, 0); background-color: rgb(246, 250, 125); border: 1px solid #000 !important; -moz-border-radius-topleft: 5px; -moz-border-radius-topright: 5px; background-image: url(http://naatan.com/kbg.png);
> i wish extensions preferences would go in Preferences > Extensions > ExtensionName, rather than directly Preferences > ExtensionName;
I don't like this layout but I want to be a good citizen so if it is a best practice I can use it, my other estensions MoreKomodo, TabSwitcher, ToolbarArranger and Klint must be changed, too.
> the set of buttons should contain an "edit" button as well, double-clicking an entry should be a shortcut, not the one way to do it;
You are right, next version will have the fix
> the set of buttons should be focusable using the keyboard (Tab key);
maybe a OSX issue, under WinXP and Linux Ubuntu I can focus and move using tab
> maybe it's just on OS X, but you with the default colors you can't see when an item in the list has focus
this problem is present on all platforms :(
> maybe the preview should only take a part of each item
Maybe a dedicated area with the preview, the list should contain only the patterns without colors, when use click on items the preview updates itself, do you agree?
--
dafi
Enhance KomodoEdit with MoreKomodo
It would be great if I can set the pattern on a directory
example */content/* ?
Dave
Very strange, this behavior already works.
I've my linux box configured with
*/colortab/*
*/viewsourcewith/*
and Windows (with \ separator)
*\colortab\*
*\viewsourcewith\*
What OS are you using?
--
dafi
Enhance KomodoEdit with MoreKomodo
omg - strike! :)
I tried locally /content* and i wrote here */content/* and this was correct :)
great!
Dave
I've created a survey (with limesurvey) with a single question about the new UI.
May you help me to decide which to use?
You can add also a comment if you want
http://apps.sourceforge.net/limesurvey/dafizilla/index.php?sid=62919&lan...
--
dafi
Enhance KomodoEdit with MoreKomodo
This extension rocks!!!
Now that I have tried it, I simply cannot imagine to use Komodo without it again. Very nice!!
Patrick Metz
The version 1.0.2 contains the new UI based on user choice.
Thanks to vote the survey
--
dafi
Enhance KomodoEdit with MoreKomodo
Very very good extension. Thanks a lot for your effort!
Dafi,
Have a look over to this topic: http://community.activestate.com/faq/customizing-the-komodo-ui#comment-1...
I reckon it might be of interest.
Cheers,
Stan
Hi again,
Here's my feedback as per previous topic. Take this with a grain of salt as it's just my opinion and I'm sure many of you might disagree:
So what I have in mind in a parser that reads a CSS file, figures out what the User has specified for background-color, border, etc. Presents a nice Settings dialogue (what you have in there at the moment is fine). Upon Saving any changes the properties that were not supported (i.e. if I had a padding-left: 10px in there) are also persisted, but anything I've updated in the UI is reflected on the CSS file.
You existing engine works very well, don't get me wrong -- it's just that I think using 20KB of JS to get the job done could be avoided and replaced with a single CSS file (no hooks, observers, etc.)
Cheers,
Stan
Thanks Stan,
I agree with your for 99%, I'm lazy, very lazy and I simply prefer a comfortable UI instead of editing directly files.
I've already a new interface for ColorTab (not yet released), based on scintilla you can modify the styles using syntax highlighted CSS code (this is the advanced mode).
I can add a "Standard" UI from with user can choose only a few attributes (background color, text color and image)
I don't know how many users prefer ColorTab to userChrome.css editing so actually I'm adding features useful only for me but any idea, criticism or hint is welcomed, we are a community at all (I hope)!
thanks again for your important feedback
friendly,
davide
--
dafi
Enhance KomodoEdit with MoreKomodo
Hi Davide,
I like the UI as well, I think it gives user with no CSS or programming experience the right tools to customise Komodo's UI. However I was concerned about the engine (which is about 20KB of JavaScript). I think it would be much more appropriate if your settings dialogue generated a CSS file which is applied to the chrome, rather than listening for events (view_created, etc.) I noticed you save the settings in a JSON format, so it shouldn't be a big hassle to generate a CSS out of this. I hope this clarifies my feedback a bit.
And yes, deffo we are a community, though at time I feel alone :D
Cheers,
Stan
I've realized ColorTab is only a non-sense extension.
The better approach is yours or simply use Stylish under Komodo.
The only very very little advantage over CSS selectors is the glob routine, using ColorTab you can define patterns like /opt/project/*/css/* (notice two wildchars), AFAIK selectors allow only "begins with", "ends with" and "contains".
I use similar patterns for my projects but I think only a couple of users can find useful this feature.
I think to no longer support ColorTab.
thanks to open my eyes
friendly,
davide
--
dafi
Enhance KomodoEdit with MoreKomodo
Hey,
No, no, no -- my opinion is not the ultimate one Lol. I reckon there are at least five more ways in which this extension could be implemented and neither one of these is, well, the best one. In my view a Stylish approach is good enough. But it has so many flaws and it's limited to the file name.
Your approach allows not only to look at the file name, but also to match directories (very useful when all files end with .php, but you want the distinction of M-V-C), to match the language set in Komodo and lots more. And let's not forget the cool UI which allows you to set all this up.
So don't drop it yet. Keep it current and help Users who run into problems.
Cheers,
Stan