--- Log opened Tue Feb 10 00:00:05 2009
00:35 < mae__> ok I pushed up a very very rough first stab at the code generation tool
00:35 < mae__> I haven't added it to build-all yet
00:35 < mae__> but if ye are brave
00:35 < mae__> cd happstack
00:36 < mae__> cabal install
00:36 < mae__> then try
00:36 < mae__> happstack new project <dir>
00:36 < mae__> or
00:36 < mae__> happstack
00:36 < mae__> for usage
00:41 < h_buildbot> Build for ghc-6.8.3 failed. Check http://buildbot.happstack.com/ for details.
00:41 < mae__> ok i fixed the build
00:41 < mae__> should be ok now
00:41 < mae__> h_buildbot:
00:41 < mae__> h_buildbot: hey
00:41 < h_buildbot> Use: build, status, pause, resume, ping
00:42 < mae__> h_buildbot: ping
00:42 < h_buildbot> pong
00:42 < mae__> h_buildbot: status
00:42 < h_buildbot> Building ghc-6.10.1
00:42 < h_buildbot> Build for ghc-6.10.1 failed. Check http://buildbot.happstack.com/ for details.
00:43 < mae__> For all who are interested, I am speaking about Happstack with Thomas Hartman, see http://blog.happstack.com/2009/02/03/socalfp-presentation-patch-tag-as-a-startup-using-happstack/ for more info.
00:43 < mae__> (event is tommorrow)
00:43 < mae__> (at UCLA)
00:44 < mae__> h_buildbot: build
00:44 < h_buildbot> Build for all started. If one was running, no new one is started.
00:51 < h_buildbot> Build for ghc-6.8.3_STABLE OK. Test suite ran. 16/73 test cases failed. Check http://buildbot.happstack.com/ for details.
00:55 < dsrogers> I've got an implementation of WebT that reuses both ErrorT and MaybeT.  And one small monad to handle the filter composing
00:56 < dsrogers> and I'm wondering if I can find a monad that already implemented that...
00:57 < h_buildbot> Build for ghc-6.10.1_STABLE OK. Test suite ran. 16/73 test cases failed. Check http://buildbot.happstack.com/ for details.
01:00 < mae__> dsrogers: you the man :)
01:00 < mae__> fate brought us together
01:00 < mae__> code reuse to the rescue!
01:04 < h_buildbot> Build for ghc-6.8.3 OK. Test suite ran. 15/75 test cases failed. Check http://buildbot.happstack.com/ for details.
01:09 < h_buildbot> Build for ghc-6.10.1 OK. Test suite ran. 15/75 test cases failed. Check http://buildbot.happstack.com/ for details.
01:30 < mae__> hola
12:38 < wchogg> Not to keep harping on stuff, but it doesn't look like the Happstack.Server.JSON module is actually used anywhere.  Another candidate for culling?
12:40 < Saizan_> wchogg: we should determine which convenience it provides and probably reimplement that on top of an external json library
12:41 < Saizan_> if we only remove the unneeded parts we end up with HAppS-State rather than a webframework :)
12:43 < wchogg> Saizain_ : Well, honestly I don't see what it provides over the Galois json library.  It looks like it's half finished.
12:48 < Saizan_> wchogg: yeah, then maybe we want to e.g. make a ToMessage instance for the galois' json or something like that
12:49 < Saizan_> wchogg: in the happstack package
12:51 < koeien> Saizan_: i think a collection of useful packages is very useful, even if not all packages are happstack-X
12:55 < paulvisschers> I think we should actually remove any module that isn't used by many people, and keep happs very lightweight in this early stage
12:55 < paulvisschers> we can add more modules later, when the core is more mature
12:55 < paulvisschers> and reintroduce things we remove now
13:18 < Saizan_> koeien: well, there are a lot of libraries around, but if you don't provide the minimum code to use them inside happs then happs has little value
13:18 < Saizan_> (for relevant libraries i mean)
13:20 < stepcut> happs makes you so efficient, that you don't need third party libraries, you have time to write them all yourself
13:21 < stepcut> In other news, I like to imagine what it would be like if the world were reversed
13:22 < stepcut> imagine if everyone used happstack-state. And then some guy comes along and has this idea for a 'new and better' way where you store your state in some other process, and you talk to this process by sending a string to it that uses some funky domain specific language, and the data store can only handle primitive types like Int and String, so you are going to have to convert all your datastructures into simple types and back.
13:23 < stepcut> do you think it would catch on?
13:23 < koeien> i think so
13:23 < koeien> such a thing would be very popular ;)
13:23 < stepcut> I dunno
13:24 < koeien> let's call it TQL, Trivial Query Language
13:24 < stepcut> if you were already familiar with and comfortable with happstack-state, I think you would need something more compelling
13:25 < Saizan_> stepcut: does happs-state have sharding in this world?:)
13:25 < stepcut> Saizan_: yes
14:28 < stepcut> 6.10.2 RC1 should be out next week, that should fix the haddock+TH issues hopefully
14:29 < koeien> "internal name"?
14:29 < koeien> or the borking of haddock on TH?
14:29 < stepcut> the borking of haddock on TH
14:30 < stepcut> no idea about the internal name
14:49 < thetallgu1> Do you know if ghc 6.10.2 is the current ghc head or is there a branch?
14:52 < stepcut> no idea
14:53 < thetallgu1> wrong channel
--- Log closed Wed Feb 11 00:00:06 2009