LSL-Editor

Hello Mo Hax,

All llDetect* functions are not implemented (yet).

Its on the TODO list

Hi Alphons--
I've identified a couple issues, plus a couple enhancement suggests.

Here's a script that lists/shows the items:

// Syntax Errors/Warnings Not Identified by LSL-Editor v2.20
// ---------------------------------------------------------
string gStr = "5";
string gSentence = "The time to code is";
list gFruits = ["apple","orange"];

// (1) Enhancement request
// Non-Referenced declared variables should receive a warning
string gDeclaredButNotUsed = "Hello";
   // -- LSL-Editor does not give a warning
   // -- lslint.exe flags as: WARN:: (  9,  1): variable `gDeclaredButNotUsed' declared but never used.


// (2) Enhancement request
// Non-Referenced declared functions should receive a warning
string UnreferencedFunction(integer nbr)
{
	return "The number is " + (string)nbr;
}
   // -- LSL-Editor does not give a warning
   // -- lslint.exe flags as: WARN:: ( 16,  1): function `UnreferencedFunction' declared but never used.


default
{
	state_entry()
	{
        // (3) Syntax Error not identified by LSL-Editor
		string sWrong = (string)(integer)gStr;
			// -- LSL-Editor does flag as an error
			// -- In-World Editor flags as: (28, 33) : ERROR : Syntax error
			// -- lslint.exe flags as: ERROR:: ( 29, 28): syntax error, unexpected INTEGER
		
		// No problem for LSL-Editor with the correct syntax
		string sCorrect = (string)((integer)gStr);
		llOwnerSay("The correct casting results: " + sCorrect);
			// -- LSL-Editor Returns: The correct casting results: 5
			// -- In-World Returns: The correct casting results: 5
				
		// (4) Evaluation Error - String concatenation memory-conserve quirk
		// String concatenation quirk not evaluated the same as in-world 
		gSentence = (gSentence = "") + gSentence + " " + "now.";
		llOwnerSay(gSentence);
			// -- LSL-Editor Returns: now.
			// -- In-World Returns: The time to code is now.
		
		// (5) Evaluation Error - List concatenation memory-conserve quirk
		// List concatenation quirk not evaluated the same as in-world 
		gFruits = (gFruits = []) + gFruits + ["pear"];
		llOwnerSay(llDumpList2String(gFruits, ", "));
			// -- LSL-Editor Returns: pear
			// -- In-World Returns: apple, orange, pear
	}
}

Note: For the LSL "Quirks" items 4 & 5, if you can add code to work with the quirks, I would suggest making a toggle option for it, since LL may make a change at some point where it no longer functions

Hello Trevor Langdon,

Thanks for report. All issues mentioned are low priority at the moment. So I'll put them on the to-do list. There are more features in SecondLife which are really bad. Maybe it is not a good suggestion to make thinks worse than LSLEditor delivers at the moment. We have had the single quote thingy. (post of 09-16-2007) On the "Quirks", we could better ask the Lindens to make the memory limit higher. I can not easily fix the casting handicap of SecondLife, or reproduce an error, if you like. So we have to live with it. I know this makes behaviour of LSLEditor different than In-World. But most of the problems can be overcome by good programming practice. Maybe a place on the known-issues page is a good idea.

Thanks again.

As of today release 2.21 of LSL-Editor can be downloaded (or let the auto update do the job).

LSL-Editor: is a standalone Windows "Editor / Compiler / Debugger / Syntax checker / Runtime environment" for Second Life scripts, based on .NET framework. Because it does not need Second Life grid nor viewer, it is very useful when the grid is down for maintenance, or when you are not connected to it. It can compile and execute many LSL scripts, but also the code completion, features make it a "must have". An HTML Help LSLWiki can be downloaded and used within LSLEditor to make this a true offline working environment.

This is just a minor update. Currently I'm working on SVN for the solution explorer. If you see some hooks for SVN, don't use them. They are not disabled, but are not tested.

One nice (hidden) feature is to make use of lslint for additional syntax checking.
Make a subdirectory plugins in the same directory where LSLEditor resides and place lslint.exe in this plugins directory (get it from w-hat.com/lslint). When starting LSLEditor, go to the tools menu options - Environment - Plugins - Check lslint and hit the OK button. If you go to the tools menu once more, there should be an lslint which does syntax checking every time when you select it.

The error highlighting is a bit improved, so you don't have to search for any cursor when clicking on errors. (Attachment shows lslint in action)

Enjoy my work. Donations are really appreciated.

-Alphons.

WOOT! Awesome on integrating LSLint!!!

getting an 'Internet Explorer cannot display the webpage' error when i try to go to www.lsleditor.org

[edit: finally worked for me]

Alright, I will admit it. I am a seriuos scripter and devoted to Scite-EZ w/ lslint. I actually remember thinking it was kind of silly when you 1st started LSLEditor a year ago. Then when I gave it a try a month or so ago, I came back here and said that it is much improved and I have started using it along with Scite to test some script functions.

