Hacking Question for devs

  • Thread starter Thread starter waninkoko
  • Start date Start date
  • Views Views 18,187
  • Replies Replies 86

Which way should I use to load Custom IOS modules and plugins?

  • Load them automatically when cIOS is loaded (built-in)

    Votes: 0 0.0%
  • Load them from the application (not built-in)

    Votes: 0 0.0%

  • Total voters
    0
but i'd say noobs make noob apps anyway. so why not giving the real devs some more room for their apps. these are the ones that the community really needs (probably).
 
just a thought... but could this latest rev install to a different slot? like 239 for example?

old apps can continue to use cios249 with the module built in, and the devs of new apps can use ios239 (or w/e) with the module not built in

Anyways, just a thought
 
waninkoko said:
It's not because of that. I don't want noobs crying because old apps don't work.

I hate to say it, but it's really dumb to make a decision based on crying noobs. Most devs are more likely to use your cIOS when it'll use external modules (for flexibility, and quick fixes when bugs occur, or new protections emerge). And after all, the devs create the applications that noobs will use.
 
And do the old apps that use 249 need the modules? Most of them just need to authenticate as super user or the Trucha Bug, I guess this can be done without any modules.
And who cares about old USB Loaders?
 
DeadlyFoez said:
I care and many other people care too. WiiFlow is one of the best usb loaders out there IMO. It would suck if it couldn't work with newer revisions of cIOS. Although someone could update it, and the many other apps out there, but it would be a lot of work.
Which "many other apps" are they that actually use the modules and not the Trucha Bug/Identify function?
 
waninkoko said:
I forgot to say rev18 will have the ability to load custom modules externally (although it includes built-in modules).

Best of both then
wink.gif
 
okay, so its going to be a combination of both?

ie. old homebrew apps will still work with the internal module, and new homebrew apps can either use the internal module OR a custom external module?

if that's the case, then that should make everyone happy
biggrin.gif


thx wanin
 
Still nice that you've included the option of some custom modules, though. Then if people need to replace something more extensively they can use Hermes'.
 
Backward compatibilty seems to be the main disadvantage, can't this be solved by leaving cIOS249rev17 alone for now. Then use a new slot for the cIOS with external modules, say IOS149?

That way old apps continue to work. Unsophisticated apps can continue to be written for IOS249. Smarter apps that need external modules can be written to take advantage of external modules in cIOS149?
 
xflak40 said:
i suggested that awhile ago (w/ slot 239, but same thing), and deadlyfoez reiterated it... i'm assuming from his lack of response that wanin doesn't like the idea
Sorry, I thought I read the whole thread. I missed page 5. D'Oh.
 
waninkoko said:
That's not something too easy to do, nor "proper". This is something to be analyzed very very carefully, cause it's hard to do and delicated.

Btw, right now I see the external modules option is winning but I don't know if it will achieve enough votes against the built-in modules options to consider its implementation in rev18.

I'm going to bed now so I'll check the poll tomorrow morning.

SNEEK does it, it's open-source so you could look how it's done.
 
thesund0g said:
Why not choose which modules at install -- if it isn't already loaded but required by the app, load it then.

...we would end up with a massive amount of different configurations -> very differing problems -> ???? -> fail.
 
waninkoko said:
But built-in modules cannot be replaced by external modules.
couldt you implement it as

look in app folder for the module
if not available, fail back to default module build in

if no sd/hdd is available, it only uses internal modules

so you will get both ways working
and everyone will be happy
 
ChaosEnergy said:
waninkoko said:
But built-in modules cannot be replaced by external modules.
couldt you implement it as

look in app folder for the module
if not available, fail back to default module build in

if no sd/hdd is available, it only uses internal modules

so you will get both ways working
and everyone will be happy
That could be doable if waninkoko can use the "hook" system vBulletin and Wordpress uses but those are PHP. I don't know what Waninkoko is using, maybe C++?
 

Site & Scene News

Popular threads in this forum