The line, “Meet the new boss, same as the old boss” comes to mind. Scala is a relative new language and is a functional language. Lift is a web framework which runs scala. For the last few days ive dabbled with both and aside from somewhat fun ive had working with it I have to point out that I dont get it…
No, I dont mean i dont know how to use it. Ive created a few example projects already but just dont get why the the developers decided to change the syntax SO MUCH. Its like …what??? why??? just for the hell of it??? Also one of the selling points for scala is how well it plays with Java. Most of you know from previous articles how i think Java is not for the web so I dont get why scala would be any different. It runs on the JVM and list runs on a servlet container (ex Tomcat). So all the headaches that i had with Tomcat, Java, and the web application are back…great. So far these are my first impressions of both scala and lift. I plan to create a small TO-DO list using both technologies and publish a small tutorial soon.
It was either scala/lift or learn Ruby well. I chose something completely out in left field. We’ll see, heck Scala+Lift is bosting thats it a few times faster than Ruby on Rails. So…
January 22nd, 2009 in
Research |
No Comments
This will be a quick entry. Are you having issues using the Zend_Paginator view functions? Yea me too. This affects all releases and isnt really a bug but more of a annoyance if you dont know whats going on.
What is the issue?
Well if you installed a fresh copy of PHP or if you prefer to code with <?php ?> open and close tags appose to <? ?> you might be affected. Since a fresh copy of PHP contains the PHP.ini flag short_open_tags = Off this causes some chaos and doesnt allow the Zend_Paginator::paginationControl function for example as well as $this->next $this->previous attributes to not work in a View.
The Fix
Open your php.ini file. You can check which php.ini your using by using phpinfo(); and check the Currently Loaded php.ini path. open the file up and set the short_open_tags flag to On then restart Apache.
You should see it work. TADA!
Armando Padilla – Time to get some dinner.
So about a month after initially starting on the code, I finally released two versions of the Zend_Service_Netflix wrapper for the Zend Framework, submitted a proposal to the Zend Framework Team, and changed the status on my proposal from “New” to “Ready for Review”. Pheww was that hard work put to good use. It feels good to get this off and running with the initial release.
What’s included in the release?
Like I mentioned before i created 2 releases. One release contains only the catalog functionality. It allows developers to use title search, title auto complete which can be used in conjunction with AJAX to create a autocomplete search box, retrieve detailed title information, and search actors/directors. This package is intended for developers that want to use the extensive Netflix catalog on their own web site without the added functionality found in the full version of the release.
The second release, the FULL release, contains not only the catalog functionality but also allows developers to manage user queues, manage user ratings, retrieve user reviews, and most importantly create the request access url, the URL which users NEED to click that allows their app to retrieve restricted content. So if the developer wanted to create a Zend Framework powered app that allowed users to add, delete, and update their “Watch Queue” or “Instant Watch Queue” they can do this by calling a simple method within this package.
Where can i get the release?
I committed the releases to the Google Code site Located here, Zend Framework Netflix. The packages are properly named so you wont have trouble distinguishing which one you need.
Whats next?
The next steps for this project is to have the Zend Framework team review some of the code, my submitted outline, and hopefully approve it. On my end I will continue to work on the code. There are 2 items which i need to iron out, Updating Ratings, Deleting an Item from the users Queue, and updating the code to support the SIGNITURE METHOD HMAC-SHA1. I will place these items and other “gotchas” on the google code twiki to continue to track my progress. I will also clean up my PHPUnit tests.
I would like to also create a small set of examples for the user to refer to, as well as a small application users can see the code in use. Again i will provide the details on the google code twiki and here as well.
I’m anxious to hear back from anyone that’s using it how i can improve on it and what they think is a better approach.
Armando Padilla
Links of interest? Maybe?