After not finding any good opensource game roster applications, I decided to write my own. Three or four weeks later, I've lost count, I'm pretty much done. I now have a php database app that tracks pilots, pilot info, awards, ranks, units, and access rights.
I have put together a depot site for Xoops 1.x themes. The site is at Xthemes.goto-domain.com. There are 112 themes available. Plus the themes preview option.
As administrator of the dutch Xoops Startpage daughter, I'm trying to offer a good overview on Xoops and Xoops related links for international and dutch users.
Update of Herko's old RC-3.0.5 news expire hack for 1.3.8. Also:
- Fixed navigation problem with next page if you have many expired articles.
- Herko added a new storyform.inc.php in admin so now it fills in the current date and time if a post has no dates set, and if it has them set, it shows the set dates (as in Xoops2). Thanks!
There has been a change in handling of theme files in RC3 (which is about to be released in the next few days), as well as several modifications to the naming conventions.
The skin files will no longer be included in a themeset, but managed separately as theme files under the themes directory as we did in XOOPS 1.x. Only the module template files are included in a themeset, thus we will rename theme sets as template sets from RC3.
Why this change?
The development of theme files has become too complicated, or requires overly much work with template and skin files combined. In addition, storing them into DB made hard for the files to be modified on a frequent basis. We also have noticed that skin files are touched more often by the site administrators than are the template files. By completely separating them apart to template and theme sets, we hope that it would not only facilitate the development of theme files for XOOP2, but also make the site administration and management much easier.
It seems as though some steam is picking up on the theme front so, I’ll post what I learned while creating my theme for BoardJIVE.com. One of the first pre-requisites that you need to have is a basic understanding HTML (preferably 4.01 transitional) and CSS.
Another key here is to understand that not all browsers support all these standards so, test your theme with as many browsers as possible. If you don’t have a Mac, ask someone who does to check it out and get back with you so that you have a majority of platforms covered.