[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[rgui-dev] [Fwd: [Yaml-core] schemas: two layers, extensibility]
From: |
Tom Sawyer |
Subject: |
[rgui-dev] [Fwd: [Yaml-core] schemas: two layers, extensibility] |
Date: |
03 Sep 2002 10:02:09 -0600 |
hi all, fowarding this b/c it coincidently deals with a couple things
we've hit on.
i think its interesting that steve mentions small-lests vs. big-lists,
as i was recently thinking about the form vs. function in terms of this
as well. i.e. if you specify that something is selectable, you may then
offer anopther paramter for a compact rendition vs. a verbose. just some
thoughts.
anyway the use of yaml is also interesting. we've been discussin yaml
schemas on the yaml mailing list.
cheers,
tom
-----Forwarded Message-----
> From: Steve Howell <address@hidden>
> To: address@hidden
> Subject: [Yaml-core] schemas: two layers, extensibility
> Date: 03 Sep 2002 11:10:49 -0400
>
> Tom,
>
> I like your explanation of how schemas might have different representations,
> depending on what level you were looking at them. I also agree with you that
> the lower-level representation is the more important one to nail down. You
> could certainly have a higher-level schema representation be parsed into a
> lower-level representation by some sort of proofreader too.
>
> Another thing we should consider when making a schema language is
> extensibility.
> A schema is really just metadata for a particular set of YAML documents. My
> favorite use case for schemas is generating GUI apps for YAML data, because
> it's
> a use case that Brian and I implemented successfully with his Perl version of
> YAML. Suppose you had two different GUI widgets for entering lists, where one
> works better for small lists, and the other works better for big lists. You
> might want an extra field in your schema for specifying that widget. A
> verbose
> syntax makes that easy.
>
> name: Corporation
> type: map
> items:
> - name: Board of directors
> type: seq
> widget: small_list
> - name: Employees
> type: seq
> widget: large_list
>
> This simple extension to the schema might save you a ton of custom coding, and
> you can still parse the schema with an ordinary YAML loader.
>
> Cheers,
>
> Steve Howell
> http://showell.westhost.com/
>
> P.S. Tom, my mailer doesn't deal well with PGP signatures, so I can't easily
> qoute your emails. I'm working on finding a better mailer.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Yaml-core mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/yaml-core
>
--
tom sawyer, aka transami
address@hidden
signature.asc
Description: This is a digitally signed message part
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [rgui-dev] [Fwd: [Yaml-core] schemas: two layers, extensibility],
Tom Sawyer <=