[bf1942] BF2 Event Logging

[Forrest Thiessen]

I do a lot with Plone (based on Zope), so I can say from experience that
yes, you're right--Zope could do it just fine. In this case, however,
the "Python" we're talking about is a Python interpreter that's embedded
in BF2 (a wonderfuly brilliant design decision by DICE--we'll be able to
do a lot with it!), so the coding has to be for that embedded
interpreter.  Zope might have a place on the side as a place to develop
an engine for displaying statistics, but if we had BF2-Python code that
stored the stats data into a MySQL database, then displaying data from
the database would be a pretty simple task that you wouldn't really need
the power of Zope for.

--Forrest

Brenda wrote:

> Just an innocent bystander but I "think" you could even use Zope to do
> that and develop your applications easily in an oop environment.
>
>
>
> On 6/16/05 4:19 PM, "Joe" <sechon at blackmud.com> wrote:
>
>     Heck, can we write a python -> sql connector!? If so, no more
>     parser and LIVE stats updates! The php end of it is easy if we can
>     get the game feeding events into an sql database. Maybe even have
>     it funnel all the logs to one sql db then parse that db for the
>     data we want, still need a parser but might be easier to
>     manage..Hmmm..
>
>
>         -----Original Message-----
>         *From:* Joe  [mailto:sechon at blackmud.com]
>         <mailto:sechon at blackmud.com%5D>
>         *Sent:* Thursday, June 16, 2005 3:16  PM
>         *To:* bf1942 at icculus.org
>         *Subject:* RE: [bf1942] BF2 Event  Logging
>
>
>         I  asked shiny about supporting bf2 with selectbf and he just
>         avoided the  question, then failed to respond at all. I'm more
>         interested in writing my own  from the ground up than working
>         with that pile of patches. A _LOT_ of work  would be needed to
>         be done to selectbf to bring it to the point where it can
>          handle bf2's features fully, and well, I just don't see it
>         worthwhile in it's  current state. I've pulled it apart
>         complete including the parser to change  things here and
>         there, and we can do this so much faster by dropping that crap
>          java parser and moving on I'd say.
>
>
>             -----Original Message-----
>             *From:* Forrest Thiessen  [mailto:thiessen at alum.mit.edu]
>             <mailto:thiessen at alum.mit.edu%5D>
>             *Sent:* Thursday, June 16, 2005 2:49  PM
>             *To:* bf1942 at icculus.org
>             *Subject:* Re: [bf1942] BF2  Event Logging
>
>             Ugh.  Looking through some of the  Python stuff, I saw the
>             "hooks" that could be used to do this, so you're  right,
>             it can be done. . . I was kind of hoping BF2 would start
>             out with the  same XML log files that BFV introduced,
>             though, and then left it to the  "community" to take it
>             further.
>
>             I guess I'll give some thought to  what it would take to
>             implement BFV-style XML logs.  Again,  ugh.
>
>             --Forrest
>
>
>             Brigham Stevens wrote:  
>
>                 I believe there is no default logging.
>                 It is something that you have to hook into with python
>                 to come up with
>                 an actual log file. EA left it for the community to
>                 implement... I'm
>                 hoping that someone (heheh) will fix it up so the log
>                 files are close to
>                 the old log format and then we can fix up selectbf
>                 easily to do it, but
>                 it might make sense to do something else.
>
>                 Forrest Thiessen wrote:
>
>                   
>                  
>
>                     Has anyone figured out how to turn on event
>                     logging in the BF2 demo
>                     server? I've tried several obvious things (like
>                     sv.serverEventLogging
>                     1), with no joy.
>
>                     --Forrest
>
>
>                      
>
>                         
>
>
>                   
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/bf1942/attachments/20050616/9c4b518e/attachment.htm>