I agree with you Roger. I think this is how we should consider aiki
apps for now. This is more practical as well with our time and
resources. In the future, hopefully we can get to the place where we
make more powerful apps.
I'm still unclear technically however, with the direction you speak of
Ro
> But if apps are sites then what is the difference between them, I mean
> in database?
Certain apps are meta-sites. You can make a site about books,cliparts,
fonts, news, and can have apps to login or to admin site. I called meta,
because a login apps no worries about books, fonts, news.
Develo
I don't know about this one "Apps that have widgets are also defined as
sites.", but maybe it will resolve issue how to ship apps since apps
don't have stored widgets anywhere in aiki database. If the architecture
of aiki will allow to have installable sites then we can use them.
But if apps are s
Did we get this resolved?
On Thu, Mar 15, 2012 at 11:38 PM, Jon Phillips wrote:
> I think as well, rg1024, you have looked at the current architecture
> the most. I'm not sure what is possible now versus, the future.
>
> Jakub, the config class that rg1024 built can handle these differences
> in
I think as well, rg1024, you have looked at the current architecture
the most. I'm not sure what is possible now versus, the future.
Jakub, the config class that rg1024 built can handle these differences
in sites now.
I'm unclear about the distinctions overall, and why I made those wiki
pages try
I think that sites should work for instance if on the same server will
be sharism, OFLB and OCAL they will have different users, different
domain and different widgets, they will need different $config.
So what benefit will we have when login can have "*". It look like
templates (that I propose) t
The two proposal can't be mixed. The problems is what is a site, or a
multi-site.
A site is only certain output from the SAME data. For example: you can have
a frontpage, a backpage and
a rss feed. If you consider these as sites developing is easier: you can
use "*" in display_urls; a new widget i
This is apps to sites delay. Apps spec is good and we use it, the
blueprint say to replace apps by sites like login (login as a site).
Take into consideration that owner of the site (they should separated
and have separated users) what to modify an app and this affect other
sites.
With login is j
I reread it, so what is the problem?
http://aikiframework.org/wiki/Apps
I think figured out this apps spec is important.
I understand what a site is, but seems like the confusion is if apps
can work across sites? IMO, apps can work for one ore more sites, and
exist with a singular url like /mode
9 matches
Mail list logo