But now with the ability to integrate lslint into LSLEditor as a plugin, it totally rocks now. For the other serious scripters out there, you really need to give this a try again.

Auto format and indent scripts by hitting ctrl D. Tired of looking at the crap in the scripting forum? Copy paste it to LSLEditor and hit ctrl D and you can SEE the code again as it should be seen.

Auto complete and mouseover for function info.

You can also download the wiki for offline work and of course hit F1 to bring up the relevant entry.

Run and test multi script projects.

The ability to see the actual calls that will be going to the simulator in the debug window helps to spot code that could be better.

Finally lslint integration. Just dbl click the error and go right to the line.

Alphons, you have my thanks and I just sent some $L your way.

I love the editor. Love the way it breaks down nto Projects and objects. Looks like i'll be replacing my Textpad (for LSL at least). But a couple of thoughts:-

a) Any chance of a toolbar? Seems lacking to not be able to quickly click Run, etc. (just a minor niggle)

b) Any chance of getting the 'placeholder' version of notecards as well? I try to script all my config systems to cater for named, but placeholder configurations. It would be useful to be able to test those aspects.

c) Any chance of a 'Linked prim' distinction within the objects, for making sure the internal communications/link-messages are working.

I'll 2nd THAT!!!

Alphons--
Thanks much! No problem on the "quirks", just thought I would mention it and had a little fun writing the little demonstration script

/me decides it's time to add to my initial donation!

heehee. Now that I have donated some money........................................................

Feature Requests:

Ability to add & remove bookmarks for larger scripts.

Shortcut to jump to next bookmark.

Ability to find phrase and bookmark all.

If you made the source public I would port it to *nix.

AnnMarie Coronet,
Yes, a toolbar would be nice, goes on the todo list. I don't know what you mean by placeholder for notecards. If you use the solution explorer, notecards in the same object can be read directly. On the current version of LSLEditor, reading of notecards in the same directory as lsleditor, is broken . Should be fixed in the next release (on Tuesday). On the linked prim issue, there is some progress in having links between objects in the solution explorer. It is a first implementation but it can emulate the LINK_ROOT , LINK_SET , LINK_ALL_OTHERS ,LINK_ALL_CHILDREN and LINK_THIS numbers. All the other link functions are not implemented yet but are also on the todo list.

Trevor Langdon, thanks! As always

Jesse Barnett, appreciated, sure bookmarking would be nice. I hate the RichTextBox currently used in the LSLEditor. It gives me to little hooks to do nice things on selecting, coloring, code folding etc. It also makes it hard to port to some other platforms and is slow on refreshing.

Jana Kamachi, I have tried to compile some code on Linux using Mono. But the dependencies on the RichTextBox breaks things really bad. Maybe some LSLEditor light version would be possible however.

A lot of people ask me to make the source code public. I think this is possible. I love the idea to have some donation Jar, filled with the current donations so far. When it is full, share the source on a public repository. Working 1 year on the project a fair value would do!!

