Recent Updates RSS Hide threads | Keyboard Shortcuts

  • Nathan Rice 11:05 am on July 7, 2009 Permalink | Reply
    Tags: Announcement

    The latest round of revisions are available for download. Some bugs are fixed, and some features have been added.

     
  • Nathan Rice 9:43 pm on July 3, 2009 Permalink | Reply

    I’m experimenting with putting the call to include user.functions.php in a function hooked to prodigy_init at a priority of 11, so that it gets called after the entire Prodigy framework is loaded.

    This would eliminate the need to remove_actions in a function attached to prodigy_init in the user.functions.php file, as well as allow the user.functions.php file to take advantage of functions created in prodigy.

    Bottom line, I’m trying to help you avoid the unnecessary nesting of functions just to get simple things to work.

    I’m hoping there won’t be any serious repercussions to doing it this way. So far, I can’t think of any.

     
  • Nathan Rice 8:26 am on June 30, 2009 Permalink | Reply
    Tags: Issue

    I just tried adding a second sidebar to Legacy using the prodigy_create_widget_area() function and it didn’t work. It probably has something to do with the sequence of execution, but I’m not sure. I need to take a look at it.

     
    • Vix 5:42 pm on July 1, 2009 Permalink | Reply

      I figured out why widgets couldn’t be added.

      Legacy’s functions.php lacks the forward slash between STYLESHEETPATH and user.functions.php on Line 52 – so the file wasn’t being included.

      • Nathan Rice 8:46 pm on July 3, 2009 Permalink | Reply

        Wow, talk about your rookie mistake. I’ve updated this in the master files for Legacy, and I’m resuming testing over the weekend. Hopefully, being able to add sidebars will be a functional feature for the public beta (coming soon).

  • Nathan Rice 8:49 pm on June 29, 2009 Permalink | Reply
    Tags: documentation

    Hey everyone, I just added some thorough hook documentation to the Prodigy site. Hopefully, this will make things a LOT easier when trying to figure out how things work with Prodigy, and more importantly, how to extend it to do whatever you want it to (which it pretty much can!).

    Anyway, here’s the link to the Prodigy Hook Reference. Please take a look, and as always, let me know if you have questions or comments.

     
  • Nathan Rice 10:29 pm on June 28, 2009 Permalink | Reply
    Tags: introduction

    Hey, guys and gals! It’s time to kick off the beta stage of the Prodigy development. Please use this site to post fixes, issues, and discussions about how I can make Prodigy the best theme framework available.

    Also, feel free to ask questions about how Prodigy works, too. If there are any specific questions, I’d be happy to handle them.

    If you would like access to post on this site, please email me and I’ll set you up with an account. This is a private beta, so please don’t broadcast this blog’s location to the world.

    Nathan

     
    • Carlos Correza 10:59 am on June 29, 2009 Permalink | Reply

      first impression is good. I like that it doesn’t have millions of crazy options. it “feels” more like wordpress that way, as opposed to re-inventing the wheel. Pearson has a ton of controls but they make sense.

      The problem I’ve run into with some ‘premium’ themes is; sometimes features and external rsources they support change over time and I end up having to re-write half the theme. I prefer to use hooks to inject whatever functionality I require again, that’s a nod to Chris Pearson and thesis. It seems like that’s the path you’re following with prodigy.

      Something you’ve done that I like is to make use of child themes for style. That’s how Darren and Ben customize Mimbo Pro. You’ve really combined my favorite features from my favorite developers into your own unique framework.

      I love how “thin” the framework is. This is really nice clean work.

      • Nathan Rice 9:17 pm on June 29, 2009 Permalink | Reply

        Options are great. And at some point, I’ll probably add some functions that make it really easy to create an options page for you child theme. But I doubt highly there will ever be an options page that is displayed by default for any theme that uses Prodigy. Still thinking about it, though.

        Abstraction is the main reason I build this framework … by getting all markup generated hooked to some action hook, it makes modifications really easy to make and protect when you upgrade. I’m glad you like that part too! :-)

        Keeping styles out of the framework is something I’m fairly committed to. It has pros and cons, but I’ve chosen to do it this way for very specific reasons. I hope it turns out well.

        Thanks for the feedback. Keep using the theme and come back often to let me know what could be done better!

    • Keith S. 5:16 pm on June 29, 2009 Permalink | Reply

      I haven’t done much with Prodigy short of installing it on my dev server and setting up some sample content for it, but from what I’ve seen so far, I REALLY like it.

      • Nathan Rice 9:18 pm on June 29, 2009 Permalink | Reply

        REALLY good to hear!!! I hope you’ll come back here and give some good feedback once you have a little more experience with it. Thanks!

    • Vix 11:06 pm on June 30, 2009 Permalink | Reply

      The only problem I’m having so far is my inability to add new widget sidebars but I see from above that you’ve caught that bug.

      I’ll be porting over one of my themes tonight and I’ll report any issues I encounter.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
esc
cancel