I finally got browser based aggie to work thanks to Sean and a bit more fiddling. It appears you need to grant the "Write" right to the wwwroot folder as well as the BrowserAggie installed folder (or I misunderstood seans instructions). Is this a bug?
I miss the collapsed view from the Aggie pixel skin, but the rest is quite nice and polished - although I'm unsure of the function of some of the buttons (the Scan button, for example). There are the traditional browser-based page update problems - the need to press F5 occasionally to see updated pages. I couldn't find a way to simulate a press of the Go! button thereby wiping out old news without pressing the "Update" button on each feed.
Anyway, well done Sean and keep up the good work.
Posted by Simon at November 8, 2002 03:01 PMscan button = go button.
After clicking the scan button you'll need to click the view button to get to the updated news page. I'm still working on making that more automated but I haven't had much time lately.
Also, giving write permission to the ASPNET user isn't a bug. It's necessary. Being a web app by default it doesn't have write permission but since Aggie writes a bunch of stuff to disk, you need to grant the write. The app needs to update the opml file as well as write cache information. A way around that would be to build a database for it and have everything stored there. I also need to work the preferences piece so that you can change skins just as in Aggie. All I need is more hours in the day or less sleep. 8)
Posted by sean at Nov 8, 2002 3:42 PMCool. I'll keep using it and see how I get on - it's nice not to have to load a program, I just go to the page in my browser which is always open!
If you find any of those extra hours be sure to send some my way!
Posted by Simon Steele at Nov 9, 2002 11:42 AM