Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Twee?
I see a new release of Twine, but can no longer find a download for twee (not that I need the old one, but it's absence is troubling). Has twee been abandoned?
Comments
If not, this new Twine is completely unusable for me - I cannot use the graphical editor.
and a twine story file that's just the Start, StoryIncludes that points to the .twee file and StorySettings.
This way, I can code everything in the .twee file, and use Twine to build the story.
StorySettings doesn't seem to work unless it's in the main story file, and it'll complain about a missing Start, so you want one,
but the Start will get overridden by the Start in the .twee file.
Could you elaborate on this -- is there a reason you can't use it, or just prefer not to?
My current story consists of 27 .tw files, and it is still very early in development. I'd say the story is about 20-30K words right now, plus a fair amount of javascript and CSS. That's one of the big attractions to me was the ability to easily organize my writing how I like and use a good text editor.
As for the GUI, it just isn't of interest to me. I've tried it and can't see myself ever being comfortable using it. If I have to use it to create stories, I'll switch to something else.
I'm really surprised twee and Twine aren't actually sharing the same codebase, since there is a fair amount of functional overlap. But, I guess they weren't designed that way.
To elaborate, the full method of this makeshift solution is as follows:
* Open Twine
* Create a new story containing a StoryIncludes passage
* Save the .tws in the same directory as all your .tw / .twee files*.
* Put the file names* of all .tw / .twee files into the StoryIncludes passage.
* Build the output HTML file somewhere.
* Turn on the 'Auto Build' menu option.
The 'Auto Build' option means that the HTML file will be rebuilt every time one of the .tw / .twee files is saved in its editor. This means you can simply refresh the file in your web browser and instantly see changes, as long as you leave Twine open in the background.
*If you've got them in separate folders, simply place it in the nearest common ancestor folder and adjust the file names into relative paths accordingly.
last weekend, I was fiddling with a homebrew Story Building browser app (like the abandoned tweebox). It would be very twee like... Something simpler than Twine2 and strictly for building stories. It would have limitations in how you save the built story due to it being browser based but it would be allot like twee without the python or command line requirements.
I stopped just short of embedding the story formats because I was experimenting with getting the basics working and hadn't gotten to the scope phase of the concept. I wasn't sure if i should make individual versions for each story format (drag in source(s), download). or go all out with radio options and a file management interface.
I'm now leaning towards the first option. Quick and simple, drag=>drop=>download. functionality.
Would you be interested in something like this?
I guess this would be OK if I decide to switch to the new system, but I would much prefer a command line compiler. Currently, I have a python script that builds my twee app for me using find and a few other command line tools to assemble the twee command. So, I do nothing but edit text files and hit the up array to reuse the previous command. It opens the game up in chrome for me if the twee compiler succeeded, so it's completely invisible to me even if I have done some major rearrangement of passages into new files.
As for Hanks offer, I have no idea what tweebox is, so I can't say:) If it's a tool that builds a Twine project out of twee code, I guess I might, but, again, I want to avoid doing anything other than writing my story...at least as much as possible:) And I don't want the tools to get in the way.
I know that there are much, much larger Twine games out there than mine is, but I don't want to have to scroll forever looking for a particular passage when I can just use grep to find what I'm looking for and go right to the file. Also, using TextWrangler, I get spell checking built into my editor, which I don't think Twine has and the syntax highlighting is OK. Hardly the best, but it's sufficient for my needs. Twine probably does a better job at that, since it really understands the syntax.
I wasn't, however, too lazy to completely reimplement twee in a new language, using the new template format. I can't really in good faith recommend that other people use this; I threw it together in six hours and I'm really not sure if I'm actually parsing to tiddlywiki format properly, or using the same templating rules as Twine 1.4 does -- since my only reference for this were the 1.4 target files and the outdated twee code -- but it seems to have all the 1.4 functionality with the same interface as twee, so if anyone is really desperate to upgrade and happens to have Haskell dev tools already installed, well, have at it.
I might see if I can fiddle with the existing twee code and get that up-to-date, but I don't know python at all, so don't hold your breath. :V
To be honest, before this topic came up, I did not think too many people used twee nowadays. While my focus right now is on developing Twine 2, I don't see why the core couldn't be adapted as, say, a Node-based command line tool someday.
Fellow twee users, the SugarCube header provides many of the same or similar features as the 1.4 release of Twine, and works with both 1.35 and 1.4.
I'd say there are several of us, since there is a small sampling here. If it's possible to keep the code clean enough so that you can work on a Twee compiler once Twine 2 is stable, then that would be great.
As for Erik's suggestion, I totally agree. I'm using SugarCube and am very pleased with it. So much so, that when I saw the list of the 1.4 stuff, I couldn't really decide that there was anything new for me there.
Xax, if you are interested in having others use your code, I'd be happy to try it. But...what in the world is a .hs file?
A Haskell source code file.
.hs is Haskell. ( http://www.haskell.org/haskellwiki/Haskell )
The script is actually pretty small (83 lines including a lot of empty ones), since TiddlyWiki was already designed to be used in different contexts. The TweeApp class defines two properties and two methods and the rest is just command line parsing.
If there are any problems or feature requests, please let me know.
I for one have found myself using Twine to rough out a story's structure and usually end up writing the rest in souce code. It's nice to be able to cut out the middle man.
You have my gratitude.
Grab the Twine source from Git. Add the Twine source dir to your PATH, or symlink it from a directory that is in your PATH. Then run "twee" on the command line like this: If you want to use SugarCube, unzip a recent SugarCube release ZIP under the "targets" directory. Then run: On Windows you'll probably have to wrap it in a batch file that executes Python with "twee" as the argument.
Does "ls -la /usr/bin/python*" print anything?
Alternatively, you could add a symlink for python2 pointing to python2.7. For example:
If you followed mth's instructions, you should have a twee file in the root of your Twine directory. It now comes along with Twine (although I don't think a release version of Twine has shipped with it yet, which is why you have to get it from the github repo at the moment). Where did that twee1.4.1 directory inside your Twine directory come from?
The folder "twee1.4.1" that you see is the Twine folder that I got from https://github.com/tweecode/twine. I renamed it to "twee1.4.1" to differentiate it from previous versions.
The parent folder "Twine" that I have is were I keep all my stories and Twine and softwares.
I hope this clarifies my folder hierarchy!
Could the error occurs because I have an accented "" in my path?
Also, I remember that for the old twee1.7.1, I had to change a line to make it work, according to a forum post that I read long ago. At line number 88, I had to change this into this: Could it be the same problem?
Edit: Please test with this Git branch. The dependency of Twee on wxWidgets is removed there, by splitting up the module that caused wxWidgets to be imported.
Keep me posted if you have a fix. I'll be glad to help test it. In the meantime, I reverted to my old twee1.7.1 with the old story formats.