2/3/13; 8:29:46 PM by <b>davewiner</b>
	Version 2.74 -- halftime feature
		Include "created" in the atts display at the bottom of the screen.
		Instead of viewing the long GMT-based date, use the viewDate routine we use in the Open command table, more user-friendly.
2/3/13; 4:38:16 PM by <b>davewiner</b>
	Version 2.73
		new + icon
			Creates a new headline down from the BCH it has no subs or they aren't expanded, or to the right if they are. prompts you for the text of the headline. this is a guider feature for people on desktops, and a realizer for people on tablets. 
		buttons in ask dialog are uniform size, 80 pixels wide as in other dialogs.
		tried out multiple-select. works as advertised. will make a huge difference in utility.
2/3/13; 3:47:18 PM by <b>davewiner</b>
	I've been playing around with what a presentation preview might look like.
		http://modalwithwebpage.blorkmark.com/
	If you have any ideas how to make it look better...
	Enjoy the game and go Niners! :-)
2/3/13; 1:11:29 PM by <b>davewiner</b>
	Kyle, something to put on your list.
		A call to give me OPML for the BCH and its subs.
		As if it were an outline itself. 
		I want to use this to pass off a rendering job to a server.
		Basically to have the BCO be a parameter to a RPC.
			BCO == Bar Cursor Outline.
2/3/13; 12:34:47 PM by <b>davewiner</b>
	Version 2.72
		fixed up dialog sizes
			prefs dialog
			atts dialog
			handle Return key in the Username dialog.
			Also button size in the Username dialog.
2/3/13; 12:15:27 PM by <b>davewiner</b>
	My first programming language was FORTRAN, on punched cards.
		My second language was Simula 67 -- and I was bitching and moaning about the lack of GOTOs.
	I agree about privacy and outlines. 
		That's going to require several "features" and something of a re-think.
		But it's important.
	You did have a change-note about the collapse attribute. 
		And it's important to close the loop on stuff like that. And no harm at all in doing it twice! :-)
		I worry about these things and until I hear it's been taken care of, I don't stop worrying.
		So thanks for taking care of it and thanks for letting me know.
	Could you do a review of how I start up now?
		There was a little bit of guessing in there, and it seems to work.
		But the way the code is arranged, it's worse than GOTO statements in FORTRAN.
		Way way way before your time. :-)
2/3/13; 9:42:58 AM by <b>davewiner</b>
	Kyle, I sent you a copy of trex.root via email.
2/3/13; 9:30:53 AM by <b>davewiner</b>
	Version 2.71
		Don't autosave if opGetTitle () returns undefined.
		Kyle, please verify that this is a good way to determine if the outline has not been set up yet.
		I'm guessing it is because I can now see when it's trashing the outline. I get a tooltip saying "Saving undefined." 
		I figure I should not be doing that. :-)
		Note that in order to autosave, opHasChanged () must be true. 
2/3/13; 9:23:20 AM by <b>davewiner</b>
	Version 2.70
		New flow of control on startup.
		After initializing, reading the cookie, setting up the backgroundProcess script, we call a new ajax server routine, validateUser. If it returns "true" we go ahead and set up the outliner with the previously open outline. If it returns "false" we put up a username/password dialog. When the user enters a username and password we go through the validation dance again, and repeat until we get a valid combination.
		It's tricky code, for me especially, because I'm not used to this flow -- but I'm getting used to it.
		But we have to really check this for breakage. I'd rather not be chasing down bugs in this flow from now until forever. :-)
		This will also allow me to address the autosave problem where we're saving an empty outline over one that's not empty. I think it's just a synchronicity issue -- we're saving something before it's set up. I'll check to see if the title is undefined before saving. That'll be in the next version. 
		Also the dialogs are mis-shapen -- because I started cleaning up the CSS. I don't think it'll take very long before they're back in the proper shape. 
2/2/13; 4:13:54 PM by <b>davewiner</b>
	Questions
		Right now all outlines are public. The OPML is stored in publicly accessible buckets on S3. The outlines are visible through the worldoutline. Is this good? Should we have a private mode? Or should they be private by default?
		What should a user see if they aren't logged into a worldoutline server?
		Is there any way to gray out menu choices?
		We have a problem in that our menu commands and keystrokes don't flow through the same code. I handle menu commands separately from some of the keystrokes. This should be cleaned up so we have a chance of controlling the UI depending on what the user can do.
		What bugs are we not finding because neither of us are using the product in some mode?
