lemme axe you a question
so i'm back to the debate of if it's worth working on an xspf resolver with a nice open source player on github called tomahawk? well my argument previously was that not everyone wants a completely new player. how many people are going to switch players so they can handle a playlist format? (not even a new content format)... thus i am still going to continue working on the resolver codebase.
the one thing about a resolver is it is only as fruitful as it's support for import targets (or as tomahawk and most anyone else would say plugins.) tomahawk uses javascript for it's resolver plugins, i may look into supporting that however all plugins made for my codebase are either c/c++ or a language that'll create a dynamic object that has C like exports, or if that isn't for you.. lua.
plugins for the resolver go farther than just supporting a new import target, you can also extend most all parts of the app with them. this is the case with most my codebases these days, including friendnet and datapusher.
the one thing about a resolver is it is only as fruitful as it's support for import targets (or as tomahawk and most anyone else would say plugins.) tomahawk uses javascript for it's resolver plugins, i may look into supporting that however all plugins made for my codebase are either c/c++ or a language that'll create a dynamic object that has C like exports, or if that isn't for you.. lua.
plugins for the resolver go farther than just supporting a new import target, you can also extend most all parts of the app with them. this is the case with most my codebases these days, including friendnet and datapusher.
Labels: datapusher, resolver, tomahawk, xspf

0 Comments:
Post a Comment
<< Home