Line 68:
Line 68:
::::::Dashxdr: I believe what teuidj is saying is that a WAD file is simply a container, and there is no real reason to use it to contain the contents of a channel. Its the contents that matter, and the WAD is extracted by a WAD installer anyway, so it makes more sense just to embed the actual channel contents in the installer binary, rather than a WAD. And there's no need to pack a WAD therefore. However the problem with that is it makes life hard for the end user, if the contents of a channel must be packed in a binary, rather than just dropping a WAD on the SD card and installing it. But WADs are the distribution method of choice for warez VC/WW, so any sort of installer for them is facilitating warez. I'm not trying to take either side in this argument, just trying to clarify some stuff. --[[User:SifJar|SifJar]] 20:10, 22 November 2010 (CET)
::::::Dashxdr: I believe what teuidj is saying is that a WAD file is simply a container, and there is no real reason to use it to contain the contents of a channel. Its the contents that matter, and the WAD is extracted by a WAD installer anyway, so it makes more sense just to embed the actual channel contents in the installer binary, rather than a WAD. And there's no need to pack a WAD therefore. However the problem with that is it makes life hard for the end user, if the contents of a channel must be packed in a binary, rather than just dropping a WAD on the SD card and installing it. But WADs are the distribution method of choice for warez VC/WW, so any sort of installer for them is facilitating warez. I'm not trying to take either side in this argument, just trying to clarify some stuff. --[[User:SifJar|SifJar]] 20:10, 22 November 2010 (CET)
:::::@SifJar Thanks for that information. The thing I see is that the process one must go through to create a channel for the Wii is cryptic and poorly documented. It is easy to follow the warez / VC/WW path, so people go that way. But I want to follow an open source road all the way and I want to be able to create things myself. WiiMC has an installer. It was provided by some associate of the author of WiiMC, as a courtesy. I want it for such things to be trivial to do, without having to say please or thank you. It's not there yet. I don't give a rat's ass about the potential for use in warez / piracy (and besides, that "battle" is lost already, pirates PWN'd the Wii long ago, can't we face reality already?). I'm only after freedom. WADs are established, that much is obvious. I want a path that lets me create channels and install them, using non-M$ related open source tools, and if the WAD format is used, that's fine. One clear advantage is being able to leverage a lot of existing tools. Another note, the approach of making a custom installer for each application is ridiculous, everyone has to reinvent the wheel. Why not replace WiiBrew's apps/* structure with apps/*.WAD, and WiiBrew just launches the contents of a WAD without it having to even be installed as a channel? One would get the cool animating logos and sound effects. And a built in function of the HomeBrew channel could be to install a WAD as a channel. I'm just thinking out loud here. [[User:Dashxdr|Dashxdr]] 21:31, 22 November 2010 (CET)
:::::@SifJar Thanks for that information. The thing I see is that the process one must go through to create a channel for the Wii is cryptic and poorly documented. It is easy to follow the warez / VC/WW path, so people go that way. But I want to follow an open source road all the way and I want to be able to create things myself. WiiMC has an installer. It was provided by some associate of the author of WiiMC, as a courtesy. I want it for such things to be trivial to do, without having to say please or thank you. It's not there yet. I don't give a rat's ass about the potential for use in warez / piracy (and besides, that "battle" is lost already, pirates PWN'd the Wii long ago, can't we face reality already?). I'm only after freedom. WADs are established, that much is obvious. I want a path that lets me create channels and install them, using non-M$ related open source tools, and if the WAD format is used, that's fine. One clear advantage is being able to leverage a lot of existing tools. Another note, the approach of making a custom installer for each application is ridiculous, everyone has to reinvent the wheel. Why not replace WiiBrew's apps/* structure with apps/*.WAD, and WiiBrew just launches the contents of a WAD without it having to even be installed as a channel? One would get the cool animating logos and sound effects. And a built in function of the HomeBrew channel could be to install a WAD as a channel. I'm just thinking out loud here. [[User:Dashxdr|Dashxdr]] 21:31, 22 November 2010 (CET)
+
:::::::I really don't understand your logic behind having HBC launch .WAD files instead of .DOL or .ELF files...It makes zero sense. .WAD files are simply .DOL files with a few other files all wrapped up together. What is the point of wrapping them up, just for HBC to have to unwrap them to run them? It is completely illogical. As for the HBC showing banners thing: That would require a LOT of coding. TT would have to implement a full clone of Nintendo's banner handling code, which I'm not sure is 100% reverse engineered yet, and for very little gain. It is much easier to implement a custom identification system, like i dunno...a file containing a name and description, perhaps in XML format, and an icon, perhaps in PNG format? Also, you can already create custom channels using 100% open source and non- .NET tools thanks to Benzin and Wii.py. You may have to fix some errors with wii.py, but nobody said it was easy. As for HBC installing WADs, never gonna happen, simply because it'd be very hard to implement anti-piracy. And while as you say, piracy is rampant in the Wii "scene", that does NOT mean TT are gonna release a tool capable of piracy. --[[User:SifJar|SifJar]] 23:32, 22 November 2010 (CET)