This thursday my client will upload his new site using my first "API" for plogger. This site is however heavily reduced in functions, even though I have programmed and edited all aspects of plogger, including comments and EXIF reading and such (all functions available in html version). But as I came along I realized i'm probably the only one ever using my work. Mostly due to lack of experience in writing an API.
Now I am eager starting writing a complete API in it's best shape. What I whish for is that one day I can spread this along the way and help others building their sites using this API fairly uncomplicated. But I would appreciate some help here. I have never written any thing this "general" before. I get stuck even when I try finding a naming convention, what the heck should I call my functions / objects and such so people will understand it when they use it? And tons of other questions regarding usability and development.
Since AS 3.0 is quite close to the fundamentals of programming so I guess there are quite a bunch of you gals and guys that can help me building this.
Flickr has an API called Flashr. But Flickr is nor opensource or free of usage as Plogger is. Plogger is everything that is needed having a online photogallery, or as I mostly use it, as an online portfolio.
At what level could I expect help from anyone? Who's with me? :)
And last but not least. I will, unless someone says else, use the name Flogger as project name for this!
i do a lot of customizing myself... i created an anonymous upload capability, integrated highslide js, and currently looking to incorporate an independant layer organization with up to five levels of organization or none...
i'd be happy to help out any way i can through development or just testing... you can email me details if you would like. shaunm AT xecu DOT net