On Mon, 2009-06-22 at 19:01 +0200, Loic Dachary wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I would like the following implemented: > > 0 System administration > > A new machine will be created and a new network installed on it.. The > table names, variants and betting structure (holdem, 5/10 no limit).
Are the default table names ok ? > There must be two bots playing on the first two tables. The poker > server must be configured with auto-refill set to the best buyin for > the 5/10 no limit betting structure. Does someone now the best buy in for 5-10-no-limit ? 2000 ? > The machine will be available at > http://pmw.pokersource.info/. The web server configuration must be > modified so that the home page is the poker game instead of a > subdirectory of jpoker. > > 1 jpoker skinning > > The jpoker installation must be skinned with exactly the same skin as > http://playformusic.com/, as found at > http://unique.pokersource.info/p4m-new/skin.html. In addition, the > login widget and the sign-up widget must be skinned using the same > graphics as the login box and the sign-up form of > http://playformusic.com/ Are you ok relying on a mercurial nested clone of jpoker in /usr/src like unique.pokersource.info, rather than the packaged version ? > > 2 sign-up widget > > A sign-up widget must be implemented and integrated with the existing > jpoker login box so that it is called when the user clicks on the > sign-up button. The sign-up must pop a lightbox with at least three > fields : login, password (password confirmation) and email address. > It can be merged or inspired from the userinfo widget that allows > editing of the database entry for a user. Upon validation the > poker-network packet ( see pokerpacket.py ) creating an account with > the email set must be sent. The error messages, if any, must be > displayed in the standard poker dialog box. If success is notified to > the jpoker client by the poker-network server, a confirmation message > must be displayed and the sign-up form lightbox dismissed. The user > must be logged in as a side effect ( he must not need to login after a > successfull signup ). If we use PackerPokerCreateAccount, the problem is that currently it is bypassing newly introduced pokerauth (see pokerservice.py:5796). sql = "INSERT INTO users (created, name, password, email, affiliate) values (%d, '%s', '%s', '%s', '%d')" % (seconds(), packet.name, packet.password, packet.email, packet.affiliate) An alternative would be to use PacketPokerLogin, and userInfo to set the email if the user creation succeed. > Please let me know if something is unclear, I'll do my best to answer > your questions. > Thanks in advance for your answers. -- Johan Euphrosine <[email protected]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pokersource-users mailing list [email protected] https://mail.gna.org/listinfo/pokersource-users
