Talk:Main Page/Archive/2006-2011: Difference between revisions

Jump to navigation Jump to search
m
fixing paragraphs & splitting up addition section
m (fixing paragraphs & splitting up addition section)
Line 1: Line 1:
== Making the manual accessible via wiki software ==
= Making the manual accessible via wiki software =
On the other hand, I would recommend to also look into making "The Manual" editable via some sort of web based frontend, this would also ensure that people are able to easily contribute modifications to the manual, which is really the ultimate source for flightgear users.  
On the other hand, I would recommend to also look into making "The Manual" editable via some sort of web based frontend, this would also ensure that people are able to easily contribute modifications to the manual, which is really the ultimate source for flightgear users.  
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).
Line 5: Line 5:
As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. [[User:Gorilla|Gorilla]] 06:33, 2 March 2008 (EST)
As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. [[User:Gorilla|Gorilla]] 06:33, 2 March 2008 (EST)


== Using a dedicated FAQ database ==
= Using a dedicated FAQ database =
Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).
Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).


== Using a dedicated bug tracker ==
= Using a dedicated bug tracker =


A couple of days ago I started setting up a local test bugZilla installation, while I am currently unable to provide reliable hosting, I would really not mind installing it on whatever webspace is available, likewise I can provide the preconfigured database dump if someone else wants to use the preconfigured Flightgear specific categories.--[[User:FlightZilla|FlightZilla]] 17:59, 17 June 2006 (EDT)
A couple of days ago I started setting up a local test bugZilla installation, while I am currently unable to provide reliable hosting, I would really not mind installing it on whatever webspace is available, likewise I can provide the preconfigured database dump if someone else wants to use the preconfigured Flightgear specific categories.--[[User:FlightZilla|FlightZilla]] 17:59, 17 June 2006 (EDT)
Line 20: Line 20:
Unfortunately, it seems to me, this wiki is not popular among developers and users. -- [[User:Alfozavr|Alfozavr]] 06:59, 17 June 2007 (EDT)
Unfortunately, it seems to me, this wiki is not popular among developers and users. -- [[User:Alfozavr|Alfozavr]] 06:59, 17 June 2007 (EDT)


== Backups ==
= Backups =
Is the database regularly backed up? What about hosting the wiki directly at flightgear.org?
Is the database regularly backed up? What about hosting the wiki directly at flightgear.org?
--[[User:MILSTD|MILSTD]] 15:25, 4 February 2008 (EST)
--[[User:MILSTD|MILSTD]] 15:25, 4 February 2008 (EST)
Line 27: Line 27:
----
----


== Updates ==
= Updates =


I've updated MediaWiki to 1.11.1 so if you notice any regressions let me know. [[User:Hellosimon|Hellosimon]] 15:03, 2 March 2008 (EST)
I've updated MediaWiki to 1.11.1 so if you notice any regressions let me know. [[User:Hellosimon|Hellosimon]] 15:03, 2 March 2008 (EST)
Line 33: Line 33:
The wiki has moved to a new server which should relieve the performance problems.  [[User:Hellosimon|Hellosimon]] 11:26, 10 June 2008 (EDT)
The wiki has moved to a new server which should relieve the performance problems.  [[User:Hellosimon|Hellosimon]] 11:26, 10 June 2008 (EDT)


=== Regressions ===
== Regressions ==
* code passages (i.e. XML) are not highlighted anymore
* code passages (i.e. XML) are not highlighted anymore


=== Proposed Additions ===
= Proposed Additions =
== Syntax Highlighting ==
* what about some sort of true syntax-highlighting module, that would properly highlight XML & C++ ?
* what about some sort of true syntax-highlighting module, that would properly highlight XML & C++ ?
== PDF Export ==
*  PDF Export - [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF]
*  PDF Export - [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF]


Line 51: Line 54:
I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
* how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?
* how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?
= Issues =


==Formatting problem==
==Formatting problem==
2,561

edits

Navigation menu