BZFlagWiki - User contributions [en]

GSoC: LibBZW

2008-06-10T04:51:23Z

Lukstr: update description bzfs.cxx

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future [[BZW]] functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within [[BZFlag]]. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. [[BZFS]] will depend on libBZW, and is within /bzflag/src).

==Features==
*BZW file parsing

==Functionality==
libBZW will initially contain methods and functionality from the following sources:
Just so I can keep track of what files I will need initially, obtained via grep, primitive list.
Need to add summaries of functionality desired to be copied/reproduced/replicated from each file. --Lukstr
*bzflag/
**src/
***bzfs/
****'''bzfs.cxx''' -- ''Read worlds (via stream/blob or filename), retrieve WorldInfo''
****'''BZWReader.h'''
****'''BZWReader.cxx'''
****'''BZWError.cxx'''
****'''BZWError.h'''
****'''CmdLineOptions.cxx'''
***bzflag/
****'''World.cxx'''
**tools/
***modeltool/
****'''modeltool.cxx''' -- ''Creating/writing bzw files''
*bzwworkbench/
**src/
***model/
****'''BZWParser.cpp''' -- ''Cleaner parser than bzfs?''
****'''Model.cpp'''
**include/
***model/
****'''BZWParser.h'''
****'''Model.h'''

==API==

GSoC: LibBZW

2008-06-10T04:39:14Z

Lukstr: /* Functionality */

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future [[BZW]] functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within [[BZFlag]]. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. [[BZFS]] will depend on libBZW, and is within /bzflag/src).

==Features==
*BZW file parsing

==Functionality==
libBZW will initially contain methods and functionality from the following sources:
Just so I can keep track of what files I will need initially, obtained via grep, primitive list.
Need to add summaries of functionality desired to be copied/reproduced/replicated from each file. --Lukstr
*bzflag/
**src/
***bzfs/
****'''bzfs.cxx''' -- ''Read worlds (via iostream), retrieve WorldInfo''
****'''BZWReader.h'''
****'''BZWReader.cxx'''
****'''BZWError.cxx'''
****'''BZWError.h'''
****'''CmdLineOptions.cxx'''
***bzflag/
****'''World.cxx'''
**tools/
***modeltool/
****'''modeltool.cxx''' -- ''Creating/writing bzw files''
*bzwworkbench/
**src/
***model/
****'''BZWParser.cpp''' -- ''Cleaner parser than bzfs?''
****'''Model.cpp'''
**include/
***model/
****'''BZWParser.h'''
****'''Model.h'''

==API==

GSoC: LibBZW

2008-06-10T04:38:27Z

Lukstr: added bzfs.cxx knowledge

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future [[BZW]] functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within [[BZFlag]]. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. [[BZFS]] will depend on libBZW, and is within /bzflag/src).

==Features==
*BZW file parsing

==Functionality==
libBZW will initially contain methods and functionality from the following sources:
Just so I can keep track of what files I will need initially, obtained via grep, primitive list.
Need to add summaries of functionality desired to be replicated from each file. --Lukstr
*bzflag/
**src/
***bzfs/
****'''bzfs.cxx''' -- ''Read worlds (via iostream), retrieve WorldInfo''
****'''BZWReader.h'''
****'''BZWReader.cxx'''
****'''BZWError.cxx'''
****'''BZWError.h'''
****'''CmdLineOptions.cxx'''
***bzflag/
****'''World.cxx'''
**tools/
***modeltool/
****'''modeltool.cxx''' -- ''Creating/writing bzw files''
*bzwworkbench/
**src/
***model/
****'''BZWParser.cpp''' -- ''Cleaner parser than bzfs?''
****'''Model.cpp'''
**include/
***model/
****'''BZWParser.h'''
****'''Model.h'''

==API==

GSoC: LibBZW

2008-06-10T02:52:30Z

Lukstr: added files to look at

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future [[BZW]] functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within [[BZFlag]]. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. [[BZFS]] will depend on libBZW, and is within /bzflag/src).

==Features==
*BZW file parsing

