Giter VIP home page Giter VIP logo

processing-docs's Introduction

⚠️ This repository is now deprecated and will be archived soon. If you have any issues or want to submit a pull request, please direct them to the processing-website repo. Make sure to check the README for information on how to contribute to the documentation.

Processing Documentation

This is the official source code for the Processing reference, examples, tutorials, and processing.org web site.

If you have found an error in the Processing reference, examples, tutorials, or website you can file it here under the "issues" tab.

The processing repository contains the source code for Processing itself. (Please use that link to file issues regarding the Processing software.)

processing-docs's People

Contributors

amnonowed avatar benfry avatar codeanticode avatar deannalam avatar filip avatar fjenett avatar gabbar1947 avatar gohai avatar jakubvaltar avatar jeremydouglass avatar jkosoy avatar jongacnik avatar kayserifserif avatar kevinstadler avatar lennyjpg avatar ndeleon avatar peskal avatar philiprugo avatar prisonerjohn avatar reas avatar sableraf avatar sansumbrella avatar scotthmurray avatar shiffman avatar sojamo avatar speclad avatar tyler-yin avatar v3ga avatar wirsing avatar ybakos avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

processing-docs's Issues

Attempt to donate via PayPal fails

Issue by alignedleft
Monday Apr 28, 2014 at 01:40 GMT
Originally opened as processing/processing-web-archive#396


On the Download page, an attempt to donate via PayPal may occasionally fail before relaying the visitor to PayPal's site, instead displaying an otherwise empty page with the text Error:Array([0]=>). See screenshot from Firefox:

processing-error

This issue first reported by a site visitor on April 17, and subsequently reproduced by me in Firefox and Safari.

https://processing.org/download/

@amongiants Could you look into it? I don't know if this was a temporary issue on the PayPal side, or something on our end.

new PJOGL class

Issue by mckennapsean
Monday Nov 04, 2013 at 22:26 GMT
Originally opened as processing/processing-web-archive#281


Processing 2.1 introduced a new PJOGL extended class over the PGL class. This changes how you get a GL2 object in Processing, from what I can gather.

I could find no documentation of these changes online, such as on the Processing wiki. I wasn't sure where else to post this (or if I could contribute to it, or not).

Basically, you have to change how you get a GL2 object:

GL2 gl = ((PJOGL) pgl.beginPGL()).gl.getGL2();

I am unclear if there is any way to make this backwards-compatible, which is a bit unfortunate if it is not possible.

In fact, it appears that even the Javadoc online is out-of-date for this change (no PJOGL). Fortunately, the codebase has an updated copy on Github.

Perlin noise documentation

Issue by solsword
Friday May 30, 2014 at 05:44 GMT
Originally opened as processing/processing-web-archive#423


The documentation for the noise() function claims that it is a Perlin noise implementation. Actually, the noise function it implements is value noise [1], which is not nearly as good for most applications as real Perlin noise (see a comparison at [2]). The documentation should be updated to reflect this, especially given the frequent confusion of value noise and Perlin noise and the fact that Processing is probably for many their first introduction to the concept of continuous noise functions.

[1] http://en.wikipedia.org/wiki/Value_noise
[2] http://imgur.com/guiiWRU

reference - relations

Issue by allonestring
Wednesday Jan 22, 2014 at 21:02 GMT
Originally opened as processing/processing-web-archive#336


Showing related commands gives beginners (and not so beginners) the opportunity to expand their repertoire, so can I suggest more ...

• it would be nice if stroke() had strokeJoin() and strokeCap() in its related section

• though they mention each other in the text, it would be nice to have size(), width and height related to each other

• similarly, frameRate, frameRate() and frameCount

misleading description of reverse() in FloatList, IntList

Issue by bkgray
Monday May 19, 2014 at 15:46 GMT
Originally opened as processing/processing-web-archive#422


The description for reverse() on FloatList and IntList reference pages ( /reference/FloatList.html and /reference/IntList.html) is:

reverse() Reverse sort, orders values by first digit

