Piotras | 1 Dec 10:56

New midgard-data


	Hi!

I merged repligard and datagard in one data package under src directory in CVS HEAD.

This means:
	- repligard is no longer maintainable in core ( 1.8 is probably last release with repligard ) 
	- datagard is moved from tools/datagard to data
	
A very good thing is that now one is able to create midgard-data package with simple command
`make dist` in data dir. This will create full tarball with MidCOM , Ageir and Spider.
makedist script is also rebuilded ( much smaller and simpler now ).

However I need help with Makefile for data. 
MidCOM , Aegir and Spider are downloaded and placed in correct locations in tarball using dist-hook.
I can not place them in nobase_dist_data_DATA then.
( this should force them to be automagically installed using make install ) 
Using own install: overwrites nobase_dist_data_DATA. 
( so install: should have own logic while nobase_dist_data_DATA could be kept instead )

Ideas?

Another *weird* issue:
MidCOM is downloaded to correct location and unbzipped. However after tarball is created
midcom is additionally unpacked ( without directories , all files ) to tarball.

So tarball contains midgard-data-VERSION and pleeeeenty of midcom files.

Ideas?

(Continue reading)

Piotras | 6 Dec 10:38

Re: Midgard Style


To sum up:

I wonder about changing core style to collector. Something like generic feature to collect data from tree. 
http://midgard.tigris.org/source/browse/midgard/src/core/midgard/midgard/midgard_style.h?rev=1.3&view=markup

You can notice that 

midgard_style_register(midgard *mgd, const gchar *name, MgdStyle *style);

requires Midgard Object. Not midgard_style object. 
The only limitation is that value or code properties are hardcoded, so we could easily change internals to 
something like this:

midgard_style_register(midgard *mgd, const gchar *name, MgdStyle *style, ... );

with va_list as properties of object which should be used for collector.
( or anything similiar, but I think you get an idea ) 

Basic API is described in mRFC #22 
http://www.midgard-project.org/development/mrfc/0022.html

These seem to me a sensible proposals to manage queue(stack) management:

1. Extend Torben's proposal with register style with priority.
	
	register_style(int priority, string style_uri);

	This function should (de)register styles in queue.
	So if style uri is already 	registered with priority 10:
(Continue reading)

Torben Nehmer | 6 Dec 14:21
Gravatar

Style Queue/MRFC 22 comments (was: Midgard Style)


Hi all,

--Piotras wrote on 2005-12-06 10:38:
> To sum up:
> 
> [snipped C details I don't get in all extent anyway]
> 
> Basic API is described in mRFC #22 
> http://www.midgard-project.org/development/mrfc/0022.html

I'll comment that one separately below. The basic idea is good, although I don't
agree to a few naming convention things.

What I absolutely agree is this (said it in IRC often enough):

| Midgard provides a $_MIDGARD['style'] object for manipulating the style queue
| on PHP level. [...]

Skip all this procedural stuff please.

> These seem to me a sensible proposals to manage queue(stack) management:
> 
> 1. Extend Torben's proposal with register style with priority.  
>
> register_style(int priority, string style_uri);
>
> register_style(int priority, string style_uri);
> 
> This function should (de)register styles in queue.
(Continue reading)

Piotras | 6 Dec 15:50

Re: Style Queue/MRFC 22 comments (was: Midgard Style)

Torben Nehmer <torben@...> wrote:

> > Basic API is described in mRFC #22 
> > http://www.midgard-project.org/development/mrfc/0022.html
> 
> I'll comment that one separately below. The basic idea is good, although I don't
> agree to a few naming convention things.
> 
> What I absolutely agree is this (said it in IRC often enough):
> 
> | Midgard provides a $_MIDGARD['style'] object for manipulating the style queue
> | on PHP level. [...]
> 
> Skip all this procedural stuff please.

Sorry , I was always told that mixing uppercase with lowercase with brackets and with 
apostrophes makes words very unreadable ;)

> Ok, with which priorities are the site style and the page elements registered?

Page elements are internal ones so you shouldn't override them I think.
No idea about site styles, especially for m-t like solutions.

> There should be constants to make this work. Basically, this could allow stuff like:
> 
> $_MIDGARD['style']->register(MIDGARD_PAGE + 10, ...);
> $_MIDGARD['style']->register(MIDGARD_STYLE + 10, ...);
> 
> These priorities should be far enough apart to allow quite flexible styling, for
> example host styles somewhere at 1000 and page stuff perhaps 10000.
(Continue reading)

Torben Nehmer | 6 Dec 16:11
Gravatar