2/2/13; 12:04:49 PM by <b>davewiner</b>
	Figured out how to keep users in the loop without creating a horribly complex editorial system.
		We should have a river tab in Concord, which is news about the product.
		Or maybe a button they can press that pops up a river. 
		Then all we need two worknotes sites, one for you and one for me.
		And the river is the combination of both our worknotes flow, thru RSS.
		Simple. 
	Be careful -- there's a bug in autosave. It will sometimes save an empty outline over one that isn't empty.
		I've lost a lot of "work" this way.
		But since I'm not really using Concord yet for real work, it hasn't hurt me.
		You are -- so be careful! :-)
	Read-only outlines are really interesting
		How different is a read-only outline from the blog posts on scripting.com?
		Think of Concord as a reading environment as well as a writing environment.
	Archived January I/O posts.
2/1/13; 7:47:52 PM by <b>davewiner</b>
	Version 2.69
		Fluid layout.
		Company name.
		White space.
		About button. 
		I call this the "bligleveler" release.
		Don't ask why.
	I'll check in later, may do a little work after dinner.
	TTFN.
2/1/13; 6:45:41 PM by <b>davewiner</b>
	Thanks, I understand.
	How would you do it? 
		Suppose I wanted to add a second outline to Hello Outliner.
		What would it look like? What would I have to change?
2/1/13; 6:30:27 PM by <b>davewiner</b>
	Kyle, we need to figure out how to have more than one outline on a page. 
		However we do the I/O stuff, we will need to do that. 
		Probably using tabs somehow.
		Look at this page for inspiration.
			http://tabs.mediahackers.org/?panel=dave
2/1/13; 6:15:44 PM by <b>davewiner</b>
	Version 2.68
		New Toggle Comment command in the Outliner menu.
		Autosave no more often than once per ten seconds.
		Add to menu: Cmd-[ for promote, cmd-] for demote. (The keystrokes are already handled by the outliner.)
		Add View Blog command to the Blog menu.
2/1/13; 6:00:55 PM by <b>davewiner</b>
	I think we have to try to get our testers on something like the I/O -- integrated in the UI of concord.
2/1/13; 6:00:14 PM by <b>davewiner</b>
	Kyle, seems to work well.
		Did you have to hack it up or was it straightforward?
2/1/13; 4:09:24 PM by <b>davewiner</b>
	There's another possibility for fixing the look of the wordpress text.
		I added classes to all the text, and with those classes you could do all the formatting I described. 
		Maybe they give the user access to styles. I'll check.
		They have a CSS stylesheet editor, but it's $30 a year to save the styles.
		Probably worth doing. Much cheaper than adding rules. :-)
	I'm going out for a bit...
2/1/13; 3:30:01 PM by <b>davewiner</b>
	Not sure where they're coming from. 
	Right now that's not my highest priority.
	And they're so visible, it won't be hard to remember to look for them.
	But look how crappy the text looks.
	That's an important puzzle.
	the outline
2/1/13; 3:16:38 PM by <b>davewiner</b>
	Worth looking at this post.
		http://concordtest.wordpress.com/2013/02/01/sports-and-teams-8/
	That's the best we can produce with concord right now, with the tools we have.
2/1/13; 12:57:47 PM by <b>davewiner</b>
	No issue with // used to delimit a comment. Just use the chevron in place of the wedge, the same way OPML Editor does. I can explain next time we talk on the phone. 
	I'm taking a break now..
2/1/13; 12:51:14 PM by <b>davewiner</b>
	Kyle, this is something for your list -- whenever it fits into your work flow.
		It's hard to click on the first or last character of a headline. 
		Say I want to position the cursor at the very end, so I can type another sentence. 
		Or right at the beginning to add a word or two.
2/1/13; 12:26:26 PM by <b>davewiner</b>
	Version 2.67
		when saving the status message shows in the tooltip
			this is supposed to feel natural, because you clicked in that icon.
			or if you didn't, the operation certainly is associated with the icon (and it showing up there might be a hint for some that it's another way to save).
			not sure if this is the way i want it to work, but i'll leave it like this for a while.
		refresh atts display after saving a blog post to show the new value of ctsaves, and possibly other atts.
		indentation via ul with special styles
			The top level heads in a wordpress posts are in <p>s. 
			Subsequent levels are <li>s contained within a <ul>.
			I added classes to all the elements so that one could create a stylesheet that would be good for displaying Concord outline content.
		idpost problem fixed
			after a successful save, if the metaweblogpost node already has an idpost att, don't set its idpost att. 
			idposts seem indestructible now! :-)
		context menu cannot be hierarchic
			Looks like we won't be getting them from the Bootstrap guys.
			They don't like them.
			Mark Otto: "Multiple levels of dropdowns are not coming to Bootstrap. If you need the multiple levels, you should probably try another implementation of that content. It's not a great paradigm to begin with and piling on other levels never works well for users."
			But I did add separators to the context menu. :-)
			BTW, if Otto were on my team I'd say -- "depends on who the user is" -- I like having an Instant Outliner sub-menu in my context menu. 
			Also I like having a sub-menu of all the categories on my WordPress blog. How am I supposed to do that without hierarchic menus! Oy.
		Lots of testing of wordpress blog posts
			It's a lot more reliable this morning than it was last night.
			I think I could now write a blog post, or change notes and have it be reflected reliably.
			I actually could write a nice tree of essays.
				http://concordtest.wordpress.com/2013/02/01/sports-and-teams-8/
			Really felt smooth. Very good for an outliner that's just a couple of months old. 
			These things need seasoning. :-)
		Rules <i>will</i> work. This is importatn.
			We can use Rules here. 
			Local styles work in Wordpress. They don't strip them. 
			So you can say <p style="color: blue;">Hi Mom</p> and it'll show up in blue. 
		Screen shot of Concord as I edited today. It's getting there. 
