Jump to content
You are about to reply to a thread that has been inactive for 3047 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Posted

It has been a long time since I did any serious scripting.  Like 6 years.  We used LSL Editor back then but I don't know if it has kept up with changes.

What is everyone currently using?  I would like some form of IDE besides keyword highlighting. Is LSL Editor still the goto tool?

Posted

It's not a silly question at all, Rhonda.  Someone asks it here about once a year, and the answer isn't always the same.  LSL Editor is still good.  I know a lot of people like it.  Innula introduced me to SublimeText a year ago, though, and I am way more impressed with it.  It is a lot more flexible than LSL Editor, and has many handy functions that I have come to rely on, like the way it helps you identify orphaned bits of code and unnecessary variables.  There is a nominal fee for the program but in fact the trial version is fully functional and there is no time limit on how long you can use it. 

That said, I am still lazy enough that I tend to write short scripts (less than 100 lines or so) with the dirt grade editor in the viewer rather than firing up any external editor.  It has lousy error messages and it has some annoying quirks, but I can put up with those if I'm writing a simple script where I am not likely to lose my sense of direction.

Posted

I still use LSL Editor 2.55, mostly because I can run a debug after a long scripting session and catch all the silly errors. Well... most of them...

There are a few bits that are not quite right, or missing new features. For instance, a few llParticle options and occasionally either complaining about some syntax that is in fact OK, or not complaining about something that the SL compiler rejects. I can't remember exactly what those are but there are only a couple and easily spotted. Obviously I don't hit them often.

So overall, I still like LSL Editor.

Other than that, I use UltraEdit studio for programming in anything else; php, javascript, C++, whatever. I like the built-in communications functions too, for talking to various kit around here.

Posted

Primarily I use Notepad++, because it's a universal, free (and extensible!) editor. I can get syntax highlighting in many languages, which is important to me because I'm often writing web applications (or desktop applications) at the same time as LSL, and a single Ctrl+Tab between the two files (or side-by-side view) is super-awesome.

Given that it can also handle FTP/SFTP, I can use it to link directly into my personal systems for note-taking and plain-text storage, which saves time when using it as a scratchpad/pseudo-code editor. I don't often write local code.

It did take some finnicking to get LSL highlighting to work, and the process for updating the dictionary is manual. It has good controls for visuals, which is important as I work in a wide variety of settings, and there's a billion different ways to display the text (encoding, direction, collapse levels and very powerful search (incl. Regex) tools.

LSL is one of the least frequent languages I write in, so maybe this isn't the best perspective. But Notepad++ is pretty powerful.

Posted

For LSL, another vote for LSLEditor. Mostly as I like to use a specific tool for a specific job plus I rather like the 'constrained feel' that reminds me of what target I am writing at (little extras like a defined user name, key, group key etc also a bonus).

I have any number of other tools for gp work (VS) as well as some more specialised (game engine stuffs for eg). Tried the others with addons but never really got much beyond trying once. If and when I make the total leap to linux then will have to but for now - suits the job. No, its not workable under wine worse luck.

 

Posted

This is a long story for no apparent reason so if you want to bail now before the TL;DR sets in, I'll understand.

 

With Warcraft's new expansion out, Clover has been playing with her husband more so I took the time to do a thorough look at a lot of the mesh heads available. Demos, demos, demos.  My first criteria was that it had to work with one of the appliers I already have. After that I tried on each demo with the preferred skin applied and tossed out a few that did not suit me. Eventually I whittled it down to 6 heads.  I set up a static pose and  locked in the camera with a small script so I could go back to exactly the same shot each time I changed demos.  This way I got the exact same portrait with each of the 6 candidates.

To really take a look at it, I set up a "board" of 2 cubes flattened (tapered) to show 3 portraits side by side.  I wrote a quick script to pick the name of the last head's picture that was touched and set it as hover text, highlight the one picked and keep a count of how many times each one was touched.  Any touches by people not in my family group are ignored, of course.

Anyway, Clover came on late last night as I was finishing up and I told her to touch the ones she liked as it would help me decide.  Her reply was "You had to script a vote board to try on demos???"

What can I say.  I'm a nerd.  I like to code.  I have been away from it for too long. 

Posted

As Rolig suggests, I'm a fan of Sublime Text.  Its LSL plug-in is well-maintained, and it also has support for most other languages (all plug-ins are community-contribued).

You can compile scripts in in, which is very useful, and it's good at pointing you to the exact error.   It's also very easy to jump between matching brackets and braces, which is so helpful when you've got a long and complex listen event, for example,  

Well-worth a try.

You are about to reply to a thread that has been inactive for 3047 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...