From: why t. l. s. <yam...@wh...> - 2002-07-29 14:25:26
|
The latest set of changes over the weekend: - version: 0.32 date: 2002-07-29 changes: - Opened up unquoted strings to more characters, is closer to spec now. - Round tripping started with YTS. - Problems with foreign characters fixed. Thanks, Robert Wagner. - Problems with Array#to_yaml and Hash#to_yaml not giving a newline when nested. Again, RW. - Bugs in positive timezones with Time#to_yaml fixed by Tobias Peters! - version: 0.31 date: 2002-07-27 changes: - Fixed bug in multiline quoted strings. - Added YTS cases for odd newline and spaced block scalars. I'm also considering changing the name of YAML4r. I've had a number of folks say it's corny and I've agreed all along, but haven't yet though of a better name. I'm soliciting for your help if you have any ideas. I've thought Rype might work. Ruby's Yaml Parser and Emitter. Ruby's Yaml Perpetrator Extraordinaire. It's close to several other Ruby projects, though. Rite, for example. So, I dunno. Steve noticed the patches I mention in my CHANGELOG and wrote: > You must be getting real users, huh? Very cool. Where did you find them? What > are they using the stuff for? > > If there's a good story to tell, you should send it to the list. I make weekly postings to Ruby-talk, summarizing the week's work and each week I get a few interested patrons. I've had some very good dialogues lately, and better quality of patches come in. Clark's made mention that YAML4r is the most compliant parser currently. While this is fine and good, the users are quickly helping me see how far behind the emitter is. Tobias Peters in particular has sent some good ideas for the aliasing mechanism on the emitter (there is none currently). Lots of these guys are hesitant about reading the entire spec. I think I'm going to write-up a simple intro for the YAML4r site. You'll likely see it pop up in Wiki soon. I don't give any credit to Clark and Steve for this release, but I do acknowledge them in the README. They have been enormously helpful and aware. _why |
From: Steve H. <sh...@zi...> - 2002-07-29 16:23:33
|
From: "why the lucky stiff" <yam...@wh...> > Lots of these guys are hesitant about reading the entire spec. I think I'm going to write-up a > simple intro for the YAML4r site. You'll likely see it pop up in Wiki soon. > NEED FOR TUTORIAL It would be great to have an alternative to the spec for new YAML users. The spec's obviously more of a reference document than an introduction to YAML, although Chapter 1 certainly does a nice job of describing the basic goals of YAML, and there are examples galore too. USING MOINMOIN INCLUDE FEATURE The Wiki would be a great place to draft a YAML tutorial/introductory document. MoinMoin has a particularly nice feature for long, collaborative documents. Try this adding this to a MoinMoin page: [[Include(YamlPeople)]] Here's a good place to try it: http://wiki.yaml.org/yamlwiki/WikiSandbox?action=show The Include feature would allow us to work on different sections of a tutorial, but they could appear to the user as one big document. The only drawback is that a Wiki tutorial might not have the same formatting polish as a static HTML document, not to mention the mutability factor. The solution, of course, is that we can write a simple script to generate a static HTML document from the MoinMoin pages, and then we can periodically link the static copies of the tutorial to the main yaml.org website. DOWN WITH THE ORCA We should change our MoinMoin to use relevant bits from yaml.org's style sheet. The new look-and-feel for the main site is nice. We need to get rid of the cartoon whale, at the very least. Neil, my account does not have the permissions to do this. Any chance you can fix this for me? MOINMOIN/PERFORCE INTEGRATION The best way to learn YAML is by example. Thanks to Why's work on the testing suite, we have some great example YAML documents, with mappings both to Ruby and Python. Those documents would make great filler for a tutorial, and there are other miscellaneous documents that would work nicely in a tutorial. It would be good to connect some of our Perforce documents to MoinMoin. MoinMoin's data files are in this directory: /usr/local/share/moin/yamlwiki/data/text We could write a little cron job that periodically did a p4 sync of key files into the MoinMoin folder. We could then mark the documents with a ## comment that says not to edit the documents via MoinMoin. (We could then integrate the two tools more fully as we got more sophisticated.) Perforce allows you to set up your client so that it grabs docs from various places, and perforce could even rename the docs to WikiName-compatible formats. |
From: Neil W. <neilw@ActiveState.com> - 2002-07-29 17:53:37
|
Steve Howell [29/07/02 12:23 -0400]: > DOWN WITH THE ORCA > > We should change our MoinMoin to use relevant bits from yaml.org's > style sheet. The new look-and-feel for the main site is nice. We > need to get rid of the cartoon whale, at the very least. Neil, my > account does not have the permissions to do this. Any chance you can > fix this for me? Should be working now. You're a member of the 'moinadmin' group, which should now have write access to everything under these paths: /usr/local/share/moin/yamlwiki/ /usr/local/share/moin/htdocs/ Let me know if you can't do something. Later, Neil |