2 Jun 20:26
2 Jun 21:08
Announcement: Midgard 1.7beta1 "FlyHigh" released
Midgard 1.7beta1 "FlyHigh" released. Lodz, June 2nd 2005 -- The Midgard Project has released the first beta release version of the 1.7 Midgard Open Source Content Management Framework. Midgard provides a reliable, carrier-grade CMS framework build for the the LAMP platform. Midgard's core features include internationalization, accessibility, scalability and PHP connectivity. This development release includes a Midgard2 technology preview. Major features included: * New Midgard Site Wizard for easily setting up websites * Multilang support * PAM and NTLM support * New midgard-data * Improved Datagard Midgard database installer * MgdSchema , GObjects and XML defined PHP objects * MidgardQueryBuilder class , SQL queries creator and executor * PHP5 extension without old classic Midgard API Multilang feature makes Midgard more flexible as it separates metadata from the current language of objects. Now is easy to use with the new midgard-data package which allows to create or update databases very easily even for Midgard beginners. PAM (Pluggable Authentication Modules) lets applications authenticate with external password repositories. NTLM, single sign-on solution used in Windows(Continue reading)
3 Jun 11:37
Re: Announcement: Midgard 1.7beta1 "FlyHigh" released
"Piotras" <pp@...> wrote: Hi all! > Midgard 1.7beta1 "FlyHigh" released. In meantime I tried to make documentation's "draft" for new functionality. http://www.midgard-project.org/documentation/reference/mgdschema_objects/ Piotras
3 Jun 11:55
Re: Announcement: Midgard 1.7beta1 "FlyHigh" released
Piotras <pp@...> wrote: > In meantime I tried to make documentation's "draft" for new functionality. > > http://www.midgard-project.org/documentation/reference/mgdschema_objects/ MidgardQueryBuilder has no own section on m-p.org. Please follow Bergie's blog: http://bergie.iki.fi/blog/sunday-notes-from-mgdschema-workshop.html Piotras
9 Jun 17:59
Suggestions for a webtestingframework
Hi, take a look at this irclog. Midcom needs a testingframework. Does anyone have any experience with any tools and ideas on which tools are fit for the job and should be used? 7:42 <bergie> did you have plans about automated tests? 17:43 <tarjei> yes I was thinking about some. We need to think about a testing framework for the whole midcom/midgard process that makes development go very fast 17:43 <tarjei> i.e. that helps us find bugs early 17:44 <bergie> that would be great. we've had some problems with regressions 17:44 <tarjei> the first step would be to have two demo/test v-servers one for latest midcom and one for latest midgard 17:45 <tarjei> I posted a few urls to you some time ago did you look at them? 17:46 <bergie> I don't remember this. irc or email? 17:46 <tarjei> irc I think 17:47 <tarjei> I might have posted them to someone else :/ 17:47 <tarjei> for core the pear unittests should be a good idea 17:49 <bergie> ok 17:50 <tarjei> http://tigerteam.se/dl/gwee/ <-- we should run it against midcom 17:51 <tarjei> * Provide minimal configuration/install requirements for people building the tests. 17:51 <tarjei> * Provide the simplest possible learning curve for people building the tests. 17:51 <tarjei> * Provide an extensible and configurable infrastructure to developers to allow them to either use prebuilt tests or to roll their own as needed. 17:51 <tarjei> ups c-n-paste error(Continue reading)
10 Jun 08:48
autoconf/autowhatever problems with latest midgard-lib CVS
Hi,
I just tried to recompile midgard-lib to test a bugfix, and when I run
midgard-lib bootstrap again (the makefile.am had changed) I got this:
aclocal:configure.in:30: warning: macro `AM_PATH_CHECK' not found in library
configure.in: installing `./ylwrap'
configure.in:30: error: possibly undefined macro: AM_PATH_CHECK
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
Interestingly, the top-level bootstrap script it didn't produce an error, but
when configuring, I stumbled over the same thing again:
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
./configure: line 20053: syntax error near unexpected token `,'
./configure: line 20053: `AM_PATH_CHECK(, have_check="yes",'
$ autoconf --version
autoconf (GNU Autoconf) 2.59
$ automake --version
automake (GNU automake) 1.9.5
$ libtool --version
ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.95 2004/04/11 05:50:42) Debian: 220 $
Live long and Prosper!
(Continue reading)
10 Jun 09:26
Side-Effects of the Wiki Transition on m-p.org?
Hi, did you already move the docs into the wiki format? I'm wondering a bit about this: http://www.midgard-project.org/documentation/reference/topic/ Live long and Prosper! Torben Nehmer -- Torben Nehmer, Guenzburg, Bavaria, Germany http://www.nathan-syntronics.de, mailto:torben@... PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
10 Jun 09:40
Re: autoconf/autowhatever problems with latest midgard-lib CVS
Hi, Torben wrote: > I just tried to recompile midgard-lib to test a bugfix, and when I run > midgard-lib bootstrap again (the makefile.am had changed) I got this: > > aclocal:configure.in:30: warning: macro `AM_PATH_CHECK' not found in library > configure.in: installing `./ylwrap' > configure.in:30: error: possibly undefined macro: AM_PATH_CHECK > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. See my previous message on unit testing, you need to install the Check unit testing framework. BR, Jukka Zitting
10 Jun 09:45
[Fwd: Unit testing in core]
Hmm, It seems that I can only post from my work address. My message from yesterday follows. BR, Jukka Zitting -------- Original Message -------- Subject: Unit testing in core Date: Thu, 09 Jun 2005 10:52:18 +0300 From: Jukka Zitting <jukka@...> To: dev@... Hi dev, I'm about to commit a set of changes to the query builder (including support for nested OR constraints). I feel a lot safer making such changes if there is a simple and easy to run unit test suite catching mistakes in my logic. Because the earlier test programs were a little brittle, I decided to start using the Check unit test framework [1] in midgard-lib. I just committed the changes in configure.in/Makefile.am and a simple no-op test case in test/check_midgard.c. I used the Check with Autotools notes from [2] to set things up. This change adds no new dependencies for the end users (configure will just ignore the unit tests if Check is not found), but developers who(Continue reading)
10 Jun 09:46
Nested constraints in query builder
Hi dev,
Based on a request from Rambo, I have just committed a set of QB changes
that make it possible to build more complex queries than before. More
specifically, the changes enable you to include nested groups of
constraints that are combined using either the AND or OR operator. To
illustrate, the following example would return all articles in topic 123
whose name is _either_ foo or bar:
$builder = new MidgardQueryBuilder("NewMidgardArticle");
$builder->addConstraint("topic", "=", 123);
$builder->beginGroup("OR");
$builder->addConstraint("name", "=", "foo");
$builder->addConstraint("name", "=", "bar");
$builder->endGroup();
$objects = $builder->execute();
It is possible to nest the beginGroup/endGroup methods, but make sure
that you always end all the groups you have started.
I've included a simple core test case for the new functionality, but
haven't yet tried these changes on the PHP level. Rambo will probably
let me know if there's something wrong. 
BR,
Jukka Zitting
RSS Feed