<?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://permalink.gmane.org/gmane.comp.php.general">
    <title>gmane.comp.php.general</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general</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.php.general/226039"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226038"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226037"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226036"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226035"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226034"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226033"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226032"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226031"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226030"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226029"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226028"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226027"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226026"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226025"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226024"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226023"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226022"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226021"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.php.general/226020"/>
      </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.php.general/226039">
    <title>Re: Re: Crudin - CRUD INterface Generator - Open Source Project</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226039</link>
    <description>&lt;pre&gt;On Fri, May 25, 2012 at 3:53 PM, Maciek Sokolewicz
&amp;lt;maciek.sokolewicz&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

hmm.. Demo &amp;gt; Login &amp;gt; New Table ...

Erro: You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use
near 'ORDER BY `new table`.`id` desc LIMIT 0, 60' at line 1


What is the purpose of your framework?  From the documentation, I can
see that it has tables of permissions for the users.  Looking at the
permission table, it seems you're attempting to replicate MySQL
permission.  If its purpose is generate the UI for CRUD, how
comparable is it to Yii?  When you just specify the table name in GUI,
Yii generates the entire UI with client side validation also, IIRC.
In the back-end, it has a class for that table and retrieves the table
data into the class objects via ORM.

&lt;/pre&gt;</description>
    <dc:creator>Tommy Pham</dc:creator>
    <dc:date>2012-05-26T01:27:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226038">
    <title>Re: Crudin - CRUD INterface Generator - Open Source Project</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226038</link>
    <description>&lt;pre&gt;
Hi Rodrigo,
I must admit I am having trouble understanding what you're making here. 
I tried looking at your demo page, but since it's half-Portuguese, and 
half(-crud)-English, it makes it impossible for me to understand even 
half of what it says.

Could you please explain, properly, what your system DOES exactly, and 
why I would want to use it? Because currently I just don't understand 
what it is supposed to help me with exactly.


&lt;/pre&gt;</description>
    <dc:creator>Maciek Sokolewicz</dc:creator>
    <dc:date>2012-05-25T22:53:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226037">
    <title>Crudin - CRUD INterface Generator - Open Source Project</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226037</link>
    <description>&lt;pre&gt;Hi,

