<div dir="ltr">I think there are three ideas floating around here:<div><br></div><div>* Installing to the package database is sub-optimal. I'm in agreement here, this is a stop-gap measure so we can reuse direct-plugins as-is.</div>
<div>* This probably doesn't work with cabal-dev yet. I hope to fix this in the not-too-distant future. This new approach should make this possible, perhaps even easy.</div><div>* The browser should automatically refresh. wai-handler-devel does this already via a refresh meta tag (I *think* that's what I used...). Should be easy to add.</div>
<div><br></div><div>One other thing that I'd like to do: display compile errors in the browser. That will likely involve grabbing output sent to stderr. In other words, non trivial, but not particularly difficult.</div>
<div><br></div><div>Consider the implementation as-is for the 0.8.0 release to be alpha, and we'll hopefully improve upon it quickly.</div><div><br></div><div>Michael<br><br><div class="gmail_quote">On Tue, Apr 19, 2011 at 4:11 AM, Greg Weber <span dir="ltr"><<a href="mailto:greg@gregweber.info">greg@gregweber.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">good idea. I find prompting annoying though. Perhaps after the scaffold site is generate it can state:<div><br></div>
<div>
Now run your application with the command: "yesod devel"</div><div>Just a warning: "yesod devel" will install this cabal package in your cabal database.<div><div></div><div class="h5"><br>
<br><div class="gmail_quote">On Mon, Apr 18, 2011 at 5:55 PM, Felipe Almeida Lessa <span dir="ltr"><<a href="mailto:felipe.lessa@gmail.com" target="_blank">felipe.lessa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Mon, Apr 18, 2011 at 9:40 PM, Greg Weber <<a href="mailto:greg@gregweber.info" target="_blank">greg@gregweber.info</a>> wrote:<br>
> I agree that this isn't optimal (and should be avoided in the long-term),<br>
> but is it problematic in practice? It seems that the main problem would be<br>
> if the name conflicted with an existing one- but we are willing to put the<br>
> burden on the user to create a unique package name.<br>
<br>
</div>I just think that somehow the user should be warned that the package<br>
is going to be installed. Something like<br>
<br>
$ ls .yesod_devel_accepted<br>
ls: cannot access .yesod_devel_accepted: No such file or directory<br>
$ yesod devel<br>
This opereration needs to install your package to the user database.<br>
Do you want to proceed? You will not be asked again.<br>
Proceed? (y/N) y<br>
...<br>
$ ls .yesod_devel_accepted<br>
.yesod_devel_accepted<br>
$ yesod devel<br>
...<br>
<br>
Cheers,<br>
<br>
--<br>
<font color="#888888">Felipe.<br>
</font></blockquote></div><br></div></div></div>
</blockquote></div><br></div></div>