The Future of Thesis OpenHook

I final­ly upgrad­ed King­domGeek to The­sis 1.6 — I’m rather late to the game, which might sur­prise some of you.

Truth is, I’m no longer much involved with The­sis at all, for a vari­ety of rea­sons which I don’t real­ly care to go into at this point. How­ev­er, I still have the Open­Hook plu­g­in, which I’m not about to aban­don. I have some ideas to improve Open­Hook, but if I’m going to push for­ward with it, I need to do so using the lat­est The­sis code­base. (Inci­den­tal­ly, the lat­est code­base total­ly nerfed the cus­tom styling I was using… so we’re back to default for the time being. I real­ly dis­like that I now have to over­ride col­ors. I dove into The­sis because it was min­i­mal­is­tic and easy to style; now I have to do half my work in a cus­tom style sheet and half of it in the lay­out pan­el… Sim­pli­fy, sim­pli­fy, simplify.)

I upgrad­ed King­domGeek because, against all com­mon sense, I pre­fer to do my devel­op­ment here. I do this for two rea­sons: King­domGeek isn’t my pri­ma­ry source of income, so down­time does­n’t kill me. Also, you users are far more like­ly to catch cer­tain gaffes that I may take months to find, if I ever do. In oth­er words, many eyes are bet­ter than two. Oh, and yes, I real­ize my nav menu looks ter­ri­ble. You can still click it, though; go ahead, don’t be afraid… You’re mak­ing it self-con­scious now.

The next ver­sion of Open­Hook, I hope, will great­ly improve user expe­ri­ence and effi­cien­cy. I plan to rewrite things from the ground up to make the code sim­pler and sex­i­er — in the spir­it of The­sis itself. What this means is that I will be poten­tial­ly nuk­ing all of your cur­rent Open­Hook cus­tomiza­tions (that’s one of many pos­si­ble bugs I’m envi­sion­ing in this sce­nario…). In oth­er words, when you see an update noti­fi­ca­tion, don’t dive head­long into it. Check feed­back on Twit­ter first — it’ll either be praise or curs­ing for @OnSixes; take that and decide whether to upgrade or not when the time comes. ;) (Yes, I do test my code, but like I said, bugs slip by me. I’ve not attuned my per­fec­tion­ism enough to be a great coder.)

So what will Open­Hook have in the future? (And this is future… Don’t expect an update any­time too soon.) Well, there are a num­ber of things I have in mind (maybe I’ll final­ly ajax­i­fy things a bit?), but the big win that I have on the top of my list is sand­box­ing. On more than one occa­sion I’ve heard of users mak­ing some mod­i­fi­ca­tions only to dis­cov­er their blog is screwed up. Fatal errors are the pits, and I’m hop­ing to set up Open­Hook to pro­tect against fatal errors. (Less­er errors are still whol­ly your responsibility. ;)

Now’s the time to drop fea­ture requests, though. I’m a bit out of touch with the The­sis com­mu­ni­ty — I don’t have the time for it like I used to, pri­mar­i­ly — so let me know for what you all have been long­ing, ‘kay?

13 thoughts on “The Future of Thesis OpenHook”

  1. You actu­al­ly don’t HAVE to split your work if you don’t want to. The options in the lay­out pan­el are over­rid­den by any­thing you do in custom_functions or custom_styles.

    I think the sand­box­ing idea is a great one. I rou­tine­ly miss clos­ing a tag in cus­tom func­tions & throw the entire site into an error.

    I’m sure there are oth­er requests I have, I’ll think on it & come back with more.

  2. Hey Rick — Think jQuery “Accor­dion” for the next update. Also, hit me on Twit­ter. I’d be hap­py to help youuuu :)

  3. I know I can over­ride via the cus­tom stylesheet, but then that just adds unnec­es­sary bloat — styles are defined in The­sis’ lay­out file and then again in the cus­tom one. Way back in The­sis’ ear­ly day, it had one stylesheet that had min­i­mal styles to dis­play the sin­gle, default style. I liked that; sim­ple, ele­gant, and much eas­i­er to cus­tomize via a cus­tom stylesheet. Less over­head is almost always a good thing — it’s the rea­son I keep a copy of the Sand­box theme around for reference.

    Yes, Greg, some sort of handy accor­dion-like effect has been on my notes for a while now. Some­day I’ll take the time to fig­ure out how jQuery actu­al­ly works. I’ll keep your offer in mind. :)

    And thanks for the encour­age­ment, Chris. Hap­py hol­i­days to you as well!

  4. Hi Rick!

    First of all hope you have a Mer­ry Christ­mas and thank you for all your hard work on OpenHook!

    This may fall com­plete­ly out­side the scope of what you envi­sion for Open­Hook but I would real­ly like a way to incor­po­rate bet­ter fonts using TypeKit.

    I would like a way to enter my Type­Kit key and then have my Type­Kit fonts list­ed as one of the avail­able fonts with­in The­sis Design Options.

    It looks like is now imple­ment­ing this.

    Thats my list. :)

    Thanks again,


  5. Thanks Rick, I am famil­iar with that plu­g­in. I guess the miss­ing link would be some type of link to make the fonts visible/available in with­in The­sis Design Options.

    Thanks again!

  6. That’d require Chris mak­ing the design pan­el ful­ly plu­g­in-acces­si­ble; you might nudge him with that request. Could make for some inter­est­ing pos­si­bil­i­ties. :D

  7. Greet­ings;
    I’m not sure my ques­tion is being post­ed on the The­sis boards, so many thanks in advance for your time. I’ve been using Open­Hooks to put spiffy graph­ics (for page links) on my home page. As I attempt to edit those graph­ics and links, they seem to be dupli­cat­ing them­selves on the page! At this point, I seem to be up the four copies of any graph­ic I put into the “before teas­er box” hook (or any oth­er, for that mat­ter). I have a sin­gle image in the “fea­ture box” hook, and it con­tin­ues to work prop­er­ly. Any advice or guid­ance to this rel­a­tive new­bie would be appreciated. 

    Thanks and blessings;

  8. Type­kit no. Request them to make an open source Word­Press plu­g­in. It’s out­side the scope of Open­Hook, which from the begin­ning has had more to do with func­tion and less to do with style. I appre­ci­ate the sug­ges­tion, though, it’s just that I’m not the per­son to sug­gest it to.

Leave a Comment

Your email address will not be published. Required fields are marked *

Use your Gravatar-enabled email address while commenting to automatically enhance your comment with some of Gravatar's open profile data.

Comments must be made in accordance with the comment policy. This site uses Akismet to reduce spam; learn how your comment data is processed.

You may use Markdown to format your comments; additionally, these HTML tags and attributes may be used: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Rick Beckman