"Sean D. Ackley" wrote:
> I guess what I meant was, we are all in this at no real monetary
> benefit, right? We all have to eat, and I don't know what your
> driving force behind Midgard development is.
For me, it's fun and the now famous 'itch that needed scratching'.
> I would rather ask, when it would be a possibility. You say it is
> being worked on, and thats great, but is there any part of this project
> where funding would be useful? Lets say, for instance, that we
> needed to get certain changes made to Midgard. I would see there being two avenues:
>
> 1. Get ourselves a developer, and finish what we need by ourselves.
> 2. Contract out you (since you have intimate knowledge of the sources), and have you
>do it.
>
> This would (a) benefit the plans for Midgard development, and (b) make our project
>finished faster.
Sure, and much obliged. While the project as a whole may have a spot or
two where
funding could be useful, I wouldn't send funds directed at me
personally.
I'm investing pretty much any spare time I have in my Midgard projects,
and
I will not be able to take time off from my regular work, funded or not.
Extra
cash will only mean more skydives for me (and consequently less time for
Midgard :).
> Or (3) you could just tell me, "heh, just be patient, and the software will be
>released..."
>
> Bottom line is, heh, I want to help out, but I also have an agenda, and
> I wanted to be honest with why I am helping.
I'm not asking you to be patient (much). I am currently working on it,
so if you
have specific requirements not covered by the small description that is
in the tar
file. It is my estimation that it will take about one week to public
alpha, two to three
weeks to stabilize, all depending on the number of testers and the
intensity of the
testing. I guess you just volunteered :)
You will find an updated patch at
http://www.midgard-project.org/~emiliano/recext-1.4b3-2.tar.gz
This is a patch against the current CVS version of
php/functions/midgard.c
It adds two methods, list_params and param, which are available after
mgd_<object>_get.
Parameters are subdivided into domains for grouping.
$object->list_params() lists all parameter domains for the object
$object->list_params($domainname) lists all parameters in the domain
$object->param($domain, $name) -> return parameter value
$object->param($domain, $name, $value) -> set the parameter value
$object->param($domain, $name, '') -> delete the parameter
The parameters will be available after mgd_<object>_get as
$object->domain_name (and will this be usuable as &(object.domain_name);
The underscore is less than perfect; it may conflict with method names.
I'm open
to suggestions, but I would like to keep the domain/name system, and if
there is
a way to return compund objects, or have object properties be hashes or
such, I'd
appreciate a pointer to how that's done. I'm not sure either would work
with
the &(...); syntax but there's one way to find out.
This patch is of course very alpha, and only rudimentally tested ("Hey
it works and
didn't segfault this time!"). It will also have more functionality in
the future:
setting multiple params in one call from a hash, and search functions
(both from
Jean-Pierre).
> In any case, I will look at the sources as you suggested, and send you some feedback.
> I am a pretty complete beta tester, so if you want me to check out your build on my
> machine, just jot me off an e-mail when you release a new candidate and I will
> give you my feedback.
Works for me.
> Plus, remember, I can start compiling the docs, is this what you would like me to do?
That would be AbFab.
In fact, I would like to invite all to have a look at
http://www.oreilly.com/oreilly/author/. While there is obviously nothing
very concrete
yet, Ken Pooley has a good opportunity to bring a manuscript under the
direct attention
of an O'Reilly editor. No guarantees, no big prize, but one hell of an
opportunity.
If we want to grab this opportunity we will _obviously_ have to shape up
our manual.
Pick through the manual and find spots that are in error, incomplete, or
incomprehensible. Point them out, or if you feel so inclined, adopt
them. I've been
working in close concert with Ron Parker and the pace at which we have
created something
workable about SiteGroups pleasantly surprised me -- the combination of
curious user
and technical insider has worked well for us.
I will put aside some time to do one more of these projects, so if there
is a particular
part of Midgard anyone wishes to get to know better, and don't mind
fleshing it out for use
in the manual, give me a buzz. I'm hoping others that allready have good
knowledge of
the workings will find the time to do something similar.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
