Code Monkey home page Code Monkey logo

latexing's Introduction

LaTeXing

LaTeXing - Professional Typesetting - An extension for Sublime Text which makes your life easier and more comfortable while creating your documents.

Installation

If you already have package control, just follow these steps:

  • Open the Sublime Text command palette
  • Select Package Control: Install Package
  • Select LaTeXing
  • Restart Sublime Text

License

MIT

latexing's People

Contributors

csch0 avatar gabrielkrell 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

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

latexing's Issues

LaTeXing (Knitr): "Confused" syntax highlighting with unmatched "$"

Consider the following screen captures:

captura de pantalla 2014-06-22 a la s 17 14 42
captura de pantalla 2014-06-22 a la s 17 14 59
captura de pantalla 2014-06-22 a la s 17 14 50

The highlighter for LaTeXing's knitr syntax is confused by unmatched $; "confused" in the sense that, unlike in pure LaTeX, in R $ usually is unmatched. In the first and second screen shots, of a simple .Rnw document in LaTeXing (Knitr) syntax and in @randy3k's R-Box-R Sweave syntax, respectively, I have three unmatched $ in the first knitr chunk, after which LaTeXing's knitr highlighter interprets most everything as in math mode, coloring it red; the third screen shot is of the same document without said code chunk (colored with LaTeXing's knitr highlighter).

This appears to be purely an aesthetic issue, i.e., I have yet to have any related problems building files.

single quotes in knitr code chunk

I think there's a bug in the autocomplete of single quotation marks ('') in latex: autocomplete works for single quotes (`') outside of parentheses, but when done inside parentheses it uses ('').

Licensing Options

Hello,

I am trying out latexing and after 15 minutes of use the popup is every single time I build. To make maters worse, I cant even purchase a license right now! Do you have some way of disabling this while licensing is disabled?

Thank you!

Pressing tab inbetween curlies should escape both

I have auto_match enabled which is of course a very useful feature, but sadly LaTeXing does not have a method of easily creating two literal curlies.

