As part of the Coding-Together project
at the University of Stanford the ea-Geier has been ported to run as
local app on the iPhone & iPad (for more information see cs193p.m2m.at).
Wednesday, 12 September 2012
Saturday, 1 September 2012
ea-Geier ported to iPhone & iPad
As part of the Coding-Together project at the University of Stanford the ea-Geier has been ported to run as local app on the iPhone & iPad (for more information see cs193p.m2m.at).
It should be available in the AppStore soon.
In the meantime a preview is available at YouTube.
It should be available in the AppStore soon.
In the meantime a preview is available at YouTube.
ea-Geier wiki updated to 1.19.2
The ea-Geier wiki has been updated to the current MediaWiki version 1.19.2.
The update was smooth, without problems. If you find any, please let us know.
The update was smooth, without problems. If you find any, please let us know.
Friday, 15 June 2012
ea-Geier wiki updated to 1.19.1
The ea-Geier wiki has been updated to the current MediaWiki version 1.19.1. Unfortunately MediaWiki has changed the localization functionality slightly. Thus the settings for the German version of the wiki had to be changed form "de" to "De". In addition the localization of urls seems to be broken in the current version which we could circumvent by patching the ea-Geier skin.
If you notice further localization bugs, please let us know.
If you notice further localization bugs, please let us know.
Thursday, 10 May 2012
domain transfer
... since the transfer of the site to the new server with a new provider went smoothly, we are now going to move the domain handling to the new provider, too. The DNS settings have been mirrored to the new name servers, the ChProv request has been started. We do not expect any hickups, but if there are any, please be patient.
Tuesday, 1 May 2012
ea-Geier demo move
Setting up the the demo for the ea-Geier, we followed our own instructions from the documentation.
It seems the installed php version of the new server does not like the bundled version of the third-party library ADOdb 4.95a. It actually runs but throws some warnings that his library uses depreciated functions. To prevent that, we could switch of the warnings, but we choose to just download and setup the new version of ADOdb 5.16 like described in the documentation.
It seems they added a new switch for bulk binding in 5.1 thus this has to be enabled in /code/base/db.class.php.
The same issue arises with the Swift library. Using the version optimized for php5 instead of php4 and changing the appropriate lines in /code/base/mail.class.php removes the warnings - however functionality would be unaltered even without those changes.
And simpletest has changed, too. Now in version 1.1.0 (previously we had 1.0.1beta) addTestFile has been replaced by addFile, and due to the complete change to php5 without backwards compatibility to php4 constructors are handled differently.
The ea-Geier demo currently (formerly) reachable via http://www.ea-geier.at/ea-demo/ has been moved successfully to http://demo.ea-geier.at/. The old link will be forwarded to the new one.
We will update the necessary changes in the code base shortly ...
It seems the installed php version of the new server does not like the bundled version of the third-party library ADOdb 4.95a. It actually runs but throws some warnings that his library uses depreciated functions. To prevent that, we could switch of the warnings, but we choose to just download and setup the new version of ADOdb 5.16 like described in the documentation.
It seems they added a new switch for bulk binding in 5.1 thus this has to be enabled in /code/base/db.class.php.
The same issue arises with the Swift library. Using the version optimized for php5 instead of php4 and changing the appropriate lines in /code/base/mail.class.php removes the warnings - however functionality would be unaltered even without those changes.
And simpletest has changed, too. Now in version 1.1.0 (previously we had 1.0.1beta) addTestFile has been replaced by addFile, and due to the complete change to php5 without backwards compatibility to php4 constructors are handled differently.
The ea-Geier demo currently (formerly) reachable via http://www.ea-geier.at/ea-demo/ has been moved successfully to http://demo.ea-geier.at/. The old link will be forwarded to the new one.
We will update the necessary changes in the code base shortly ...
Sunday, 29 April 2012
ea-Geier WIKI move finished
The ea-Geier WIKI currently (formerly) reachable via http://www.ea-geier.at/wiki.en/ (English version) and http://www.ea-geier.at/wiki.de/ (German version) has been moved successfully to http://en.ea-geier.at and http://de.ea-geier.at. The old links will be forwarded to the new ones.
rss extension for mediawiki
The rss extension suffers from minor warnings about previously undefined variables, but also from a change in the api of mediawiki on how to access the database, and a change in how dates are formated.
We documented at the discussion page of the extension and on our user page on medawiki itself.
We documented at the discussion page of the extension and on our user page on medawiki itself.
multilang extension for mediawiki
Only minor changes where needed to tweek the multilang extension for the current mediawiki version, which we documented at the discussion page of the extension and on our user page on medawiki itself.
Saturday, 28 April 2012
move of the ea-Geier wiki started
Moving the ea-Geier wiki seems to be a little more difficult due to the age of the old server and the limitations the provider imposed superfluously.
rsync did not work out, the code had to be moved by scp, which copied the complete file for each symbolic link. So all original symbolic links had to be set manually...
A database dump was only possible in an aged MySQL 4.x dialect. Thus all TYPE=... references in the table definitions had to be changed to ENGINE=..., and timestamp(14) had to be adjusted as well.
... finally the transfered code did not run. Due to the limitations mentioned above, we had to use a quite old version of MediaWiki 1.6.10 which was patched only with security updates. Unfortunately this version used Namespace as class, which php5.3.x does not like that much.
However, upgrade to the current version 1.18.3 for the wiki itself was nearly smooth.
The way templates work changed a bit which needed upgrades to the ea-Geier skin.
But all extensions we used stopped working for the new version, none of them are supported any more.
... currently we are working on fixing that ...
rsync did not work out, the code had to be moved by scp, which copied the complete file for each symbolic link. So all original symbolic links had to be set manually...
A database dump was only possible in an aged MySQL 4.x dialect. Thus all TYPE=... references in the table definitions had to be changed to ENGINE=..., and timestamp(14) had to be adjusted as well.
... finally the transfered code did not run. Due to the limitations mentioned above, we had to use a quite old version of MediaWiki 1.6.10 which was patched only with security updates. Unfortunately this version used Namespace as class, which php5.3.x does not like that much.
However, upgrade to the current version 1.18.3 for the wiki itself was nearly smooth.
The way templates work changed a bit which needed upgrades to the ea-Geier skin.
But all extensions we used stopped working for the new version, none of them are supported any more.
... currently we are working on fixing that ...
ea-Geier API cloned
The ea-Geier API currently (formerly) reachable via http://www.ea-geier.at/ea-doc/ has been cloned to http://api.ea-geier.at/. The old link will be forwarded to the new one.
The move was smooth, no problems.
The move was smooth, no problems.
ea-Geier will be back - carbon neutral
After a sabbatical of nearly five years, the ea-Geier will see new life.
While the ea-Geier has been downloaded quite heavily and supposedly used as such, no real problems have appeared, no security issues. Some feature requests could be satisfied using small patches ...
As next big step, the ea-Geier will move to a new server. With new hardware, more space, bandwidth and - best of all - hosted carbon neutral!
While the ea-Geier has been downloaded quite heavily and supposedly used as such, no real problems have appeared, no security issues. Some feature requests could be satisfied using small patches ...
As next big step, the ea-Geier will move to a new server. With new hardware, more space, bandwidth and - best of all - hosted carbon neutral!
Subscribe to:
Posts (Atom)