Debuggable.com - Comments

Restarting a command line PHP script [Comment by Felix Geisendörfer]

no-reply@debuggable.com — Wed, 15 Jul 2009 15:17:37 +0000

@JC What shell / OS are you using?

Sales Almost Closing for CakeFest#3 in Berlin! [Comment by Felix Geisendörfer]

no-reply@debuggable.com — Wed, 15 Jul 2009 13:03:38 +0000

@Rob: The Raleigh video has not been made available because unfortunately the audio track turned out to be very poor : /. However, the footage of this cakefest seems very good so far and we are going to blog about it soon as well.

Parsing XML With The DOM Library [Comment by Elemental]

no-reply@debuggable.com — Wed, 15 Jul 2009 10:24:10 +0000

thanks for the post, PHP4 and XML handling was a real pain!

PHP5 is a dream to manipulate XML.

An Ajax file upload progressbar [Comment by Juan]

no-reply@debuggable.com — Tue, 14 Jul 2009 20:56:51 +0000

juanpablostange.blogspot.com/2009/07/upload-progress-bar-100-php.html

Hope its usefull for somebody

Sales Almost Closing for CakeFest#3 in Berlin! [Comment by Tim Koschützki]

no-reply@debuggable.com — Tue, 14 Jul 2009 15:30:43 +0000

Alright, so CakeFest was amazing!

Sales Almost Closing for CakeFest#3 in Berlin! [Comment by Rob Richmond]

no-reply@debuggable.com — Tue, 14 Jul 2009 11:33:44 +0000

Question...anybody know where the content for this CakeFest is going to be posted? Or if it will be posted? I am still waiting for the video we did at the CakeFest is Raleigh, NC.

How to have multiple paginated widgets on the same page with CakePHP [Comment by Daniel Voyce]

no-reply@debuggable.com — Mon, 13 Jul 2009 14:00:28 +0000

Ok im with you now :) Did you get it working in the end?

thanks for the quick reply dude!

How to have multiple paginated widgets on the same page with CakePHP [Comment by Chris]

no-reply@debuggable.com — Mon, 13 Jul 2009 13:53:02 +0000

I changed the code that goes in appmodel.. function pageForPagination

I dont have the code anymore don't ask.. hehe but am pretty sure it went like this.

function pageForPagination($model) {
$page = 1;
$params = Dispatcher::parseParams(Dispatcher::uri());
$sameModel = isset($params['named']['model']) && $params['named']['model'] == $model;
$pageInUrl = isset($params['named']['page']);

if ($sameModel && $pageInUrl) {
$page = $params['named']['page'];
}

$this->passedArgs['page'] = $page;
return $page;
}

How to have multiple paginated widgets on the same page with CakePHP [Comment by Daniel Voyce]

no-reply@debuggable.com — Mon, 13 Jul 2009 13:10:45 +0000

Hi Chris,

Could you post your code in its entirity please? I cant work out which part you have replaced with what. I have a page with 8 different widgets on it and trying to paginate them all independently

Dan

Command line fun in CakePHP 1.2 [Comment by LiNo]

no-reply@debuggable.com — Mon, 13 Jul 2009 02:03:32 +0000

Hello everyone, just like to ask if it is possible to bake an additional model/controller/view for a new database table to an existing project?

Restarting a command line PHP script [Comment by JC]

no-reply@debuggable.com — Thu, 09 Jul 2009 05:36:04 +0000

Hi Felix,

I came across this post today because I was looking for a solution to the same situation.

The problem with your glorious hack is that the original php processes will hang around until finally the last one fully exits (because the call to die will wait for the return value of exec before it finally dies). This means that the resources that each script uses (most critically the RAM) will continue to be in use.

I solved the problem by using a modified version of Sebastian's bash script above. This allows the php process to exit and free all resources before the bash script re-instates the script again.

Just an FYI.

An Ajax file upload progressbar [Comment by Raymond Software Indonesia]

no-reply@debuggable.com — Sun, 05 Jul 2009 17:10:22 +0000

The link "check out the documentation" on the demo page is broken.

PHP code generator [Comment by nathan]

no-reply@debuggable.com — Sun, 05 Jul 2009 08:09:06 +0000