This is not a valid description. There is no sorting involved. The method simply reverses the order of the elements in the list. The description on the reference page for the method is correct.

RSS feed is broken?

Issue by JobLeonard
Wednesday Apr 23, 2014 at 12:12 GMT
Originally opened as processing/processing-web-archive#388


I used to have an RSS feed for the main website, getting updates about... well, anything posted there really. It seems it has been removed? Is it possible to get it back, as it is my preferred way to stay up-to-date.

Bring back Alphabetical Reference

Issue by MAKIO135
Monday Jun 10, 2013 at 18:09 GMT
Originally opened as processing/processing-web-archive#183


When looking for the doc of a specific method, reference ordered by name (as it was previously in the reference/alpha.html) is way faster.

Having it back would be great. And it should be quick and easy since the alpha.html page comes with the new release inside processing-2.0/modes/java/reference/alpha.html

blendMode does not mention blending happens per channel

Issue by hamoid
Sunday May 04, 2014 at 13:56 GMT
Originally opened as processing/processing-web-archive#413


I think it might be good to mention in the documentation that blending operations are done on each channel separately. Red is compared with red, green with green, blue with blue.

From http://processing.org/reference/blendMode_.html , "only the lightest colour succeeds" may lead to believe that when blending two colors using LIGHTEST or DARKEST, it will result in one of the two original colors (the lighter one or the darker one). The truth is that we may get a third color, which is the combination of both. "#FF00FF LIGHTEST #008800" results in #FF88FF (and not in the brighter of the two colors, which is #FF00FF), because each channel is processed separately.

Here one might expect to see the magenta prevail because the green box is darker:

size(100, 100, P2D); // (JAVA2D + blendMode = unexpected stuff)
background(0);
noStroke();
blendMode(LIGHTEST);
fill(#FF00FF);
rect(10, 10, 60, 60);
fill(#008800);
rect(30, 30, 60, 60);

a

online Processing reference doesn't list client.active() property of Client however property exists.

Issue by edickins
Sunday Jul 14, 2013 at 12:00 GMT
Originally opened as processing/processing-web-archive#221


Hi

I was looking to see if the Net.Client class throws errors and found this post http://processing.org/discourse/beta/num_1221502447.html which explains that it doesn't.

An answer in that thread recommends 'use client.active() to determine whether the client has failed/disconnected/whatever.'.

The client.active() property is not listed in the online Processing reference and thought I would post here in case it is an oversight that it is missing from the reference.

Processing: Android Tutorial Issue

Issue by Voltarr
Thursday Oct 10, 2013 at 04:19 GMT
Originally opened as processing/processing-web-archive#267


Hi,
Noticing that when switching to Android mode and hitting run you can get the following error which you might want to include in the tutorial:

BUILD FAILED
/Applications/adt-bundle-mac-x86_64-20130917/sdk/tools/ant/build.xml:542: Unable to resolve project target 'android-10'

when the SDK gets installed, it installs the latest API 18. I had to go back and manually install the older API 10 [Android 2.3.3]. That got me further along and I didn't get the same error but now it says: "Waiting for device....Lost connection with device while launching. Try again." Then the console says, "Shutting down my adb server"

Help...

Local reference pages use incorrect paths to jQuery and font files

Issue by alignedleft
Tuesday Apr 15, 2014 at 19:59 GMT
Originally opened as processing/processing-web-archive#384


The reference as published on processing.org correctly references jQuery and web font files, but the version compiled for local use fails to use local paths. Note these errors shown in the console when viewing local reference pages:

From Safari:
pastedgraphic-1

From Chrome:
screen shot 2014-04-15 at 12 48 44 pm

This has at least two negative impacts:

  1. Local reference pages are sometimes very slow (5-10 seconds) to load and render in Safari and Firefox. My hunch is that they have a long timeout and wait a few seconds before giving up on loading the external files. (There is no noticeable delay in Chrome.)

  2. Italicized text is not shown as such, because the italic version The Serif isn't loaded. For example, here is a paragraph from the sphereDetail() page on the website. Note the italics that are (correctly) visible in the phrase "…and so should not be called prior…"

screen shot 2014-04-15 at 12 52 39 pm

Here is the same paragraph, as seen in the local reference. Note that italics are (incorrectly) absent.

screen shot 2014-04-15 at 12 52 31 pm

This issue may be related to:

processing/processing-web-archive#162
processing/processing-web-archive#163
processing/processing-web-archive#353

@amongiants Can you take a look at this, or point me to where the local reference paths are set?

Enhance reference for beginContour() endContour

Issue by firlifanz
Saturday May 10, 2014 at 20:51 GMT
Originally opened as processing/processing-web-archive#417


I tried to create a ring using beginContour and endContour. I found out, that it is important to draw the outer shape e.g. in clockwise direction and the inner shape in counter clockwise direction to create a hole in the shape. I think this fact should be mentioned in the reference.
Demo Sketch:
/** RingDemo may/10/2014 by Peter Bosshard Schneider

  • A contribution to the reference of processing stating that it is important
  • to draw the inner contour of a combined shape counter clockwise to the outer shape.*/

float inner_radius, outer_radius; // inner and outer radius
float cp1_x, cp2_x, cp3_x, cp4_x; // control points x
float cp1_y, cp2_y, cp3_y, cp4_y; // control points y
float ap1_x, ap2_x, ap3_x, ap4_x; // anchor points x
float ap1_y, ap2_y, ap3_y, ap4_y; // anchor points y
float cx_1, cx_2, cy_1, cy_2; // center of the rings
float ring_width = 50; // ring width
float cpd = 8; // control points diameter
float apd = 10; // anchor points diameter

void setup() {
size(600, 300);
background(0);

// outer and inner radius of the rings
outer_radius = width*0.2;
inner_radius = outer_radius - ring_width;

// center of the rings
cx_1 = width/4;
cx_2 = width/4*3;
cy_1 = cy_2 = height/2;
}

void draw() {
background(0);
rectMode(CENTER);

//draw a rectangle in the background
fill(0,180,255);
noStroke();
rect(width/2,height/2,width_0.6,height_0.6);

// left ring
pushMatrix();
translate(cx_1, cy_1);

//outer circle
ap1_x = 0;
ap1_y = -outer_radius;
ap2_x = outer_radius;
ap2_y = 0;
ap3_x = 0;
ap3_y = outer_radius;
ap4_x = -outer_radius;
ap4_y = 0;
cp1_x = -outer_radius;
cp1_y = -outer_radius;
cp2_x = outer_radius;
cp2_y = -outer_radius;
cp3_x = outer_radius;
cp3_y = outer_radius;
cp4_x = -outer_radius;
cp4_y = outer_radius;

// draw achor points of left outercircle
noFill();
stroke(0, 255, 0);
ellipse(ap1_x, ap1_y, apd, apd);
ellipse(ap2_x, ap2_y, apd, apd);
ellipse(ap3_x, ap3_y, apd, apd);
ellipse(ap4_x, ap4_y, apd, apd);

// draw control points of left outer circle
stroke(255, 0, 0);
ellipse(cp1_x, cp1_y, cpd, cpd);
ellipse(cp2_x, cp2_y, cpd, cpd);
ellipse(cp3_x, cp3_y, cpd, cpd);
ellipse(cp4_x, cp4_y, cpd, cpd);

// draw lines between anchor points and control points
stroke(255, 180, 0);
line(ap1_x, ap1_y, cp1_x, cp1_y);
line(ap2_x, ap2_y, cp2_x, cp2_y);
line(ap3_x, ap3_y, cp3_x, cp3_y);
line(ap4_x, ap4_y, cp4_x, cp4_y);

// draw outer circle clockwise
stroke(255);
fill(153,100);

beginShape();
vertex(ap1_x, ap1_y);
bezierVertex(ap1_x, ap1_y, cp2_x, cp2_y, ap2_x, ap2_y);
bezierVertex(ap2_x, ap2_y, cp3_x, cp3_y, ap3_x, ap3_y);
bezierVertex(ap3_x, ap3_y, cp4_x, cp4_y, ap4_x, ap4_y);
bezierVertex(ap4_x, ap4_y, cp1_x, cp1_y, ap1_x, ap1_y);

// inner left circle
ap1_x = 0;
ap1_y = -inner_radius;
ap2_x = inner_radius;
ap2_y = 0;
ap3_x = 0;
ap3_y = inner_radius;
ap4_x = -inner_radius;
ap4_y = 0;
cp1_x = -inner_radius;
cp1_y = -inner_radius;
cp2_x = inner_radius;
cp2_y = -inner_radius;
cp3_x = inner_radius;
cp3_y = inner_radius;
cp4_x = -inner_radius;
cp4_y = inner_radius;

beginContour();
// draw inner circle clockwise
vertex(ap1_x, ap1_y);
bezierVertex(ap1_x, ap1_y, cp2_x, cp2_y, ap2_x, ap2_y);
bezierVertex(ap2_x, ap2_y, cp3_x, cp3_y, ap3_x, ap3_y);
bezierVertex(ap3_x, ap3_y, cp4_x, cp4_y, ap4_x, ap4_y);
bezierVertex(ap4_x, ap4_y, cp1_x, cp1_y, ap1_x, ap1_y);
endContour();
endShape(CLOSE);

// draw achor points of left inner circle
noFill();
stroke(0, 255, 0);
ellipse(ap1_x, ap1_y, apd, apd);
ellipse(ap2_x, ap2_y, apd, apd);
ellipse(ap3_x, ap3_y, apd, apd);
ellipse(ap4_x, ap4_y, apd, apd);

// draw control points of left inner circle
stroke(255, 0, 0);
ellipse(cp1_x, cp1_y, cpd, cpd);
ellipse(cp2_x, cp2_y, cpd, cpd);
ellipse(cp3_x, cp3_y, cpd, cpd);
ellipse(cp4_x, cp4_y, cpd, cpd);

// draw lines between anchor points and control points
stroke(255, 180, 0);
line(ap1_x, ap1_y, cp1_x, cp1_y);
line(ap2_x, ap2_y, cp2_x, cp2_y);
line(ap3_x, ap3_y, cp3_x, cp3_y);
line(ap4_x, ap4_y, cp4_x, cp4_y);
popMatrix();

///////////////////////////////////////////////////////////
// right ring
pushMatrix();
translate(cx_2, cy_2);
//outer circle
ap1_x = 0;
ap1_y = -outer_radius;
ap2_x = outer_radius;
ap2_y = 0;
ap3_x = 0;
ap3_y = outer_radius;
ap4_x = -outer_radius;
ap4_y = 0;
cp1_x = -outer_radius;
cp1_y = -outer_radius;
cp2_x = outer_radius;
cp2_y = -outer_radius;
cp3_x = outer_radius;
cp3_y = outer_radius;
cp4_x = -outer_radius;
cp4_y = outer_radius;

// draw outer circle clockwise
// draw achor points of right outercircle
noFill();
stroke(0, 255, 0);
ellipse(ap1_x, ap1_y, apd, apd);
ellipse(ap2_x, ap2_y, apd, apd);
ellipse(ap3_x, ap3_y, apd, apd);
ellipse(ap4_x, ap4_y, apd, apd);

// draw control points of left outer circle
stroke(255, 0, 0);
ellipse(cp1_x, cp1_y, cpd, cpd);
ellipse(cp2_x, cp2_y, cpd, cpd);
ellipse(cp3_x, cp3_y, cpd, cpd);
ellipse(cp4_x, cp4_y, cpd, cpd);

// draw lines between anchor points and control points
stroke(255, 180, 0);
line(ap1_x, ap1_y, cp1_x, cp1_y);
line(ap2_x, ap2_y, cp2_x, cp2_y);
line(ap3_x, ap3_y, cp3_x, cp3_y);
line(ap4_x, ap4_y, cp4_x, cp4_y);

// draw right outer circle
stroke(255);
fill(153,100);
beginShape();
vertex(ap1_x, ap1_y);
bezierVertex(ap1_x, ap1_y, cp2_x, cp2_y, ap2_x, ap2_y);
bezierVertex(ap2_x, ap2_y, cp3_x, cp3_y, ap3_x, ap3_y);
bezierVertex(ap3_x, ap3_y, cp4_x, cp4_y, ap4_x, ap4_y);
bezierVertex(ap4_x, ap4_y, cp1_x, cp1_y, ap1_x, ap1_y);

ap1_x = 0;
ap1_y = -inner_radius;
ap2_x = -inner_radius;
ap2_y = 0;
ap3_x = 0;
ap3_y = inner_radius;
ap4_x = inner_radius;
ap4_y = 0;
cp1_x = inner_radius;
cp1_y = -inner_radius;
cp2_x = -inner_radius;
cp2_y = -inner_radius;
cp3_x = -inner_radius;
cp3_y = inner_radius;
cp4_x = inner_radius;
cp4_y = inner_radius;

// draw right inner circle counter clockwise
beginContour();
vertex(ap1_x, ap1_y);
bezierVertex(ap1_x, ap1_y, cp2_x, cp2_y, ap2_x, ap2_y);
bezierVertex(ap2_x, ap2_y, cp3_x, cp3_y, ap3_x, ap3_y);
bezierVertex(ap3_x, ap3_y, cp4_x, cp4_y, ap4_x, ap4_y);
bezierVertex(ap4_x, ap4_y, cp1_x, cp1_y, ap1_x, ap1_y);
endContour();
endShape(CLOSE);

// draw achor points of right inner circle
noFill();
stroke(0, 255, 0);
ellipse(ap1_x, ap1_y, apd, apd);
ellipse(ap2_x, ap2_y, apd, apd);
ellipse(ap3_x, ap3_y, apd, apd);
ellipse(ap4_x, ap4_y, apd, apd);

// draw control points of left inner circle
stroke(255, 0, 0);
ellipse(cp1_x, cp1_y, cpd, cpd);
ellipse(cp2_x, cp2_y, cpd, cpd);
ellipse(cp3_x, cp3_y, cpd, cpd);
ellipse(cp4_x, cp4_y, cpd, cpd);

// draw lines between anchor points and control points
stroke(255, 180, 0);
line(ap1_x, ap1_y, cp1_x, cp1_y);
line(ap2_x, ap2_y, cp2_x, cp2_y);
line(ap3_x, ap3_y, cp3_x, cp3_y);
line(ap4_x, ap4_y, cp4_x, cp4_y);

popMatrix();
}

Get current fill etc.

Issue by GKFX
Wednesday Jan 29, 2014 at 16:40 GMT
Originally opened as processing/processing-web-archive#338


At processing/processing#321 (add get methods for all attributes), there is debate over how to offer the current fill etc. to the user.
I would like to suggest the simple solution of just saying in the fill() etc. reference "Advanced users may want to retrieve the variable from <relevant spot in PGraphics (link)>".
This would have minimal impact on new users, who (a) generally don't want to do this, and (b) hopefully wouldn't be scared off by the Javadoc after it has been labelled "for advanced users".
It also avoids API bloat.

pushStyle() and popStyle() should be in Color > Setting

Issue by iirelu
Friday Mar 28, 2014 at 22:00 GMT
Originally opened as processing/processing-web-archive#374


As it stands, they are currently in Structure, which is supposed to be for core language features. They should logically be moved to Color > Setting, as that is where many of the things they affect are.

pushMatrix() and popMatrix() are already in the same category as the things they affect, which made me realise pushStyle() and popStyle() where in the wrong place.

Users confused by cameraName option in Capture constructors

Issue by atduskgreg
Monday Apr 07, 2014 at 02:02 GMT
Originally opened as processing/processing-web-archive#377


I've gotten a lot of emails from users of OpenCV for Processing who are confused about how to select from the multiple cameras listed as available by Capture.list(). They end up writing code that looks like this:

String[] cameras = Capture.list();
cam = new Capture(this, 640, 480, cameras[3]);

And then, of course, the Capture object fails to connect to any real camera because the strings returned by Capture.list() aren't camera names.

I mentioned this to Dan Shiffman and he suggested I post an issue here. Maybe it's something we can fix with the documentation just by pointing out the relationship between Capture.list() and the two constructors that take a cameraName on the Capture docs page? Or maybe we should add a new constructor to Capture?

Capture(PApplet parent, String captureListEntry);

where captureListEntry would be a string from the Capture.list() array from which we could parse all of the other options.

-- Greg

PS. In case it's useful, here's the email snippet I've been sending to users who have this problem.

This issue with selecting cameras trips up a lot of people.

Two of the Capture constructors take camera names as an option:

Capture(parent, requestWidth, requestHeight, cameraName)
Capture(parent, requestWidth, requestHeight, cameraName, frameRate)

If you print out Capture.list() you'll get something like this:

[0] "name=FaceTime HD Camera,size=1280x720,fps=30"
[1] "name=FaceTime HD Camera,size=1280x720,fps=15"
[2] "name=FaceTime HD Camera,size=1280x720,fps=1"
[3] "name=FaceTime HD Camera,size=640x360,fps=30"
[4] "name=FaceTime HD Camera,size=640x360,fps=15"
[5] "name=FaceTime HD Camera,size=640x360,fps=1"
[6] "name=FaceTime HD Camera,size=320x180,fps=30"
[7] "name=FaceTime HD Camera,size=320x180,fps=15"
[8] "name=FaceTime HD Camera,size=320x180,fps=1"
[9] "name=FaceTime HD Camera,size=160x90,fps=30"
[10] "name=FaceTime HD Camera,size=160x90,fps=15"
[11] "name=FaceTime HD Camera,size=160x90,fps=1"
[12] "name=FaceTime HD Camera,size=80x45,fps=30"
[13] "name=FaceTime HD Camera,size=80x45,fps=15"
[14] "name=FaceTime HD Camera,size=80x45,fps=1"

Each full entry there contains more than just the name, clearly. For example, cameras[3] is:

"name=FaceTime HD Camera,size=640x360,fps=30"

whereas the name of that camera is just:

"FaceTime HD Camera"

So that's the string you have to put into the Capture constructor. The other two parameters (size and fps), you pass in as numbers not as part of the string. So, for example:

Capture cam = Capture(this, 640, 480, "FaceTime HD Camera", 30);

would select cameras[3] and

Capture cam = Capture(this, 80, 45, "FaceTime HD Camera", 1);

would select cameras[14]

Does that make sense?

Remove unused files.

Issue by aengelke
Thursday Jun 05, 2014 at 17:43 GMT
Originally opened as processing/processing-web-archive#430


For these files I couldn't find any usage:

content/index.html
content/curated_images/000.gif
content/curated_images/001.gif
content/curated_images/ac.jpg
content/curated_images/catalina.jpg
content/curated_images/collider.jpg   
content/curated_images/fluidtime.jpg 
content/curated_images/haohao.jpg
content/curated_images/hodgin.jpg
content/curated_images/igoe-bird.png
content/curated_images/igoe.jpg
content/curated_images/inequality.gif    
content/curated_images/koblin.jpg
content/curated_images/lifevslife.gif  
content/curated_images/liquidliquid.gif
content/curated_images/moovl.gif
content/curated_images/mz.png
content/curated_images/nikeone.jpg
content/curated_images/pixelroller.jpg
content/curated_images/silenc.png
content/curated_images/slub.gif
content/curated_images/wave.gif
content/curated_images/xmas.gif
content/curated_images/yahoo.jpg
css/changes.css
css/forms.css
css/processing.css
css/processing_beta.css
css/radio.png
css/radio_checkes.png
generate/_old/*
img/*.gif
img/processing_forum_tab-sel.png
img/processing_forum_back.jpg
img/processing-old.ico
javascript/MM_functions.js
javascript/mode-select.js
javascript/slideshow.js
learning/**
todo.txt

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.