==Functionality==
libBZW will initially contain methods and functionality from the following sources:
Just so I can keep track of what files I will need initially, obtained via grep, primitive list.
Need to add summaries of functionality desired to be replicated from each file. --Lukstr
*bzflag/
**src/
***bzfs/
****'''bzfs.cxx'''
****'''BZWReader.h'''
****'''BZWReader.cxx'''
****'''BZWError.cxx'''
****'''BZWError.h'''
****'''CmdLineOptions.cxx'''
***bzflag/
****'''World.cxx'''
**tools/
***modeltool/
****'''modeltool.cxx''' -- ''Creating/writing bzw files''
*bzwworkbench/
**src/
***model/
****'''BZWParser.cpp''' -- ''Cleaner parser than bzfs?''
****'''Model.cpp'''
**include/
***model/
****'''BZWParser.h'''
****'''Model.h'''

==API==

GSoC: LibBZW

2008-06-07T01:54:22Z

Lukstr: added content

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future [[BZW]] functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within [[BZFlag]]. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. [[BZFS]] will depend on libBZW, and is within /bzflag/src).

==Features==
*BZW file parsing

==Functionality==
libBZW will initially contain methods and functionality from the following sources:
Just so I can keep track of what files I will need initially, obtained via grep, primitive list.
Need to add summaries of functionality desired to be replicated from each file. --Lukstr
*bzflag/
**src/
***bzfs/
****bzfs.cxx
****BZWReader.h
****BZWReader.cxx
****BZWError.cxx
****BZWError.h
****CmdLineOptions.cxx
***bzflag/
****World.cxx
**tools/
***modeltool/
****modeltool.cxx -- ''Creating/writing bzw files''

GSoC: LibBZW

2008-06-06T09:14:06Z

Lukstr: Made comments proper.

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future [[BZW]] functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within [[BZFlag]]. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. [[BZFS]] will depend on libBZW, and is within /bzflag/src).

==Features==
*BZW file parsing

==Functionality==
libBZW will initially contain methods and functionality from the following sources:
Just so I can keep track of what files I will need initially, obtained via grep, primitive list.
Need to add summaries of functionality desired to be replicated from each file. --Lukstr
*bzflag/
**src/
***bzfs/
****bzfs.cxx
****BZWReader.h
****BZWReader.cxx
****BZWError.cxx
****BZWError.h
****CmdLineOptions.cxx
***bzflag/
****World.cxx
**tools/
***modeltool/
****modeltool.cxx -- ''Is there anything here desireable? --Lukstr''

GSoC: LibBZW

2008-06-06T09:00:18Z

Lukstr: Fixed incomplete sentance, added bullet

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future [[BZW]] functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within [[BZFlag]]. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. [[BZFS]] will depend on libBZW, and is within /bzflag/src).

==Features==
*BZW file parsing

==Functionality==
libBZW will initially contain methods and functionality from the following sources:
Just so I can keep track of what files I will need initially, obtained via grep, primitive list.
Need to add summaries of functionality desired to be replicated from each file. --Lukstr
*bzflag/
**src/
***bzfs/
****bzfs.cxx
****BZWReader.h
****BZWReader.cxx
****BZWError.cxx
****BZWError.h
****CmdLineOptions.cxx
***bzflag/
****World.cxx
**tools/
***modeltool/
****modeltool.cxx
Is there anything here desireable? --Lukstr
**misc/
***3ds2bzw.c
Likewise, here? --Lukstr

GSoC: LibBZW

2008-06-06T08:58:29Z

Lukstr: Added list of files to be "investigated"

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future [[BZW]] functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within [[BZFlag]]. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. [[BZFS]] will depend on libBZW, and is within /bzflag/src).

==Features==
BZW file parsing into

==Functionality==
libBZW will initially contain methods and functionality from the following sources:
Just so I can keep track of what files I will need initially, obtained via grep, primitive list.
Need to add summaries of functionality desired to be replicated from each file. --Lukstr
*bzflag/
**src/
***bzfs/
****bzfs.cxx
****BZWReader.h
****BZWReader.cxx
****BZWError.cxx
****BZWError.h
****CmdLineOptions.cxx
***bzflag/
****World.cxx
**tools/
***modeltool/
****modeltool.cxx
Is there anything here desireable? --Lukstr
**misc/
***3ds2bzw.c
Likewise, here? --Lukstr

