diff --git a/README.md b/README.md index fc07e2299..c28a17f96 100644 --- a/README.md +++ b/README.md @@ -7,13 +7,19 @@ For live demos and code samples, [visit the website](http://jsil.org). For help on getting started using JSILc, see [the wiki](https://github.com/sq/JSIL/wiki). +JSIL is currently in partial maintenance mode (due to time constraints on the maintainer's part), but bug reports and questions are still actively responded to. Pull requests still welcome! + License ======= -Copyright 2011 K. Gadd +Copyright 2011 K. Gadd + +Additional contributions by Igor Kiselev and assorted community members. + License: MIT/X11 -Replay/Record support & emscripten integration sponsored by Mozilla Corporation +Replay/Record support & Emscripten integration sponsored by Mozilla Corporation + License: MIT/X11 Acknowledgements @@ -35,7 +41,13 @@ The Upstream folder also contains: * A specific version of the NUnit.Framework assembly, used by the automated tests. This ensures that they compile correctly regardless of which version of NUnit you have installed. * Win32 build of PNGQuant for optimizing PNG files. (Jef Poskanzer, Greg Roelofs) * Mono ILASM for CIL tests execution + +The following NuGet packages are used: + * Grunt + * Node + * NPM + * NUnit + * NUnit Test Adapter + * FSharp CodeDom -Logo by [John Flynn](http://www.bryneshrimp.com). - -Assorted code and test case contributions by the various contributors on the GitHub project page - already too many to list here. +Logo by [John Flynn](http://www.bryneshrimp.com). \ No newline at end of file diff --git a/jsil.org/index.html b/jsil.org/index.html index ea5823e90..f4b29e97d 100644 --- a/jsil.org/index.html +++ b/jsil.org/index.html @@ -11,7 +11,7 @@

JSIL

-

JSIL is a compiler that transforms .NET applications and libraries from their native executable format - CIL bytecode - into standards-compliant, cross-browser JavaScript. You can take this JavaScript and run it in a web browser or any other modern JavaScript runtime. Unlike other cross-compiler tools targeting JavaScript, JSIL produces readable, easy-to-debug JavaScript that resembles the code a developer might write by hand, while still maintaining the behavior and structure of the original .NET code. Because JSIL transforms bytecode, it can support most .NET-based languages - C# to JavaScript and VB.NET to JavaScript work right out of the box.

+

JSIL is a compiler that transforms .NET applications and libraries from their native executable format - CIL bytecode - into standards-compliant, cross-browser JavaScript. You can take this JavaScript and run it in a web browser or any other modern JavaScript runtime. Unlike other cross-compiler tools targeting JavaScript, JSIL produces easy-to-debug JavaScript while still maintaining the behavior and structure of the original .NET code. Because JSIL transforms bytecode, it can support most .NET-based languages - C# to JavaScript and VB.NET to JavaScript work right out of the box, and F# is partially supported. Nearly the entire feature set of the .NET runtime (including pointers and P/Invoke) is supported, and most of the open-source BCL is translatable by the compiler.

Demos

@@ -28,25 +28,14 @@

Demos

Code Samples

- - + See try.jsil.org.

Getting Started

Use JSIL

  1. Clone the repository using Git, from 'https://github.com/sq/JSIL.git'. (Make sure you pull the submodules!)
  2. -
  3. Build JSIL.sln in Visual Studio 2010. (Express is fine.)
  4. +
  5. Build JSIL.sln in Visual Studio 2015. (Community Edition is sufficient.)
  6. Run JSILc.exe on your application. (See the wiki for help.)
  7. Marvel at convoluted error messages! (JSIL is still in development. You will hit bugs.)
@@ -54,11 +43,9 @@

Contribute to JSIL

  1. Fork JSIL on GitHub. (Working locally from a clone is okay too.)
  2. Write tests for bugs or new features! (Without tests, JSIL would always be broken.)
  3. -
  4. Fix broken tests! (Adding a test for a bug is helpful even if you can't fix it.)
  5. +
  6. Fix broken tests! Tests can be run from VS2015's integrated testing tools.(Adding a test for a bug is helpful even if you can't fix it.)
  7. Push to your GitHub fork! (If you don't, I can't see your awesome changes.)
  8. Create a pull request on GitHub. (Submitting a patch is okay too.)
  9. -
  10. ???
  11. -
  12. Profit!

Complain about JSIL

Not everybody has time to write code! That's okay. You can report issues, or just talk about JSIL on the internet or something!