3dbrew - User contributions [en]

005tools

2013-04-30T08:23:23Z

McHaggis: Added github link

{{Infobox homebrew
| title = 005tools
| image =
| type = pc utility
| author = [[User:McHaggis|McHaggis]]
| download = http://filetrip.net/nds-downloads/applications/download-005tools-01b-f30775.html
| website = https://github.com/darthstroyer/005tools
| version = 0.01b
}}

005tools is a simple command line application designed to work with devices that can transfer game saves from CTR-005 (3DS) and NTR-005 (DS/DSi) game cards to your PC. The source code is platform independent, so it can be compiled to run on any system.

== Supported Devices ==

Currently, the application only supports the R4i Save Dongle. The code is very flexible, so supporting other devices should be fairly straightforward if I can get my hands on one.

== Notes ==

The official R4i software writes 3DS cards in full and then writes the first 16kB ''again''. 005tools mimics this but I haven't bothered to change how the progress bar works, so don't be surprised when the progress bar resets after writing all the data.

Also, when writing 3DS/very large cards on the R4i Save Dongle, you'll notice the progress bar freeze after the first 128 bytes are written. The official software does the same thing, and writing resumes ~7 seconds later. I have no idea why it does this, but the device actually stops responding during this time, probably doing some processing of it's own.

== Changelog ==

'''v0.01b'''
* Writing to 3DS cards works now
* Improved save size detection for 3DS cards
* Fixed progress bar on Win32
* Added some error detection

'''v0.01a'''
* First version

== Known Issues ==

* Writing to NTR-005 cards smaller than 1kB doesn't work (reading does).
* The official R4i software flags specific games to be treated like CTR cards and very large NTR cards for writing. This isn't implemented in 005tools yet.

== Screenshot ==

[[File:005tools.png]]

005tools

2012-10-08T11:53:20Z

McHaggis: /* Notes */ Fixed typo from when I originally wrote this section

{{Infobox homebrew
| title = 005tools
| image =
| type = pc utility
| author = [[User:McHaggis|McHaggis]]
| download = http://filetrip.net/nds-downloads/applications/download-005tools-01b-f30775.html
| website =
| version = 0.01b
}}

005tools is a simple command line application designed to work with devices that can transfer game saves from CTR-005 (3DS) and NTR-005 (DS/DSi) game cards to your PC. The source code is platform independent, so it can be compiled to run on any system.

== Supported Devices ==

Currently, the application only supports the R4i Save Dongle. The code is very flexible, so supporting other devices should be fairly straightforward if I can get my hands on one.

== Notes ==

The official R4i software writes 3DS cards in full and then writes the first 16kB ''again''. 005tools mimics this but I haven't bothered to change how the progress bar works, so don't be surprised when the progress bar resets after writing all the data.

Also, when writing 3DS/very large cards on the R4i Save Dongle, you'll notice the progress bar freeze after the first 128 bytes are written. The official software does the same thing, and writing resumes ~7 seconds later. I have no idea why it does this, but the device actually stops responding during this time, probably doing some processing of it's own.

== Changelog ==

'''v0.01b'''
* Writing to 3DS cards works now
* Improved save size detection for 3DS cards
* Fixed progress bar on Win32
* Added some error detection

'''v0.01a'''
* First version

== Known Issues ==

* Writing to NTR-005 cards smaller than 1kB doesn't work (reading does).
* The official R4i software flags specific games to be treated like CTR cards and very large NTR cards for writing. This isn't implemented in 005tools yet.

== Screenshot ==

[[File:005tools.png]]

005Tools

2012-09-23T10:05:23Z

McHaggis: moved 005Tools to 005tools

#REDIRECT [[005tools]]

005tools

2012-09-23T10:05:23Z

McHaggis: moved 005Tools to 005tools

{{Infobox homebrew
| title = 005tools
| image =
| type = pc utility
| author = [[User:McHaggis|McHaggis]]
| download = http://filetrip.net/nds-downloads/applications/download-005tools-01b-f30775.html
| website =
| version = 0.01b
}}

005tools is a simple command line application designed to work with devices that can transfer game saves from CTR-005 (3DS) and NTR-005 (DS/DSi) game cards to your PC. The source code is platform independent, so it can be compiled to run on any system.