What happens currently (| is the cursor):

  1. press { -> {|}
  2. press tab -> \{|}

What I expect to happend:

  1. press { -> {|}
  2. press tab -> \{|\}

I tried looking into your keymap but all the \\\\\\\\ drive me crazy and you likely know better what's happening there - or there is another workflow here that I don't know.

§ shortcut no loger working

When I try to enter a completion using §, I get the following error printed to the sublime console:

Writing file /Users/sglyon/School/NYU/NYUclasses/Winter2014/Metrics/Homework/HW5/parts/Part1.Rnw with encoding UTF-8 (atomic)
Traceback (most recent call last):
  File "X/json/decoder.py", line 242, in JSONArray
  File "X/json/scanner.py", line 63, in _scan_once
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 549, in run_
    return self.run(edit)
  File "./latexing/insert.py", line 53, in run
  File "./latexing/tools.py", line 430, in load_resource
  File "X/json/__init__.py", line 309, in loads
  File "X/json/decoder.py", line 352, in decode
  File "X/json/decoder.py", line 368, in raw_decode
  File "X/json/scanner.py", line 38, in _scan_once
  File "X/json/decoder.py", line 198, in JSONObject
  File "X/json/scanner.py", line 40, in _scan_once
  File "X/json/decoder.py", line 244, in JSONArray
ValueError: Expecting object: line 34 column 9 (char 1751)

Not sure what the problem is...

Project options

I have a few questions about project options.

Interaction with settings in files

What is the rationale behind having project options override the ones embedded in the file? It would seem more logical to have the most specific resource override the less specific ones, something like the order Default, User, Project, File.
For example if you have a project with one main file but then a subdir with a small subproject you may want to override the project root in the subdir only using per-file settings.
In which use case is the current behaviour desirable?

Expansion of variables

It would seem that variables such as $file_path are not expanded in project options.
It could be a useful feature for options like root especially when you have a project including multiple subproject (sub directories): you could write something like `"root": "$file_path/main.tex" for instance.

Commands for setting the root

In ST3 you can do something like

d = window.get_project_data()
d.get("options",{})["root"] = view.file_name()
window.set_project_data(d)

Incorporating this into a "Set current file as root" command could be nice.
Useful addition to "root" snippet: offer a command to display panel from which to select the root (lists open+project files like in quick search) then insert the snippet in current view with selected path.

Double quotes in knitr code chunk

Related:

Session info:

  • Mac 10.9.3
  • Sublime Text 3
  • Latexing v1.2.1 (installed via Package Control)

Say I want to set the highlighting theme in a .Rnw document; I may do so like this:

<<highlighting, cache = FALSE, echo = FALSE>>=
theme <- knit_theme$get("fruit")
knit_theme$set(theme)
@

However, for me at least, in Latexing (Knitr), double quotes are automatically matched and converted into ``", which causes a parsing error upon building with the default build. Getting a simple pair of double quotes then becomes a hassle.


1 I cannot access the issue without first creating an account on Bitbucket 👎

Support for latex2rtf

Hi,
it would be great if Latexing supports latex2rtf from the command palette so that I can easily export my tex files to rtf. Right now, the process is a little elaborate particularly when output_directory is set to true. Here is what I have to do:

  1. Open my Latexing user settings
  2. Temporarily change these two settings to false and 0.
"output_directory": false,
"output_directory_mode": 0,
  1. Compile my tex file in ST (now the auxiliary files should be in the same folder as the tex file)
  2. Now I can run latex2rtf from the console and get pretty good results.
  3. When I am done, I change the settings again and delete the auxiliary

Latexing could make this much easier!

compiling with LaTeXing

Hey,

Just bought a license for LaTeXing and it seems to be working pretty well overall. Still every time I compile using the shortcuts it seems to show up one error if the there is already an earlier version within the working directory... If i remove the the file before compiling it works fine.. but you know the point With the plugin..

Using Sublime text 3, TeX LIve, on windows 7

Best regards

Mechasaurus

When providing completions, please use a literal tab (or only one)

In snippets or completions in general, Sublime Text will replace any instance of the \t tab character with whatever your tab settings are for this view (2 spaces here). It seems, however, that you are using 4 literal spaces instead, which would translate to two tabs in my configuration.

Or you actually have two tabs in the align snippet which, on second thought, seems more likely.

Search current file for refs in partial build mode

If using the partial build mode the label's of the current file are not automatically added to the quick panel in case the current file is not included already in the main file.

This is just a small issue, since the project cannot build in regular mode without including it but useful if you are working in partial mode.

Issue with creating new environment

I’m having an issue with the cmd + l, cmd + n keybinding, which creates a new environment. In particular, adding a curly bracket in order to add an argument to the environment has the unexpected result of automatically inserting a close bracket after the first line of text inside the environment.

Here’s what I’ve been doing:

  1. Hit cmd+l, cmd+n
  2. Enter environment name (e.g., minipage)
  3. Hit tab and enter anything on zero or one lines inside the environment
  4. Move cursor to right of environment name and its close bracket (e.g., if | = the cursor, {minipage}| )
  5. Type an open bracket to add an argument to the environment (e.g., {minipage}{ )

The unexpected result:

  1. Say I’ve got the following already (again, here and below the | shows cursor location):
    \begin{minipage}|
    Hello!
    \end{minipage}
  2. If I type { at the cursor location, I will get the following result:
    \begin{minipage}{|
    Hello!
    }
    \end{minipage}

What I had expected to happen:

  1. Say I’ve got the following already (again, here and below the | shows cursor location):
    \begin{minipage}|
    Hello!
    \end{minipage}
  2. If I type { at the cursor location, I should get:
    \begin{minipage}{|}
    Hello!
    \end{minipage}

math syntax highlighing

there is a difference in highlighting for an equation environment and the inline math environment:

\begin{equation}
v_{i}\left(l, m\right)
\end{equation}

color-highlights \left and \right, whereas
$v_{i}\left(l, m\right)$
does not.

"auto_trigger_fill" is not working

I am not able to get the list of my citations when I write \cite{
I had this problem before; disappeared for some time and come back again. I don't know the cause: so annoying.

Console Colors

the console color scheme should match the editor colors. currently, a white console background does not fit with dark themes.

Popup windows with completion

Hello! After a long search I think that this issue belong to LaTeXing (my best guess). In brief, I am desperately annoyed by the completion window in Sublime. I did my "auto_complete":false but that does not help.

I am using knitR and this popup window with completions jumps out also when I am within R-snippets. This is a snapshot:
167144b0-0c50-11e4-9cc3-90b41a2a6ac9

I wonder if you can help me and explain how to turn this off. The thing is that, very often, this slows you down instead of helping you to achieve better productivity.

Many thanks, PM

Disable tab binding

Is there a way to disable the tab binding that LaTeXing adds to sublime? (I see that I could just comment out the keybindings in "Keybindings - Default", but is there a way to do this modifying ONLY the User settings/keybindings file?)

How to actually write a backtick?

Backtick brings up the insert special symbol menu, which is nice, but I would like to use a modifier combination so I can write backticks to make double quotes. I can assign the command to a new key combination, but that doesn't unbind the backtick key. I can't figure out how to unbind the command.

Always build main tex file?

When you include several chapters in a Latex project, you will always build the main tex file. If you by accident click build on one of the "chapters files"(the one included) and click build, you get a huge error.. Instead, it would be great to specify which tex file who would be built each time.

Document not compiling

I'm trying to compile a tex file and I get the following error in st3 Could not open log file, please check your system. Be sure you are using the latest version of your LaTeX distribution.

The stderr.log file contains this:

Latexmk: -synctex=1 bad option
Latexmk: -outdir=/path/to/file bad option

Latexmk: Bad options specified
Use
   latexmk -help
to get usage information

I'm using LaTeXing on Ubuntu 12.04 LTS with Sublime Text 3

Disable/configure ltx_insert_special_symbols

I don’t really like the automatic transformation of { into { when pressing tab, is it possible to disable it?

Basically, when using Snippets, tab is used to navigate inside the snippet while filling it up. Unfortunately, this collides with this automatic transformation.
For example:

  1. Insert a figure snippet (| is the cursor):

fig| [tab]

\begin{figure}[htbp]
\centering
\includegraphics[width=0.95\textwidth]{|}
\caption{caption}
\label{fig:label}
\end{figure}

If I fill the path directly and press [tab], then I move in the snippet properly.

But most of the time, I’m navigating to the caption first, filling it up, and then copy-pasting the figure path afterwards. Hence I need to [tab] out of the original cursor position, which triggers the transformation instead of navigating away…

I’ve tried modifying the keybinding to avoid matching curly brackets altogether (where ltx_insert_special_symbols is called), but was unsuccessful…

So you could either:

  • Add some additional configuration to activate/deactivate the escaping of brackets (and other symbols actually)
  • Change the matching behaviour to try to cope with snippets (most likely difficult)
  • Change the shortcut altogether? Perhaps this behaviour is better suited to ALT-Tab, or something like that?

Thanks a lot

Nagging when offline

If any of the remote bibliography services is enabled but you are temporarily offline, every time you compile the plugin will complain with a dialog. There seem to be no option to turn the nagging down. It would be good to provide an interface to control the behaviour of modal dialogs as they disrupt the workflow quite a bit.
Things like this are very marginal when you are focusing on writing a document but the modal dialogs bring it to your attention very prominently.
A combination of "verbosity" settings and use of status messages could make the user experience better.

(Mendeley) sync not working

The following output appears after entering the auth token which I got from the Mendelay site:

Traceback (most recent call last):
  File "./latexing/api/mendeley.py", line 229, in on_done
  File "./latexing/api/mendeley.py", line 43, in get_refresh_token
TypeError: 'NoneType' object is not subscriptable
reloading Packages/User/LaTeXing.sublime-settings
Writing file /home/jnns/file.tex with encoding UTF-8 (atomic)
Traceback (most recent call last):
  File "./latexing/api/mendeley.py", line 229, in on_done
  File "./latexing/api/mendeley.py", line 43, in get_refresh_token
TypeError: 'NoneType' object is not subscriptable

Yosemite / 10.10 and calls to popen seem to not have a proper environment.

(I posted this on the Sublime 3 issues list as well... pardon some of the explanatory prose, it is there for those who don't quite know what LaTeXing is)

NB

This is a little bit of a way-out-there issue that may or may not be 'real', so I am reporting it 'as noted' in case there is further pathology discovered. There are, of course, ever changing targets in a OS beta release, and this may be something that magically 'fixes itself' as updates happen.

Description

I use LaTeXing and/or LaTeXTools.

Both use os.popen to launch the LateX build command latexmk

In turn, latexmk makes various calls out to the main LaTeX programs, like xelatex, pdflatex, bibtex, biber, et al.

Unfortunately, under 10.10/Yosemite, even though the plugin can find latexmk, the launched program cannot be found:

popen ['latexmk', '-f', '-quiet', '-pdf', '-synctex=1', '-jobname=drop', '-outdir=/Users/flip/Dropbox/Magic', '/Users/flip/Dropbox/Magic/drop.tex']

which succeeds in properly launching latexmk, but latexmk can't find its helpers-

Latexmk: Run number 1 of rule 'pdflatex'
sh: pdflatex: command not found
Failure to make '/Users/flip/Dropbox/Magic/drop.pdf'

It seems like there might be an issue with popen getting a proper environment (esp the PATH) for it to launch in. As part of the ever-enhanced security in Mac OS I wonder if there are sandboxing / other limitations on things as basic as sh/bash and friends.

Also note that, the TeX distribution lives in its own place w/ symbolic links thrown around to make it convenient/useable. Everything runs out of /usr/texbin (which is a symbolic link into the actual distribution) which contains routines for finding canonical locations of TeX programs/styles/fonts/etc. So I wonder if there are constraints on traversing links in 10.10 that weren't previously there.

disable underscore rewriting

Whenever I type an underscore in the editor, it gets rewriten as \_ . Sometimes this is not what I want, as in the name of figures or labels, e.g.

\label{fig:lti_hrf} -> \label{fig:lti\_hrf}

Is it possible to disable this behaviour ?

Thanks,

Fabian

Feature request: cwl auto completion with separate preable

I'm loading most of the packages that i use in the preamble with my own .sty file 'myfile.sty', which i use for many documents. This causes that latexing doesn't detect which packages i'm using and command completion with latexing-cwl doens't work. Would it possible to fix this?

Perhaps this could be done by creating a command to tell latexing to read a certain .sty file like it would read a normal preamble (separate_preamble{read_this.sty})

Feature Request

Not sure where to put this, but it would be awesome if LaTeXing could have some tools to write system requirements. So it would keep track of SRS numbers and SRS dependency. Also it would allow you to get next available SRS number to make sure it is not overused.

Bibdesk getting clobbered

Latexing has trashed my global bibliography file:

I use a global_bib_file_path which points to my full bibliography generated in BibDesk.

When I compiled my document, I got a pop-up saying:

47 Citation(s) in my_bibdesk.bib have been updated in your remote bibliography, update the item(s) prior the typeset?"

I assumed this would update the local copy of only the necessary entries for this manuscript. However, after clicking update, my global file got overwritten in a broken format! Bibdesk can no longer read it, and it doesn't generate a bibliography.

The culprit is that it is renaming fields:

Bdsk-File-1 becomes 1, which BibDesk cannot read.

I don't think you should be editing the global file at all. If there is a compelling reason, please warn the user explicitly that it is the global file that will be modified!

A way to quickly create align* blocks or * variants in general

I use

\begin{align*}
\end{align*}

quite often, but LaTeXing only provides a snippet for the align variant and the only way I found so far to quickly modify these was:

  1. align
  2. Tab
  3. Up
  4. End
  5. Left
  6. Ctrl+D
  7. Ctrl+D
  8. Right
  9. *
  10. Down

There must be a better way to do this, even if it's just turning the aligns into a snippet field.

Mac latexmk missing but MacTeX is installed

I have installed LaTeXing through package control, and followed the steps in the official documentation. The required MacTeX was already installed on my Mac (10.9.2), but when checking system, it told me latexmk and perl are missing as:

+------------+----------+---------+---------------------------+
| Executable | Type     | Status  | Path                      |
+------------+----------+---------+---------------------------+
| perl       | required | Missing |                           |
| latexmk    | required | Missing |                           |
| texcount   | optional | Missing |                           |
| biber      | optional | Missing |                           |
| bibtex     | optional | Missing |                           |
| pdflatex   | optional | Missing |                           |
| xelatex    | optional | Missing |                           |
| lualatex   | optional | Missing |                           |
| kpsewhich  | optional | Missing |                           |
| texdoc     | optional | Missing |                           |
| sublime    | optional | Missing |                           |
| rscript    | optional | Missing |                           |
| preview    | viewer   | Found   | /Applications/Preview.app |
| skim       | viewer   | Found   | /Applications/Skim.app    |
+------------+----------+---------+---------------------------+

+---------------+
| Searched Path |
+---------------+
+---------------+
** Checked with LaTeXing 1.1.2

FYI:

rmbp:~ dongli$ which latexmk
/usr/texbin/latexmk
rmbp:~ dongli$ which perl
/usr/bin/perl

What should I do? Thank you in advance!

Zotero issue

Since some weeks, I can not access my zotero database. I have the
folowing message when I start sublime text:

"error: Cannot access Zotero.org, please check docs.latexing.com for
more details"

My zotero related settings are the following:

"zotero": true,
"zotero_cite_key_pattern": "{author}_{title}_{year}",
"zotero_user_id": "1616361",
"zotero_user_key": "--------------------------------",

I set it up several month ago, and it was working correctly until now.

Do not replace spaces by underscores in output filenames

LaTeXing currently replaces spaces in the names of LaTeX files with underscores for output filenames. For example compiling "my test file.tex" produces "my_test_files.pdf". Please add an option to switch this behaviour on and off or disable it entirely.

The replacement is undesirable because it messes up the by-filename sorting of files in file managers, ls output, and the like.

Remote bibliography import

I am trying out the remote bibliography feature (Zotero) and I quite like the idea.
However some details make it much less effective:

  1. If you import a reference special unicode characters are imported as they are in the .bib file causing BibTeX to chocke on them.

  2. If you modify the Remote.bib file (maybe to correct such import nuisances) a dialog pops up with a not very clear message:

    1 Citation(s) in remote.bib have been updated in your remote bibliography, update the item(s) prior the typeset?

    The effect of clicking on "Update" seems limited to reverting your changes to Remote.bib, which is weird since you just changed it for a reason. If you click on "Cancel" you'll be presented with the same dialog again next time you build.

Is there any workaround? What's the intended workflow?
I think this could be partially solved by having a command to incorporate the imported references into the main bib file, breaking synchronisation but making them editable. Also a setting to tell the plugin to apply some character substitutions on import would be great.


A side note: I am evaluating the plugin on a medium sized document and there are a lot of things to like. However there are some rough edges that collectively render the plugin much less attractive. I must say that if this was an open source project I would happily volunteer to fix those warts and pay for it. I am sure many would do the same as well.

LaTeXing Not Building in ST3

I want to utilize the Build system with LaTeXing, but it isn't working for me. Every time I try to use Ctrl-b or any other of the build combinations for LaTeXing I get this error in the console:

Traceback (most recent call last):
File "/opt/sublime_text/sublime_plugin.py", line 526, in run_
return self.run()
File "exec in /opt/sublime_text/Packages/Default.sublime-package", line 168, in run
TypeError

I am on Linux Mint 16 Cinnamon 64-bit, Sublime Text 3, Build 3059, LaTeXing version 1.2.0

Error laoding

I am getting this error all the time : "Error loading syntax file "Packages/LaTeXing/support/LaTeX.tmLanguage": Unable to open Packages/LaTeXing/support/LaTeX.tmLanguage"

Equation Editor

Hi, I just published a ST3 plugin that allows you to enter a TeX equation while previewing it on-the-fly.
https://github.com/bordaigorl/sublime-inserteq
It is not supported in ST2 because it uses ST3 ability to display images in tabs.

Now, the plugin works by exploiting online TeX equation renderers such as Google Charts or CodeCogs.
When editing LaTeX documents however it would be far better to have the following:

  1. the equation is rendered locally
  2. the preamble of the current (main) file is imported so custom definitions can be used

LaTeXing already supports partial compilation so this should be not too hard to integrate. My plugin offers some ideas for the interaction with the user.

If there was documentation for LaTeXing's API or it was open-source I could attempt at an implementation myself...

Partial build error

Using a subfiles/biblatex/biber system i get an error when i'm compiling one of the subfiles if the partial build feature is turned on.

I think the partial build feature from latexing creates a main file with some bibtex commands?

main.ptex:7 Package biblatex Error: '\bibliographystyle' invalid \bibliographystyle{plain}
main.ptex:8 Can be used only in preamble. \bibliography

build LaTeXing for atom

any chance of that happening?
Don't know much about the technical soundness of Atom, but I'm digging the fact that it is open-open-source (MIT) as of today. That seems like the way to go about future-proofing. With Sublime Text, alas, and the enigma who hacks it, who knows ...

Quick Build name

image

I hadn't understood that once a quick build is chosen via "Choose Quick Build", that this is the variant that is used for all future calls of "Primary Quick Build".

I believe it could be clarified by renaming "Choose Quick Build" to "Choose Primary Quick Build".

Problem with setting knitr options

I'm trying to alter my knitr inline hook so that it rounds decimals more gracefully. Using the default round() function will occasionally round to 1 decimal place if the second digit is a 0. The following example works with knit() in vanilla R but breaks when issuing Command + B in LaTeXing. I believe the problem may be the double quotes with sprintf(). Thanks again for your time.

\documentclass{article}
\begin{document}

<<load, include=FALSE, echo=FALSE>>=
library(knitr)

inline_hook <- function (x) {
  if (is.numeric(x)) {
    # ifelse does a vectorized comparison
    # If integer, print without decimal; otherwise print two places
    res <- ifelse(x == round(x),
      sprintf("%d", x),
      sprintf("%.2f", x)
    )
    paste(res, collapse = ", ")
  }
}

knit_hooks$set(inline = inline_hook)
@

Inline code looks like \Sexpr{123}, \Sexpr{123.4}, \Sexpr{123.45}, \Sexpr{123.456}.

And with vectors: \Sexpr{c(123, 123.4, 123.45, 123.456)}.

Regular output is not affected by the inline hook:

<<>>=
123
123.4
123.45
123.456

c(123, 123.4, 123.45, 123.456)

getOption('digits')
@
\end{document}

Error after uninstalling

After uninstalling* I get the error:

Error loading syntax file "Packages/LaTeXing/support/Latex.tmLanguage": Unable to open Packages/LaTeXing/support/Latex.tmLanguage

Easy enough to fix manually, but curious why it's not reset automatically.

* I assume the popups on every build aren't a bug.

goto compiler error fails if \input{} is used

If \input{} is used to include other files in a .tex file, the compiler reports a line number as if that text were in the parent file. This means that when you eg: double-click a compiler error, your cursor goes to the wrong line, possbily in the wrong file.

Option to regain ctrl+l as selecting a single line

I would like to have the possibility to select a single line. The standard key binding of Sublime Text is Ctrl+l. Because I wanted to have this feature back I copied all key bindings of LaTeXing that include Ctrl+l into my user key bindings and renamed Ctrl+l to Ctrl+ö.

Unfortunately, Ctrl+l does not work when Sublime displays LaTeXing as the selected syntax. Is it possible to recover the old function of Ctrl+l in LaTeXing documents?

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.