Re: [Pythoncard-users] PythonCard About dialog contest, submission deadline is May 9th

[Kevin A. <al...@se...>]

Just a reminder that the contest ends this Sunday. If you're going to 
submit something, don't wait until the last minute :)

ka

On Apr 22, 2004, at 1:17 PM, Kevin Altis wrote:

> In release 0.8 the PythonCard About dialog has been moved from 
> debug.py to its own module so that it can be more easily used by any 
> PythonCard app. You can look at the code in cvs.
>
> http://cvs.sourceforge.net/viewcvs.py/pythoncard/PythonCard/about.py
>
> Right now it is the same simplistic ScrolledMessageDialog that it used 
> to be. However, I thought it would be fun to have a contest for the 
> PythonCard About dialog so I'm accepting submissions for the About 
> dialog that we'll use in release 0.8 and above. Submissions will be 
> accepted from now through Sunday, May 9th, which gives you just over 
> two weeks.
>
> Submissions will then be voted on and in case of a tie, I will have 
> the deciding vote. While the winner will become the standard 
> PythonCard About dialog, at least a few of the runners up will 
> probably be included in the about.py module so they are also 
> available. If all of the submissions are great, we'll include them all 
> :)
>
> The rule set below seems overly long, but I want to be as clear as 
> possible.
>
> Rules (these may be modified if needed)
> * The information displayed should be in English. We may provide 
> alternate language versions of the dialog in the future, but for the 
> purposes of selecting a winner, everyone should use English for their 
> submissions.
> * You can use raw wxPython capabilities if needed.
> * The dialog must work on Windows, Mac OS X, and Linux. It is okay to 
> use alternative layouts and capabilities for each platform, but I 
> don't want to encourage the use of a dialog that only looks good on 
> one platform. For example, using some fancy Flash on Windows might not 
> be acceptable.
> * The About dialog should be a CustomDialog subclass. See the various 
> samples for examples: dbBrowser, dialogs, jabberChat, pysshed, 
> codeEditor, templates.dialogs.findDialog, codeEditor, resourceEditor. 
> You will probably want to use the resourceEditor to create your 
> dialog.
> * You should supply a function wrapper, again see the samples for 
> examples of how to do this. The function def should be:
>
> def aboutPythonCardDialog(parent=None):
>
> * While your design and code will be given attribution in the about.py 
> module, it may not carry with it any license. This will be a 
> fundamental part of PythonCard, so it will use the BSD style license 
> we've already adopted.
> * You may not use any artwork, images, other media, or source that you 
> don't own the rights to.
> * There should be some space for a PythonCard logo, at least 100 x 50 
> pixels. The logo will be a separate contest, but feel free to create 
> your own as a placeholder.
> * The dialog should be no larger than 600 x 400 so it fits on all 
> displays.
> * There should be a hypertext link to http://www.pythoncard.org/. Use 
> the Python webbrowser module to launch the web page. The link can be a 
> button, Image, ImageButton, StaticText with mouseDown handler, etc.
> * At least a minimum set of debug system info should be displayed 
> similar to the current About dialog: version info for PythonCard, 
> wxPython, Python, and the operating system platform. There is no need 
> to include PyCrust. If the information is not selectable and copyable 
> to the clipboard, then a button should be provided to put the 
> information in the clipboard.
> * You do not need to display all the info in the current About dialog, 
> even the one-line PythonCard description is optional, but there should 
> be something that says what PythonCard is.
>
> Additional guidelines:
> * The submission should be sent to the mailing list as a zip of all 
> the required files or as a URL to the source so that everyone can try 
> the dialog out. If you have questions before you make a final 
> submissiion, you can send the dialog and questions to me 
> <al...@se...>.
> * It is okay to use release 0.7.3.1 or 0.8 naming conventions. All 
> entries included in about.py be converted to the 0.8 API if needed.
> * You can request feedback from the list and modify your design up 
> until the deadline, but if you do so, I suggest maintaining the source 
> on your own site rather than sending zipped revisions continually to 
> the mailing list. If you don't have a site for storage, it can 
> probably be hosted on pythoncard.sf.net.
>
> Hopefully, that gives everyone enough freedom to create something that 
> looks great. If any of the guidelines above are unclear or you think 
> we should have different requirements, feel free to reply.
>
> ka