== Supported Devices ==

Currently, the application only supports the R4i Save Dongle. The code is very flexible, so supporting other devices should be fairly straightforward if I can get my hands on one.

== Notes ==

The official R4i software writes 3DS cards in full and then writes the first 16kB ''again''. 005tools mimics this but I haven't bothered to change how the progress bar works, so don't be surprised when the progress bar resets after writing all the data.

Also, when writing 3DS/very large cards on the R4i Save Dongle, you'll notice the progress bar freeze after the first 128kB is written. The official software does the same thing, and writing resumes ~7 seconds later. I have no idea why it does this, but the device actually stops responding during this time, probably doing some processing of it's own.

== Changelog ==

'''v0.01b'''
* Writing to 3DS cards works now
* Improved save size detection for 3DS cards
* Fixed progress bar on Win32
* Added some error detection

'''v0.01a'''
* First version

== Known Issues ==

* Writing to NTR-005 cards smaller than 1kB doesn't work (reading does).
* The official R4i software flags specific games to be treated like CTR cards and very large NTR cards for writing. This isn't implemented in 005tools yet.

== Screenshot ==

[[File:005tools.png]]

News/Archive

2012-09-23T10:04:34Z

McHaggis:

*'''24 July 12''' Nintendo released system update [[4.3.0-10]].
*'''26 June 12''' Nintendo released system update [[4.2.0-9]].
*'''19 May 12''' [[3DSExplorer|3DSExplorer v1.2.1]] updated by [[User:Elisherer|Elisherer]]
*'''15 May 12''' Nintendo released its first implementation of 3DS '[[Title list#0004000E - Add-on Content|Add-on Content]]' with the Mario Kart 1.1 update.
*'''14 May 12''' Nintendo released system update [[4.1.0-8]].
*'''24 April 12''' Nintendo released system update [[4.0.0-7]].
*'''08 February 12''' [[CiTRUS|CiTRUS v0.2]] updated by [[User:Xcution|Xcution]]
*'''04 February 12''' [[CiTRUS|CiTRUS v0.1]] released by [[User:Xcution|Xcution]]
*'''02 February 12''' [[3DSExplorer|3DSExplorer v1.2]] updated by [[User:Elisherer|elisherer]]
*'''26 January 12''' [[Crappy Tiny Reader|CTR - Crappy Tiny Reader v0.07]] updated by [[User:PsyKopaT|PsyKo]]
*'''26 January 12''' [[Crappy Tiny Reader|CTR - Crappy Tiny Reader v0.07]] updated by [[User:PsyKopaT|PsyKo]]
*'''05 January 12''' [[Crappy Tiny Reader|CTR - Crappy Tiny Reader v0.06]] updated by [[User:PsyKopaT|PsyKo]]
*'''21 December 11''' Nintendo released system update [[3.0.0-6]]
*'''21 December 11''' [[3DSExplorer|3DSExplorer v1.1.1]] updated by [[User:Elisherer|elisherer]]
*'''7 December 11''' [[3DSExplorer|3DSExplorer v0.96]] updated by [[User:Elisherer|elisherer]]
*'''4 September 11''' [[3DSViewer|3DSViewer v0.1]] released by [[User:Elisherer|elisherer]]
*'''1 August 11''' [[3DS Save DeEncrypter3DS|Save DeEncrypter v1.0]] released by [[User:Blite|Blite]]
*'''25 July 11''' Nintendo released system update [[2.1.0-4]].
*'''15 June 11''' Nintendo released system update [[2.1.0-3]].
*'''6 June 11''' Nintendo released system update [[2.0.0-2]].
*'''6 April 11''' [[DSaveManager|DSaveManager v0.1]] released by [[User:Crediar|crediar]]
*'''4 April 11''' [[3DSaveTool|3DSaveTool v0.2b]] released by [[User:Crediar|crediar]]
*'''4 April 11''' [[3DSaveTool|3DSaveTool v0.2b]] released by [[User:Crediar|crediar]]
*'''2 April 11''' [[3DSaveTool|3DSaveTool v0.1]] released by [[User:Crediar|crediar]]
*'''28 March 11''' Fixed 3DBrew wiki issues, now fully operational!
*'''18 March 11''' 3DBrew launched.

