pulpTunes Community Forums The Web Server for iTunes

Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: support for alternate front ends  (Read 1214 times)

indiepants

  • Initiate
  • *
  • Posts: 1
    • View Profile
support for alternate front ends
« on: June 06, 2009, 04:21:00 PM »
Hi there... I like what you've done so far! I'm an interface designer and pretty good front end coder. I'd love to be able to write new front ends for pulpTunes (not just reskin the default one).

I've peeked at all the bits & pieces... looks like there's code served from the app, from your website, and a mix of server processing and ajax. Would be tricky to code a whole new front end against that.

Two things would make pulpTunes an awesome playground for new interfaces:
1) let pulpTunes serve front end code stored outside the app (eg, ~/Library/Application Support on the Mac)
2) a documented ajax api that encapsulates all data access and infrastructure stuff
Logged

alpeb

  • Administrator
  • Grand Master
  • *****
  • Gender: Male
  • Posts: 451
    • View Profile
    • Email
Re: support for alternate front ends
« Reply #1 on: June 06, 2009, 05:21:15 PM »
Hi,

I agree with all your points. We have scheduled a template backend redesign for a future version, that will indeed allow for a better control on how all those resources are fetched. Regarding the api, yup, that's gonna need some docs. Specially if we allow for the creation of plugins for the future as well.

Thanks for the feedback.
Logged