Things I am thankful for: my mom’s mincemeat pie, and that she still makes it to share with us on Thanksgiving and Christmas. Playing dominos with my parents on Thanksgiving Day, and that my daughter loves to play, too. Sleeping late the day after Thanksgiving.
Yesterday, I learned a new word: weltschmerz, loosely defined by Patrick Rothfuss as that feeling of despair one feels when the world as it exists is not the world as one wishes it to be.
Now I have a name for it, that feeling…
It’s something I have been feeling (and thinking about) for the past couple years, and more recently, thinking about in conjunction with feeling incredibly grateful for how richly I am actually blessed. It’s an odd combination (contradiction?) of feelings.
Today, more than most days, I try to focus on that gratitude.
It’s been a bit since I’ve said anything here about Komodo-CFML, and thought a quick update would be appropriate.
As of last weekend, I finally was able to get a version of Komodo-CFML to work successfully on the version 9 alpha builds of Komodo IDE ActiveState has made available beginning earlier this year. I had hoped this not be a big deal, but it ended up taking quite a bit more time and effort than I had hoped. In the end, I resorted to rebuilding the plumbing for the language extension from the ground up in order to get it to work. So, that’s done (and I am currently using v9 with Komodo-CFML as my primary CFML editor on a daily basis).
With that hurdle out of the way, my intent is to get back to implementing tag/attribute support for both Adobe ColdFusion 11 and Railo 4.2. I’m also including a handful of useful (to me, anyway) macros with the language extension. I’ve made a small handful of minor tweaks to the language syntax highlighting, most of which are in the handling of CFSCRIPT syntax as I use it more and more rather than tag-based coding.
I’m hoping to have a version 0.2.4 with all of this available by the late November timeframe, shooting for something around Thanksgiving. If you are using Komodo-CFML and want to use it with the early versions of Komodo IDE v9, let me know in the comments below and I will send you my current working version with v9 support.
I upgraded my MBP (a 15-inch, early 2011 model) to OS X Yosemite on Friday morning, and at this point I am closed to being finished with getting software installed, etc. I typically move between versions of OS X with a clean install and then re-install software and restore files (as needed). It’s not necessarily an approach that would work well for everyone, but it works for me and helps ensure I have a reasonable clean system.
My first thoughts, in no particular order:
- Helvetica Neue as the primary UI font is going to take some getting used to. My MBP is a couple years old, and is not a Retina device; that has a big impact on how it renders. I particularly notice the difference in the menu bar and in context menus. It simply does not render as clearly and legibly as the font OS X has historically used there.
- The flat UI will also take some getting used to, but I think I like it, in general, for window decorations, UI controls, icons, etc.
- I am not crazy about the shift to brighter colors for UI elements and icons. I would characterize many of them as close to garish. I tend to like understated UIs (the theme of my blog will attest to that) and while the flat aspects of the UI head in that direction, the colors most certainly do not. The blue used for UI elements, folder icons, etc., is particularly bad in this regard. The second UI tweak I made was the shift to graphite for basic UI appearance (which unfortunately does nothing for the blue folder icons); the first was to shift the dock to the right side of the display and to have it auto-hide to slide the mass of bright colors out of sight. I hardly ever use the dock (thank you, apps like QuickSilver and Alfred!), so this is something I would do anyway, but I don’t miss the explosion of bright colors from the dock.
- Transparency and effects: I haven’t decided about these, but in general they feel like a bit much to me. What benefit, for example, is there to having the blue of several selected files in a Finder pane bleed through the context menu when I right-click on them? There are places where I like a bit of window transparency but some of the transparency implemented here feels gratuitous.
My overall general impression: a mixed bag. This is the first OS X version I’ve installed (going back to when I started with OS X Leopard) where I have not had an overwhelmingly positive reaction to the UI evolution.
I’ll follow up a bit after I’ve been on Yosemite for a couple weeks with additional impressions. I’m curious to see how/if these impressions evolve with the passage to time and usage. The other aspect of this is that the system I updated is my own laptop; I have two other MBP’s I use for work and I don’t have any near-term plans to update them… I will be switching between 10.10 and 10.9 on a daily basis, which will likely bring the differences into sharp contrast.
I’ve been working intermittently on a small set of color schemes for ActiveState Komodo based on Chris Kempson’s Base16 color palette. These have reached a point where I feel OK sharing them for others to use, if interested:
I should point out that these are not “pure” Base16 schemes as there are individual settings in each theme which do not hold completely to the Base16 palettes. In most cases, these are settings where I have tuned particular settings for different contrast (e.g., comments, in at least one of them) based on my own preferences. I should also note that, based on my own tuning, I have not looked closely at setting up templates to create these with Mr. Kempson’s related Base16-Builder project but I plan to go down that road in the near future to see if that is workable.
It’s probably also worth pointing out that, for the most part, any language-specific color settings in these schemes are focused primarily on the languages I use (mostly Web-related stuff) so if I’ve missed your languages or your languages don’t seem to follow the Base16 palette, you may want to do some tweaking yourself. I’m also willing to factor those types of changes back into these as they evolve, hopefully both toward use of the Base16-Builder but also so they can be shared via Komodo’s Resources.
Edit 2014-05-14: These schemes specify Adobe’s Source Code Pro for use as the monospaced font. If you don’t have this font installed, you’ll almost certainly want to switch to your font of choice as your first tweak.