Re: Style Queue/MRFC 22 comments


Hi,

--Piotras wrote on 2005-12-06 15:50:
> [...]

Read precicly. Most questions are answered in there.

Besides:

a) you wanted to know what I would like to have
b) I don't have the time explaining everything twice

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
Torben Nehmer | 7 Dec 10:01
Gravatar

Management-Roadmap/Changes to the Midgard Web-Server ("nathan")


Hi,

as you know, my server nathan is hosting m-p.org for quite some time now, and,
before you suspect the worst, it will still do that for some time.

The reason I write this mail is related to the fact that I'll have to change a
few things around my own hosting infrastructure, which includes the addition of
a new primary server for my own purposes.

As a matter of fact, I actually want to get a new system for my own hosting
services, but since I already own Nathan, I've decided to keep that server
available for the project until further notice, as a completly dedicated
machine. With the addition of the memory upgrade sponsored by both Nemein and
myself to 2 GB it should be able to keep up the Midgard web site at least for
some time.

However, probably as of January or February (date not finally decided) I'll have
to place two restrictions on the server:

a) All IPs except the one currently assigned to midgard.nehmer.net and all its
CNAMES will be unregistered, as I will cancel the 16-IP package that server
currently owns.

b) I will reduce the monthly free traffic of the system from currently 1 TB to
100 GB. The main bandwith-hog of the site currently is this OSX 500 MB installer
package, which accounts for over 80% of the current traffic (~ 65 GB) alone.
Since exceeding the bandwith limit is quite expensive, I will place a hard
bandwith limit just below the 100 GB mark (99 most probably), which will take
the server completly offline for the remainder of the month. It is not possible
(Continue reading)

Jukka Zitting | 7 Dec 10:30
Picon

Re: New midgard-data

Hi,

Piotras wrote:
> I merged repligard and datagard in one data package under src directory in CVS HEAD.

Very nice, thanks! I never got around to doing this myself...

> However I need help with Makefile for data.

I've always wondered why we need to download the extra packages when
building the distribution. Why not commit the package files as binaries
in CVS and update them whenever new versions are available. This would
simplify the distribution building code a lot (no need to download
anything). An added benefit would be that the CVS repository would then
contain *all* the stuff going to Midgard releases.

BR,

Jukka Zitting

--

-- 
Yukatan - http://yukatan.fi/ - info@...
Software craftmanship, JCR consulting, and Java development
Jukka Zitting | 7 Dec 10:40
Picon

Re: Style Queue/MRFC 22 comments

Hi,

Just a side note: This seems like an awfully complex issue, I've long
since lost the idea of what you actually are trying to build. I really
don't think a template engine should be this complex, but of course I'm
not too deep in the details of how Midgard user interfaces are being
built nowadays.

Would anyone care to write a simple example of how the style queue is
supposed to work? Something like: "We've got styles A, B, and C with
elements X, Y, and Z; when a page U is requested, the styles are
combined like this to produce an output like that."

BR,

Jukka Zitting

--

-- 
Yukatan - http://yukatan.fi/ - info@...
Software craftmanship, JCR consulting, and Java development
Jukka Zitting | 7 Dec 14:37
Picon

Jukka's TODO

Hi,

I'll be working with Midgard for a while now on funding by Nemein. To 
keep you up to date and as a heads-up of future changes we decided to 
list all the Midgard-related stuff I'll be working on in near future:

Midgard Core:
  * Support for the same GUID in different sitegroups
  * Change log for tracking object change histories
  * Core ACL support (first distributed cache, then higher level API)
  * Full text indexing in core

Midgard-Apache:
  * Support for Apache authentication in Midgard
  * Midgard as Apache authentication module (mod_auth_midgard)

Midgard-Java:
  * Packaging and documentation

Exorcist:
  * Clustered staging-live
  * Speed and memory use improvements
  * Possible NewsML support

OpenPSA:
  * Email campaign improvements for OpenPSA (spam!)
  * Automatic bounce handling

I'll start posting mRFCs and Bugzilla issues for these features. 
Comments, ideas, and wishes are welcome.
(Continue reading)

Torben Nehmer | 7 Dec 14:42
Gravatar

Re: Jukka's TODO


Hi,

--Jukka Zitting wrote on 2005-12-07 14:37:
> Midgard Core:
>   * Support for the same GUID in different sitegroups

I think that this is a very bad idea. Mainly, because MidCOM (for a start)
depends on the fact that a GUID is completly unique. Many caching tasks depend
on this.

Besides I think that this contradicts the general idea of a GUID.

The rest looks great :)

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

Gmane