So I’m actually getting somewhere and feeling pretty happy with myself. The api class I’ve build in php allows me to collect data from url, and by supplying parametes such as type, apikey, user_agent I am able to collect the data and parse it into assosiate arrays which I find easier to work with rather than a generic object. I have also compiled a list of the currect data sources so things like Last.Fm, youtube, picasa , twitter and the parameters they need to use and stuck them into an xml file which is loaded the same way as everything else and passing out the links into the api class allows me to return all the data I need. Woop! Sticking in my username gave some results and a few warning becuase I havent yet set up error handlers for when the username doesnt exist at a service and some do not provide an error.
So yeah, getting the data is done almost, I still want to add in the ability to mix up the users names, so obviosuly the user will need to put in their name and username and maybe email etc.
I can user all of these where applicable, username will work for most but if on one site the username is different I can try a few other common ones, firstnameSurnameDob for example or initalSurname and some services actually allow search by email which would be awesomely simple.
All things to consider this afternoon and work on once I have a plan.
Then I just need to start playing with this data, for which I am going to use processing.js to begin with, this is a javascript port of Processing which is something I do love to use when I can.
Also I realised I need a secure login area I guess to maintain and update this xml file of all the data sources and add new ones and set up other pages such as what this is and what it does and privacy policy and all that jazz, so initally I was going to use a flat file architecture but its boring and I dont need something as heavy as mysql so I opted for sqlite3, something I played around with when I looked at ruby on rails.
I’d quite like to look again at RoR development it was fun but I couldn’t dig my teeth into it, now I’m a little wiser I might revisit it.
Anyhow sqlite3, nice and simple, and probably better explained here or here rather than here.
Peace!