Re: Ypaste is up and running!
Kenneth Downs <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <[email protected]> |
This looks cool. bookmarked.
Oren Ben-Kiki wrote:
> We have set up dev.yaml.org as a server for working on YAML development.
> The first active feature is ypaste, available in
> http://dev.yaml.org/ypaste/
>
> Ypaste demonstrates the parsing done by the YamlReference parser. This
> is a Haskell parser which uses exactly the spec productions (actually,
> it uses an updated set of productions, implementing JSON compatibility,
> some minor tweaks to document boundary handling, and bug fixes I
> discovered when I actually fed the productions into it).
>
> You can enter any YAML text, or upload a YAML file (there's a 16k
> limit).
>
> You will then see a two-panel view, the left is the syntax tree.
> Clicking on a syntax tree node highlights the text it matches; clicking
> on the text highlights the matching (leaf) syntax tree node.
>
> You can save the YAML and the result; this will give you a unique number
> and will allow anyone to see it using a URL like
> http://dev.yaml.org/ypaste/<the-number> - or you can use the navigation
> buttons on http://dev.yaml.org/ypaste/ to access a stored result by
> number.
>
> Use this to:
>
> - Explore the spec ("What does the spec say about parsing
> <something>?"). You probably wouldn't want/need to save the results in
> this case.
>
> - Report a bug in the productions ("The productions handle <something>
> the wrong way."). You definitely want to save the results in this case,
> and post a message in this list so I can address the problem.
>
> - Request a change in the spec ("The spec (and productions) say that
> <something> is parsed in a way that makes no sense"). Again you would
> want to save the results in this case, and post a message to this list
> to start a discussion about the proposed change.
>
> Known issues:
>
> - If there is a parse error in the text, the result only contains the
> text up to the error point, followed by a (red) syntax error message
> (which usually isn't that informative). It would be nice if, at the very
> least, the error was followed by the rest of the input, so we'd be able
> to see what triggered it. In the meanwhile, you can see the full input
> text by viewing the YAML navigation button.
>
> - No effort has been made to make this all look "pretty". It is just
> bare-bones functionality.
>
> Have fun!
>
> Oren Ben-Kiki
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Yaml-core mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/yaml-core
>
--
Kenneth Downs
Secure Data Software, Inc.
www.secdat.com www.andromeda-project.org
631-689-7200 Fax: 631-689-0527
cell: 631-379-0010
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/