OK, thank you very much for answering.
Regards,
// Rolf Lampa
Markus Krötzsch skrev:
> On Dienstag, 10. Februar 2009, Rolf Lampa [RIL] wrote:
>
>> Hi Markus,
>>
>> Is it a known issue that #set: doesn't seem to set a value passed to it
>> from a variabl
Hi Markus,
Is it a known issue that #set: doesn't seem to set a value passed to it
from a variable? Like so:
{{#set:prop={{#var:value
A parsing problem?
// Rolf Lampa
--
Create and Deploy Rich Internet Apps outsi
This looks useful.
It would be nice to also be able to give a file name as a parameter
(text file holding a list of titles). And/or a wiki page title, where
from where the script retrieves a list of titles! (see more about that
below).
Example of usage: When I auto generate entire sites from U
Jie Bao skrev:
> Dear Semantic Wiki developers and users,
>
> We are looking for your *horizontal* experiences with Semantic Wiki,
> i.e., building domain-independent tools and applications on Semantic
> MediaWiki, in the upcoming 5th session in the Semantic Wiki Mini
> series (Feb 12, 2009, Thurs
ll kinds of other useful meta information (useful at runtime).
Regards,
// Rolf Lampa
Rolf Lampa [RIL] skrev:
= Type aliases revisited =
(Perhaps I better ask abut types in the developers list).
When I have a model with a class Person (with a single link to an
Address), and a sub class Male,
= Type aliases revisited =
(Perhaps I better ask abut types in the developers list).
When I have a model with a class Person (with a single link to an
Address), and a sub class Male, like so:
[Person]*-inmates--home address-1[Address]
|
specialization (inherits)
|
Dan Bolser skrev:
> 2009/1/26 Rolf Lampa [RIL] :
>
>> Yaron Koren skrev:
>>
>>> Okay, thanks. Well, there's no chance I'm going to implement this any
>>> time soon, to answer your question.
>>>
>> :(
>>
>&g
ge from within
the templates (of Book and Author) instead?
Regards,
// Rolf Lampa
> On Mon, Jan 26, 2009 at 11:00 AM, Rolf Lampa [RIL]
> mailto:rolf.la...@rilnet.com>> wrote:
>
> Yaron Koren skrev:
>
> Okay, thanks. Well, there's no chance I'm going
>
> -Yaron
>
> On Mon, Jan 26, 2009 at 10:13 AM, Rolf Lampa [RIL]
> mailto:rolf.la...@rilnet.com>> wrote:
>
>
>
> Rolf Lampa [RIL] skrev:
>
>
> #1. Book: standard Semantic Form behavior.
> #2. Author: autocreated.
Rolf Lampa [RIL] skrev:
>
> #1. Book: standard Semantic Form behavior.
> #2. Author: autocreated.
> #3. BookAuthorLink: autocreated.
>
Actually only step #3 (BookAuthorLink) needs the (final) titles of the Book
title AND the Author title, for the single
Sigh, silly name for BookAuthorLink corrected:
#1. Book: standard Semantic Form behavior.
#2. Author: autocreated.
#3. BookAuthorLink: autocreated.
// Rolf Lampa
Rolf Lampa [RIL] skrev:
> Yaron Koren skrev:
>
>> Hi,
>>
>> Maybe I should rephrase -
or (for the same reason
as #2 above).
Please ask more.
// Rolf Lampa
>
> -Yaron
>
> On Mon, Jan 26, 2009 at 9:54 AM, Rolf Lampa [RIL]
> mailto:rolf.la...@rilnet.com>> wrote:
>
> For some reason a lot of strange extra slashes were inserted in
> the post
>
) are getting
> created automatically?
>
> -Yaron
>
> On Mon, Jan 26, 2009 at 9:02 AM, Rolf Lampa [RIL]
> mailto:rolf.la...@rilnet.com>> wrote:
>
> Hi,
>
> Since a n..n relation essentially is made out of two 1..n
> relations (seen from the "mi
eters.
Regards,
// Rolf Lampa
Yaron Koren skrev:
> Hi,
>
> I don't understand - of the three page types, which one(s) are getting
> created automatically?
>
> -Yaron
>
> On Mon, Jan 26, 2009 at 9:02 AM, Rolf Lampa [RIL]
> mailto:rolf.la...@rilnet.com>> wrote:
>
e supported; the benefit wouldn't outweigh the complexity. But it's
> good to know that for sure.
>
> Dan - your example is relatively simple and straightforward; however,
> I think it's outside the scope of this discussion, since it covers the
> case of two page ty
Regarding the typical "constraint approach" of UML (I'm thinking
especially about the 1..n relation) I'm sensing an emerging clash
between open and closed semantic paradigms here... :)
Would be interesting with some philosophical reflexions over this
possible clash of paradigm from experts on
Rolf Lampa [RIL] skrev:
> Dan Bolser skrev:
>
>> [...]
>> 1..n relationship
>> [...]
>> When creating a Book, the Author form would be handled just like a
>> template that can occur (on the Book page) multiple times. The user
>> would 'add
Dan Bolser skrev:
> [...]
> 1..n relationship
> [...]
> When creating a Book, the Author form would be handled just like a
> template that can occur (on the Book page) multiple times. The user
> would 'add author' as many times as needed (just as if the Author
> template were being added to the
Rolf Lampa [RIL] skrev:
> [...]
> Or a direct parser function(?):
>
> {{{createpage|allow-inform-create}}}
> {{#createpage: classname | role1=... | role2=... |...}}
> {{{createpage end}}}
>
Such a ParserFunction could "quietly" disregard createpage if the page
== Code generation ==
Considering code generation, a separate notation for the template (or
ParserFunction) call is preferred because such calls could be used
separately from forms (on other pages as well) and then the code
generator would need to regard only one syntax for generating the actua
Yaron Koren wrote:
> > ... suggestion for how automatic-page-creation can be
> > defined within form definitions (or wherever else you think it should
> > happen)
I'll be back with more on this later, but for a start I think one must
give some thought to the following:
= Template approach =
>
> -Yaron
>
> On Fri, Jan 23, 2009 at 4:27 AM, Rolf Lampa [RIL]
> mailto:rolf.la...@rilnet.com>> wrote:
>
>
>
> Dan Bolser skrev:
> > 2009/1/23 Alex Le Bek <mailto:alexle...@googlemail.com>>:
> >
> >> What a reli
Dan Bolser skrev:
> 2009/1/23 Alex Le Bek :
>
>> What a relief to see this discussion... I have been worrying about this and
>> would be so grateful for a solution. The use of 'multiple' on forms brings
>> this difficultly into sharp focus.
>>
>
> Can one SF form create multiple pages?
>
#declare is sensitive to space chars after the equal sign when used in a
template. Example:
{{#declare:PropertyName=ParamName}} : OK
{{#declare:PropertyName= ParamName}} : NOT OK
^
I also tried all other combinations, but those are OK:
{{ #declare: PropertyName =ParamNam
24 matches
Mail list logo
