The t2-start's discuss from tessel

Clean up Linux tab of Command Line Basics

The Linux tab at the Command Line Basics page uses Mac descriptions, but Windows command line screenshots, this should get its proper, linux/unix-based instructions.

render blocks of bash script so they look different from javascript code blocks

they currently don't function (see #40)

Change EACCES hint on OSX install instructions

Our current instructions for working around npm permissions errors might be too specific:

It would probably be better to link to npm's official docs on the subject. (Thanks @wyze for mentioning these, didn't realize they existed.)

Add a page about GPIO and community modules

Camera tutorial is a little unfinished

@rwaldron somehow this slipped by both of us :/

The all-caps section for the bonus is a note to self fill-in-the-blanks. And the formatting is kinda wonky. Whoops.

I can attack this later today.

Make the ports more obviously A and B

Currently this image

is pretty good but not obvious enough.

Would help to:

Separate out the bubbles
Make the magnification break the plane of the board so it's more noticeable

Add a section to show how access points work & what they're good for

Would be cool to showcase this new use case in the start experience. @HipsterBrown any thoughts on what this should include?

Confused about instructions for setup

New user here. I was following the instructions for "Find Your Tessel" and was a little confused when it returned multiple Tessels:

I didn't realize that other Tessels on the LAN would be returned. Maybe clarify that the USB connection is the one new users are looking for.

blinky example doesn't match t2 init

Out put from t2 init and the code paste on http://tessel.github.io/t2-start/blinky.html are different. Need to update the blinky code on http://tessel.github.io/t2-start/blinky.html to match t2 init

formatting is inconsistent

CLI commands vs .js lines of code aren't consistently formatted (mostly just CLI commands are all over the map)

build fails on linux if $HOME/.node-gyp doesn't exist

it was solved by creating the folder and re running the command

> [email protected] install /usr/local/lib/node_modules/t2-cli/node_modules/usb
> node-pre-gyp install --fallback-to-build

gyp WARN EACCES user "root" does not have permission to access the dev dir "/home/mariano/.node-gyp/4.2.6"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/t2-cli/node_modules/usb/.node-gyp"
make: Entering directory '/usr/local/lib/node_modules/t2-cli/node_modules/usb/build'
make: *** No rule to make target '../.node-gyp/4.2.6/include/node/common.gypi', needed by 'Makefile'.  Stop.
make: Leaving directory '/usr/local/lib/node_modules/t2-cli/node_modules/usb/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/t2-cli/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.0-18-generic
gyp ERR! command "/usr/bin/nodejs" "/usr/local/lib/node_modules/t2-cli/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/usr/local/lib/node_modules/t2-cli/node_modules/usb/src/binding/usb_bindings.node" "--module_name=usb_bindings" "--module_path=/usr/local/lib/node_modules/t2-cli/node_modules/usb/src/binding"
gyp ERR! cwd /usr/local/lib/node_modules/t2-cli/node_modules/usb
gyp ERR! node -v v4.2.6
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/nodejs /usr/local/lib/node_modules/t2-cli/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/local/lib/node_modules/t2-cli/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/usr/local/lib/node_modules/t2-cli/node_modules/usb/src/binding' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/t2-cli/node_modules/usb/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:821:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Linux 4.4.0-18-generic
node-pre-gyp ERR! command "/usr/bin/nodejs" "/usr/local/lib/node_modules/t2-cli/node_modules/usb/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /usr/local/lib/node_modules/t2-cli/node_modules/usb
node-pre-gyp ERR! node -v v4.2.6
node-pre-gyp ERR! node-pre-gyp -v v0.6.24
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/nodejs /usr/local/lib/node_modules/t2-cli/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/local/lib/node_modules/t2-cli/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/usr/local/lib/node_modules/t2-cli/node_modules/usb/src/binding' (1)
/usr/local/lib
└── (empty)

npm ERR! Linux 4.4.0-18-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "t2-cli"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the usb package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs usb
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls usb
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/mariano/npm-debug.log
npm ERR! code 1