GSoC: LibBZW

2008-03-28T02:11:26Z

Lukstr: added wiki links

GSoC: LibBZW

2008-03-28T02:10:07Z

Lukstr: Created and added some details regarding implementation

{{DesignDocument}}
''libBZW is a proposed library that will encompass current and future BZW functionality, replacing independant implementations in various applications, including bzfs.''
==Implementation==
libBZW will be implemented as a static library within BZFlag. Applications/builds depending on libBZW should be within the BZFlag tree as well for sanity's sake (i.e. bzfs will depend on libbzw, and is within /bzflag/src).

User:Lukstr

2008-03-27T16:42:26Z

Lukstr: Undid such madness.

Please ask any questions or comments in discussion, or bug me on IRC.
==Google Summer of Code Application==
===Abstract===
Currently, much of the code involving BZFlag's worlds and world files is repeated and reimplemented throughout different projects, and as such any changes made to the BZW format require changes to each implementation. In order to ease future development and help increase the modularity of BZFlag, a libBZW is proposed. This library would abstract the inner workings of the BZW format, such as parsing, and allow applications to handle BZW files with ease. Once such a library is in place, BZFlag and related programs should have identical functionality.

===Addendum===
Nothing here as of yet.

==About==
I am a 20 year old undergraduate in the Engineering Systems & Computing program at the University of Guelph (in Ontario, Canada). I've been programming since roughly 1999, when I was first introduced to Visual Basic. Very shortly after I matured to C++, with brief adventures into web development (more on this later). The first game I ever wrote (ignore Visual Basic nonsense) was a Mario Bros. clone. I received much assistance during this time from older students, but soon began to do much programming on my own. I toyed with Flash programming/scripting for a few years before returning to C++ during high school. I realized many errors in my ways and moved to C, in order to build a better programming foundation. Currently, I primarily code in C, C++ and Java (solely for school purposes, not of my own free will, usually). I spent a summer coding in C# for a company producing rugged mobile devices that mostly ran Microsoft Windows CE and Pocket PC. Until a few years ago I coded entirely in a Windows environment, and am quite familiar with it, however now prefer Unix-like systems for development and use. I am an advocate of code reuse and abstraction. I enjoy playing squash when I have the time, and alpine or downhill skiing when the opportunity presents itself. I've been playing video games always, though interspersed with lengthy periods of programming.

User:Lukstr

2008-03-27T15:43:19Z

Lukstr: added a small libBZW discussion area.

User:Lukstr

2008-03-25T17:24:20Z

Lukstr: /* Google Summer of Code Application */ added abstract from actual GSoC application

User:Lukstr

2008-03-25T17:07:10Z

Lukstr: Changed section to reflect linking from gsoc application

Please ask any questions or comments in discussion, or bug me on IRC.
==Google Summer of Code Application==
===Addendum===
Nothing here as of yet.

==About==
I am a 20 year old undergraduate in the Engineering Systems & Computing program at the University of Guelph (in Ontario, Canada). I've been programming since roughly 1999, when I was first introduced to Visual Basic. Very shortly after I matured to C++, with brief adventures into web development (more on this later). The first game I ever wrote (ignore Visual Basic nonsense) was a Mario Bros. clone. I received much assistance during this time from older students, but soon began to do much programming on my own. I toyed with Flash programming/scripting for a few years before returning to C++ during high school. I realized many errors in my ways and moved to C, in order to build a better programming foundation. Currently, I primarily code in C, C++ and Java (solely for school purposes, not of my own free will, usually). I spent a summer coding in C# for a company producing rugged mobile devices that mostly ran Microsoft Windows CE and Pocket PC. Until a few years ago I coded entirely in a Windows environment, and am quite familiar with it, however now prefer Unix-like systems for development and use. I am an advocate of code reuse and abstraction. I enjoy playing squash when I have the time, and alpine or downhill skiing when the opportunity presents itself. I've been playing video games always, though interspersed with lengthy periods of programming.

User:Lukstr

2008-03-22T20:34:16Z

Lukstr: Created

To be filled in shortly with GSoC application draft and personal info.