== 3DBrew International ==
Our community is international community.

We hace freedom,we can express in our language! (but you have to write it in English before;)

News

2012-09-23T10:04:20Z

McHaggis:

<noinclude>
==Adding an item==
* Log in to the wiki. Editing is disabled if you don't have an account.
* Add the news event to the top of the list, using this format for the date: <tt><nowiki>'''</nowiki>{{#time: d F y}}<nowiki>''' </nowiki></tt>. Please include the application's creator, version number, and a link to a page on 3DBrew about the application. No external links please.
* '''Move the last entry to the [[:News/Archive|news archive]]. There should be no more than 4 entrees in the list.'''

==Archives==
For older news, see the [[:News/Archive|news archive]].

=== News ===
</noinclude>
*'''23 September 12''' [[005tools|005tools v0.1b]] by [[User:McHaggis|McHaggis]]
*'''19 September 12''' Nintendo released system update [[4.4.0-10]].
*'''17 August 12''' Nintendo released New Super Mario Bros. 2, the first 3DS title released simultaneously in stores and as an [[eShop]] download.
*'''28 July 12''' [[3DSExplorer|3DSExplorer v1.3]] (modified by 3DSGuy) updated by [[User:Elisherer|Elisherer]]

News

2012-09-23T10:04:05Z

McHaggis:

005tools

2012-09-23T09:50:10Z

McHaggis: Created page with "{{Infobox homebrew | title = 005tools | image = | type = pc utility | author = McHaggis | download = http://filetrip.net/nds-downloads/applications/download-00..."

{{Infobox homebrew
| title = 005tools
| image =
| type = pc utility
| author = [[User:McHaggis|McHaggis]]
| download = http://filetrip.net/nds-downloads/applications/download-005tools-01b-f30775.html
| website =
| version = 0.01b
}}

005tools is a simple command line application designed to work with devices that can transfer game saves from CTR-005 (3DS) and NTR-005 (DS/DSi) game cards to your PC. The source code is platform independent, so it can be compiled to run on any system.

== Supported Devices ==

Currently, the application only supports the R4i Save Dongle. The code is very flexible, so supporting other devices should be fairly straightforward if I can get my hands on one.

== Notes ==

The official R4i software writes 3DS cards in full and then writes the first 16kB ''again''. 005tools mimics this but I haven't bothered to change how the progress bar works, so don't be surprised when the progress bar resets after writing all the data.

Also, when writing 3DS/very large cards on the R4i Save Dongle, you'll notice the progress bar freeze after the first 128kB is written. The official software does the same thing, and writing resumes ~7 seconds later. I have no idea why it does this, but the device actually stops responding during this time, probably doing some processing of it's own.

== Changelog ==

'''v0.01b'''
* Writing to 3DS cards works now
* Improved save size detection for 3DS cards
* Fixed progress bar on Win32
* Added some error detection

'''v0.01a'''
* First version

== Known Issues ==

* Writing to NTR-005 cards smaller than 1kB doesn't work (reading does).
* The official R4i software flags specific games to be treated like CTR cards and very large NTR cards for writing. This isn't implemented in 005tools yet.

== Screenshot ==

[[File:005tools.png]]

File:005tools.png

2012-09-23T09:37:44Z

McHaggis: Screenshot for 005tools by McHaggis

Screenshot for 005tools by McHaggis

Internet Browser

2012-03-21T18:03:00Z

McHaggis: /* Touch/Mouse Events */

The 3DS Internet Browser was added in the June 2011 Update for JPN/EUR/USA.

