Getting Started - Revision history

Tom: /* First Steps */

2016-07-28T14:28:43Z

‎First Steps

Tom: /* First Steps */

2016-01-10T21:56:18Z

‎First Steps

Tom: /* Dive into it */

2016-01-10T21:53:50Z

‎Dive into it

Tom: /* Plugin Development */

2016-01-10T21:52:32Z

‎Plugin Development

Dirk: link to new Nightly Tarball article

2011-05-28T21:05:02Z

link to new Nightly Tarball article

Dirk: link to more detailled instructions for using a Mercurial checkout

2010-03-14T08:58:04Z

link to more detailled instructions for using a Mercurial checkout

Dirk: added a link to "beginner" issues on the bugtracker

2010-03-06T15:29:31Z

added a link to "beginner" issues on the bugtracker

Dirk: updated link to installation instructions

2010-02-10T13:16:35Z

updated link to installation instructions

Dirk: added link to Submitting Patches

2009-05-01T20:27:07Z

added link to Submitting Patches

Dirk: added link to Plugin Toolkit

2009-03-15T19:52:04Z

added link to Plugin Toolkit

← Older revision		Revision as of 14:28, 28 July 2016
Line 12:		Line 12:

	For an overview, you can also [https://github.com/Geeklog-Core/geeklog browse the Git repository] online or look through the [http://project.geeklog.net/src/ documented Geeklog source code].		For an overview, you can also [https://github.com/Geeklog-Core/geeklog browse the Git repository] online or look through the [http://project.geeklog.net/src/ documented Geeklog source code].
		+
		+	If you want to ask a Geeklog developer a few questions you can usually find one or more of us hanging out on [https://gitter.im/Geeklog-Core/geeklog Gitter in the Geeklog room].

	== Dive into it ==		== Dive into it ==

@@ Line 5: / Line 5: @@
 If you haven't already done so, [http://www.geeklog.net/filemgmt/viewcat.php?cid=8 download] and [http://www.geeklog.net/docs/english/install.html install] the current stable version. This will give you an idea how things are supposed to work.
-Next, try the development version. You can either [[Using Mercurial|use Mercurial]] or download the [[Nightly Tarball]]. If you're checking out from the Mercurial repository, you also need the [http://project.geeklog.net/nightly/geeklog-pear.tar.gz PEAR classes]. The PEAR classes are already included in the nightly tarball. ([[Installing from the Mercurial Repository|more detailed instructions here]])
+Next, try the development version. You can either [[Using GitHub|use GitHub]] or download the [[Nightly Tarball]]. If you're checking out from the Git repository, you also need the [https://github.com/Geeklog-Core/pear/archive/master.zip PEAR classes]. The PEAR classes are already included in the nightly tarball. ([[Installing from the Mercurial Repository|more detailed instructions here]])
 Once you got the development version up and running, you should read Alan McKay's excellent [[Beginner's Guide to Programming|Beginner's Guide to Geeklog Programming]], which will explain to you how to do things the Geeklog way.
@@ Line 11: / Line 11: @@
 We also recommend you have a look at our [[Coding Guidelines]]. Summary for the impatient: We're mostly following the PEAR coding standards.
-For an overview, you can also [http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/ browse the Mercurial repository] online or look through the [http://project.geeklog.net/src/ documented Geeklog source code].
+For an overview, you can also [https://github.com/Geeklog-Core/geeklog browse the Git repository] online or look through the [http://project.geeklog.net/src/ documented Geeklog source code].
 == Dive into it ==

@@ Line 18: / Line 18: @@
 ''(trying to paraphrase [http://groups.google.com/group/google-summer-of-code-discuss/msg/630ba342ab440c27 this post] by Eric Weddington)''
-Once you have a rough idea how things work, try browsing our [http://project.geeklog.net/tracking/view_all_bug_page.php bugtracker]. Pick a bug that interests you. Try to reproduce it. If you can add any useful information to the bug (e.g. steps to reproduce the problem), go ahead and leave a comment.
+Once you have a rough idea how things work, try browsing our [https://github.com/Geeklog-Core/geeklog/issues bugtracker]. Pick a bug that interests you. Try to reproduce it. If you can add any useful information to the bug (e.g. steps to reproduce the problem), go ahead and leave a comment.
 See if you can find the area in the source code where the problem occurs. Try to think of a way to fix it and either fix it ([[Submitting Patches|patches]] are always welcome!) or, again, leave a comment.
-Don't worry, not all the open bugs are hard. Some are fairly easy and are only open because nobody had a chance to fix them yet (look for issues tagged "[http://project.geeklog.net/tracking/search.php?hide_status_id=90&tag_string=beginner beginner]"). Even if you can't solve the problem, you'll learn a lot in the process.
+Don't worry, not all the open bugs are hard. Some are fairly easy and are only open because nobody had a chance to fix them yet. Even if you can't solve the problem, you'll learn a lot in the process.
 == Plugin Development ==

@@ Line 29: / Line 29: @@
 If you're interested in developing a new or improving an existing Geeklog plugin, start with the [[Plugin Developers Handbook]]. It's somewhat outdated in places (plugin [[Plugin Autoinstall|install]] and [[Plugin Auto-Uninstall|uninstall]] became a lot easier in recent Geeklog versions, for example), but it's still the best place to get an overview.
-The most up-to-date description of Geeklog's plugin API is the [http://project.geeklog.net/src/Geeklog/_system---lib-plugins.php.html lib-plugins.php] file.
+The most up-to-date description of Geeklog's plugin API is the [https://github.com/Geeklog-Core/geeklog/blob/master/system/lib-plugins.php lib-plugins.php] file.
 To start writing a new plugin, try the [[Plugin Toolkit]].

@@ Line 5: / Line 5: @@
 If you haven't already done so, [http://www.geeklog.net/filemgmt/viewcat.php?cid=8 download] and [http://www.geeklog.net/docs/english/install.html install] the current stable version. This will give you an idea how things are supposed to work.
-Next, try the development version. You can either [[Using Mercurial|use Mercurial]] or download the [http://project.geeklog.net/nightly/geeklog-nightly.tar.gz nightly tarball]. If you're checking out from the Mercurial repository, you also need the [http://project.geeklog.net/nightly/geeklog-pear.tar.gz PEAR classes]. The PEAR classes are already included in the nightly tarball. ([[Installing from the Mercurial Repository|more detailed instructions here]])
+Next, try the development version. You can either [[Using Mercurial|use Mercurial]] or download the [[Nightly Tarball]]. If you're checking out from the Mercurial repository, you also need the [http://project.geeklog.net/nightly/geeklog-pear.tar.gz PEAR classes]. The PEAR classes are already included in the nightly tarball. ([[Installing from the Mercurial Repository|more detailed instructions here]])
 Once you got the development version up and running, you should read Alan McKay's excellent [[Beginner's Guide to Programming|Beginner's Guide to Geeklog Programming]], which will explain to you how to do things the Geeklog way.

← Older revision		Revision as of 15:29, 6 March 2010
Line 22:		Line 22:
	See if you can find the area in the source code where the problem occurs. Try to think of a way to fix it and either fix it ([[Submitting Patches\|patches]] are always welcome!) or, again, leave a comment.		See if you can find the area in the source code where the problem occurs. Try to think of a way to fix it and either fix it ([[Submitting Patches\|patches]] are always welcome!) or, again, leave a comment.

−	Don't worry, not all the open bugs are hard. Some are fairly easy and are only open because nobody had a chance to fix them yet. Even if you can't solve the problem, you'll learn a lot in the process.	+	Don't worry, not all the open bugs are hard. Some are fairly easy and are only open because nobody had a chance to fix them yet (look for issues tagged "[http://project.geeklog.net/tracking/search.php?hide_status_id=90&tag_string=beginner beginner]"). Even if you can't solve the problem, you'll learn a lot in the process.

@@ Line 3: / Line 3: @@
 == First Steps ==
-If you haven't already done so, [http://www.geeklog.net/filemgmt/viewcat.php?cid=8 download] and [http://www.geeklog.net/docs/install.html install] the current stable version. This will give you an idea how things are supposed to work.
+If you haven't already done so, [http://www.geeklog.net/filemgmt/viewcat.php?cid=8 download] and [http://www.geeklog.net/docs/english/install.html install] the current stable version. This will give you an idea how things are supposed to work.
 Next, try the development version. You can either [[Using Mercurial|use Mercurial]] or download the [http://project.geeklog.net/nightly/geeklog-nightly.tar.gz nightly tarball]. If you're checking out from the Mercurial repository, you also need the [http://project.geeklog.net/nightly/geeklog-pear.tar.gz PEAR classes]. The PEAR classes are already included in the nightly tarball. ([http://www.geeklog.net/staticpages/index.php/CVS more detailed instructions here])

← Older revision		Revision as of 19:52, 15 March 2009
Line 30:		Line 30:

	The most up-to-date description of Geeklog's plugin API is the [http://project.geeklog.net/src/Geeklog/_system---lib-plugins.php.html lib-plugins.php] file.		The most up-to-date description of Geeklog's plugin API is the [http://project.geeklog.net/src/Geeklog/_system---lib-plugins.php.html lib-plugins.php] file.
		+
		+	To start writing a new plugin, try the [[Plugin Toolkit]].


	[[Category:Development]]		[[Category:Development]]