Next release (tomorrow) is a nice one, one-year-old-feature of LSLEditor that all vars should be initialized before usage is completely eliminated. This one took me a lot of hair-pulling out of my head (this is a Dutch saying, don't know if there is an English one) but at 4.00am this morning I managed to fix this ugly bug. Did not do heavily testing, because I had to go to sleep, so things could be broken. I will set up an archive for older versions of LSLEditor, so there is some fallback for the future.

Enough said, happy coding!!

As far as the placeholder for notecards, I was refering to a duplication of how SL handles them. If you create a notecard, but haven't actally gone into it and Saved it (adding a space then deleting it to get the Save button up), SL treats it as a 'placeholder' and calling GetInventoryKey on it will return NULL_KEY. I try to cover my back in my scripts, so i test not only for the notecard's existence, but also to see if its a placeholder or not (and give a relevant warning to the user). There are other possible actions that can be triggered by the situation too in my script.

At the moment, once you create a notecard in LSL Editor, it is automatically a fully exisiting, if empty, notecard. A check-box on the properties of the notecard, to 'treat as placeholder', would give the chance of debugging against this SL quirk, while still keeping the notecard filled with config data to test later.


Sorry if I'm rambling a bit. Been awake since 4am, and i think i need a caffeine IV to kickstart me

And I love where this Editor is going. It's already become a mainstay in my SL scripting.

As of today release 2.22 of LSL-Editor can be downloaded (or let the auto update do the job).

LSL-Editor: is a standalone Windows "Editor / Compiler / Debugger / Syntax checker / Runtime environment" for Second Life scripts, based on .NET framework. Because it does not need Second Life grid nor viewer, it is very useful when the grid is down for maintenance, or when you are not connected to it. It can compile and execute many LSL scripts, but also the code completion, features make it a "must have". An HTML Help LSLWiki can be downloaded and used within LSLEditor to make this a true offline working environment.

This release contains a few bug fixes, but most of the work is done on internals functions and objects. One of the biggest challenges was to get rid of the “vars have to be initialized before usage” thing. Other work is related to the solution explorer. It is not finished, but there are some functions, like llMessageLinked, which can benefit from the parent-child relations when adding objects to objects in the solution explorer. However, functions like llCreateLink are not implemented!

As of today, there is an in-world group called LSLEditor
Everyone, feel free to join!

The hosting of the offline LSL wiki file is changed to archiv.to because the other host gave nasty popups when using the internal download feature for the helpfile, or even made LSLEditor crash.

Give it a try (if you not already done so) on the menu – tools – environment – help – check offline wiki. It should download the help file at the speed of light.

This release is not tested much because I have these other projects I am working on. If things are broken, and hurts your current work. I have made an archive on the website (download division) where ‘older’ versions of LSLEditor can be downloaded.

Thanks to all the beta-testers and bugreport senders. It keeps me going.

Enjoy scripting!

Attached, a screendump of testing message linking using parent-child relations.

Alphons,

I have submitted 3 bugreports concerning anomalous operation of the Root/Child1/Child2 object in the previous message concerning rel 2.22. Apparently linknumbers are incorrectly initialised in the Root and Children.

Regards Gregory

Thanks Gregory for the reports, I have received them.

Only simple root / child relations are working. The linknumbers are not implemented yet. Maybe I'd better did not mention the link support in the release, and first get the basics implemented, but my enthusiasm dragged me away. Your reports give me some handles to test new implementation.

This weekend I will go outside. It has been months since I have seen real daylight There is this dance event here in Rotterdam (Netherlands) staring famous DJ Ferry Corsten. He is doing a gig of 9+ hours. He planned it for 8 hours, but when daylight saving time stops, we get an extra hour http://www.fullonferry.com/2007/fullonferry.html (less suitable for work) so the work on the Editor is paused for a few days.

Yes you have been working waaaaay to hard (and thank you for that).

Have a blast this weekend Alphons!!!!!!!!!!!!!!!!

I agree so many updates in such a short time. I would say that you have earned a break but that implies that you are 'earning' when working with LSLEditor when we all know it is a labour of love.

Hehe.

Enjoy the weekend and dont worry we will be ready for you when you get back.

Regards Gregory

Hehehe, thanks guys!!

AnnMarie Coronet, your placeholder req. for notecards is noted. You are not 'rambling' at all. Just a fair request. You get your NULL_KEY soon

Alphons--
Agree with others, ENJOY your "free" time

When you return, I found an issue for you to check out, lol

Apparently, the LSL-Editor is not freeing up the link message queue in between debug stop/starts.

Following a stop/start sending a command that generates a link message results in the previous sessions link messages for that routine being sent plus the current one. An increase by one will continue with each subsequent stop/start of the debug session.

Closing the project solution, then re-opening the project clears out the erroneous link message queue.

Hey Alphons,

Knock one time if you are still alive.

Knock twice if you met a new girl at the dance party and you are having a blast.

o/ knock three times on your coffin if you want my love, o/
o/ twice on the pipe, if the anwser, answeris no, no, no.. o/
Black Tape For A Blue Girl - Knock (remix? of "Knock 3 Times" by Tony Orlando)

There is a serious point here. Do we wish to continue to use LSLEditor and can we leave it to Alphons alone? Heaven forbid that anything has happened to him but what if it has?

Alphons, when you read this do not take it as a crticism but an expression of our admiration for the work you have done and continue to do.

What steps have you taken to secure LSLEditor for those who would follow after?

Hello all ,

I'm still alive (and kicking) just took a short time to work on another project, which was in fact delayed because of LSLEditor. Also had to replace some damaged brain cells. And more.

But don't worry, if something would happen to my well-being. There are some 200+ (login)accounts which are taken care of by someone I fully trust, doing the right thing. And the LSLEditor project is one of them. But hey, don't kill me yet, I'm fairly happy And passwords are stored in Passwordsafe (nice sourceforge.net project by the way)

Also, I do make backups (yes I'm one of those people) on regular intervals. So source code is save when my laptop or house will burn down to the ground. Even if my home town would be hit by some nuclear blast, source-code is at a different (geo) location. And should be retrievable by the backup team.

In mean time I also changed my internet DSL connection. Had some troubles with the new modem. Experimenting on the SNR ratio, and finally I had to upgrade firmware before getting a stable high-speed connection again and having two telephone ports on the apparatus for using VOIP and SIP. This joke took me 1 week… So I was quite busy to get it all up and running again.

The bad news is, there is no much progression in this release. But I want to get it out, syncing my working copy again. There were to little changes and fixes to release it last week. But why wait any longer.

Thanks for all the support and suggestions.

-A.

I really disagree with the premise of this post, LSLEditor is a fantanstic effort which Alphons is doing for his own reasons and making available for free. IMHO there's no option for "can we leave it to Alphons alone" or not.

It's his baby and he's doing a remarkable job of it.