Multi-links

Heres a new idea of mine, there should be new options under tools for inter-linking and set parent object , that the inter-linking would work by grouping objects already linked to anoter object thus making the inter-linked objects abke to have scripts in them that a regular link could not, like rotating.

Hierarchical linking? It's on the to-do list for the distant future.

I sure hope so. Just wonder how distant...

Well, let's look at what we know they're working on now: bugfixes and Havok 2. Cory's said they were planning to transition to a fully XML-based UI eventually, so that's on the list...

What else is there that people have demanded? They fixed the audio system in 1.4, so that's pretty much done with. Other highly popular features include:

1. outgoing XML-RPC using one of the solutions being talked about at the Badgeometry wiki's XML-RPC Discussion page.
   
2. fixes to the DRM permissions so they actually function
   
3. a better inventory management system/better UI
   
4. proper inventory for object contents (folders, anyone?)
   
5. XML UI
   
6. Scriptable UI
   
7. The ability to link solid and phantom objects together
   
8. Hierarchial linking
   
9. instancing of objects to reduce bandwidth (and increase available prims?)
   
10. client-side-generated sign textures using basic layout markup
    
11. scriptable, posable NPC "prims"
    

A few of those are pretty closely connected, or would first require another feature on the list as well.

So, what did we get in 1.1 - 1.4?

1. countless speed increases
   
2. new particle system
   
3. specific code for vehicles
   
4. bump mapping and environment mapping (in my opinion, the jury's still out on whether or not bump mapping qualifies as "what did we get" rather than "what did we have done to us?"
   
5. skirts
   
6. a new mapping system
   
7. Increased the prim count from 10k to 15k
   
8. The abolishment of the tax system (say what you want about the 1.2 pricing model, but the tax system was either fair to the 10% of residents that created 90% of the content, or the 90% of the residents that created 10%. Because of the way it worked, it couldn't ever be fair to both.)
   
9. built-in security functions and access control for land parcels
   
10. the ability to buy sims
    
11. texture preview
    
12. llSetPrimitiveParams (hey, it was specifically asked for!)
    
13. outgoing email
    
14. XML-RPC
    
15. new audio system
    
16. streaming MP3s
    
17. custom animations
    

All of these are things that were specifically asked for. Of course, there were countless smaller changes as well, but these are just a few I can think of offhand. So that's what we got in a year's worth of development. Obviously, there's still lots of relatively minor things that we could use, (like fixes for all the remaining horrible UI bugs that 1.4 introduced) but for the most part, we've already had most of what we asked for granted.

Some big features may take quite a bit of time for the Lindens to get around to; NPCs, for instance, or a fully scriptable UI like Mozilla's XUL, able to communicate with server-side LSL scripts. Yeah, those could be a while. I don't think it's too unreasonable to suggest that we could have most of that list in a year's time. It all depends on what the Lindens decide to devote time to. I remain confident that anything that's actually technologically feasible will get implemented given enough demand.

If you want it done, get people interested. Tell the Lindens what you want, why you want it and what you yourself would use it for. If there's visible demand, it'll happen.

I want an easier way to meet interesting people without wading through 300 teenagers in the process.
The hippo was a good idea, but for the love of god, you cant look at me in the eyes and say that you actually expect people to wear an attachment at all times for your system to work.

Feature suggestion for the feature suggestion forums: Put a sticky post on top with a list of planned and already suggested features similar to the above!