<p>+1</p>
<p>- Dan Allen</p>
<p>Sent from my Android-powered phone:<br>
An open platform for carriers, consumers and developers</p>
<div class="gmail_quote">On May 11, 2011 6:38 AM, "Paul Bakker" <<a href="http://paul.bakker.nl">paul.bakker.nl</a>@<a href="http://gmail.com">gmail.com</a>> wrote:<br type="attribution">> I agree.<br>
> <br>> Prompt 1<br>> "Do you want to save the plugin source? (do so if you plan to change the<br>> plugin) y/N"<br>> <br>> prompt 2<br>> "Where would you like to save the plugin source?"<br>
> <br>> Paul<br>> <br>> On Wed, May 11, 2011 at 3:31 PM, Lincoln Baxter, III <<br>> <a href="mailto:lincolnbaxter@gmail.com">lincolnbaxter@gmail.com</a>> wrote:<br>> <br>>> Agreed. A simple prompt asking if they would like to save the source for<br>
>> later would probably be sufficient to isolate this choice from the workflow<br>>> usability standpoint. Defaulting to "No" but if "Yes" is chosen, they will<br>>> get a second prompt for where they would like to save the project.<br>
>><br>>> Thoughts?<br>>> ~Lincoln<br>>><br>>><br>>> On Wed, May 11, 2011 at 4:51 AM, Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> wrote:<br>>><br>
>>> I say we prompt. After all, if you are downloading source, I'm very likely<br>>>> going to want to know where you are putting that source. We could remember<br>>>> the parent folder the first time they save source (make the config variable)<br>
>>> and suggest that location the second time they do it. That would be a<br>>>> stellar experience.<br>>>><br>>>> (We could even remind them they are free to hack on it, then reload).<br>
>>><br>>>> -Dan<br>>>><br>>>><br>>>> On Wed, May 11, 2011 at 01:45, Paul Bakker <<a href="http://paul.bakker.nl">paul.bakker.nl</a>@<a href="http://gmail.com">gmail.com</a>>wrote:<br>
>>><br>>>>> I think it's better to not put editable source code in .forge. With<br>>>>> upgrades of API's etc. it's sometimes necessary to throw away the .forge<br>>>>> dir. I like the idea though, so maybe we can ask the user: "where do you<br>
>>>> want to save the plugin project?" on plugin installation which by default<br>>>>> saves in .forge/plugins so that we don't mess up the user's file system.<br>>>>><br>>>>> Paul<br>
>>>><br>>>>> On Wed, May 11, 2011 at 10:27 AM, Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>>wrote:<br>>>>><br>>>>>> As I've been demoing forge, I've been pitching that one of the most<br>
>>>>> elegant aspects of the git-plugin command is that it automatically sets you<br>>>>>> up with source code to hack on. After experimenting with a plugin tonight, I<br>>>>>> realized that while the final artifact gets put in ~/.forge/plugins, the<br>
>>>>> repository is hidden away in a cryptic directory in my temporary folder. I<br>>>>>> think behavior should be changed to make it more welcoming for developers to<br>>>>>> contribute back.<br>
>>>>><br>>>>>> I propose one of the following two locations, though feel free to choose<br>>>>>> a more flexible option:<br>>>>>><br>>>>>> ~/.forge/plugin-repos<br>
>>>>> ~/forge/plugins<br>>>>>><br>>>>>> ...or read an option from .forge/config. Perhaps prompt the user where<br>>>>>> to stick the source even.<br>>>>>><br>
>>>>> -Dan<br>>>>>><br>>>>>> --<br>>>>>> Dan Allen<br>>>>>> Principal Software Engineer, Red Hat | Author of Seam in Action<br>>>>>> Registered Linux User #231597<br>
>>>>><br>>>>>> <a href="http://www.google.com/profiles/dan.j.allen#about">http://www.google.com/profiles/dan.j.allen#about</a><br>>>>>> <a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
>>>>> <a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>>>>>><br>>>>>><br>>>>>> _______________________________________________<br>
>>>>> forge-dev mailing list<br>>>>>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
>>>>><br>>>>>><br>>>>><br>>>>> _______________________________________________<br>>>>> forge-dev mailing list<br>>>>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>>>>><br>>>>><br>>>><br>>>><br>>>> --<br>
>>> Dan Allen<br>>>> Principal Software Engineer, Red Hat | Author of Seam in Action<br>>>> Registered Linux User #231597<br>>>><br>>>> <a href="http://www.google.com/profiles/dan.j.allen#about">http://www.google.com/profiles/dan.j.allen#about</a><br>
>>> <a href="http://mojavelinux.com">http://mojavelinux.com</a><br>>>> <a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>>>><br>>>><br>>>> _______________________________________________<br>
>>> forge-dev mailing list<br>>>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>>>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
>>><br>>>><br>>><br>>><br>>> --<br>>> Lincoln Baxter, III<br>>> <a href="http://ocpsoft.com">http://ocpsoft.com</a><br>>> <a href="http://scrumshark.com">http://scrumshark.com</a><br>
>> "Keep it Simple"<br>>><br>>> _______________________________________________<br>>> forge-dev mailing list<br>>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>>><br>>><br></div>