From the Internet Browser help section:
In compliance with the LGPL, the source code of the OSS is available via the Nintendo website.
This source code can be downloaded here:
[http://mediacontent.nintendo-europe.com/NOE/images/service/OpenSources.zip]

The 3D Internet Browser is [http://en.wikipedia.org/wiki/Netfront Netfront] Browser NX v1.0 based on [http://en.wikipedia.org/wiki/WebKit WebKit] engine.

The browser supports up to 64 bookmarks.

User-agent is (for example)
* '''Mozilla/5.0 (Nintendo 3DS; U; ; fr) Version/1.7412.EU''' ''for a EUR/fr Nintendo 3DS''
* '''Mozilla/5.0 (Nintendo 3DS; U; ; en) Version/1.7455.US''' ''for a USA/en Nintendo 3DS''
* The versions are just for example...

==Web Standards==
*HTML 4.01
*HTML 5 (120/400 score on [http://www.html5test.com HTML5Test.com])
*XHTML 1.1
*CSS 1
*CSS 2.1
*CSS 3 (some functionality is unavailable)
*DOM Levels 1-3
*ECMAScript (partial support for ECMA-262 5th Edition)
*XMLHttpRequest Level 2
*Canvas Element (some functionality is unavailable)

==Protocols==
*HTTP 1.0
*HTTP 1.1
*SSLv3
*TLS 1.0

==Image Formats==
*[[File_Formats|MPO]]
*GIF
*JPEG
*PNG
*BMP
*ICO (some files cannot be displayed)

==Plug-Ins==

Plug-ins (such as Adobe Flash) are not supported.

==Other details==

*It scored 90/100 on [http://acid3.acidtests.org/ Acid3] test
*Images from the Internet can be saved to the [[SD Filesystem|SD Card]] and viewed using the [[Nintendo 3DS Camera]] application.
*Images saved to an [[SD Filesystem|SD Card]] or to the Nintendo 3DS system memory can be uploaded to blogs or other sites that allow the uploading of photos using :
<input type="file" />
* HTML5Test.com say that Drag and drop is supported but it's not (code on WebKit is ready, but it's not implemented on interface of browser)

==Tips==

=== Detect User Agent ===

To detect if the user agent is Nintendo 3DS Browser :

<script type="text/javascript">
if (navigator.userAgent.indexOf('Nintendo 3DS') == -1) { //If the UserAgent is not "Nintendo 3DS"
location.replace('http://www.3dbrew.org'); //Redirect to an other page
}
</script>

* You can check <em>navigator.platform=="Nintendo 3DS"</em> as well.

=== Scrolling ===

Scrolling can be altered by modifying <em>document.body.scrollTop</em> and <em>document.body.scrollLeft</em>. However, there are drawbacks related to working with these properties:

* Both properties return 0 when accessed
* Setting one property resets the other property's scroll position

In order to set both at the same time (without either resetting to 0), use <em>window.scrollTo</em>.

=== Events ===
==== Key Events ====
The following buttons trigger the <em>onkeydown</em>, <em>onkeypress</em> and <em>onkeyup</em> events:

{|class="wikitable" width="20%"
! Code !! Button
|-
| 13 || A
|-
| 37 || Left
|-
| 38 || Up
|-
| 39 || Right
|-
| 40 || Down
|}

The events cannot have their default action cancelled. Other buttons do not trigger key events.

==== Touch/Mouse Events ====
<em>onmousedown</em>, <em>onmouseup</em> & <em>onclick</em> are all triggered by the browser. However, the <em>onmousedown</em> event doesn't trigger until you lift the stylus or you've held it on the screen for ~2 seconds—which is when text selection mode is activated—making it pretty much the same as <em>onmouseup</em>. The events cannot have their default action cancelled.

The <em>onmousemove</em> and common touch/gesture events are not supported.

== Screen Resolution ==

The up screen resolution is 400×240. However, the viewable area in the browser is only <b>400×220</b>.

The touch screen resolution is 320×240. However, the viewable area in the browser is only <b>320×212</b>.

You can have a page span both screens. However, the browser will behave as if the bottom screen is the only active screen and the top screen is scrolled off. This is important when computing CSS coordinates. Items positioned from "bottom" will be positioned based on 220px and not the full 432px of both screens.

== Using Both Screens ==

Generally the easiest way to accomplish the correct layout is to create HTML elements that "contain" the top and bottom screens. Here's an example:

<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=400">
<style>
body { margin: 0px; }
#topscreen { width: 400px; height: 220px; overflow: hidden; }
#bottomscreen { width: 320px; height: 212px; overflow: hidden; margin: 0 auto; }
</style>
</head>
<body>
<div id="topscreen">Top Screen</div>
<div id="bottomscreen">Bottom Screen</div>
</body>
</html>

This scheme allows the page to be easily manipulated through JavaScript. In order to have the window snap to the correct position, use the following JavaScript code:

window.setInterval(function () {
window.scrollTo(40, 220);
}, 50);

This automatically resets the position if the user accidentally scrolls the page.

==Example Sites==

* [http://geekshadow.com/gaming/dev/weaponscolors/3DS/ Weapons and Colors] (Short URL for 3DS : http://bit.ly/3DSwc)
* [http://3ds.andysmith.co.uk/jFox.html jFox] (Short URL for 3DS : http://bit.ly/iB7FqW)
* [http://ditto3d.com/3ds Ditto3D]
* [http://www.nintendo.com/3ds/internetbrowser/bookmarks Nintendo 3DS Bookmarks] - This is the first bookmark pre-installed in the browser.

Internet Browser

2012-03-21T11:41:24Z

McHaggis: /* Using Both Screens */ DOCTYPE should be used to prevent quirks mode

The 3DS Internet Browser was added in the June 2011 Update for JPN/EUR/USA.

From the Internet Browser help section:
In compliance with the LGPL, the source code of the OSS is available via the Nintendo website.
This source code can be downloaded here:
[http://mediacontent.nintendo-europe.com/NOE/images/service/OpenSources.zip]

The 3D Internet Browser is [http://en.wikipedia.org/wiki/Netfront Netfront] Browser NX v1.0 based on [http://en.wikipedia.org/wiki/WebKit WebKit] engine.

The browser supports up to 64 bookmarks.

User-agent is (for example)
* '''Mozilla/5.0 (Nintendo 3DS; U; ; fr) Version/1.7412.EU''' ''for a EUR/fr Nintendo 3DS''
* '''Mozilla/5.0 (Nintendo 3DS; U; ; en) Version/1.7455.US''' ''for a USA/en Nintendo 3DS''
* The versions are just for example...

==Web Standards==
*HTML 4.01
*HTML 5 (120/400 score on [http://www.html5test.com HTML5Test.com])
*XHTML 1.1
*CSS 1
*CSS 2.1
*CSS 3 (some functionality is unavailable)
*DOM Levels 1-3
*ECMAScript (partial support for ECMA-262 5th Edition)
*XMLHttpRequest Level 2
*Canvas Element (some functionality is unavailable)

==Protocols==
*HTTP 1.0
*HTTP 1.1
*SSLv3
*TLS 1.0

==Image Formats==
*[[File_Formats|MPO]]
*GIF
*JPEG
*PNG
*BMP
*ICO (some files cannot be displayed)

==Plug-Ins==

Plug-ins (such as Adobe Flash) are not supported.

==Other details==

*It scored 90/100 on [http://acid3.acidtests.org/ Acid3] test
*Images from the Internet can be saved to the [[SD Filesystem|SD Card]] and viewed using the [[Nintendo 3DS Camera]] application.
*Images saved to an [[SD Filesystem|SD Card]] or to the Nintendo 3DS system memory can be uploaded to blogs or other sites that allow the uploading of photos using :
<input type="file" />
* HTML5Test.com say that Drag and drop is supported but it's not (code on WebKit is ready, but it's not implemented on interface of browser)

==Tips==

=== Detect User Agent ===

To detect if the user agent is Nintendo 3DS Browser :

<script type="text/javascript">
if (navigator.userAgent.indexOf('Nintendo 3DS') == -1) { //If the UserAgent is not "Nintendo 3DS"
location.replace('http://www.3dbrew.org'); //Redirect to an other page
}
</script>

* You can check <em>navigator.platform=="Nintendo 3DS"</em> as well.

=== Scrolling ===

Scrolling can be altered by modifying <em>document.body.scrollTop</em> and <em>document.body.scrollLeft</em>. However, there are drawbacks related to working with these properties:

* Both properties return 0 when accessed
* Setting one property resets the other property's scroll position

In order to set both at the same time (without either resetting to 0), use <em>window.scrollTo</em>.

=== Events ===
==== Key Events ====
The following buttons trigger the <em>onkeydown</em>, <em>onkeypress</em> and <em>onkeyup</em> events:

{|class="wikitable" width="20%"
! Code !! Button
|-
| 13 || A
|-
| 37 || Left
|-
| 38 || Up
|-
| 39 || Right
|-
| 40 || Down
|}

The events cannot have their default action cancelled. Other buttons do not trigger key events.

==== Touch/Mouse Events ====
<em>onmousedown</em>, <em>onmouseup</em> & <em>onclick</em> are all triggered by the browser. However, the <em>onmousedown</em> event doesn't trigger until you've held the stylus on the screen for ~2 seconds, which is when text selection mode is activated. The events cannot have their default action cancelled.

The <em>onmousemove</em> and common touch/gesture events are not supported.

== Screen Resolution ==

The up screen resolution is 400×240. However, the viewable area in the browser is only <b>400×220</b>.

The touch screen resolution is 320×240. However, the viewable area in the browser is only <b>320×212</b>.

You can have a page span both screens. However, the browser will behave as if the bottom screen is the only active screen and the top screen is scrolled off. This is important when computing CSS coordinates. Items positioned from "bottom" will be positioned based on 220px and not the full 432px of both screens.

== Using Both Screens ==

Generally the easiest way to accomplish the correct layout is to create HTML elements that "contain" the top and bottom screens. Here's an example:

<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=400">
<style>
body { margin: 0px; }
#topscreen { width: 400px; height: 220px; overflow: hidden; }
#bottomscreen { width: 320px; height: 212px; overflow: hidden; margin: 0 auto; }
</style>
</head>
<body>
<div id="topscreen">Top Screen</div>
<div id="bottomscreen">Bottom Screen</div>
</body>
</html>

This scheme allows the page to be easily manipulated through JavaScript. In order to have the window snap to the correct position, use the following JavaScript code:

window.setInterval(function () {
window.scrollTo(40, 220);
}, 50);

This automatically resets the position if the user accidentally scrolls the page.

==Example Sites==

* [http://geekshadow.com/gaming/dev/weaponscolors/3DS/ Weapons and Colors] (Short URL for 3DS : http://bit.ly/3DSwc)
* [http://3ds.andysmith.co.uk/jFox.html jFox] (Short URL for 3DS : http://bit.ly/iB7FqW)
* [http://ditto3d.com/3ds Ditto3D]
* [http://www.nintendo.com/3ds/internetbrowser/bookmarks Nintendo 3DS Bookmarks] - This is the first bookmark pre-installed in the browser.

Internet Browser

2012-03-21T11:31:00Z

McHaggis: General improvements, updated the dual screen view code and added a little of my own research

The 3DS Internet Browser was added in the June 2011 Update for JPN/EUR/USA.

From the Internet Browser help section:
In compliance with the LGPL, the source code of the OSS is available via the Nintendo website.
This source code can be downloaded here:
[http://mediacontent.nintendo-europe.com/NOE/images/service/OpenSources.zip]

The 3D Internet Browser is [http://en.wikipedia.org/wiki/Netfront Netfront] Browser NX v1.0 based on [http://en.wikipedia.org/wiki/WebKit WebKit] engine.

The browser supports up to 64 bookmarks.

User-agent is (for example)
* '''Mozilla/5.0 (Nintendo 3DS; U; ; fr) Version/1.7412.EU''' ''for a EUR/fr Nintendo 3DS''
* '''Mozilla/5.0 (Nintendo 3DS; U; ; en) Version/1.7455.US''' ''for a USA/en Nintendo 3DS''
* The versions are just for example...

==Web Standards==
*HTML 4.01
*HTML 5 (120/400 score on [http://www.html5test.com HTML5Test.com])
*XHTML 1.1
*CSS 1
*CSS 2.1
*CSS 3 (some functionality is unavailable)
*DOM Levels 1-3
*ECMAScript (partial support for ECMA-262 5th Edition)
*XMLHttpRequest Level 2
*Canvas Element (some functionality is unavailable)

==Protocols==
*HTTP 1.0
*HTTP 1.1
*SSLv3
*TLS 1.0

==Image Formats==
*[[File_Formats|MPO]]
*GIF
*JPEG
*PNG
*BMP
*ICO (some files cannot be displayed)

==Plug-Ins==

Plug-ins (such as Adobe Flash) are not supported.

==Other details==

*It scored 90/100 on [http://acid3.acidtests.org/ Acid3] test
*Images from the Internet can be saved to the [[SD Filesystem|SD Card]] and viewed using the [[Nintendo 3DS Camera]] application.
*Images saved to an [[SD Filesystem|SD Card]] or to the Nintendo 3DS system memory can be uploaded to blogs or other sites that allow the uploading of photos using :
<input type="file" />
* HTML5Test.com say that Drag and drop is supported but it's not (code on WebKit is ready, but it's not implemented on interface of browser)

==Tips==

=== Detect User Agent ===

To detect if the user agent is Nintendo 3DS Browser :

<script type="text/javascript">
if (navigator.userAgent.indexOf('Nintendo 3DS') == -1) { //If the UserAgent is not "Nintendo 3DS"
location.replace('http://www.3dbrew.org'); //Redirect to an other page
}
</script>

* You can check <em>navigator.platform=="Nintendo 3DS"</em> as well.

=== Scrolling ===

Scrolling can be altered by modifying <em>document.body.scrollTop</em> and <em>document.body.scrollLeft</em>. However, there are drawbacks related to working with these properties:

* Both properties return 0 when accessed
* Setting one property resets the other property's scroll position

In order to set both at the same time (without either resetting to 0), use <em>window.scrollTo</em>.

=== Events ===
==== Key Events ====
The following buttons trigger the <em>onkeydown</em>, <em>onkeypress</em> and <em>onkeyup</em> events:

{|class="wikitable" width="20%"
! Code !! Button
|-
| 13 || A
|-
| 37 || Left
|-
| 38 || Up
|-
| 39 || Right
|-
| 40 || Down
|}

The events cannot have their default action cancelled. Other buttons do not trigger key events.

==== Touch/Mouse Events ====
<em>onmousedown</em>, <em>onmouseup</em> & <em>onclick</em> are all triggered by the browser. However, the <em>onmousedown</em> event doesn't trigger until you've held the stylus on the screen for ~2 seconds, which is when text selection mode is activated. The events cannot have their default action cancelled.

The <em>onmousemove</em> and common touch/gesture events are not supported.

== Screen Resolution ==

The up screen resolution is 400×240. However, the viewable area in the browser is only <b>400×220</b>.

The touch screen resolution is 320×240. However, the viewable area in the browser is only <b>320×212</b>.

You can have a page span both screens. However, the browser will behave as if the bottom screen is the only active screen and the top screen is scrolled off. This is important when computing CSS coordinates. Items positioned from "bottom" will be positioned based on 220px and not the full 432px of both screens.

== Using Both Screens ==

Generally the easiest way to accomplish the correct layout is to create HTML elements that "contain" the top and bottom screens. Here's an example:

<html>
<head>
<meta name="viewport" content="width=400">
<style>
body { margin: 0px; }
#topscreen { width: 400px; height: 220px; overflow: hidden; }
#bottomscreen { width: 320px; height: 212px; overflow: hidden; margin: 0 auto; }
</style>
</head>
<body>
<div id="topscreen">Top Screen</div>
<div id="bottomscreen">Bottom Screen</div>
</body>
</html>

This scheme allows the page to be easily manipulated through JavaScript. In order to have the window snap to the correct position, use the following JavaScript code:

window.setInterval(function () {
window.scrollTo(40, 220);
}, 50);

This automatically resets the position if the user accidentally scrolls the page.

==Example Sites==

* [http://geekshadow.com/gaming/dev/weaponscolors/3DS/ Weapons and Colors] (Short URL for 3DS : http://bit.ly/3DSwc)
* [http://3ds.andysmith.co.uk/jFox.html jFox] (Short URL for 3DS : http://bit.ly/iB7FqW)
* [http://ditto3d.com/3ds Ditto3D]
* [http://www.nintendo.com/3ds/internetbrowser/bookmarks Nintendo 3DS Bookmarks] - This is the first bookmark pre-installed in the browser.