[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [uiml] Tentative Schedule for Completing the Working Draft
Jo, Thank you for your input! I think your idea is excellent! I think it should definitely be included in v4.1. >>There are still some unexplored issues. It might require types on our parameters (as in the vocabulary) to know what values to pass to which parameter. << This may not be necessary... The types could probably be inferred from the vocabulary. After all, in most cases the template parameters are being used to fill in property values in the template and the d-property tags in the vocabulary should already specify the type. Does that make sense? Regards, James Helms Director of Research and Development Harmonia, Inc. P.O. Box 11282 Blacksburg, VA 24062 Office: (540) 951-5900 x 205 Cell: (540) 558-9722 -----Original Message----- From: jo.vermeulen@gmail.com [mailto:jo.vermeulen@gmail.com] On Behalf Of Jo Vermeulen Sent: Monday, August 06, 2007 8:39 AM To: James Helms Cc: Robbie Schaefer; jean.vanderdonckt@uclouvain.be; Kris Luyten; Heinz Josef Eikerling Subject: Re: [uiml] Tentative Schedule for Completing the Working Draft On 8/3/07, Jo Vermeulen <jo.vermeulen@uhasselt.be> wrote: > Hello James et al., > > In attachment my version with comments. I still need to do some work > on the template parametrization section (I'm trying to make it more of > a specification and less of a proposal (-:), but the rest of the > document should be OK. > > I will send you an update on the template parametrization by Monday. Hello everyone, James, I am still polishing the template parameterization section, I'll send you the final version in a few hours. I wanted to share an idea I had while working on the template parameterization section. With the current spec, it's possible to pass string constants to templates using template parameterization. This is already very useful :-) However, suppose we want to pass a value we don't know beforehand or a more complex type? Suppose we want to pass a value returned by the application logic (obtained by using a call element), the value of a property (e.g. <property part-name="btn_quit" name="label"/>) or a list of values (specified by <constant model="list">...</constant>). We can get all of this pretty easily by allowing all of the property element's possible children inside the <template-param> element as well (e.g. call, property, constant, etc.). There are still some unexplored issues. It might require types on our parameters (as in the vocabulary) to know what values to pass to which parameter. Then again, by adopting almost everything from the property element, we might prefer to rename d-template-param to d-property and template-param to property :-) They could be seen as "properties" of a template, which is then sort-of a d-class, although that might cause confusion ... Needless to say that this is currently not implemented in our renderer and that it's too late for inclusion in UIML 4.0. However, it might be a nice extension on template parameterization for a future version of UIML (4.1?). Feel free to comment on this as always! :-) Best regards, -- Jo Vermeulen Researcher EDM - Hasselt University Wetenschapspark 2 3590 Diepenbeek, Belgium tel: +32 (0)11 268411 email: jo.vermeulen@uhasselt.be web: http://jozilla.net/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]