> What would be interesting is to see the edition capabilities of LAMS integrated to the LMS (for instance
> .LRN), instead of replicating some LMS capabilities inside LAMS. Any plans on this?
Yes and no.
On the yes part, we have the concept of Tool Adapters that would allow LMS tools to be added to LAMS as if they would be native LAMS tools/activities. So you would be able to drag-and-drop them and create sequences just like you do normally in the LAMS Authoring environment.
These Tool Adapters work as a, well, an adapter between the external tool and LAMS Core following the LAMS Tool's Contract*, which is basically the protocol (in a way) that LAMS tools 'talk' to the core.
Now the no bit, it's because we haven't been able to work on these adapters. At all yet.
The adapters would require work in both ends... a tool wrapper in .LRN side and a bunch of REST like interfaces on the LAMS end.
I'll keep you updated with these in the next few months.
Also, if you need this today, there's an easy hack where you can use the LAMS' Shared Resources tool and add the URL for your .LRN activity to it. So when the students hit the LAMS Shared Resources tool, the .LRN URL gets displayed directly. But again, this is not quite the drag-and-drop experience.
Hope that helps
* Here's a presentation on how the LAMS Tool Contract works.