<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.web.ezcomponents.devel">
    <title>gmane.comp.web.ezcomponents.devel</title>
    <link>http://blog.gmane.org/gmane.comp.web.ezcomponents.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4048"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4047"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4046"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4045"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4044"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4043"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4042"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4041"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4040"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4039"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4038"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4037"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4036"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4035"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4034"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4033"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4032"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4031"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4030"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4029"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4048">
    <title>Re: ezcWebdavSimpleBackend class</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4048</link>
    <description>Hi Urs,

On 12/01/2008 11:45 PM Urs Lang wrote:


The ezcWebdavFileBackend and ezcWebdavMemoryBackend (which is private,
but still you can look at it in the source) both extend
ezcWebdavSimpleBackend.


The class resides in Webdav/src/auth/digest_base.php. Which version of
ezc do you use, on what operating system and which installation method
did you choose? Maybe you are running Windows and forgot to re-run the
ezc setup script after updating from SVN?

HTH,
Toby
</description>
    <dc:creator>Tobias Schlitt</dc:creator>
    <dc:date>2008-12-01T23:02:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4047">
    <title>ezcWebdavSimpleBackend class</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4047</link>
    <description/>
    <dc:creator>Urs Lang</dc:creator>
    <dc:date>2008-12-01T22:45:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4046">
    <title>Re: [svn-components] 9451 - in /trunk/Mail: ChangeLog docs/tutorial/tutorial_tools.php src/tools.php tests/tools_test.php</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4046</link>
    <description>Hi!

On 11/26/2008 01:05 PM Alexandru Stanoi wrote:


You should probably format and comment this regex a bit, using the "x"
modifier.

Regards,
Toby
</description>
    <dc:creator>Tobias Schlitt</dc:creator>
    <dc:date>2008-11-26T19:14:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4045">
    <title>Re: ezcWorkflow difference between cancelling and ending aexecution</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4045</link>
    <description/>
    <dc:creator>Sebastian Bergmann</dc:creator>
    <dc:date>2008-11-20T06:51:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4044">
    <title>ezcWorkflow difference between cancelling and ending aexecution</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4044</link>
    <description>Hi,

I'm wondering if there's any particular reason why
ezcWorkflow-&gt;cancel() doesn't call the method doEnd (which cleans
execution_state and workflow_execution tables).

The cancel() and end() methods has the same outcome in the execution's
attributes (activatedNodes, waitingFor) but in the database that new
status are not updated. This allow the execution to be resumed if I
reload the instance from the database.

Can someone explain me better the difference between cancelling and
ending a workflow instance and the current behaviour?

Thanks,

</description>
    <dc:creator>Cinxgler Mariaca Minda</dc:creator>
    <dc:date>2008-11-19T20:46:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4043">
    <title>Re: HowTo incoperate ManyToMany Related data inezcPersistentObject, a proposal.</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4043</link>
    <description>I've had exactly the same problem, filled it in issue
http://issues.ez.no/IssueView.php?Id=13170&amp;activeItem=2

and had a similiar idea. :-)

Best regards,

Thomas Koch

Am Saturday 15 November 2008 11:15:55 schrieb Benjamin Eberlei:



</description>
    <dc:creator>Thomas Koch</dc:creator>
    <dc:date>2008-11-15T14:57:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4042">
    <title>Re: [svn-components] 9390 - in /trunk/Base:src/file.phptests/file_copy_recursive_test.php</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4042</link>
    <description/>
    <dc:creator>Sebastian Bergmann</dc:creator>
    <dc:date>2008-11-15T10:43:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4041">
    <title>HowTo incoperate ManyToMany Related data inezcPersistentObject, a proposal.</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4041</link>
    <description>There are cases when in many to many relationships you need additional data 
that is only relevant, when in the context of the m:n relation but in neither 
object context alone. Currently this is not possible in ezcComponents.

I have looked at the ezcPersistentSession and relation related source code and 
came to the conclusion that is not an easy task to integrate without looking 
somewhat hackish.

My first thought was to extend ezcPersistentSession::addRelatedOject to accept
a new parameter with the additional data to be saved in the relation table via 
an relation data object. This is a very bad solution, since you now have the 
problem of how to retrieve the addtional data, and how their representations 
is defined and can be accessed.

Then again, the data within m:n relation tables is only needed, when the 
relation is in full context, so i came up with a nicer solution that 
recognizes this relationsip: I would add a new 
ezcPersistentManyToManyDataRelation class that extends 
ezcPersistentManyToManyRelation. It has an additional property 
'manyToManyClass', which is a representation of the aggregated
data of destination and relation table.

"manyToManyClass" has to full fill a a state aggregation interface 
ezcPersistentObjectAggregate, that has to functions getStates() and 
setStates() which return arrays of setState() and getState() of the related 
objects where keys are unique definition table names '$def-&gt;table'. Internally 
then all resolutions between the different tables can be resolved by iterating
over the getStates() records and calling the appropriate means for each object 
state of the aggregate.

A note: Technically the relation table with data has no definition and hence 
the definition manager will fail to locate it.

