For UbuStream v2.2, I'm adding support for an n-tier group hierarchy so groups can contain groups (or a mix of groups and stations). While this will be handy to keep the UI manageable and avoid having to page through endless groups, I have been spurred to do this so DynSource apps can publish "nested" sections to more closely follow the structure of the web site they are using as their source.
I'm looking for input on the best way to enable DynSource apps to communicate the nested sections back to UbuStream. Currently, I'm thinking along the lines of using the xxxxSections.plx file to do this in such a way that the xxxxPlaylist.plx file can remain unchanged (so minimal changes to your app to support it). The new sections file might look like this:
The playlist.plx file would just use section names as it does today and UbuStream would figure out where in the hierarchy to put the playlist items. This is possible because "groups" and "group relationships" will be stored separately in the database. This mandates that group names must not only be unique within a DynSource but also unique within the UbuStream database. (Further, a name must be unique across all group/station items, so groups and stations can't have the same name). It makes sense to qualify names to ensure uniqueness, in any case.
Would this work for you? Any show-stoppers?
I'm also working on trying to create a small web site just for DynSource apps. Currently, there's no place to do this on the wiki (well, there's the DynSource page under the UbuStream plugin page, but that relies on me updating it all the time) so, to find available DynSource apps, users must search through forum threads looking for posts with attachments. The web site I'm planning would allow DynSource authors to maintain info about their "mini-plugin" and to upload new versions whenever they liked. It should provide "one stop shopping" for anyone looking for currently available DynSource apps. I'll put an obvious link to it on the UbuStream wiki page. If I do this (and it'll cost money to get it hosted), would y'all use the site?
EDIT: Forgot to mention that I'm also adding a Setup button to the DynSource panel in the config app. This will invoke an application that you can provide for maintaining any config data your app requires (eg. <dynsource_name>Form.exe). For instance, if you store any info the user enters in a .Net application configuration file associated with your main app, then your main app can easily read it in at run time.
I'm looking for input on the best way to enable DynSource apps to communicate the nested sections back to UbuStream. Currently, I'm thinking along the lines of using the xxxxSections.plx file to do this in such a way that the xxxxPlaylist.plx file can remain unchanged (so minimal changes to your app to support it). The new sections file might look like this:
Code:
[sections]
Player=Windows Media Player
section1=News
section1.1=World
section1.2=Business
section1.3=Features
section1.3.1=Politics
section1.3.2=Sci-Tech
section1.3.3=Health
section1.4=Sports
section2=Entertainment
section2.1=Movies
section2.2=Music
section3=Special Reports
NumberOfEntries=12
Version=2
Would this work for you? Any show-stoppers?
I'm also working on trying to create a small web site just for DynSource apps. Currently, there's no place to do this on the wiki (well, there's the DynSource page under the UbuStream plugin page, but that relies on me updating it all the time) so, to find available DynSource apps, users must search through forum threads looking for posts with attachments. The web site I'm planning would allow DynSource authors to maintain info about their "mini-plugin" and to upload new versions whenever they liked. It should provide "one stop shopping" for anyone looking for currently available DynSource apps. I'll put an obvious link to it on the UbuStream wiki page. If I do this (and it'll cost money to get it hosted), would y'all use the site?
EDIT: Forgot to mention that I'm also adding a Setup button to the DynSource panel in the config app. This will invoke an application that you can provide for maintaining any config data your app requires (eg. <dynsource_name>Form.exe). For instance, if you store any info the user enters in a .Net application configuration file associated with your main app, then your main app can easily read it in at run time.
[SIZE=1]GBPVR v1.3.11 [/SIZE][SIZE=1]HVR-1250, [/SIZE][SIZE=1]ES7300[/SIZE][SIZE=1], 4GB, GeForce 9300, LianLi, Vista.[/SIZE]
[SIZE=1]GBPVR v1.0.08 [/SIZE][SIZE=1]PVR-150, [/SIZE][SIZE=1]P4 2.26GHz, [/SIZE][SIZE=1]1GB,[/SIZE][SIZE=1] GeForce 6200, [/SIZE]Coupden, XP[SIZE=1]
[/SIZE]
Author: UbuStream plugin, UbuRadio plugin, EPGExtra utility.
[SIZE=1]GBPVR v1.0.08 [/SIZE][SIZE=1]PVR-150, [/SIZE][SIZE=1]P4 2.26GHz, [/SIZE][SIZE=1]1GB,[/SIZE][SIZE=1] GeForce 6200, [/SIZE]Coupden, XP[SIZE=1]
[/SIZE]
Author: UbuStream plugin, UbuRadio plugin, EPGExtra utility.