You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
---|
From: Andrew T. <and...@gm...> - 2007-08-25 02:40:42
|
I improved the images for the chessdrills, the old ones were just giving me headaches to look at. Also, I added a convenience function to the ChessDrill interface for Sven, SetSquareHilight(). There are currently three levels of hilighting available, but more can be added. I would like to implement a drill to get a better idea of what we need to add for future expansion. Unless somebody has an objection, I am going to implement the knight-sight drill. ~Andrew |
From: Thomas J. <tho...@gm...> - 2007-08-22 01:55:29
|
Andrew, that's great! I'll try to start integrating some of the drills over the next couple of days. Awesome work! Tom On 8/20/07, Andrew Thompson <and...@gm...> wrote: > > To: the awesomest chess drill programming team in the world! > > I have finished enough of the GUI that I think you guys can get > started working on your parts now. > The complete list of functions in ChessDrills.h that are functional: > Start() > ShouldAllowPiecePickup() > PieceWasPickedUp() > ShouldAllowPiecePlacement() > PieceWasPlaced() > SquareWasSelected() > MovePiece() (both of them) > ClearBoard() > > As you already know, to create a drill you will need to sub-class > ChessDrill. > Then, once it is created, to get it to work with the GUI, you will > need to modify drills/DrillList.h. > Basically, you need to add the name of the drill, and add a bit of > code that constructs it. > Also, you should probably add it to the makefile. If your drill is > just a .cpp file and a .h file, you can put it in the drills > directory, and edit the makefile adding the name of your class to the > _NMS variable (at the top of the makefile). > If your drill is in a seperate directory, then you should create a > makefile in that directory as well. Then modify the Makefile in the > drills directory to have a line 'make -C <yourDirectory>'. If you do > this, make sure the makefile drops the object files off in the 'obj' > directory and they will be included automatically in the final > project. > > Future planned work: finishing the functionality, making the GUI look > good, and port it to windows. If anyone has any suggestions on what > they might need to be done sooner than other things, let me know. > Also, I expect as we move forward, we will find that the ChessDrills.h > interface will need to change. We've already been through a couple > revisions, but if you have an idea of how to make it better, let me > know as well. > > If anyone has questions about how it all fits together, or needs help > with anything let me know. If anyone wants to learn GUI programming, > let me know as well and I will help you with that. :) > > Finally I'd just like to apologize for taking so long to get to this > point, work has really been wearing me out. Sorry 'bout it. > > May all your code be bugless, all your context switches fast, and all > your merges easy, > ~Andrew > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Chessdrills-devel mailing list > Che...@li... > https://lists.sourceforge.net/lists/listinfo/chessdrills-devel > |
From: Andrew T. <and...@gm...> - 2007-08-20 07:24:41
|
To: the awesomest chess drill programming team in the world! I have finished enough of the GUI that I think you guys can get started working on your parts now. The complete list of functions in ChessDrills.h that are functional: Start() ShouldAllowPiecePickup() PieceWasPickedUp() ShouldAllowPiecePlacement() PieceWasPlaced() SquareWasSelected() MovePiece() (both of them) ClearBoard() As you already know, to create a drill you will need to sub-class ChessDrill. Then, once it is created, to get it to work with the GUI, you will need to modify drills/DrillList.h. Basically, you need to add the name of the drill, and add a bit of code that constructs it. Also, you should probably add it to the makefile. If your drill is just a .cpp file and a .h file, you can put it in the drills directory, and edit the makefile adding the name of your class to the _NMS variable (at the top of the makefile). If your drill is in a seperate directory, then you should create a makefile in that directory as well. Then modify the Makefile in the drills directory to have a line 'make -C <yourDirectory>'. If you do this, make sure the makefile drops the object files off in the 'obj' directory and they will be included automatically in the final project. Future planned work: finishing the functionality, making the GUI look good, and port it to windows. If anyone has any suggestions on what they might need to be done sooner than other things, let me know. Also, I expect as we move forward, we will find that the ChessDrills.h interface will need to change. We've already been through a couple revisions, but if you have an idea of how to make it better, let me know as well. If anyone has questions about how it all fits together, or needs help with anything let me know. If anyone wants to learn GUI programming, let me know as well and I will help you with that. :) Finally I'd just like to apologize for taking so long to get to this point, work has really been wearing me out. Sorry 'bout it. May all your code be bugless, all your context switches fast, and all your merges easy, ~Andrew |
From: Thomas J. <tho...@gm...> - 2007-07-16 21:07:42
|
Hi guys, I finally got chessdrills-svn set up. This list should get an email each time anyone commits to subversion. You can subscribe to it through the Sourceforge website, or by sending email to che...@li.... I'm really glad to see that the GUI is making steady progress thanks to Andrew, and I'm excited about adding some new drills once the GUI is ready! Tom |