this would provide a slick interface for creating php files directly from database queries. i would suggest creating a set of method that act as open(), but would be shorthand, like $code->foreach('foo','bar'), $code->class('foo','bar') ('class foo extends bar {'), $code->if('foo') and so forth. Also $code->comment('bar!')

XHTML is a joke [Comment by Nate Abele]

no-reply@debuggable.com — Fri, 03 Jul 2009 20:38:23 +0000

@Ben Ramsey: I agree, and I don't think anyone has anything against well-formed markup in and of itself; that's not the point.

I think of the debate as being analogous to the debate between static and dynamic languages. XHTML takes the static typing approach of saying, 'if you don't implement this correctly [regardless of whether or not it's *functionally* incorrect] then I'm not even compiling this for you'. Whereas in dynamic languages, it'll continue to run, and as long as you're not leaving the engine in an unstable state. However, your unit tests (a.k.a. markup validation) will bitch at you until you get it right.

This is, IMO, the correct approach. We have a system for determining the 'correctness' of a document, but expecting a lack of correctness to totally break your page is like not even allowing your application to execute without all your tests passing. Now, if you want that level of strictness, that's your decision to make, but it shouldn't be made for you by browser vendors or standards bodies.

@Andrew Jones: I forgive you. :-) But now you know, and knowing is half the battle. ♪ G-I-Joe!! But seriously, as much as I'd like to "just code it right the first time"... well, sometimes I don't, and we've all had errors that only get caught in production. I guess we can't all be perfect like you. :-P

Hehehe... kidding, kidding.

XHTML is a joke [Comment by Ben Ramsey]

no-reply@debuggable.com — Fri, 03 Jul 2009 20:16:22 +0000

I believe the movement to subvert XHTML will harm the Open Data Movement, the Linking Open Data Community Project, and, ultimately, progress toward realizing the Semantic Web.

If we want to make the Semantic Web a possibility, then we need HTML serialized as XML. Thus, we need XHTML. We need to understand that HTML is no longer simply a presentation format, but that it is also a data interchange format.

XHTML is a joke [Comment by Andrew Jones]

no-reply@debuggable.com — Fri, 03 Jul 2009 19:49:37 +0000

@Nate: Wow, I had no idea I was responsible for destroying the web. My bad.

I'm absolutely not saying that getting pixel-perfect rendering in all browsers is the goal. Even if the page looked 50% different from the original design, that doesn't change the fact that if I mess up the code, something will break. I don't know why this is such an unthinkable concept. Leave off a closing ">" and it breaks. Them's the rules.

Yes, it's nice when browsers are "forgiving", but if you code it properly the first time, you won't have to worry about being forgiven as much.

And on a side note, yes, it is absolutely the job of a front-end developer to make the page look as much like the original design as possible. I've never had a designer give me a comp and say, "just get close". So if you can't make it work in every browser (with some graceful degradation in IE6), then you either need to go back and negotiate with your designer, or get better at your job.

XHTML is a joke [Comment by Nate Abele]

no-reply@debuggable.com — Fri, 03 Jul 2009 19:36:20 +0000

@Andrew Jones: I think you've got it exactly wrong, and your view is diametrically opposed to the very notion on which web development (as well as browser development) is predicated.

Unless you're relying on proprietary browser extensions, absolute 'fidelity' of page rendering is a pipe dream at best. It is completely impossible to get pixel-perfect renderings of your designs across all browser/OS platforms. Of the dozens of combos, you're lucky if you even hit three. If your designers expect fidelity, they're working in the wrong medium; tell them to go back to print.

Additionally, as graceful degradation is a core tenet of browser implementation as well as good markup & code, the idea that one misplaced ">" would completely break the entire page is tantamount to replacing your site with a banner that says "You can only view this site on IE6", because you're coming from the same mis-informed idea that 'if your browser can't render this *exactly* right, then you get nothing!'

It's people like you that started to destroy the web when IE6 was peaking; and everyone who has failed to adapt since then has been either laughed out or kicked out of their profession.

XHTML is a joke [Comment by Andrew Jones]

no-reply@debuggable.com — Fri, 03 Jul 2009 16:23:13 +0000

