One of the nice things about the Solar Framework is the ability to define table layout within the models.. Its not something you have to do but when you do Solar will auto create the table if it does not exist.

This makes development fun because when ever you change a model you can just drop the table and it will get remade on the fly.

Auto create however has 2 issues.. 1. Pre populating data, 2. Table settings outside of Solar's realm (like temp tables).

Ok so maybe "Alert" is a lame name but I really wasn't going for "cool".

My new house gets a little warm some afternoons and I don't always remember to close the windows in the morning to keep the cool air in, or open them at night to cool things down.

What is a programmer to do? Pull out the Solar Framework and throw together a simple solution that will email him when certain conditions are met.

Behold http://alert.cyberlot.net/

Not all frameworks support true models and this is one thing that really sets the Solar Framework apart from a lot of frameworks.

So what sets Solar apart? Lets replicate what Zend Framework references on models in Solar.. You can find the ZF Docs Here

And for those of using the Solar framework or any other framework that uses the following url format your typekey login system is now broke..

Luckly its an easy fix!

Typekey is now Typepad and there new system currently pukes on the link generated by the Solar_View_Helper_Typekey link generator.

To fix change your link change the config for href from

"https://www.typekey.com:443/t/typekey/login"

to

"https://www.typekey.com/t/typekey/login"

Yes, shouldn't make a diffrence but it does.. One gives you a blank white screen, the other a new login box.

Here is a quick reference list to a ton of Solar Framework Articles around the web.

Going to go through a quick walk through of how to use a hacked together version of my old jquery library with solar. You can find the class source files Here

With my new job I have been using Solar a lot and learning something new at every corner. This is my attempt to document some of those things I run into that may not be in the manual yet, may not be clear or may just be useful to all.

There has been a flurry of work around Firebug recently including announcements that Zend Framework and Symfony both now have Firebug logging support through the use of the Firephp. As of this weekend Solar can be added to the list with its own support.

Been playing around with the latest Solar Framework trunk svn install. Its something I have done in the past with FlashUnity in that you provide an svn directory that has the proper directory structure and external links to quickly bring in a working copy of the application.

Anyway I wanted to do some basic profiling with Xdebug but now that I am on a mac I don't have an easy way to view the cachegrind files. With Xdebug 1.x I used to use a pop up window to directly output the results of the profiling but this option was removed in 2.x.

I am currently working on getting basic SAML2.0 support into Solar for an ongoing project at Mashery.com and for security SAML2.0 uses a trusted cert signing.

Basically you sign the a request, send it to your identity provider.. They check the person credentials and send you a response signed with there own key.

Why isn't this possible between a browser and a website? When I go signup for an online account at my bank why can't I provide them my personnal identity they can then use to verify all future requests are "me".