2/1/13; 12:05:27 PM by <b>davewiner</b>
	Look at the OPML Editor for prior art.
		The single keystroke for making a comment is Cmd-\
		Note how it cascades (this is important). The comment-ness of a parent is inherited by its children. So you can comment out a whole branch just by commenting the top-level head. This should be represented visually too.
		We used the chevron because that was the comment character in UserTalk.
		When we ported to Windows we also supported // to delimit a comment.
		Since Javascript uses // too, find a character that's as close to that as possible.
		If you can't find one, let's talk.
2/1/13; 11:04:44 AM by <b>davewiner</b>
	Oy. Sorry to put you through that. I should have gone in that direction myself. 
2/1/13; 10:35:34 AM by <b>davewiner</b>
	Added glue for the "add" call -- opAddAtts, and changed the two calls to opSetAtts to opAddAtts. 
	However I don't see how either of the two calls could cause idpost atts to disappear.
	The first is called on insert -- the headline is new, it didn't have any atts beforehand to be lost.
	And the second is called on clicking OK in the Edit Atts dialog. In that case we have all the atts, so we're writing all the atts. 
	And I was able to lose the idpost att without ever editing the atts. So I don't think that could be it. 
	The other attribute-setting is done by calls of this form: blogpost.attributes.setOne (name, val).
	So I suspect we have <b>not</b> found the reason for the idpost att being lost. 
	Update
		Repeated the same steps that lost the idpost att previously and it's gone again.
		I'm beginning to think this is reproducible.
	Steps to reproduce
		1. New post, enter a title.
		2. Enter a headline. Save by clicking on the disk icon. Note that idpost att is present on the parent headline. 
		3. Enter a headline. Save by clicking on the disk icon.  Note that idpost att is now gone.
2/1/13; 10:03:15 AM by <b>davewiner</b>
	Now -- on the other hand -- it appears there are circumstances under which my posts will lose its idpost att. That would be a problem with the outliner. I'm going to see if I can catch it doing it. If you can think of anything that might cause that, it would be good to check it out. 
	Reproducible breakage
		1. Choose New Post from the Blog menu.
		2. Enter a title.
		3. It will create a new headline, but the display is wrong.
		Screen shot.
	I just got it to lose the idpost att. Saved the post twice.
2/1/13; 9:45:18 AM by <b>davewiner</b>
	OK.
	Seeing other people's notes can be distracting. Perhaps I should take my notes offline in another outline, and only post them here when I have a new release or need help?
		Maybe that would work better?
	Kyle -- the only reason for you to look at wordpress is for the CSS. The rest of it is my responsibility. 
		And even that isn't really your problem. Keep focused. When I'm asking for your help, I'll put your name at the beginning, as I did in the line above.
	Working on the CSS for wordpress text.
		Still not clear how much they respect the CSS.
		But -- using <blockquote> for indentation is not right. 
		The correct way to do it is to use <ul>s. That's what they're for.
		At the top level, the docs are <p>s. Any subordinate text is in <ul>s and <li>s.
	I'm having a serious problem with the wordpress code. It's creating new posts sometimes. That must mean that idpost param isn't being transmitted or it's 0. Have to figure out what's going on here.
	My current test post.
2/1/13; 9:20:00 AM by <b>davewiner</b>
	Got rid of flashing in the msg area below the outline.
		This is where I've settled on displaying the atts, at least for now.
		It shares the space with the msg (s) function -- which displays status messages while code is running.
		For example, when we save the outline, a "Saving..." message appears there. 
		When we erase the message with a msg ("") instead of erasing it, we mark it as dirty, and it will be re-displayed next time the backgroundProcess function is called.
		This prevents the atts from re-displaying between the wordpress save and the outline save.