Paket.VisualStudio
Paket.VisualStudio copied to clipboard
Create cool UI for Paket's output
In https://github.com/fsprojects/Paket.VisualStudio/blob/master/src/Paket.VisualStudio/PaketOutputPane.cs#L39 we register Paket's output to the VS output pane. This is good to look up what happened, but during sync commands like "Add package" we don't get any feedback.
In atom we have the following:
Since we have already ReactiveUI in place we should open a nice output dialog in https://github.com/fsprojects/Paket.VisualStudio/blob/master/src/Paket.VisualStudio/Commands/AddPackageProcess.cs#L47 and show Paket's output there.
/cc @TheAngryByrd
Great idea. Looks like I could easily open a dialog and show the trace output.
How do we know when an Add succeeded or failed? Does the Add function throw an exception?
Sorry I don't know the paket api too well. I'll probably start poking around myself though.
Yes it will throw.
Also need this for the other commands like update, install, restore...
Have any thoughts on where those should go or be displayed?
I think it should go to the output dialog that you created
2015-05-19 13:34 GMT+02:00 Jimmy Byrd [email protected]:
Have any thoughts on where those should go or be displayed?
— Reply to this email directly or view it on GitHub https://github.com/fsprojects/Paket.VisualStudio/issues/37#issuecomment-103453342 .
Where are all the places a person can do these commands? I spy with my little print screen eye:
Also, do we still want to go with a WPF window opening and the output window flying in?
Yes that's what I meant On May 22, 2015 10:23 PM, "Jimmy Byrd" [email protected] wrote:
Where are all the places a person do these menu options? I spy with my little print screen eye: [image: package] https://cloud.githubusercontent.com/assets/1490044/7779019/c1710f06-009e-11e5-8a4e-00f4315d2ce0.png [image: paketdeps] https://cloud.githubusercontent.com/assets/1490044/7779018/c1710326-009e-11e5-8127-772d9961dec0.png [image: paketrefs] https://cloud.githubusercontent.com/assets/1490044/7779020/c1727544-009e-11e5-8d8b-9b770fd35364.png
Also, do we still want to go with a WPF window opening and the output window flying in?
— Reply to this email directly or view it on GitHub https://github.com/fsprojects/Paket.VisualStudio/issues/37#issuecomment-104759098 .
Did you have a chance to look into this? Would love to see that working.
Sorry I dropped the ball on this. I'll push what bits I have, should do some of what we want.