How to run a local version of this?

Should have this in the readme

Installation: It might be better to use nvm

I have found that if I use the instructions at

https://github.com/tessel/t2-start/blame/gh-pages/install.md#L35

I end up having permission problems when I subsequently try to npm install t2-cli. It might be better to use

https://github.com/creationix/nvm#install-script

On Windows the code blocks are displayed in serif fonts

Apparently the source overrides all code block formatting for the font-family with "Andale Mono", which, if unavailable for the system, falls back (with no fallback) to a serif font.

Forum links for modules are broken

via @snollygolly: "About half of the modules have forum links which are broken."

Document a good way to make GIFs for the module pages

As mentioned in #16, we need to update our output GIFs. We let them slide with the out-of-date terminal for a while, but now it's pretty blatant because the hardware looks different:

Like this one from http://tessel.github.io/t2-start/modules/rfid.html:

We should document a method in the README for how to do this.

I made these original ones. Here's what I remember:

Video from a camera
Screen captures made in Quicktime
I made the terminal text super CTRL + + so it would show up in a tiny GIF
Spliced together videos in probably iMovie or something
These excellent command line tools http://parkerhiggins.net/2012/10/howto-create-an-animated-gif-from-a-video-with-command-line-tools/
Manually deleting frames to make them smaller - yes I know there's a better way
Host the images on S3, though now we use Imgur (see #16)

To complete this issue, PR the readme with a process as good as or better than mine. 💃

footer starts in the wrong place

like this

What should be in the T2 start experience?

Let's start this discussion.

Hello world blinky
Hello internet– connect & tweet
Regular modules
USB modules
Module ports as pins?
Page of community modules

Update default Twitter handle in Twitter example

Page: http://tessel.github.io/t2-start/tweet.html

since we've recently transitioned to @tesselproject from @technicalhumans we need to change the example code to match.

Make Windows prerequisites more clear

Windows users apparently need to have:

Python 2.7 or greater
Visual Studio or a C++ compiler from somewhere else

link highlighting on the left nav bar doesn't work

Like this:

Proposed patch: get rid of nav highlighting. Then we can add this back in as an enhancement later.

Host all images on imgur

All images are currently hosted in S3 which is a little less than ideal, especially for contribution sake.

Should we move these? Should we use an infinite image host like imgur? Should we hack Github to support our binary image habit?

Strip Tessel header and footer.

When this repo is integrated into the main website, we can automatically apply the proper Tessel header/footer (we'll switch the URL to http://tessel.io/start for this case)

We want a much cleaner look, i.e. http://rustbyexample.com/

images are of T1

action: replace them. Needed image assets:

install tabs are broken

these tabs:

If you click on them, you get the div in the URL but the tab doesn't change

Make this the page that tessel.io/start goes to

Make all the views Markdown

Jade is used extensively in the rest of Tessel's web properties. Do we want to use that as a publishing mechanism too?

This would require a publish step before uploading new changes, which is a little less magic than gh-pages automatically publishing. OTOH, it's very straightforward. And HTML is hard to manually touch.

BLE instructions are old

They should no longer have a section about obtaining root and running hciconfig

Formatting on "view on Github" is strange

you can see this on every module page

fix: make it a sans serif font in a similar style to the rest of the page

Update process doesn't mention provisioning device

Add a favicon

Remove irrelevant tenpin modules

"tessel list" does not return connections

running t2 list can not find the tessel connected to same wifi network that the computer is connected over. Amber light is blinking which is supposed to mean it's connected. There is only a single wifi network at my location. Running t2 wifi -n {network} -p {password} returns: WIFI enabled, WIFI connected. SSID:{network name}, password: {password}, security: psk2. But then t2 list only shows the usb connection.

Climate module docs use image of climate-si7005

http://tessel.github.io/t2-start/modules/climate.html has an image in step 3 of a si-7005, but the instructions reference a si-7020. The image should probably be updated, and the open question is whether the si-7005 should even be mentioned. I have one, which is why I noticed.

Linux Node install instructions are outdated

We currently encourage Linux users to run sudo apt-get install nodejs but that will install an old version (0.10.x I believe?). We may want to update that to point to this link.

document need to use Node below 4.x

Until tessel/t2-cli#321 is fixed

Should go on page http://tessel.github.io/t2-start/

nvm module is a good way to do this

Tessel 2 start experience links to T1 start incorrectly

it goes to tessel.io/start but needs to go to tessel.io/t1-start

add highlighting of active link on the left nav bar

add class "active" when that link is active

Rearrange start experience based on USB-only update?

Do we want any changes to the T2 start experience based on tessel/t2-cli#595?

We have currently arranged the start experience to require people to get Tessel online before they update. In Tessel 1, updates happened on the same page as installation.

Moving update back to the first page

Creates a cleaner divide between "I am installing things" and "I am using the Tessel 2" (which also affords us more flexibility if e.g. we want to put module usage before Wifi usage)
Let us put Blinky earlier - a first success before Wifi connection or trying to get lists working
Makes the installation phase take longer
Rearranges a start experience that may already be familiar to people

The purpose of the first run is to create success as quickly as possible, so:

How confident are we that t2 update will be successful for people?
How confident are we about Wifi connection will be a success?
Do we need people to update in order for Blinky to work?

Any thoughts on the matter (@johnnyman727 @rwaldron @tcr @HipsterBrown @flaki in particular)?

Add a link from this start experience to T1 start

Remove `--slim` from start experience

it's default now tessel/t2-cli#420 (comment)

depends on a CLI release

OS X 10.11.4 or better is required for Tessel USB support

Once Node.js and npm are installed to OS X, unless you are at 10.11.4 or better trying to enumerate Tessel 2 devices on USB will deadlock in the kernel.

(See here: https://forums.tessel.io/t/tessel-on-os-x-el-capitan/2298)

The node process will be stuck, and the CPU use for the kernel will spike to 100% and stay there. You will have to reboot the box to clear this up. Attempting to kill the locked node process just causes it to turn into a zombie process.

The kernel is spinning on something in the USB subsystem. I apologize for not getting the "sample" output these offending processes.

Over on the Tessel forums I was referred to this USB OS X issue which seems relevant.

Upgrading to 10.11.4 (which I was not automatically notified of, otherwise I probably would have already accepted it!) solve the problem and allowed me to enumerate and provision the Tessel device via t2.

Add web example

Calling an API, e.g. Twitter, PubNub, something like that.

Switch to Jekyll publishing system

Because we want simplest ease of contribution as possible, gh-pages should be an explicit target (so people can fork, test, then merge). Jekyll publishing is the appropriate choice.

Docs link should go somewhere T2-relevant

or perhaps tessel.io/docs should become T2 relevant.

For now probably https://github.com/tessel/t2-firmware#t2-hardware-api as the endpoint

Multiple language support

How do we show a Rust getting started, JS getting started?

Somewhat relatedly, what about foreign languages – is this something we want to support at all?

(right now we have:

)

npm install -g t2-cli fails without "sudo" on OSX due to no access to /usr/local/bin

Even with proper ~/.npm permissions, one needs sudo anyway, because otherwise install -g fails due to not being able to access /usr/local/bin/t2:

npm ERR! Error: EACCES, unlink '/usr/local/bin/t2'
npm ERR!     at Error (native)
npm ERR!  { [Error: EACCES, unlink '/usr/local/bin/t2'] errno: -13, code: 'EACCES', path: '/usr/local/bin/t2' }

Convert this into a Gitbook?

This is a possibility, and gives us the benefit of depending on some open source (supported) code rather than our own concoction.

/cc @Frijol for thoughts

tessel / t2-start Goto Github PK

t2-start's Issues

Recommend Projects

Recommend Topics

Recommend Org