Arriving (very) late to this discussion. My gut assumption here is that most, if not all, of the responders to this post are primarily back-end developers? My primary role is that of front-end developer (html/css/js) and I've been using XHTML Strict exclusively for the last couple years. My response to your statement "the slightest mistake in your markup will cause your page to NOT RENDER!" is this: duh.

To me, that's exactly the point. It may be easy for a back-end dev to think that the fidelity of the original design is secondary (or lower) in priority to back-end code. And I can't exactly blame you. But my entire job is predicated around the idea that I'm taking a designer's vision and building it as precisely as possible. Now, if that designer is also you, it's your choice whether to code your front-end properly. But in a multi-person team, I don't have that luxury, and I don't allow other front-end devs that luxury either.

XHTML is a joke [Comment by Andrea Giammarchi]

no-reply@debuggable.com — Fri, 03 Jul 2009 14:49:53 +0000

@Felix, HTML5 does not mean you can omit tags, forget to close them, etc etc ... I think code, whatever layer it is, should be well formed, clean, and reasonably simple to read/understand. This should mean less problem for parsers which means more speed for both clients and servers (when layouts are elaborated there as well). I do not get all this complaining about XHTML and 1.0 is widely supported and it guarantees reasonable results even in non A-Grade browsers. As XML brings data and should be well formed, XHTML or whatever DOCTYPE you like brings the layout. Strict means you are following more rules and if you want to forget a layer just because is the "latest one" ... well, you should consider design rather than web programming/development, and forget contrasts cause lines are more important for the structure? As summary, as far as I remember I have never had a fatal error problem in almost 10 years, maybe I have been lucky? In any case an error means somebody, possibly not the parser, did a mistake somewhere ... do you think it makes sense to blame a standard for this? Just my 2 pennies. Regards

CouchDB Insert Benchmarks [Comment by Kristina]

no-reply@debuggable.com — Mon, 29 Jun 2009 21:56:12 +0000

Hi! Thanks for the script! I tried out your benchmark with MongoDB, and put the results up at www.snailinaturtleneck.com/blog/?p=74, if anyone's interested. (The short summary: MongoDB was a lot faster.)

For people using other DB's: feel free to send me your results so I can add them to my comparison graph!

Screencast #1: Using vendor branching and CakePHP [Comment by newbie in cake]

no-reply@debuggable.com — Mon, 29 Jun 2009 20:29:04 +0000

felix i want to ask you about adding video in my cake website...
can you explain step by step.. how to add video player in our cake website???

thaks before

Exceptional Cake [Comment by TEHEK]

no-reply@debuggable.com — Mon, 29 Jun 2009 10:58:02 +0000

Hey, nice job there! Hope in future they will use something like this to do something decent with the error output to users.

I'm running CakePHP 1.2.3 and I had to do some change to your code:

app/error.php : Line 18

Replace
$Exception->render();

with
print $Exception->render();

// actually, how did it work without it in the first place? O_o

also thinking of adding layout switcher in case something except standard text input will be needed..

THanks again!

Release early, Release often, A SVN/FTP Deployment Task [Comment by kinoman]

no-reply@debuggable.com — Sun, 28 Jun 2009 08:45:17 +0000

http://video.faq.net.ua/ ----- прямые ссылки на фильмы с отличным качеством.
:):):)

CouchDB Insert Benchmarks [Comment by Steve Oliveira]

no-reply@debuggable.com — Fri, 26 Jun 2009 00:43:10 +0000

Thanks for posting that video Damien Katz video, Felix. That was pretty damn inspirational.

CouchDB Insert Benchmarks [Comment by Damien Katz]

no-reply@debuggable.com — Thu, 25 Jun 2009 22:24:43 +0000

The reason you see the amount the file grows to vary, and generally increase, is because of the btree by_id and by_seq indexes, who's update cost per document are LOG(N). So the slow growth rate increase is expected.

The reason the compaction increases the file size might be becauase you are doing larger transactions instead than the compaction does, which works by reading some data and filling a buffer, and then writing it and it's indexes out. If that buffer is smaller than your buld transactions, it will compact larger than the original file.