I've been fleshing out Trizzle with more pages for browsing the Trizzle database (the "Trizzbase.") Most of the pages are simple CRUD implementations-no further AJAX coolness to reveal, I'm afraid-but the pages are necessary, both for the user and also for my own debugging.
- The view tag page now shows albums and playlists that have been associated with that tag in addition to artists. (example: nodepression)
- The recent playlists page shows, not unsurprisingly, recent playlists entered into Trizzle.
- I've started implementing lazy registration. When you first hit a Trizzle page a user ID is created and stored in both the database, and also a cookie. This means that playlists created in the system will be associated with the user, even if the ui doesn't necessarily reveal that.
I'm working right now architecting an integrated search/browse page that will provide a single ui for searching and browsing playlists, artists, albums, songs and tags. However, I've learned enough about AJAX to know that a page like this needs to have some planning happen before actual coding, lest things spiral out of control very quickly.
Recent Comments