MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
Nightingale Forums - How to work on a bug

Nightingale Forums

Full Version: How to work on a bug
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello, since we are working on a fork, it would be great to first see if your bug is a Songbird bug before reporting issue.

I opened a "metabug" at Songbird Bugzilla in order to track down what we want to be resolved for Nightingale.

In the "Depends on" field you can see those bugs.

If you have any Songbird bug in mind that should be resolved tell me in this topic ! Thanks Big Grin
Thanks GeekShadow, great to have a metabug for community bugs Smile
...dreaming of Songbird and Nightingale on the same codebase except API-Keys and Branding and more community SB core developers again!

Do we have a SHOUTcast partnership (API key), or can't we offer SHOUTcast for NG 1.8?
(10-20-2011, 05:44 AM)rsjtdrjgfuzkfg Wrote: [ -> ]Thanks GeekShadow, great to have a metabug for community bugs Smile
...dreaming of Songbird and Nightingale on the same codebase except API-Keys and Branding and more community SB core developers again!

Do we have a SHOUTcast partnership (API key), or can't we offer SHOUTcast for NG 1.8?
Not yet for SHOUTcast, I will investigate on this quickly. I just hope they are up to date with the API version Big Grin
SHOUTcast's API is up to date, I updated it some time ago Smile
The issue is the API key used (in shoutcast.js). I'm not sure how to get one. After we are on 1.10, we might just link to Songbird's, but for now I think we need an own key; what do you think?
(10-20-2011, 06:47 AM)rsjtdrjgfuzkfg Wrote: [ -> ]SHOUTcast's API is up to date, I updated it some time ago Smile
The issue is the API key used (in shoutcast.js). I'm not sure how to get one. After we are on 1.10, we might just link to Songbird's, but for now I think we need an own key; what do you think?

Right, well I will look now.

Another topic, do you want to integrate Playlists Folder in the core of NGale 1.8 ? We can do that Smile


Quote:The new SHOUTcast 2.0 API platform has been released and we are currently focused on migrating current 1.0 API partners to the 2.0 APIs.

Unfortunately, due to this migration, we are not currently accepting new partners.

If you are a current licensed partner, please contact contact us to coordinate your migration as soon as possible .

If you would like to contact our team about possibly joining the SHOUTcast Radio API Partner Program when it resumes taking new partners, please send us an email and include a product/application description. A member of the SHOUTcast team will contact you when new partner requests are being accepted.

I just sent a mail...

(10-20-2011, 08:54 AM)GeekShadow Wrote: [ -> ]Another topic, do you want to integrate Playlists Folder in the core of NGale 1.8 ? We can do that Smile

I still think playlist folders is more core feature than AddOn, so I'd be glad to see it integrated - but is it worth the effort or should we include it like albumart in SB - at least until we're at 1.10?
Whatever you guys decide, could we possibly get Songbird and it's extension devs to cooperate, and perhaps later on when 1.10 is out, have the install.rdf's be built with support for both ngale and songbird? Furthermore, with something like that, both the api for songbird and ngale could be included in shoutcast, last.FM, etc, so that the proper name displays no matter which player the user ends up running.
(10-21-2011, 05:13 AM)ilikenwf Wrote: [ -> ]Whatever you guys decide, could we possibly get Songbird and it's extension devs to cooperate, and perhaps later on when 1.10 is out, have the install.rdf's be built with support for both ngale and songbird? Furthermore, with something like that, both the api for songbird and ngale could be included in shoutcast, last.FM, etc, so that the proper name displays no matter which player the user ends up running.

Didn't we want to stay with Songbird's core in 1.10? Without all the renaming thing?
We're not renaming but we are moving to gecko 6+ ...maybe we could get that patched into songbird anyway.