Re: [Flightgear-devel] Changelog for 2.4.0
Am 14.07.2011 23:22, schrieb Gijs de Rooy: Feel free to add/edit/remove http://wiki.flightgear.org/Changelog_2.4.0 Well done - thanks. I changed a few lines after browsing through the commitlogs until I hit the tag for 2.2.0-RC1 Torsten -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Changelog for 2.4.0
Many thanks to everyone involved for compiling the ChangeLog !! Stuart Buchanan wrote: I've added native multiscreen support. Native multiscreen was supported very early in FlightGear/OSG. We've been presenting three-monitor setups using a single instance of FlightGear at LinuxTag end of May 2007 in Berlin, way _before_ the first OSG-based 'official' release: http://www.oflebbe.de/FgShow2/pages/DSCF1198.html Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Changelog for 2.4.0
Okay, it isn't plain text (we can easily convert it once it's done, altough I cannot think of a place where we'd publish a plain-text-changelog, apparently we stopped updating the fgdata/NEWS file), but this will allow us to work together on a nice release announcement/changelog, so nothing important is missed and everything is stated correctly and properly spelled. Feel free to add/edit/remove http://wiki.flightgear.org/Changelog_2.4.0 -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Changelog for 2.4.0
On Thu, Jul 14, 2011 at 10:22 PM, Gijs de Rooy wrote: Okay, it isn't plain text (we can easily convert it once it's done, altough I cannot think of a place where we'd publish a plain-text-changelog, apparently we stopped updating the fgdata/NEWS file), but this will allow us to work together on a nice release announcement/changelog, so nothing important is missed and everything is stated correctly and properly spelled. Feel free to add/edit/remove http://wiki.flightgear.org/Changelog_2.4.0 Good work Gijs. It's been such a long time since the last release, I had to look a the v2.0.0 changelog to check what was new! In looking at the last changelog, we mentioned shader support, so I think we might want to de-emphasise it slightly. There have been significant developments in that area, but shaders themselves are not new. I've added native multiscreen support. I think there are a couple of items currently on the list that are fairly minor, and detract from some of the major improvements that have happened. I'd suggest that they are removed, but didn't want to remove them without comment: Aircraft operations: - Indicated airspeed (IAS) limitations can be indicated on the airspeed indicator - Surely this is a straightforward model improvement rather than a new feature? - Improved autopilots - Seems a duplicate of Wind-up prevention on simple autopilot systems - A new head-up display (HUD) system - is this really new? AI Traffic - should these be included in Scenery Improvements? Navigation: - Autopilots can be driven by NAV or GPS instruments - surely this isn't new? I suspect this refers to a particular aircraft -Stuart -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Changelog for 2.4.0
Hi, I have two tasks for the next release to give away: 1) is anybody willing to donate some time browsing through the commitlogs of SimGear, FlightGear and FGDATA to provide a changelog for the release? It certainly should not contain every single new aircraft but an abstract of what cool new features our users may expect. 2) anybody volunteers for browsing through the Thanks file and probably add those who deserve to be mentioned? Preferred are plain text files. Thanks, Torsten -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Changelog for 2.4.0
Torsten wrote: 1) is anybody willing to donate some time browsing through the commitlogs of SimGear, FlightGear and FGDATA to provide a changelog for the release? Durk started with one for 2.3.0. I hope we didn't loose any features in the meantime ;) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg30225.html I'd like to add to that (taken from newsletters and forum): Support for lightmaps, which allow aircraft and scenery developers to create realistic lighting effects relatively easy.TCAS, works with AI and multiplayer aircraft, provides aural warnings for conflicting traffic and is also capable of driving a realistic traffic display. AI aircraft also respond to TCAS alerts and take evasive Mouse acceleration, one can click on the lever and drag the mouse forward in order to advance thrust. Or any other lever-action. Seen on several aircraft, including Torsten's!! :)An interactive Boeing CDU. Not fully functional yet, but accepts several inputs already. Aircraft worth mentioning IMO Vostok That's all I can come up with so far. Cheers, Gijs -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Changelog for 2.4.0
Am 06.07.2011 18:23, schrieb Gijs de Rooy: Torsten wrote: 1) is anybody willing to donate some time browsing through the commitlogs of SimGear, FlightGear and FGDATA to provide a changelog for the release? Durk started with one for 2.3.0. I hope we didn't loose any features in the meantime ;) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg30225.html I'd like to add to that (taken from newsletters and forum): * Support for lightmaps, which allow aircraft and scenery developers to create realistic lighting effects relatively easy. * TCAS, works with AI and multiplayer aircraft, provides aural warnings for conflicting traffic and is also capable of driving a realistic traffic display. AI aircraft also respond to TCAS alerts and take evasive * Mouse acceleration, one can click on the lever and drag the mouse forward in order to advance thrust. Or any other lever-action. Seen on several aircraft,* including Torsten's!! :)* * An interactive Boeing CDU. Not fully functional yet, but accepts several inputs already. Aircraft worth mentioning IMO * Vostok That's all I can come up with so far. Thanks, that's a good start. What I am really looking for is a complete ready-to-go file we can deploy (hint!). Torsten -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Changelog for 2.4.0
On Wednesday, July 06, 2011 18:15:45 Torsten Dreyer wrote:
Hi,
I have two tasks for the next release to give away:
1) is anybody willing to donate some time browsing through the
commitlogs of SimGear, FlightGear and FGDATA to provide a changelog for
the release?
That sounds like a huge task. I've put together a little script to help the
poor fellow who will go at it. This script will crawl through gitorious commit
logs and create some plain text files (inside current directory) with all
commit messages since some date. The number of pages to be crawled can be
edited inside to fine-tune the starting date. With current values it will
start in November/December last year.
Usage: crawler.py fg | sg | fgdata
Results will look like this:
#367: raise log level for some routemanager error messages
Fix #220, Ctrl-U no longer working for YASim
Fixed faulty frame transformation of moment of inertia.
#348 related: More places where missing files were not reported properly
#!/usr/bin/env python
# Copyright (C) 2011 Adrian Musceac
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see http://www.gnu.org/licenses/.
import os, sys
import io
import time
from urllib2 import *
from HTMLParser import *
import re
class Parserul(HTMLParser):
def __init__(self):
self.getit=False
self.text=''
self.bufr=''
HTMLParser.__init__(self)
def handle_starttag(self,tag,attrs):
if tag.lower()=='div':
for att in attrs:
if att[1]=='commit_message':
self.getit=True
def handle_data(self,data):
if self.getit==True:
if data:
self.bufr = self.bufr + data
def handle_endtag(self,tag):
if tag.lower()=='div' and self.getit==True:
self.text = self.text + '\n' + self.bufr
self.bufr=''
self.getit=False
class Parserul2(HTMLParser):
def __init__(self):
self.getit=False
self.next_link=''
HTMLParser.__init__(self)
def handle_starttag(self,tag,attrs):
if tag.lower()=='a':
if len(attrs) 2:
if attrs[1][0]=='class' and attrs[1][1]=='next_page' and attrs[2][0]=='rel' and attrs[2][1]=='next':
self.next_link=attrs[0][1]
def get_next_link(self):
return self.next_link
def crawl_gitorious():
parser=Parserul()
parser_link=Parserul2()
prefix='http://gitorious.org'
if(sys.argv[1]=='fg'):
next_link='/fg/flightgear/commits/next'
git='flightgear'
# Edit number of pages to crawl in flightgear commit log #
xx=20
elif(sys.argv[1]=='sg'):
next_link='/fg/simgear/commits/next'
git='simgear'
# Edit number of pages to crawl in simgear commit log #
xx=10
elif(sys.argv[1]=='fgdata'):
next_link='/fg/fgdata/commits/master'
# Edit number of pages to crawl in fgdata commit log #
git='fgdata'
xx=25
while 1:
ff = open('./'+git+'.log','ab')
f= urlopen(prefix+next_link)
g=f.read()
parser.feed(g)
parser_link.feed(g)
next_link=parser_link.get_next_link()
buf = re.sub('[^]+?','',parser.text)
ff.write(buf)
ff.close()
f.close()
parser.close()
parser_link.close()
tmp=next_link.split('page=')
if int(tmp[1]) xx: break
time.sleep(3) # DOS is bad manners
if __name__ == __main__:
if len(sys.argv) 2:
print 'Usage: crawler.py fg | sg | fgdata'
sys.exit()
else:
crawl_gitorious()
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Changelog for 2.4.0
On Wednesday, July 06, 2011 18:15:45 Torsten Dreyer wrote:
Hi,
Actually the correct script is the one attached here (it's late).
Hope it helps.
Adrian
#!/usr/bin/env python
# Copyright (C) 2011 Adrian Musceac
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see http://www.gnu.org/licenses/.
import os, sys
import io
import time
from urllib2 import *
from HTMLParser import *
import re
class Parserul(HTMLParser):
def __init__(self):
self.getit=False
self.text=''
self.bufr=''
HTMLParser.__init__(self)
def handle_starttag(self,tag,attrs):
if tag.lower()=='div':
for att in attrs:
if att[1]=='commit_message':
self.getit=True
def handle_data(self,data):
if self.getit==True:
if data:
self.bufr = self.bufr + data
def handle_endtag(self,tag):
if tag.lower()=='div' and self.getit==True:
self.text = self.text + '\n' + self.bufr
self.bufr=''
self.getit=False
class Parserul2(HTMLParser):
def __init__(self):
self.getit=False
self.next_link=''
HTMLParser.__init__(self)
def handle_starttag(self,tag,attrs):
if tag.lower()=='a':
if len(attrs) 2:
if attrs[1][0]=='class' and attrs[1][1]=='next_page' and attrs[2][0]=='rel' and attrs[2][1]=='next':
self.next_link=attrs[0][1]
def get_next_link(self):
return self.next_link
def crawl_gitorious():
prefix='http://gitorious.org'
if(sys.argv[1]=='fg'):
next_link='/fg/flightgear/commits/next'
git='flightgear'
# Edit number of pages to crawl in flightgear commit log #
xx=20
elif(sys.argv[1]=='sg'):
next_link='/fg/simgear/commits/next'
git='simgear'
# Edit number of pages to crawl in simgear commit log #
xx=10
elif(sys.argv[1]=='fgdata'):
next_link='/fg/fgdata/commits/master'
# Edit number of pages to crawl in fgdata commit log #
git='fgdata'
xx=25
while 1:
parser=Parserul()
parser_link=Parserul2()
ff = open('./'+git+'.log','ab')
f= urlopen(prefix+next_link)
print next_link
g=f.read()
parser.feed(g)
parser_link.feed(g)
next_link=parser_link.get_next_link()
buf = re.sub('[^]+?','',parser.text)
ff.write(buf)
ff.close()
f.close()
parser.close()
parser_link.close()
tmp=next_link.split('page=')
if int(tmp[1]) xx: break
time.sleep(3) # DOS is bad manners
if __name__ == __main__:
if len(sys.argv) 2:
print 'Usage: crawler.py fg | sg | fgdata'
sys.exit()
else:
crawl_gitorious()
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
