[typo] Typo's memory footprint

Steve Longdo steve.longdo at gmail.com
Tue Aug 1 15:20:27 EDT 2006


What needs to happen to transistion out of the current component model into
the vendor/plugin model?

I have heard the new routing code allows plugins to register named routes
when they are loaded into a parent app.  This would allow for sidebars that
could have more than one "content page".

On 8/1/06, Piers Cawley <pdcawley at bofh.org.uk> wrote:
>
> "Steve Longdo" <steve.longdo at gmail.com> writes:
>
> > It is a funtion of the sidebar and textfilter controller where it
> > dynamically loads all files in the directories into memory:
> >
> > Dir["#{RAILS_ROOT}/components/plugins/sidebars/[_a-z]*.rb"].each do |f|
> >  require_dependency f
> > end
> >
> > So it is cool because when new plugins are added they automagically load
> up,
> > but unfortunate when, like Sparklines, they have a large overhead
> > associated.
> >
> > As for knobs, you could have something that wrote a more specific
> regular
> > expression for the load instead of just [_a-z]*.rb...
>
> This is something that could be helped by the mooted move of sidebar
> plugins to vendor/plugins. Essentially you'd only need to install
> those sidebars you use.
>
> --
> Piers Cawley <pdcawley at bofh.org.uk>
> http://www.bofh.org.uk/
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>

-- 
Thanks,
-Steve
http://www.stevelongdo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20060801/c76d8fa7/attachment.html 


More information about the Typo-list mailing list