How to make writing LSL scripts easier - Revision history

Ratany Resident: /* git */

2015-12-30T18:19:15Z

git

← Older revision		Revision as of 11:19, 30 December 2015
Line 1,378:		Line 1,378:
	==git==		==git==

	Git isn´t really involved here, other than that the build system and examples described and used in this article --- and the article itself --- is available as a [~~https~~://~~github~~.~~com/Ratany~~/lsl-repo git repository] for your and my convenience. It´s convenient for you because you can easily download it.		Git isn´t really involved here, other than that the build system and examples described and used in this article --- and the article itself --- is available as a [git://dawn.adminart.net/lsl-repo.git git repository] for your and my convenience. It´s convenient for you because you can easily download it.

	It´s convenient for me because git makes it easy to keep the repository up to date. If several people would contribute to what is in the repository, it would be convenient for them as well because git makes it easy to put together the work done by many people on the same thing.		It´s convenient for me because git makes it easy to keep the repository up to date. If several people would contribute to what is in the repository, it would be convenient for them as well because git makes it easy to put together the work done by many people on the same thing.
Line 1,388:		Line 1,388:
	You can also undo changes by going back to previous commits and experiment with variations (by creating so-called branches). Git works for this much better than making backups or copies of your sources. With backups or copies, it doesn´t take long before I can´t remember what a backup or copy was about and what has changed and whether the copy has become obsolete or not.		You can also undo changes by going back to previous commits and experiment with variations (by creating so-called branches). Git works for this much better than making backups or copies of your sources. With backups or copies, it doesn´t take long before I can´t remember what a backup or copy was about and what has changed and whether the copy has become obsolete or not.

	These features can make it worthwile to use git even when you don´t share your sources or don´t have several people working on the same project. There is lots of documentation about git, and one place you may want to check out is the [https://~~help.github~~.com/ ~~help pages~~] ~~on github.com~~.		These features can make it worthwile to use git even when you don´t share your sources or don´t have several people working on the same project. There is lots of documentation about git, and one place you may want to check out is the [https://git-scm.com/doc documentation].

	Emacs supports git out of the box, see [http://alexott.net/en/writings/emacs-vcs/EmacsGit.html here] and [http://www.emacswiki.org/emacs/Git there].		Emacs supports git out of the box, see [http://alexott.net/en/writings/emacs-vcs/EmacsGit.html here] and [http://www.emacswiki.org/emacs/Git there].

Ratany Resident: /* Editor */

2015-12-30T18:16:29Z

Editor

← Older revision		Revision as of 11:16, 30 December 2015
Line 145:		Line 145:
	* You can preprocess and postprocess and do whatever else you like with your sources before uploading a script: You can use a build system.		* You can preprocess and postprocess and do whatever else you like with your sources before uploading a script: You can use a build system.

	* You can share your sources and work together with others because you can use tools like [http://git-scm.com/ git] and websites ~~like [https://github.com/ github]~~. Even when you don´t share your sources, git is a very useful tool.		* You can share your sources and work together with others because you can use tools like [http://git-scm.com/ git] and websites which will host your repositories for free. Even when you don´t share your sources, git is a very useful tool to keep track of the changes you're making.

	* Your window manager handles the windows of your editor so that you are not limited to the window of your sl client which doesn´t do a great job when it comes to managing windows. You are not limited to a single monitor, and how fast you can move the cursor in the editor does not depend on the FPS-rate of your sl client.		* Your window manager handles the windows of your editor so that you are not limited to the window of your sl client which doesn´t do a great job when it comes to managing windows. You are not limited to a single monitor, and how fast you can move the cursor in the editor does not depend on the FPS-rate of your sl client.

Ratany Resident: /* Automatically Replacing Scripts */

2015-12-30T18:14:31Z

Automatically Replacing Scripts

← Older revision		Revision as of 11:14, 30 December 2015
Line 246:		Line 246:
	You can easily write a program that replaces files yourself. I wrote one when I got tired of all the replacing. It´s not really a program, but a [http://www.perl.org/ perl] script. It´s written in perl because perl is particularly well suited for the purpose.		You can easily write a program that replaces files yourself. I wrote one when I got tired of all the replacing. It´s not really a program, but a [http://www.perl.org/ perl] script. It´s written in perl because perl is particularly well suited for the purpose.

	You´ll find this script in the [~~https~~://~~github~~.~~com/Ratany~~/lsl-repo git repository that accompanies this article] as "projects/bin/replace.pl". It works like this:		You´ll find this script in the [git://dawn.adminart.net/lsl-repo.git git repository that accompanies this article] as "projects/bin/replace.pl". It works like this:


Line 280:		Line 280:
	One way to test if it works is to make sure that the look-up table does not exist and then to click on the "Edit" button of the built-in script editor in your sl client. If the look-up table exists, you find the table as "projects/make/replaceassignments.txt". When your favourite editor starts to let you edit both the file your sl client saved and the (empty) look-up table, it is very likely that it´s working.		One way to test if it works is to make sure that the look-up table does not exist and then to click on the "Edit" button of the built-in script editor in your sl client. If the look-up table exists, you find the table as "projects/make/replaceassignments.txt". When your favourite editor starts to let you edit both the file your sl client saved and the (empty) look-up table, it is very likely that it´s working.

	The build system fills the look-up table for you. It adds entries for new scripts as needed when you run 'make'. It does not delete entries from the table. To make such entries, the perl script "projects/bin/addtotable.pl" in the [~~https~~://~~github~~.~~com/Ratany~~/lsl-repo git repository that accompanies this article] is used.		The build system fills the look-up table for you. It adds entries for new scripts as needed when you run 'make'. It does not delete entries from the table. To make such entries, the perl script "projects/bin/addtotable.pl" in the [git://dawn.adminart.net/lsl-repo.git git repository that accompanies this article] is used.

	The first entry in the table that matches is used. If you plan to have multiple scripts with the same name, you may need to adjust addtotable.pl, replace.pl and the Makefile.		The first entry in the table that matches is used. If you plan to have multiple scripts with the same name, you may need to adjust addtotable.pl, replace.pl and the Makefile.

Ratany Resident: /* Customizing Emacs */

2015-12-30T18:12:57Z

Customizing Emacs

← Older revision		Revision as of 11:12, 30 December 2015
Line 190:		Line 190:
	====Customizing Emacs====		====Customizing Emacs====

	The [~~https~~://~~github~~.~~com/Ratany~~/lsl-repo git repository that accompanies this article] has a directory "emacs". It is recommended that you copy this directory to a suitable location like your home directory.		The [git://dawn.adminart.net/lsl-repo.git git repository that accompanies this article] has a directory "emacs". It is recommended that you copy this directory to a suitable location like your home directory.

	Two files are in this directory, "emacs" and "lsl-mode.el". "lsl-mode.el" provides a syntax highlighting mode for emacs. When you start emacs, it loads a file, usually "~/.emacs", and evaluates its contents. You could say it´s a configuration file.		Two files are in this directory, "emacs" and "lsl-mode.el". "lsl-mode.el" provides a syntax highlighting mode for emacs. When you start emacs, it loads a file, usually "~/.emacs", and evaluates its contents. You could say it´s a configuration file.

Ratany Resident: /* Syntax Highlighting */

2015-12-30T18:11:28Z

Syntax Highlighting

← Older revision		Revision as of 11:11, 30 December 2015
Line 176:		Line 176:
	You can use [[Emacs_LSL_Mode]].		You can use [[Emacs_LSL_Mode]].

	A mofied version of lsl-mode is in the [~~https~~://~~github~~.~~com/Ratany~~/lsl-repo git repository that accompanies this article] as "emacs/lsl-mode.el". This version has been modified for use with a file I named "lslstddef.h" ("projects/include/lslstddef.h" in the repository) to give you better syntax highlighting with it.		A mofied version of lsl-mode is in the [git://dawn.adminart.net/lsl-repo.git git repository that accompanies this article] as "emacs/lsl-mode.el". This version has been modified for use with a file I named "lslstddef.h" ("projects/include/lslstddef.h" in the repository) to give you better syntax highlighting with it.

	====Tags====		====Tags====

Ratany Resident: /* How to make creating LSL scripts easier */

2015-12-30T18:09:44Z

How to make creating LSL scripts easier

← Older revision		Revision as of 11:09, 30 December 2015
Line 11:		Line 11:


	This article is accompanied by a [~~git clone~~ git://dawn.adminart.net/lsl-repo.git repository]. It is recommended that you pull (download) the repository. The repository contains some example sources used with this article, a few perl scripts and a Makefile. They are organised in a directory structure which they are designed to work with. You will have your own build system for LSL scripts when you have pulled this repository.		This article is accompanied by a [git://dawn.adminart.net/lsl-repo.git repository]. It is recommended that you pull (download) the repository. The repository contains some example sources used with this article, a few perl scripts and a Makefile. They are organised in a directory structure which they are designed to work with. You will have your own build system for LSL scripts when you have pulled this repository.

	The repository does not contain basic standard tools like perl, cpp, make or an editor. This article does not attempt to tell you how to install these. You know better how to install software on your computer than I do, and how you install software also depends on which operating system you are using.		The repository does not contain basic standard tools like perl, cpp, make or an editor. This article does not attempt to tell you how to install these. You know better how to install software on your computer than I do, and how you install software also depends on which operating system you are using.

Ratany Resident: /* How to make creating LSL scripts easier */

2015-12-30T18:08:53Z

How to make creating LSL scripts easier

← Older revision		Revision as of 11:08, 30 December 2015
Line 11:		Line 11:


	This article is accompanied by a [~~https~~://~~github~~.~~com/Ratany~~/lsl-repo git repository]. It is recommended that you pull (download) the repository. The repository contains some example sources used with this article, a few perl scripts and a Makefile. They are organised in a directory structure which they are designed to work with. You will have your own build system for LSL scripts when you have pulled this repository.		This article is accompanied by a [git clone git://dawn.adminart.net/lsl-repo.git repository]. It is recommended that you pull (download) the repository. The repository contains some example sources used with this article, a few perl scripts and a Makefile. They are organised in a directory structure which they are designed to work with. You will have your own build system for LSL scripts when you have pulled this repository.

	The repository does not contain basic standard tools like perl, cpp, make or an editor. This article does not attempt to tell you how to install these. You know better how to install software on your computer than I do, and how you install software also depends on which operating system you are using.		The repository does not contain basic standard tools like perl, cpp, make or an editor. This article does not attempt to tell you how to install these. You know better how to install software on your computer than I do, and how you install software also depends on which operating system you are using.

	I´m using Linux, which is freely available in many different distributions. I´m using [http://fedoraproject.org/ Fedora], so to install [http://www.gnu.org/software/emacs/ emacs], I run 'yum install emacs'. If you don´t use Fedora, telling you this probably doesn´t help you. Or you switch to Fedora; it works remarkably well.		I´m using Linux, currently Gentoo.

	Documentation is plentiful. You may find different software that does the same or similar things and may work better for you or not.		Documentation is plentiful. You may find different software that does the same or similar things and may work better for you or not.


	~~Knowledge is fluent and volatile. Software is power.~~

	==Editing this Article==		==Editing this Article==

Ratany Resident: /* Repository */

2015-12-30T18:06:26Z

Repository

← Older revision		Revision as of 11:06, 30 December 2015
Line 32:		Line 32:
	==Repository==		==Repository==

	It´s probably more fun to be able to try out things yourself while reading this article. If you want to do so, pull the [~~https~~://~~github~~.~~com/Ratany~~/lsl-repo repository]. You can run 'git clone ~~https~~://~~github~~.~~com/Ratany~~/lsl-repo.git' ~~or [https://github.com/Ratany/lsl-repo/archive/master.zip \| download]~~ it ~~as an archive~~.		It´s probably more fun to be able to try out things yourself while reading this article. If you want to do so, pull the [git://dawn.adminart.net/lsl-repo.git repository]. You can run 'git clone git://dawn.adminart.net/lsl-repo.git' to get it.

	Once cloned ~~or downloaded and unpacked~~, you have a directory called "lsl-repo". Inside this directory, you have another one called "projects".		Once cloned, you have a directory called "lsl-repo". Inside this directory, you have another one called "projects".

	You can put the "projects" directory anywhere you like, and you can give it a different name if you want to.		You can put the "projects" directory anywhere you like, and you can give it a different name if you want to.

ObviousAltIsObvious Resident: language tags to

2015-01-24T20:32:55Z

language tags to <source>

Show changes

Ratany Resident at 18:51, 13 January 2014

2014-01-13T18:51:05Z

← Older revision		Revision as of 11:51, 13 January 2014
Line 213:		Line 213:
	===Other Editors===		===Other Editors===

	In case you find that you don´t get along with emacs, you may want to check out this [[LSL_Alternate_Editors\|page about editors]]. ~~Try~~ [~~http:~~/~~/en.wikipedia.org/wiki/Vi vi], or vim, instead~~.		In case you find that you don´t get along with emacs, you may want to check out this [[LSL_Alternate_Editors\|page about editors]]. There is also a page about [[LSL_Alternate_Editors\|alternate editors]] and build systems/IDEs.

	You don´t need to try any other editors. Your time is better spent on learning emacs or vi.		Try [http://en.wikipedia.org/wiki/Vi vi], or vim, instead. You don´t need to try any other editors. Your time is better spent on learning emacs or vi.

	==Replacing Scripts==		==Replacing Scripts==
Line 1,401:		Line 1,401:
	==References==		==References==

	The [https://github.com/Ratany/lsl-repo git repository that accompanies this article] contains the sources of reference implementations of devices which are compatible with the [[LSL_Protocol/rfedip\|Ratany fine Engineering Device Interface Protocol]]. Please see "projects/rfedip-reference-implementation".		* The [https://github.com/Ratany/lsl-repo git repository that accompanies this article] contains the sources of reference implementations of devices which are compatible with the [[LSL_Protocol/rfedip\|Ratany fine Engineering Device Interface Protocol]]. Please see "projects/rfedip-reference-implementation".

			* [[LSL_Alternate_Editors\|Alternate editors]] and build systems/IDEs.

	[[User:Ratany Resident\|Ratany Resident]] 07:45, 13 January 2014 (PST)		[[User:Ratany Resident\|Ratany Resident]] 10:51, 13 January 2014 (PST)
	{{LSLC\|Tutorials}}		{{LSLC\|Tutorials}}