I am the creator of a open source project called Crudin 
(http://crudin.smarc.com.br/en)

Crudin is a system for generation of fron-ends in the MySQL, writted in PHP

Without needing to program nothing you get a complete platform with 
operations CRUD (Create, Read, Update and Delete) and much more

Crudin mounts relations, to make upload of archives and images, treat 
fields enum/set and much more

All you need is any MySQL database!

Official Site: http://crudin.smarc.com.br/en

Demonstration: http://crudin.smarc.com.br/demo

username: demo
password: demo

Regards,
Rodrigo A. Rodriguez

Em 25/05/2012 18:01, php-general-help&amp;lt; at &amp;gt;lists.php.net escreveu:


&lt;/pre&gt;</description>
    <dc:creator>Rodrigo de Almeida Rodriguez</dc:creator>
    <dc:date>2012-05-25T21:09:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226036">
    <title>Re: Simple XML, (x)html, and xpath</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226036</link>
    <description>&lt;pre&gt;
Gary,

I am not sure what you have tried, but namespaces change everything in
XPath compared to documents without them. This isn't exact, but XPath
without namespaces is often simple such as:

/html/head/title

Once you add a namespace, though, the XPath becomes something like

/*[namespace-uri()='http://www.w3.org/1999/xhtml' and
local-name()='html']/*[namespace-uri()='http://www.w3.org/1999/xhtml'
and local-name()='head']/*[namespace-uri()='http://www.w3.org/1999/xhtml'
and local-name()='title']


(I'm not sure of the exact syntax since I don't have something open
right now that I can test it in.

However, I think SimpleXML has some features that make this easier.
Take a look at this:

http://www.php.net/manual/en/simplexmlelement.registerxpathnamespace.php

Andrew

&lt;/pre&gt;</description>
    <dc:creator>Andrew Ballard</dc:creator>
    <dc:date>2012-05-25T14:25:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226035">
    <title>Re: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226035</link>
    <description>&lt;pre&gt;

Yep, not everything can it -- there are exceptions.

Cheers,

tedd


_____________________
tedd&amp;lt; at &amp;gt;sperling.com
http://sperling.com



&lt;/pre&gt;</description>
    <dc:creator>Tedd Sperling</dc:creator>
    <dc:date>2012-05-25T12:42:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226034">
    <title>Re: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226034</link>
    <description>&lt;pre&gt;

While it may be obvious to you, there is considerable study on the ways we perceive things -- this is just one we apparently take for granted ... at least now.

Cheers,

tedd


_____________________
tedd&amp;lt; at &amp;gt;sperling.com
http://sperling.com


&lt;/pre&gt;</description>
    <dc:creator>Tedd Sperling</dc:creator>
    <dc:date>2012-05-25T12:38:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226033">
    <title>Re: Simple XML, (x)html, and xpath</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226033</link>
    <description>&lt;pre&gt;

Gary &amp;lt;listgj-phpgeneral&amp;lt; at &amp;gt;yahoo.co.uk&amp;gt; hat am 25. Mai 2012 um 09:57
geschrieben:

charset=UTF-8"


Maybe you can show us your xpath expression?


Marco Behnke
Dipl. Informatiker (FH), SAE Audio Engineer Diploma
Zend Certified Engineer PHP 5.3

Tel.: 0174 / 9722336
e-Mail: marco&amp;lt; at &amp;gt;behnke.biz

Softwaretechnik Behnke
Heinrich-Heine-Str. 7D
21218 Seevetal

http://www.behnke.biz

&lt;/pre&gt;</description>
    <dc:creator>marco&lt; at &gt;behnke.biz</dc:creator>
    <dc:date>2012-05-25T08:27:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226032">
    <title>Simple XML, (x)html, and xpath</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226032</link>
    <description>&lt;pre&gt;If I use simplexml_load_string to create an XML object with the
following XHTML
,----
| &amp;lt;?xml version="1.0"?&amp;gt;
| &amp;lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
| "http://www.w3.org/TR/
| xhtml1/DTD/xhtml1-strict.dtd"&amp;gt;
| &amp;lt;html xmlns="http://www.w3.org/1999/xhtml"&amp;gt;
| &amp;lt;head&amp;gt;&amp;lt;meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
| /&amp;gt;
| &amp;lt;title&amp;gt;test title&amp;lt;/title&amp;gt;
| &amp;lt;/head&amp;gt;
| &amp;lt;body&amp;gt;
| &amp;lt;!-- comment --&amp;gt;
| &amp;lt;/body&amp;gt;
| &amp;lt;/html&amp;gt;
`----

I get this SimpleXMLElement back
,----
| object(SimpleXMLElement)#1 (2) {
|   ["head"]=&amp;gt;
|   object(SimpleXMLElement)#2 (1) {
|     ["title"]=&amp;gt;
|     string(10) "test title"
|   }
|   ["body"]=&amp;gt;
|   object(SimpleXMLElement)#3 (1) {
|     ["comment"]=&amp;gt;
|     object(SimpleXMLElement)#4 (0) {
|     }
|   }
| }
`----

but I cannot seem to get anything out of an xpath expression, no matter
what I try.

If, however, I remove the 'xmlns="http://www.w3.org/1999/xhtml"' in the
html element, it works fine. So yeah, I can just remove that text,
but... is there something wrong here,&lt;/pre&gt;</description>
    <dc:creator>Gary</dc:creator>
    <dc:date>2012-05-25T07:57:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226031">
    <title>Re: Re: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226031</link>
    <description>&lt;pre&gt;


With the odd exception being where code is more readable in a longer
format, as seen with my and several others examples of long functions
that rely heavily on switches. 

&lt;/pre&gt;</description>
    <dc:creator>Ashley Sheridan</dc:creator>
    <dc:date>2012-05-24T21:01:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226030">
    <title>Re: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226030</link>
    <description>&lt;pre&gt;up to our ability to view them in their totality. When our functions get
beyond that limit, we tend to refactor and reduce.
increased in number of lines. But, they have reached a limit that limit is
generally about the number of lines I can read in half of my monitor's
height. This of course, is dependent on monitor resolution, font-size, and
how far I am sitting from the monitor. But I think this is a natural and
physical limit that we don't normally recognize. I can cite studies that
support my theory.
and provide the average number of lines in their functions AND how many
lines of code their monitor's can display. In other words, look at your
editor; count the number of lines your monitor can display; estimate the
number of lines in your average function; and report the findings.  For
example, mine is about half -- my monitor can display 55 lines of code and
my average function is around 25 lines. YMMV.

Yes, I think that is *exactly* the criterion-- not a mystery or an emergent
thing, really, was a prett&lt;/pre&gt;</description>
    <dc:creator>tamouse mailing lists</dc:creator>
    <dc:date>2012-05-24T20:48:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226029">
    <title>Re: w.r.t. mail() function</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226029</link>
    <description>&lt;pre&gt;
well, if he is wanting the message to be placed in the outbox or sent 
folder of his email client, and this client is on his workstation and 
the sent folder is accessed via IMAP, nor is it via a web client, then 
his only option is to have his email client filter a message to the sent 
folder.

POP3 picks up new messages from your inbox.  IMAP allows you to have 
folders on/in the mail server file structure, but the mail server would 
then need a filter (ie: procmail) to move the new message over to the 
correct folder.

So, no matter what type of solution he comes up with, something, either 
his client or the mail server will need to have a filter created to move 
the message to the correct folder.

Now, I guess you could completely sidestep all security and with proper 
setting have php write the email to the correct folder in the persons 
sent box.  And he could then access it via IMAP and/or a web based email 
client.  But, this would require that php process have file level access 
to the folder which&lt;/pre&gt;</description>
    <dc:creator>Jim Lucas</dc:creator>
    <dc:date>2012-05-24T15:48:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226028">
    <title>Re: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226028</link>
    <description>&lt;pre&gt;
It starts where it starts. It doesn't make any difference how you do it, it's what you see in one view that counts.

If you are very verbose with spaces, brace styles, comments, and such, then your functions have less actual statement lines than others with more cryptic coding styles, but I would bet the line limit of total number of lines remain in place regardless. This is more a condition of physical/mental limits on humans than it is on coding style.

So, there's no "better" or "worse' point here -- it is more an observation.

Cheers,

tedd

_____________________
tedd&amp;lt; at &amp;gt;sperling.com
http://sperling.com

&lt;/pre&gt;</description>
    <dc:creator>Tedd Sperling</dc:creator>
    <dc:date>2012-05-24T15:00:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226027">
    <title>Re: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226027</link>
    <description>&lt;pre&gt;
On May 23, 2012, at 3:49 PM, Ashley Sheridan wrote:

I see you and I are like minds in many ways.

I had one large switch block that had 255 different cases. Oddly enough I was parsing a "Tiger" data file (USGS survey data) that contained 255 different record types. Each record type required a different function to parse the data and render it's portion of the overall map. That lead to me create a linked-list that held the memory addresses of both data and function. That way simply accessing the linked list coupled data to function and drew the map. It was neat.

I find it also neat, while I'm not an expert on the subject, eliminating the need for 'switch' and 'if' statements via extending classes in OO.

Shiplu provided a link, which I found interesting:

http://www.youtube.com/watch?v=4F72VULWFvc

It showed how one can eliminate such conditionals, but at the same time it massively increased the code to preform 1 + 2 * 3. :-)

And to others, I don't need comment on how I missed the point -- I didn't.

Chee&lt;/pre&gt;</description>
    <dc:creator>Tedd Sperling</dc:creator>
    <dc:date>2012-05-24T14:52:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226026">
    <title>Re: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226026</link>
    <description>&lt;pre&gt;

I, and I'm fairly sure many others, do not count docblocks, comment
lines, or lines containing only braces in the count for LOC in a
function.

&lt;/pre&gt;</description>
    <dc:creator>Jeremiah Dodds</dc:creator>
    <dc:date>2012-05-24T12:52:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226025">
    <title>Re: openssl_sign() &amp; openssl_verify() discrepancy</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226025</link>
    <description>&lt;pre&gt;
Well without you saying "should explain the problem further" I wouldn't 
have conducted the series of tests to verify each component being used 
within the sign/save &amp;amp; retrieve/verify processes.

I was passing the wrong argument in during my retrieve/verify flow.

Thanks again!


&lt;/pre&gt;</description>
    <dc:creator>jas</dc:creator>
    <dc:date>2012-05-24T12:53:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226024">
    <title>Re: Cookie use management</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226024</link>
    <description>&lt;pre&gt;( Forgot email address :) )
Jeremiah Dodds wrote:

That would probably fall under the ICO acceptance that they don't want people to 
feel that they simply have to switch site functionality off ;)

I'm doing the hosting, but many of the sites that I need to support we have not 
written the code which as a range of 'frameworks', so I'm trying to find 
something that can be added in easily - like the Piwik tracking - without having 
to rewrite the sites ...

I'm thinking I need to write my own module, but I can't believe that no-one has 
done it yet. Or perhaps they are all charging for the service :)

&lt;/pre&gt;</description>
    <dc:creator>Lester Caine</dc:creator>
    <dc:date>2012-05-24T12:51:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226023">
    <title>RE: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226023</link>
    <description>&lt;pre&gt;one

Tedd,

I think the length of code depends on a few different factors, what if you
have your docblocks, and comment lines, as well as your bracing style?
Where do you consider your function to start?

Personally, I use this bracing style:

# decide if we should work, or sleep
if($do == $something)
{
# do something here
$work = 'done';
}
else
{
# something isn't being done now
$work = 'sleep';
}


In this (really crude) example, there are 11 lines of code.  Granted, the
way you do your bracing you can lose a few lines, and within this example,
it could be written as:

# decide if we should work, or sleep
# default action for if something isn't being done
$work = 'sleep';
if($do == $something) {
# do something here
$work = 'done';
}

So, with that craptastic example, we've taken 11 lines, and compressed it to
7.

Anyways, I get the "rule of thumb" to be able to fit a function on a
"screen", or to make it as small as possible, but sometimes comments can get
in the way, and if you like your bracing sty&lt;/pre&gt;</description>
    <dc:creator>Steven Staples</dc:creator>
    <dc:date>2012-05-24T12:37:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226022">
    <title>Re: problem sending email</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226022</link>
    <description>&lt;pre&gt;
Don't prefix with From: and To: here.


Also, Gmail SMTP supports only SSL connections. I don't know this PEAR
module, but I think you need to host set to something like
ssl://smtp.gmail.com, to enforce SSL connection.

- Matijn

&lt;/pre&gt;</description>
    <dc:creator>Matijn Woudt</dc:creator>
    <dc:date>2012-05-24T12:10:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226021">
    <title>problem sending email</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226021</link>
    <description>&lt;pre&gt;hi all,i'm having this problem in sending email using pear.
it just wont send :(
here's the code ..

&amp;lt;?php
    require_once 'Mail.php';

    $from_name = "My Self";
    $to_name = "My Friend";
    $subject = "Sending Trial";
    $mailmsg = "GOD please make it work";

    $From = "From: ".$from_name." &amp;lt;mymail&amp;lt; at &amp;gt;gmail.com&amp;gt;";
    $To = "To: ".$to_name." &amp;lt;someone&amp;lt; at &amp;gt;yahoo.com&amp;gt;";
    $recipients = "someone&amp;lt; at &amp;gt;yahoo.com";

    $headers["From"] = $From;
    $headers["To"] = $To;
    $headers["Subject"] = $subject;
    $headers["Content-Type"] = "text/plain; charset=iso-8859-1";

    $smtpinfo["host"] = "smtp.gmail.com";
    $smtpinfo["port"] = "465";
    $smtpinfo["auth"] = true;
    $smtpinfo["username"] = "mymail&amp;lt; at &amp;gt;gmail.com";
    $smtpinfo["password"] = "mypassword";

    $mail_object =&amp;amp; Mail::factory("smtp", $smtpinfo);

    $mail_object-&amp;gt;send($recipients, $headers, $mailmsg);

    if (PEAR::isError($mail_object))
      echo $mail_object-&amp;gt;getMessage();
?&amp;gt;
&lt;/pre&gt;</description>
    <dc:creator>As'ad Djamalilleil</dc:creator>
    <dc:date>2012-05-24T12:00:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226020">
    <title>Re: Function size</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226020</link>
    <description>&lt;pre&gt;
This is interesting. You do realize that if I would take this switch
down to OO, I would have to create 400 different classes to replace
this switch statement? Luckily in PHP we can have more classes in a
single file, thinking about Java for example would mean I have to
create 400 new files...
I like the concept, but I don't see how it works for such switch statements.

&lt;/pre&gt;</description>
    <dc:creator>Matijn Woudt</dc:creator>
    <dc:date>2012-05-24T11:54:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.php.general/226019">
    <title>Re: w.r.t. mail() function</title>
    <link>http://permalink.gmane.org/gmane.comp.php.general/226019</link>
    <description>&lt;pre&gt;
Maybe because not everyone uses mail clients that have a filter functionality?

&lt;/pre&gt;</description>
    <dc:creator>Matijn Woudt</dc:creator>
    <dc:date>2012-05-24T11:39:44</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.php.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.php.general</link>
  </textinput>
</rdf:RDF>

