The plugin generator shouldn't have very many files to copy. Are you sure you weren't running it on an app that already was installed as normal plugin? One would either install as gem and then script/generate the plugin (which is only coded to create a handful of files and directories). It does create a lib/masterview and a few files under there but it shouldn't be the whole tree. I will double check but that wasn't what I was seeing happen. I will try to verify.
<br><br>If you can come up with a better way for us to do these cross gem dependencies I am all ears, that was causing headaches from the beginning, I didn't like it but couldn't come up with a better way yet. I also didn't like having to duplicate the files. I looked for a way to do this in svn but didn't find one yet, so created the rake task to help with it. Would be best if we could find a way to not have those issues. Of course it all gets tricky when being able to do things from straight plugin and via gems, but I really like having both ways to install. Serves more users that way. I would think that eventually plugins will evolve to using gems, not sure why they kind of abandoned them when they were created, there are nice features in gems including versioning and dependencies.
<br><br>Jeff<br><br><br><br><div><span class="gmail_quote">On 6/18/06, <b class="gmail_sendername">Deb Lewis</b> <<a href="mailto:djlewis@acm.org">djlewis@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Your original installation description of gem install say that after<br>installing masterview gem, running the masterview_plugin_generator will<br>"...create a very lightweight plugin instance for this application mainly
<br>consisting of an init.rb file which will get loaded at runtime. This init.rb<br>refers to the gem"<br><br>But... I just ran script/generate masterview_plugin for an install test and<br>it copied in the whole lib directory. I nuked lib, just to verify that it
<br>indeed wasn't needed.<br><br>So I think this is a bug in the masterview_plugin_generator, yes?<br><br>Also: mv admin controller is a feature of the main masterview gem, but it's<br>stylesheets depend on having the mv-generator also installed. Not good,
<br>this is essentially an "up-level" dependency (fundamental component shoudn't<br>depend on something optionally layered on top of it)<br><br>~ Deb<br><br><br>_______________________________________________<br>
Masterview-devel mailing list<br><a href="mailto:Masterview-devel@rubyforge.org">Masterview-devel@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/masterview-devel">http://rubyforge.org/mailman/listinfo/masterview-devel
</a><br></blockquote></div><br>