Proposal for 1.0: os:Variable tag

0 views
Skip to first unread message

goosemanjack

unread,
Oct 12, 2009, 1:55:03 PM10/12/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion
Wiki page here.

http://wiki.opensocial.org/index.php?title=Temporary_vars_in_templates_and_data_pipelining#Proposal:

Creating this thread to split discussion from deprecation of
DataAttribute discussion.

Lev Epshteyn

unread,
Oct 12, 2009, 5:28:51 PM10/12/09
to opensocial-an...@googlegroups.com
Did we not agree this was out of scope for the current iteration?

I fully support the idea of a var tag, it just seems like this is new functionality where we're still trying to fix existing spec bugs for 1.0...

goosemanjack

unread,
Oct 14, 2009, 1:31:53 PM10/14/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion
I interpreted a comment from the "deprecate DataAttribute" thread to
mean we were reconsidering bringing os:Var back into scope:

http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/2cf30bdd6fd2d757/3a670dbf0f1a8456?hl=en#msg_4be57096f88dbfc9

> And from this thread, it doesn't look like we can deprecate Cur
> outside of repeaters without the os:Var stuff.

> -Lane


Our support of keeping the scope restricted for 1.0 to bug fixes
originally came with the caveat that we wanted os:Var included for
consideration this round. We'd also like to see the syntax support
the shortened form "os:Var" in addition to/instead of "os:Variable"

--
clc


On Oct 12, 2:28 pm, Lev Epshteyn <le...@google.com> wrote:
> Did we not agree this was out of scope for the current iteration?
>
> I fully support the idea of a var tag, it just seems like this is new
> functionality where we're still trying to fix existing spec bugs for 1.0...
>
> On Mon, Oct 12, 2009 at 1:55 PM, goosemanjack <cc...@myspace.com> wrote:
>
> > Wiki page here.
>
> >http://wiki.opensocial.org/index.php?title=Temporary_vars_in_template...
> > :

goosemanjack

unread,
Oct 26, 2009, 8:58:45 PM10/26/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion
Modified proposal to use the shortened <os:Var > syntax (as everyone
seems to use) instead of the more lengthy <os:Variable> syntax.
--
clc




On Oct 14, 10:31 am, goosemanjack <cc...@myspace.com> wrote:
> I interpreted a comment from the "deprecate DataAttribute" thread to
> mean we were reconsidering bringing os:Var back into scope:
>
> http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thr...

goosemanjack

unread,
Nov 3, 2009, 6:24:38 PM11/3/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion

Patch created and available for review
http://codereview.appspot.com/143075

Lev Epshteyn

unread,
Nov 3, 2009, 6:31:07 PM11/3/09
to opensocial-an...@googlegroups.com
Chris, I had some questions about how the proposed syntax can be used for defining non-hardcoded variables - posted on the thread here: https://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/eb3606b9caa9e348#

Evan had some comments as well.

Can you respond? I feel like we need to get this hammered out conceptually before we get to patches.

--

You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.



Evan Gilbert

unread,
Nov 4, 2009, 1:53:11 AM11/4/09
to opensocial-an...@googlegroups.com
On Tue, Nov 3, 2009 at 3:31 PM, Lev Epshteyn <le...@google.com> wrote:
Chris, I had some questions about how the proposed syntax can be used for defining non-hardcoded variables - posted on the thread here: https://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/eb3606b9caa9e348#

Evan had some comments as well.

Can you respond? I feel like we need to get this hammered out conceptually before we get to patches.

Yes, talking through the conceptual level will help.

Also it would be nice to see use cases, possibly with before / after examples. A number of the examples in the code review seem to be supporting functionality that already has a convenient syntax.
Reply all
Reply to author
Forward
0 new messages