Content Development: Difference between revisions

From Second Life Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
== Development Use Cases ==
= Development Use Cases =
=== Programmed Object Creation ===
== Programmed Object Creation ==
* Creator wants to build a family of complex objects
* Creator wants to build a family of complex objects
** Creator builds or buys and uses appropriate builder tools to develop the object framework for the family of objects.
** Creator builds or buys and uses appropriate builder tools to develop the object framework for the family of objects.
** Other members of the object family are built by using the first as a component or template for building others and letting the builder tool ''compile'' the rest.
** Other members of the object family are built by using the first as a component or template for building others and letting the builder tool ''compile'' the rest.
** Design changes can be done by modifying the initial object framework and using the builder tool to ''recompile'' the family members.
** Design changes can be done by modifying the initial object framework and using the builder tool to ''recompile'' the family members.
Practically, this is probably only possible if 3rd parties can build and sell development tools that will run off world.
=== Comments ===
* Practically, this is probably only possible if 3rd parties can freely build and sell development tools that will run off world. In any event, LL's expertise and value added isn't in building such tools.
* Furthermore this means that the external object definition interface must well defined and open ended, e.g. XML so it can withstand updates.
== IDE based script development ==
* Creator wants to develop scripts in a productive IDE
** Auto-completion needs to be updated whenever the scripting API changes
** The IDE needs access to a current version of the compiler for whatever language(s) are supported.
** Debugging needs to be integrated into the development environment.
** Context dependent help should be available.
==== Comments ====
* Again, this is probably only practical if it can be built by 3rd parties and runs off-world.
* The language definition for the IDE needs to be kept updated and easily downloadable.
* The actual current compiler must be able to run off-world and emit code that can be run.

Revision as of 21:32, 20 September 2007

Development Use Cases

Programmed Object Creation

  • Creator wants to build a family of complex objects
    • Creator builds or buys and uses appropriate builder tools to develop the object framework for the family of objects.
    • Other members of the object family are built by using the first as a component or template for building others and letting the builder tool compile the rest.
    • Design changes can be done by modifying the initial object framework and using the builder tool to recompile the family members.

Comments

  • Practically, this is probably only possible if 3rd parties can freely build and sell development tools that will run off world. In any event, LL's expertise and value added isn't in building such tools.
  • Furthermore this means that the external object definition interface must well defined and open ended, e.g. XML so it can withstand updates.

IDE based script development

  • Creator wants to develop scripts in a productive IDE
    • Auto-completion needs to be updated whenever the scripting API changes
    • The IDE needs access to a current version of the compiler for whatever language(s) are supported.
    • Debugging needs to be integrated into the development environment.
    • Context dependent help should be available.

Comments

  • Again, this is probably only practical if it can be built by 3rd parties and runs off-world.
  • The language definition for the IDE needs to be kept updated and easily downloadable.
  • The actual current compiler must be able to run off-world and emit code that can be run.