[Release] Repositories Installer Add-on

anarchintosh Wrote:for the image column, why not add a url to the repo image in the svn repo?

i've done this for xbmc-adult on the unofficial repos page as an example.

no one really needs the icons when browsing the wiki page (especially that small), its only in xbmc that it is of any use.

also its a lot of work uploading every image to the wiki.

I was just adding the column and placed the image just because, I don't care what's displayed in the wiki, image, link or whatever. The best option for me would be nothing, make a column that's hidden, but don't know if possible and if it could be fetched by the add-on.

Most images are not available in the Repos SVN/Git, only via download, name/path and other variables of external links could change also, so I think uploading them to the wiki is by far more safe plus heterogeneous, avoiding any other thing that could go wrong.

Temhil Wrote:Thank for the info, I will look into it. I think in all the case I will have to create or adapt an existing windowXML for the Info view about a repo.

That the reason why I am wondering which WIndowXML is used in the skin in order to create the Window for displaying info about a repo, my guess is I can almost reuse it as it is and I would have to do it only for the main skins.

That will come probably later on when I will have more time, I didn't do WindowXML for a while :o.

I think I get what you mean with winowxml and the reference of jmarshall to "doable as a script module", something like what cdscript use https://github.com/Giftie/script.cdartma...ns/Default or NextAired http://code.google.com/p/passion-xbmc/so...253Dclosed use.

Anyway I must say I prefer a solution were you just provide the info assigned to a infolabel and the skin use it, like Advance Launcher does. Providing the info with infolabels available for addons, like ListItem.Property(Addon.XXXX), will make the "Repositories Installer Add-on" compatible with any skin from the go without interfering with the look of the same. For me that's by far, much better solution that having a "default" skin for the addon (or script) like the ones Next and CdArt use, that end being ugly things that almost never suit any skin.

Hope I made myself more clear this time and that I finally understand what you mean with windowxml.

Sorry KiSUAN,

I am not sure I fully understand, what you mean, I quickly looked at the code of the advanced launcher but I didn't see how or where we set info for the skins.

I am already settings those info but the skin does not use it in case of program.

I quickly test the launcher but I didn't go until the point you would see info displayed. Would you have screenshot? That could be helpful.

When you are talking about script addon it is not exactly what I mean but part of it, mostly it is a plugin with a UI part coded as a script, those you mentioned are only script, but you are right that the same idea.

I am totally ok to try your way, but I have never heard about a way of doing it with a addon program.

Ok, no problem, I can try to explain more, just keep I'm mind I don't really know how it works in the add-on code side, I know how to skin/xml code.

Here you have one of the views I made for AVL



Here is the code for that View Viewtype_Arcade.xml

So this view is in my Skin MOD, the one in my Signature.

AVL, as the file in my "C:\Users\User Name\AppData\Roaming\XBMC\addons" folder says (plugin.program.advanced.launcher) is a program add-on, same as yours (plugin.program.repo.installer). So I'm inferring that if it's possible for AVL, the same applies to every program addon.

From that addon (AVL), as it's shown in the SS, I'm fetching:

ListItem.Icon
ListItem.Label
ListItem.Trailer
listitem.property(fanart_image)
ListItem.Studio
ListItem.Premiered
ListItem.Genre

As far as I understand AVL scrapes the info from XXX web/database, same as or similar as you are doing with the wiki I suppose. But the info is stored in a xml file in the path C:\Users\User Name\AppData\Roaming\XBMC\userdata\addon_data\plugin.program.advanced.launcher.

That file were info scraped is stored is name launcher.xml, here is a pastebin for my launcher.xml, that's the file that AVL makes and were stores the info about the launchers I have.

From that file it seems AVL tells XBMC/skin to fetch the info that is linked to specified infolabels through AVL.

I don't know exactly how your addon works, but I suppose it fetches the info form the wiki, stores in some cache, from were later XBMC/skin fetches, for what only a very limited amount of infolabels are aveilable/coded. That's were I suppose lies the difference and how AVL does it, establishing that "laucnher.xml".

I just know that many of the infolabels available for AVL now didn`t "existed" in a beginning of the add-on, and the developer add/coded them by request and "will", linking XXX infolabel to XXX info as it he saw fit. Maybe this is only possible for this type of special addon were a launcher is made.

I will try to contact Angel and ask if what I'm guessing is so, and if what I'm asking you is possible, perhaps he could point you in the right direction and explain how in much easier way.

So, I've had a little chat with Angel and it seems it's not possible, so just forget about my request.

Thanks anyway, it was interesting to see what is doable.
I tried yesterday to do an ActivateWindow in order to use DialogAddonInfo.xml the addon view and in the plugin code I was setting the addon info:


but when the addon info was displayed it was the last addon displayed in xbmc addon manager that was displayed, the information on the selected ListItem wasn't displayed.


Mostly what I have to do it created a WindowXML using most of DialogAddonInfo.xml, it is some work, but that doable.

A new release, not with all the changes you requested yet, but we are getting close.
In order to display the info about a repository, open the context menu and select 'repository info". For time being the default window is the one with Confluence design.
Changelog:

GREAT!!!

You did what I was asking without knowing. I don't need any window to see the details, they are already coded into my views



All I need now is the fanart of the Repositories Installer Add-on I submitted http://img848.imageshack.us/img848/6884/fanart.jpg (1280x720), unless you didn't like it, I can search for other or perhaps make.

Thanks

Glad to hear that.
Concerning your fanart, no problem I will add it, I just didn't have enough time to work on it but thank for the reminder, I almost forgot :o
I didn't forget also I have to add a function install all.

Probably not before the weekend thus

Thanks for the feedback

About the fanart, all you have to do is upload to the REPO (add to zip) that I know, well name it fanart.png or jpg also.

I still can't upload images to the wiki, don't know why, already been 5 days since I made the account and more than 10 edits, maybe I'm missing something.

I think I undertstand why I was confused by what you were telling me Kisuan. It appears your skin is actually doing a lot of more than confluence.
I think is work since I set the addon info of the list item and your skin use it while with confluence user has to display the context menu and chosse 'repository info' which trigger my WindowXML implementation.
Interesting! That a shame other skins don't do the same, I think it is a shame there is no info view for program, that needed from my point of view.