The process for setting passage IDs needs to be taken out of the JavaScript in the Sugarcane and Jonah header templates (and TiddlyWiki1 & 2?) (which generate the IDs dynamically, and shifted into the tiddlywiki.py module. (Chris Klimas thinks that changes would be needed to the Tiddler and TiddlyWiki classes in the tiddlywiki.py file).
Once passage IDs are permanent, it is possible to build a raft of new functionality that takes advantage of the ability to refer to specific passages - either in Twine-to-Twine \automated communications or through use of web URLs. This change is central to allowing Twine to be designed for collaboration. (I think it is very important to undertake this modification as soon as possible.
The process for setting passage IDs needs to be taken out of the JavaScript in the Sugarcane and Jonah header templates (and TiddlyWiki1 & 2?) (which generate the IDs dynamically, and shifted into the tiddlywiki.py module. (Chris Klimas thinks that changes would be needed to the Tiddler and TiddlyWiki classes in the tiddlywiki.py file).
Once passage IDs are permanent, it is possible to build a raft of new functionality that takes advantage of the ability to refer to specific passages - either in Twine-to-Twine \automated communications or through use of web URLs. This change is central to allowing Twine to be designed for collaboration. (I think it is very important to undertake this modification as soon as possible.