From: Hans v. T. <hth...@zo...> - 2006-11-27 14:30:17
|
Hello All, The tutorial outline looks good to me, and I'd be happy to contribute. However, since I'm not a subject matter expert, I'd need some pointers to basic texts. Maybe just about GTK+, in those cases where Gth2Hs usage is a port of the same principle. The problem here seems to be, that those who know don't like to write, and those who'd like to write don't know (in my case anyway :-)). But with some good starting points, and some assured feed back (quality control), it seems feasible. I also think there are some good Gtk2hs examples available, and imo we should use these whenever possible. Best Regards, Hans van Thiel On Sat, 2006-11-25 at 20:55 +0000, Duncan Coutts wrote: > Hia folks, > > Several months ago we had a longish thread here about writing a > tutorial. We discussed tools etc and came to some conclusions on that > topic. What didn't happen however was any actual writing! :-) > > So that now that we do have the technology I'd like to ask again for > help writing an intro tutorial (or indeed tutorials on any more advanced > aspect of build GUI apps with Gtk2Hs). > > Thanks to Hans van Thiel porting a Glade tutorial from C to > Haskell/Gtk2Hs we do now have a tutorial on that subject. Subject to > approval from Hans and the original author, that tutorial will be hosted > on the Gtk2Hs site. > > So here's the setup: > > We keep the tutorials in the Gtk2Hs darcs repo in the txt2tags format. > > We have a makefiles that call txt2tags to generate XHTML or PS/PDF (via > latex) output. We also have a post-processor program that does syntax > highlighting of Haskell code and adds hyperlinks to the haddock > documentation. > > Here's an example. It's just a skeleton of a tutorial, but you get the > idea: > http://haskell.org/gtk2hs/docs/tutorial/intro/ > > And the source: > http://darcs.haskell.org/gtk2hs/docs/tutorial/intro/index.t2t > > > So how can you help? > > Get the Gtk2Hs sources and write something! :-) > > The easiest way for us to receive contributions is via darcs send, just > like ordinary code contributions. There's no need for contributions to > be major works, just adding a bit here or there or editing/fixing > existing stuff is great. > > If you don't want to use darcs then just email > gtk...@li... with your changes. > > Details: > > * Get the Gtk2Hs sources with darcs: > darcs get --partial http://darcs.haskell.org/gtk2hs/ > > * install txt2tags: http://txt2tags.sourceforge.net/download.html > > * Workflow: > 1. cd gtk2hs/docs/tutorial/intro/ > 2. $EDITOR intro.t2t > 3. make > 4. { repeat steps 2-3 until satisfied } > 5. darcs record > 6. darcs send > > > If you have particular ideas about how a tutorial should be structured > I'd be glad to hear them. > > Any questions or other suggestions? > > Duncan > |