Help building the 3DS Internet Browser

Discussion in '3DS - Homebrew Development and Emulators' started by h4xthisacc0unt, Aug 5, 2016.

  1. h4xthisacc0unt
    OP

    h4xthisacc0unt Newbie

    Newcomer
    2
    1
    Aug 5, 2016
    Moldova
    Hi, I see there is a lot of homebrew applications that doesn't have a proper interface, I also noticed that the actual 3DS Internet Browser code was open source. My idea is to help develop a framework so everybody can release their apps with a web interface with little effort, (something like Electron for the PC which has an embed webkit).

    I just downloaded the source code from the official Nintendo site but it doesn't seems to be any kind of documentation or building process (I'm not even sure is the full source code), there is some code to build the libraries which I already managed to build form arm, but I'm still unsure how to compile them into a 3dsx file.

    Am I missing something?, is it even possible to build a browser with the code provided?, My other idea was to take the wii homebrew internet browser code and try to port it to the 3ds.

    Any help will be appreciated.
     
    Shadowfied likes this.
  2. LiamTheHackermon

    LiamTheHackermon GBAtemp Regular

    Member
    130
    78
    Jul 22, 2016
    United States
    xD

    that is only part of the code idiot
     
  3. h4xthisacc0unt
    OP

    h4xthisacc0unt Newbie

    Newcomer
    2
    1
    Aug 5, 2016
    Moldova
    Actually I did said...
    :P

    But I guess those files should somehow help writing a Homebrew Internet Browser...

    Another Idea I just had is to make a special Browser launcher that boots a small server and from there it could execute the commands for the app, I think this would be easier, but still I would like to give full access to the developer, so it feels like an actual 3DS app.
     
  4. ih8ih8sn0w

    ih8ih8sn0w Koreaboo

    Member
    1,656
    720
    Aug 22, 2015
    United States
    Hell
    I think the issue with homebrew apps not having a real UI is that it is painful to design and implement in general. It would probably take twice as long, if not longer, to release an app with a UI then without. Some things (like decrypt9) have custom UIs because someone else created it, while someone else worked on features. It just isn't really worth the effort most of the time. As for the browser source, that is probably for web developers use, so it would unlikely contain data for the UI.