I think there are three ideas floating around here:
* 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.
* 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.
* 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.
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.
Consider the implementation as-is for the 0.8.0 release to be alpha, and we'll hopefully improve upon it quickly.
Michael
On Tue, Apr 19, 2011 at 4:11 AM, Greg Weber
<greg@gregweber.info> wrote:
good idea. I find prompting annoying though. Perhaps after the scaffold site is generate it can state:
Now run your application with the command: "yesod devel"
Just a warning: "yesod devel" will install this cabal package in your cabal database.
On Mon, Apr 18, 2011 at 5:55 PM, Felipe Almeida Lessa
<felipe.lessa@gmail.com> wrote:
On Mon, Apr 18, 2011 at 9:40 PM, Greg Weber <
greg@gregweber.info> wrote:
> I agree that this isn't optimal (and should be avoided in the long-term),
> but is it problematic in practice? It seems that the main problem would be
> if the name conflicted with an existing one- but we are willing to put the
> burden on the user to create a unique package name.
is going to be installed. Something like
$ ls .yesod_devel_accepted
ls: cannot access .yesod_devel_accepted: No such file or directory
$ yesod devel
This opereration needs to install your package to the user database.
Do you want to proceed? You will not be asked again.
Proceed? (y/N) y
...
$ ls .yesod_devel_accepted
.yesod_devel_accepted
$ yesod devel
...
Cheers,
--
Felipe.