Kodi Community Forum
[CLOSED] Advanced Launcher - Applications Launcher Addon for XBMC - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27)
+---- Forum: Game Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=291)
+---- Thread: [CLOSED] Advanced Launcher - Applications Launcher Addon for XBMC (/showthread.php?tid=85724)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453


- fr500 - 2011-01-28

It's cool like that yes I didn't mean thumb, extra fanart FTW. My question was more like if it's tied to

<fanart></fanart>

or

<fanartpath></fanartpath>


- Robert de Clair - 2011-01-28

Polish r309
http://www.mediafire.com/?w9jjjkdji37q1pu
I love this plugin Big Grin


- Angelscry - 2011-01-28

Robert de Clair Wrote:Polish r309
http://www.mediafire.com/?w9jjjkdji37q1pu
I love this plugin Big Grin
Thank you very much. You update will be into the next release. Wink


- Angelscry - 2011-01-28

fr500 Wrote:It's cool like that yes I didn't mean thumb, extra fanart FTW. My question was more like if it's tied to

<fanart></fanart>

or

<fanartpath></fanartpath>
Actually, for launchers the extra fanart path is equal to the <fanartpath></fanartpath> tag. For roms the extra fanart path is linked to the <fanart></fanart> tag (same path but without the filename).

Honestly I did not know what will be the best tag to use to link the extra fanarts (what why I have indicated that I need skinners feedback into the change log).

<fanartpath></fanartpath> seems to be the first option that come in mind. But if you decide to change and use fanarts images that are not into this default directory... did the extra fanarts path will still linked to <fanartpath></fanartpath> or will be updated with the new <fanart></fanart> value? Any idea what will be the best ?


- ingeon - 2011-01-28

srsobieraj Wrote:I'm not sure I understand. Do you want to edit individually or do you want to use a scraper?

Scraping can be done in 2 ways: Automatic and semi-automatic.

Automatic runs the scraper and assigns info to the ROM based on the best match.

Semi-Auto runs the scraper but asks the user to make the best match. There is presently no way to select "No match" in this mode.

If "Off" is selected, ALA will import the ROMs but not gather any info. You can then go and scrape each ROM individually.

If you're talking about the "Import plot from file" option, then you have to set each plot manually at the moment. ALA doesn't look to see if you have a plot file already (mostly because there is no pre-defined location for plot files). Perhaps this could be added in future versions, by specifying a Plot path the same way we set Thumbnail and Fanart paths.

1. Couldn`t find this on the Wiki Oo

Thanks for all the changes so far Big Grin
ps. my thumbs and fanarts still give error, thumbs/fanart

Also there is the option "import during scan" How do you start the scan ? for none/auto/semi-auto

Also how does one install the advanced.launcher.console.icons.pack.zip ? Also 1.

edit: Tried v1.0.4 and still almost same error thumbs/fanart
While scraping the fanart/thumb, it brings up the image, I select, then in the fanart/thumb folder
it then creates a file game* (no extension), an empty file named after the game,
and obviously fails to download while displaying " error Script failed! :addon.py"


Solution Mame Roms not found - Thrasher666 - 2011-01-28

timdog82001 Wrote:I recently updated advanced launcher and deleted and redid all my emulator entries in order to scan in the artwork....but some of the emulators that previously worked with the default arguments provided by advanced launcher froma previous version now no longer work with the arguments provided from the newest version of ALA.

I don't recall what if any default arguments were previously associated with MameUI32, but right now its just "%rom%" and this launches mame alright, but mame throws up "ERROR: required files are missing, the game cannot be run." I assure you, the files are most certainly there.

Anyway, what arguments are you guys using on Windows for MameUI and snes9x? It was working fine for me yesterday before I redid all the advanced launcher entries. I found a list of mameui arguments, but none of them seemed relevant. snes9x also is no longer working. It opens up the snes9x window but nothing happens, its just black inside the window.

I finally found in MameUI the "Directory" Section for the roms. MAMEUI, found the game and could play but it couldnĀ“t start with advanced launcher because of a different Filename, check this if you got this problem.


- fr500 - 2011-01-28

Angelscry Wrote:Actually, for launchers the extra fanart path is equal to the <fanartpath></fanartpath> tag. For roms the extra fanart path is linked to the <fanart></fanart> tag (same path but without the filename).

Honestly I did not know what will be the best tag to use to link the extra fanarts (what why I have indicated that I need skinners feedback into the change log).

<fanartpath></fanartpath> seems to be the first option that come in mind. But if you decide to change and use fanarts images that are not into this default directory... did the extra fanarts path will still linked to <fanartpath></fanartpath> or will be updated with the new <fanart></fanart> value? Any idea what will be the best ?


I'd say fanartpath but guess the other skinners should post their opinions on this issue too


- KiSUAN - 2011-01-29

Spanish Translation Update Spanish String.xml


- Angelscry - 2011-01-29

KiSUAN Wrote:Spanish Translation Update Spanish String.xml
Thank you. It will be added in the next version.


- Angelscry - 2011-01-29

fr500 Wrote:I'd say fanartpath but guess the other skinners should post their opinions on this issue too
I think that using the fanart tag of an item to define the extrafanart path is less restrictive than using the fanartpath tag of the launcher.

If all your fanarts images are into the fanartpath it will be exactly the same.

But if your fanarts images are into different directories, your extrafanarts images will also have to possibility to be into different directories and not defined by the fanartpath of the launcher.


- KiSUAN - 2011-01-29

Angelscry Wrote:I think that using the fanart tag of an item to define the extrafanart path is less restrictive than using the fanartpath tag of the launcher.

If all your fanarts images are into the fanartpath it will be exactly the same.

But if your fanarts images are into different directories, your extrafanarts images will also have to possibility to be into different directories and not defined by the fanartpath of the launcher.
I must ask because I feel I'm missing something, how you get the path for fanart?

Because the only thing I can fetch is the complete "path + image name" with Listitem.Property(Fanart_Image). Listitem.Path gives me the plugin path. So I feel something is missing/wrong here.


- Angelscry - 2011-01-30

KiSUAN Wrote:Listitem.Path gives me the plugin path. So I feel something is missing/wrong here.
Ok... I have just checked. Seems that for programs the Listitem.Path gives always the plugin path. What ever I assign, the returned value by XBMC is always the plugin path.


- Angelscry - 2011-01-30

Ok... I think I understand the problem. When using XBMC with movies the Listem.path is related to the path of the movie files. When using XBMC with music the Listem.path is related to the path of the audio files. For the same reasons, when using XBMC with programs the Listem.path is related to the path of the add-on files (and not to the path of the file focused by the add-on.). I think that's why the Listem.path return the add-on path. It makes sense. What I can do is to replace the Listem.path by the Listem.trailer for next version. It is not really consistent with the rest of the XBMC path and skin management... but I do not think I can do better actually. Sad


- KiSUAN - 2011-01-30

Listitem.trailer is fine with me.


- butchabay - 2011-01-30

We've done an option to choose where all the game stuff can be customized by the user in Cirrus Extended. The code for fanart image and extrafanart is in myprograms.xml the trailer and thumbs are in the respective view file.