I started adding my ideas, which will also impact Aiki markup if adopted.
Basically I think that Aiki widgets will be better if site designers are
forced to be explicit about the arguments in the URL.
Currently we design sites by setting display_url to something like "user"
and having (!(1)!) be a dynamic value like the username or userid. However,
the value of (!(1)!) is never explicit and must be guessed by examining the
entire widget content.
Instead, I suggest we use a concept of routes and tokens. So we would define
our route as:
/user/@id
and then use the value of that part of the url in the widget via:
<p>The user's id is {{@id}} </p>
This would allow a widget have two routes like so:
/user/@id
/user/settings/@id
And yet keep the content of the widget the same. This is more powerful as
well as more explicit. Now I don't have to look at your widget and guess
what (!(1)!) is supposed to refer to.
- Christopher
On Tue, Jun 21, 2011 at 2:03 PM, Roger Martín <[email protected]> wrote:
> Hi folks!
>
> In http://www.aikiframework.org/wiki/Aiki_widget_2 you can see
> documentation for widgets, mixed with some proposal.
>
> Please review this doc. I'm making changes on widget.php based on
> 'suppositions' (there is not specification and the code is very very
> confuse..)
>
> Roger
>
> _______________________________________________
> Mailing list: https://launchpad.net/~aikiframework-devel
> Post to : [email protected]
> Unsubscribe : https://launchpad.net/~aikiframework-devel
> More help : https://help.launchpad.net/ListHelp
>
>
--
———
christopher adams
86 186 1172 0021 | 1 646 201 3335
49 15 156 219931 | 886 953 036 630
chris.raysend.com
_______________________________________________
Mailing list: https://launchpad.net/~aikiframework-devel
Post to : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework-devel
More help : https://help.launchpad.net/ListHelp
