Regarding installation of extensions, why not base it in the standard gem
system?
A system must be devised to let Radiant interact with the gem system, but
when that is solved we can take advantage of all the gem infrastructure that
is already implemented.
/AITOR
On 10/11/07, Sean Cribbs <[EMAIL PROTECTED]> wrote:
>
> Plugins and Radiant extensions are substantially different; I don't
> intend to create yet another plugin repository. There are two
> components to this effort:
>
> 1) A website that can be updated by extension authors to list their
> extensions.
> 2) Some command-line utilities to install, uninstall, and update
> extensions. Ideally, this would use an XML or YAML interface to the
> website.
>
> Sean
>
> Mitch Pirtle wrote:
> > On Oct 11, 2007, at 09:44 , Sean Cribbs wrote:
> >
> >
> >> I started an application at RailsConf that would be used to keep a
> >> registry of available extensions. It has been on the back-burner for
> >> quite a while, but I'll make it a point to get it ready for the 0.6.5
> >> release.
> >>
> >
> > Why not piggyback on the workingwithrails.com effort?
> >
> > -- Mitch
> > _______________________________________________
> > Radiant mailing list
> > Post: [email protected]
> > Search: http://radiantcms.org/mailing-list/search/
> > Site: http://lists.radiantcms.org/mailman/listinfo/radiant
> >
> >
>
> _______________________________________________
> Radiant mailing list
> Post: [email protected]
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
