Yes, we need to make that clearer. Deb has been working on the user directive side of things so I'll see if she has any good ideas on that front. <br><br>So everything appears to be working if you add in any directive directories to the
config.directive_paths, but we'll make sure that either we communicate that better.<br><br>As for doing manual require's you shouldn't have to, but I wanted to provide full flexibility to do this if necessary. You could do this in
init.rb however ideally we would do it with the settings.rb, so not sure if we can simply put require's in there or not? Deb? (The main reason this might be needed is if you want to manually include a single file or to include a gem of directives).
<br><br><br><br><div><span class="gmail_quote">On 7/5/06, <b class="gmail_sendername">Ed Howland</b> <<a href="mailto:ed.howland@gmail.com">ed.howland@gmail.com</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;">
Thanks Jeff. I got confused by the masterview_plugin generator which<br>when I ran it created 'vendor/plugins/masterview/directives' which was<br>where I installed them previously. Since that option was commented<br>out, I assumed it still picked up any there and that you could add
<br>additional ones in the settings.<br><br>I suggest that you make a note of this in the announcement, since<br>others may run into this as well.<br><br>Also, I never explicitly require 'masterview' anywhere. Are you<br>
suggesting this in one of the normal Rails configuration files? Or in<br>vendor/plugins/masterview/init.rb?<br><br>Thanks<br>Ed<br><br><br><br>On 7/5/06, Jeff Barczewski <<a href="mailto:jeff.barczewski@gmail.com">jeff.barczewski@gmail.com
</a>> wrote:<br>> We didn't intentionally remove user level directives from the release. We<br>> consider it a benefit to allow user created directives.<br>><br>> I would guess that since the newer version uses new configuration of how
<br>> those user directive paths are specified that this is what broke things for<br>> you.<br>><br>> Check your config/masterview/settings.rb that you have specified<br>> config.directive_paths << /path/to/my/directives
<br>><br>> to include your directive directories.<br>><br>> I will run some tests to verify whether there are any issues with this.<br>><br>> Also note that you can also manually 'require' any files that you want if
<br>> you do it after you require 'masterview'. This will allow you to manually<br>> load any directives anywhere in your path including inside of gems. They<br>> simply have to be done after masterview though so that MasterView will
<br>> become aware of them as they load.<br>><br>> Jeff<br>><br>><br>> On 7/5/06, Ed Howland <<a href="mailto:ed.howland@gmail.com">ed.howland@gmail.com</a>> wrote:<br>> > After upgrading to
0.2.2, my directives in<br>> > vendor/plugins/masterview/directives no longer function.<br>> Scanned all<br>> > the documentation and could not find _any_ information on user created<br>> > directives.
<br>> ><br>> > Reading the code itself, there seems to be 2 commented out sections.<br>> > One refers to app/masterview/directives and the other refers to<br>> > config/masterview/directives. Seems to be a lot of TODO commentary.
<br>> ><br>> > Why were user directives disabled in this release and no notification<br>> > given? Is there a work around? I desperately need to get my code<br>> > working again.<br>> ><br>> > Thanks
<br>> ><br>> > Ed<br>> ><br>> > --<br>> > Ed Howland<br>> > <a href="http://greenprogrammer.blogspot.com">http://greenprogrammer.blogspot.com</a><br>> ><br>><br>><br><br><br>
--<br>Ed Howland<br><a href="http://greenprogrammer.blogspot.com">http://greenprogrammer.blogspot.com</a><br></blockquote></div><br>