Therefore many to many tables with data also have to have a definition file for 
this approach to work, also to define the fields that the relation table 
contains. A Definition has to exist for all the loader methods too. What 
information exactly this file should contain for my proposal to work i cant say 
for now, i'll have to build a prototype.

Any ideas and/or comments? This is by far no issue i have thought to the end, 
so in questions of detail my proposal might utterly fail. :-)

beberlei

Attachment: Some Use cases of using my proposed relation:

For a simple example in the ezcPersistentObject Tutorial context. Now 
'persons_addresses' contains additional data on how long this person is 
already registered at this address:

1. definition

$def-&gt;relations["Address"] = new ezcPersistentManyToManyDataRelation(
    "persons",
    "addresses",
    "persons_addresses"
);
$def-&gt;relations["Address"]-&gt;columnMap = array(
    new ezcPersistentDoubleTableMap( "id", "person_id", "address_id", "id" )
); 
$def-&gt;relations["Address"]-&gt;manyToManyClass = "PersonAddress";

2. PersonAddress

class PersonAddress implements ezcPersistentObjectAggregate
{
    /**
     * &lt; at &gt;var Address
     */
    private $address;

    /**
     * &lt; at &gt;var array
     */
    private $persons_addresses;

    public function getStates()
    {
        return array(
            'persons_addresses' =&gt; $this-&gt;persons_addresses,
            'addresses' =&gt; $this-&gt;address-&gt;getState();
        );
    }

    public function setStates(array $states)
    {
        foreach($states AS $table =&gt; $state) {
            switch($state) {
                case 'addresses':
                    $this-&gt;address = new Address();
                    $this-&gt;address-&gt;setState($state);
                    break;
                case 'persons_addresses':
                    $this-&gt;persons_addresses = $state;
                    break;
            }
        }
    }

    public function setRegisterDate($date)
    {
        $this-&gt;persons_addresses['register_date'] = $date;
    }
}

3 Use Case:

$person = $session-&gt;load('Person', 1);
$addresses = $person-&gt;getRelatedObjects();

foreach($addresses AS $address) {
    // now $address instanceof PersonAddress:
    $address-&gt;setRegisterDate(mktime(0, 0, 0, 5, 1, 2007));

    // session recognizes aggregation interface, iterates over the states
    $session-&gt;update($address);
}
</description>
    <dc:creator>Benjamin Eberlei</dc:creator>
    <dc:date>2008-11-15T10:15:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4040">
    <title>eZImageManager</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4040</link>
    <description/>
    <dc:creator>Rob Gaus</dc:creator>
    <dc:date>2008-11-14T22:55:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4039">
    <title>Webdav auth API change for extensibility</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4039</link>
    <description>Hi all!

I thought about changing the Webdav API for authentication slightly
before we once go stable with it, to make it easier for people to
implement additional / custom authentication schemes (like NTLM).

We currently have 3 interfaces for authentication:

interface ezcWebdavAnonymousAuthenticator
{
    public function authenticateAnonymous(
        ezcWebdavAnonymousAuth $data
    );
}

interface ezcWebdavBasicAuthenticator extends
    ezcWebdavAnonymousAuthenticator
{
    public function authenticateBasic( ezcWebdavBasicAuth $data );
}

interface ezcWebdavDigestAuthenticator extends
     ezcWebdavBasicAuthenticator
{
    public function authenticateDigest( ezcWebdavDigestAuth $data );
}

This means, that the server currently decides, which authenticator is
capable to handle which type of credential struct.

I'd suggest to go for a single authenticator interface now:

interface ezcWebdavAuthenticator
{
    public function authenticate( ezcWebdavCredentials $auth );

    public function getAuthHeader( $realm );
}

authenticate() returns true on successfull authentication, false on
failure and throws an exception if a struct is received that could not
be handled. getAuthHeader() returns an array of WWW-Authenticate headers
indicating which types of authentication are supported.

This would allow users to implement their custom authentication schemes
more easily. They need to extend the transport (and possibly client
specific transports), add a new credential struct and implement the
neccessary authentication() methods.

To make it easier to have basic and digest auth, I'd provide 2 abstract
base classes (1 for basic and anonymous, 1 for basic, digest and
anonymous) that produce the correct headers.

In addition I'd like to make the authorize() methods
(ezcWebdav(Lock)Authorizer) recieve the complete credential struct
instead of the username only. Just for the case that some authentication
scheme does not work with a username.

Does that sound reasonable to you?

Regards,
Toby
</description>
    <dc:creator>Tobias Schlitt</dc:creator>
    <dc:date>2008-11-12T06:55:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4038">
    <title>eZ Components 2008.2alpha1 released</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4038</link>
    <description>Hello!

After the earlier release of the first alpha releases of the MvcTools
components set, we're now releasing other alpha versions of other 
components.

The Document component now has support for reading and writing wiki 
formats, writing reST files and full support for XHTML. The Feed, 
Graph, Mail, PersistentObject, and Workflow components have all 
minor feature enhancements. The MvcTools component has seen many 
improvements over the first alpha after feedback. There is now also a 
tutorial[1] available.

The full release announcement can be found online [2].


[1] http://ezcomponents.org/docs/api/trunk/introduction_MvcTools.html
[2] http://ezcomponents.org/resources/news/news-2008-11-10

