CVS with KDevelop and Cervista

[Updated 10 Nov 2006]

I’ve just started learning how to use CVS on Linux with KDevelop, and there are enough gotchas that I thought it might be interesting to share what I’ve learned. I have used lots of source control in the past, but never CVS. RCS [ages ago], QVCS [windows front end for rcs], and VSS with Visual Studio.

Serious coding on Linux means that I need source control, so I had a look at what’s available. CVS seems to be the long-time standard for open-source projects. But SubVersion is new on the scene, relatively, so I took a look. But after a little study of a few doc pages, including this one, it looks like SubVersion has the nasty habit of suggesting, if not requiring, that your directory tree look in a special way for SubVersion use. That, and the fact that the SubVersion GUI client for Linux looks like it is in its pretty early days, has lead me to choose CVS and Cervisia. Any Open Source code base with a version above 1.5 has got to have seen a fair amount of use.
Continue reading “CVS with KDevelop and Cervista”

KDevelop project fails to build with CVS

SUSE 10.1, KDE 3.5.5, KDevelop 3.3.5, Cervisia 2.4.5

[RESOLVED 10 Nov 2006]
To build successfully after moving a project, use Build >> Clean Project, followed by Build >> Run Automake & Friends and Build >> Run Config.

I’m trying to learn to use source control with KDevelop. CVS seems the most popular and most stable. I looked briefly at SVN, but the GUI tool seems immature compared with Cervisia. But I can’t get CVS and KDevelop to play nicely together.
Continue reading “KDevelop project fails to build with CVS”

Hellraiser Box for Linux

This is a port of the Hellraiser box to Qt / KDE / Kdevelop on SUSE 10.1.

Box_Open_2

 

To run the program, use fileroller to unpack the file in a directory and then run the program. The image files must be in the same directory as the program. The instructions are essentially the same as for the Windows Version.

Hellraiser Lament Box Program

The sources are provided here. They are built using KDevelop 3.3.5 and Qt.
Hellraiser Lament Box Sources
There are links in the debug and optimize src directories that point back to the images in the src directory. These may have to be remade after you unpack the archive since links are not relative.

Update: Find the programs on SourceForge.

Enjoy. :-D

Google Sitemaps for Coppermine

Google has help and services for Webmasters. Among the things they provide and encourage are sitemaps. However, it’s not as complex as it all seems. WordPress and coppermine, and many other CMSs have scripts that generate these sitemaps. There are tools that run from your computer too, but these can’t know the internal structure of the site database, and so they are inefficient or don’t work for dynamic sites like WordPress and Coppermine.

With over 2000 images in my photo site, it seemed useful to generate a Google Sitemap for the Coppermine gallery. After some searching a plug-in turned up in the Coppermine Forums.

This plug-in is fairly primitive and when I tried it, it failed with an error on Google. Google produced an error about the first URI produced by the script. Also, the entire sitemap was produced as one single line, so error messages or looking at the sitemap with an editor were not user friendly.

I have repaired the script and you can find the new version by the link below. It is advertised to work for CPG 1.2.x, 1.3.x and 1.4.x. For more information, read the forum post above.

To use the script, unzip and upload it to the base coppermine directory on your site and then activate it from the browser with a URL like: http://www.yourdomain.com/cpg144/sitemap.php

Then visit the Google Webmasters Site,

  1. create an account, or log in with your google email account,
  2. add your site, using the Coppermine base directory, and
  3. then verify your site using one of the methods provided and finally
  4. point to your sitemap to tell google about it.

Here is the fixed script.

d

Sitemaps for better searching with Google

Google has help and services for Webmasters. Among the things they provide and encourage are sitemaps. However, it’s not as complex as it all seems. WordPress and coppermine, and many other CMSs have scripts that generate these sitemaps. There are tools that run from your computer too, but these can’t know the internal structure of the site database, and so they are inefficient or don’t work for dynamic sites like WordPress and Coppermine.

Sitemaps tell google about the content of sites that have dynamic content. You can find out more about services for Webmasters at google. You will need to log into an account to see these pages, but accounts are free.

You will want to look at this page to find plugins or programs to build sitemaps for your site. For example, there is a plugin for WordPress to build sitemaps – WordPress Sitemap Plug-in.

There is also a php file to build sitemaps for Coppermine.

d