Posts: 1,141
Joined: Mar 2006
Reputation:
0
actually i do like the idea of being able to adjust emulator settings from within XBMC.
Posts: 582
Joined: Sep 2006
Reputation:
1
Much appreciation for all the work that you're doing, Awen. I know quite a few people who plan to fully adopt XBMC after this piece is added.
Posts: 1,141
Joined: Mar 2006
Reputation:
0
No doubt. I've been perfecting my collections in anticipation..
Posts: 236
Joined: Oct 2008
Reputation:
0
EMK0
Senior Member
Posts: 236
just wounder are these scripts ment to handle emulator settings? or is this for something els?
Posts: 24
Joined: Nov 2008
Reputation:
0
Awen
Junior Member
Posts: 24
2009-02-09, 11:04
(This post was last modified: 2009-02-09, 13:48 by Awen.)
Yes absolutely. If 'Scraping' is the natural thing for scripts, 'Emulators settings' could be another in this case: i am personally not aware of every pieces of emulation out there... So, looks like a good way to support all them, plus handling every suggestions you all made in this thread, up to emu auto downloading eventually.
I'm still struggling with some plugin shape questioning: one script per 'platform' (say 'Arcade') handling both Mame app support and arcade roms scraping, or numerous small scripts adressing single needs...
cheers,
Posts: 24
Joined: Nov 2008
Reputation:
0
Awen
Junior Member
Posts: 24
2009-02-09, 22:03
Currently, i feel like having 3 entry points for scripts:
1) application/emulators support,
1bis) misce game tools,
2) standard game info scraping.
(2) is the standard way for you script people to work, i only have to, well, comply. (1) and (1bis) will require some work from myself or Terin (or others) to define a dedicated plugin architecture...
(1bis) exists because some applications are rich of possibilities concerning info retrieval fe: you're right to use Mame as an example, as lot of information is available from inner infos when triggering 'mame -listxml'...
So, i suppose that a 'good' mame script would handle inner parameter settings, but some other dedicated info retrieval as well, and maybe various tools like joystick configuration file generator.
(1) and (1bis) may be part of the same script/dialog, or separated menu entries... Eveything is possible at this point.
I'd be happy to read your thoughts about how you'd like scripts to be shaped and called from the core.
Posts: 582
Joined: Sep 2006
Reputation:
1
wow djh_ that looks gorgeous
Posts: 3,909
Joined: Dec 2004
Reputation:
20
Nuka1195
Skilled Python Coder
Posts: 3,909
how ia this different than if i have my own db using pysqlite? faster?
there are a couple things that would benefit this i believe.
most front ends allow custom game lists. this can be done by sql, but with my limited testing a filter would be faster. so if you could have filterby on any listitem property and the mechanism to cycle thru or select direct with a filterby(property,value) builtin. so if i had a listitem.property(gamelist,1), filter for all gamelist properties that equal 1 should be faster than sql and refilling the list. i think.
currently you can do almost everything other frontends can do just by skinning. but i haven't found a way to quickly switch gamelists. eg mala is real fast switching game lists.
i do agree plugins can handle everything including scraping though.