with kind regards,
</description>
    <dc:creator>Derick Rethans</dc:creator>
    <dc:date>2008-11-10T12:55:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4037">
    <title>Re: Horizontal Bars diagram</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4037</link>
    <description/>
    <dc:creator>Kore Nordmann</dc:creator>
    <dc:date>2008-11-10T09:06:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4036">
    <title>Re: transparent svg background</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4036</link>
    <description/>
    <dc:creator>Kore Nordmann</dc:creator>
    <dc:date>2008-11-10T09:01:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4035">
    <title>Re: Horizontal Bars diagram</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4035</link>
    <description>Thank you Kore for your answers.

Another question is: There is any way to put the distance between the
title and the graphic or the graphic and the legend? Sometimes they
are very close and I haven't found any attribute to do that.

Thanks again,

Raul

2008/11/6 Kore Nordmann &lt;kn-nIXORaQLHcI&lt; at &gt;public.gmane.org&gt;:
</description>
    <dc:creator>Raul Mateos</dc:creator>
    <dc:date>2008-11-08T19:49:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4034">
    <title>Re: transparent svg background</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4034</link>
    <description>
Try this:

$graph-&gt;background-&gt;color = 'FFFFFF';

I don't know if this is exactly what you need, though!

joao



</description>
    <dc:creator>Joao Ferreira gmail</dc:creator>
    <dc:date>2008-11-08T10:57:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4033">
    <title>transparent svg background</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4033</link>
    <description>Hi every body, very simple problem here, I'm trying to get a transparent 
SVG background, which is easy to make with a real SVG file, you just 
have to erase the background color definition.
Of course I've tried :

$graph-&gt;background-&gt;background = '';


But it didn't work, any ideas?

</description>
    <dc:creator>Julien Cochennec</dc:creator>
    <dc:date>2008-11-07T22:03:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4032">
    <title>Re: Horizontal Bars diagram</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4032</link>
    <description/>
    <dc:creator>Kore Nordmann</dc:creator>
    <dc:date>2008-11-06T09:17:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4031">
    <title>Horizontal Bars diagram</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4031</link>
    <description>Hello! I'm new in the list. I'm using the june 2008 version under
linux (ubuntu). I have discovered these great components and trying to
use for several Open Source projects.

I'm trying to do two things using the graph component and I have one question:

- First is how to create an horizontal bars diagram. Is it possible?
If so, how can I do it?

- Second, How can I change the line thickness and border color for bar
diagrams? I've seen it in
http://kore-nordmann.de/blog/comparison_of_php_image_libraries_update.html

- Third. Are there more dataSetSymbols to use in line graphs?

Kind regards and thanks in advance,

Raul
</description>
    <dc:creator>Raul Mateos</dc:creator>
    <dc:date>2008-11-04T17:00:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4030">
    <title>Experiences with Zend Core for i5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4030</link>
    <description>Hi,

I am a new to ezComponent. We are thinking about using it at our company.
We are running PHP via "ZendCore for i5" on some IBM i5 systems.

Does anybody here has any experiences with such a configuration?

Are there any known problems, hooks, suggestions for running 
ezComponents on the i5?

Thanks in advance for your advice.

Greetings
Thorsten
</description>
    <dc:creator>Thorsten Franke</dc:creator>
    <dc:date>2008-11-03T10:20:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4029">
    <title>Re: EzcWorkflow</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4029</link>
    <description>2008/10/31 Frank Stelzer &lt;fst&lt; at &gt;turtle-entertainment.de&gt;:

Hi Frank


Yes.


I need more and complex examples for i understand the workflow machine.

regards!
</description>
    <dc:creator>Daniel González</dc:creator>
    <dc:date>2008-11-03T09:59:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4028">
    <title>Re: EzcWorkflow</title>
    <link>http://permalink.gmane.org/gmane.comp.web.ezcomponents.devel/4028</link>
    <description> 
Hi Daniel,
The main documentation workflow website is here:
http://www.ezcomponents.org/docs/api/latest/introduction_Workflow.html

However, i look for more documentation then listed there.
Are there any more complex examples out there?

Cheers,
Frank

-----Ursprüngliche Nachricht-----
Von: components-bounces-p125XxirBjMXWF+eFR7m5Q&lt; at &gt;public.gmane.org [mailto:components-bounces-p125XxirBjMXWF+eFR7m5Q&lt; at &gt;public.gmane.org] Im Auftrag von Daniel González
Gesendet: Donnerstag, 30. Oktober 2008 20:29
An: components-p125XxirBjMXWF+eFR7m5Q&lt; at &gt;public.gmane.org
Betreff: [Components] EzcWorkflow

Hi, I'm looking for EzcWorkflow manuals, tutorials, examples, ect...

I see the web of EzComponents, but i need more info

Regards


Daniel González Cerviño
tel 653965048
ikarush-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org
</description>
    <dc:creator>Frank Stelzer</dc:creator>
    <dc:date>2008-10-31T12:30:40</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.ezcomponents.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.ezcomponents.devel</link>
  </textinput>
</rdf:RDF>
