Comments for Destroy every zig! http://www.gerryvandermaesen.com The official Gerry Vandermaesen blog Sun, 09 Oct 2011 12:45:11 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Sharing layouts cross-application in symfony by Gerry http://www.gerryvandermaesen.com/posts/sharing-layouts-cross-application-in-symfony/comment-page-1#comment-139 Gerry Sun, 09 Oct 2011 12:45:11 +0000 http://www.gerryvandermaesen.com/?p=26#comment-139 @Throoze, yes it is possible. The proper way to do it is to create a plugin, allowing to enable a module in multiple apps. Check out http://www.symfony-project.org/gentle-introduction/1_4/en/17-Extending-Symfony#chapter_17_plug_ins @Throoze, yes it is possible. The proper way to do it is to create a plugin, allowing to enable a module in multiple apps. Check out http://www.symfony-project.org/gentle-introduction/1_4/en/17-Extending-Symfony#chapter_17_plug_ins

]]> Comment on Sharing layouts cross-application in symfony by Throoze http://www.gerryvandermaesen.com/posts/sharing-layouts-cross-application-in-symfony/comment-page-1#comment-138 Throoze Sun, 09 Oct 2011 01:55:34 +0000 http://www.gerryvandermaesen.com/?p=26#comment-138 Is there a way to use a component in a shared layout like this? how can i set up a shared module, let's say "common" to store my common components and partials? Is there a way to use a component in a shared layout like this? how can i set up a shared module, let’s say “common” to store my common components and partials?

]]> Comment on Relaying Doctrine events to symfony by Juanmf http://www.gerryvandermaesen.com/posts/relaying-doctrine-events-to-symfony/comment-page-1#comment-135 Juanmf Wed, 13 Jul 2011 19:47:32 +0000 http://www.gerryvandermaesen.com/?p=117#comment-135 Nice! But then you should do this in every model.. not so DRY.. is it? Is there any tweak you can do to relay them from just one point in the app? and to enable it for DQL also? not just records... Cheers! Nice!
But then you should do this in every model.. not so DRY.. is it?
Is there any tweak you can do to relay them from just one point in the app?
and to enable it for DQL also? not just records…
Cheers!

]]> Comment on YeloPlayer by Just me http://www.gerryvandermaesen.com/posts/yeloplayer/comment-page-1#comment-106 Just me Fri, 11 Feb 2011 21:01:04 +0000 http://www.gerryvandermaesen.com/?p=113#comment-106 Werkt ook met Firefox, best handig, maar ik mis nog steeds de "stay on top" functie Werkt ook met Firefox, best handig, maar ik mis nog steeds de “stay on top” functie

]]> Comment on Organizing larger symfony projects with plugins by Glen http://www.gerryvandermaesen.com/posts/organizing-larger-symfony-projects-with-plugins/comment-page-1#comment-105 Glen Tue, 08 Feb 2011 10:27:49 +0000 http://www.gerryvandermaesen.com/?p=98#comment-105 Thanks it works great ! Thanks it works great !

]]> Comment on Returning your symfony form’s error schema as an array by bux http://www.gerryvandermaesen.com/posts/returning-your-symfony-forms-error-schema-as-an-array/comment-page-1#comment-100 bux Thu, 16 Dec 2010 10:40:59 +0000 http://www.gerryvandermaesen.com/?p=95#comment-100 Et voilà une version un peu plus poussé que je vient de coder: public static function transformErrorToSimpleArray($sfForm) { // Préparation des variables $array = array(); $embeddedForms = array(); if ($sfForm instanceof sfFormObject) { // On stocke chacune des erreurs globales si il en existe foreach ($sfForm->getErrorSchema()->getGlobalErrors() as $id => $error) { $array['_global'][] = $error->getMessage(); } } // Pour chaque element du formulaire foreach ($sfForm as $id => $widget) { // si il y a plusieurs champs dans ce champ, on relance la // procédure pour les parcourir un a un if (count($sfForm[$id]) > 1) { // On récupère le tableau $array_recursive = self::transformErrorToSimpleArray($sfForm[$id]); // si il contient des erreurs if (se::arrayContainsValue($array_recursive)) { // On l'ajoute au autres $array[$id] = $array_recursive; } } else { // Si c'est un simple champs et qu'il y a une erreur if (($error = $sfForm[$id]->getError())) { // On ajoute au tableau $array[$id] = $error->getMessage(); } } } return $array; } Et voilà une version un peu plus poussé que je vient de coder:

public static function transformErrorToSimpleArray($sfForm)
{

// Préparation des variables
$array = array();
$embeddedForms = array();

if ($sfForm instanceof sfFormObject)
{
// On stocke chacune des erreurs globales si il en existe
foreach ($sfForm->getErrorSchema()->getGlobalErrors() as $id => $error)
{
$array['_global'][] = $error->getMessage();
}
}

// Pour chaque element du formulaire
foreach ($sfForm as $id => $widget)
{
// si il y a plusieurs champs dans ce champ, on relance la
// procédure pour les parcourir un a un
if (count($sfForm[$id]) > 1)
{
// On récupère le tableau
$array_recursive = self::transformErrorToSimpleArray($sfForm[$id]);

// si il contient des erreurs
if (se::arrayContainsValue($array_recursive))
{
// On l’ajoute au autres
$array[$id] = $array_recursive;
}
}
else
{
// Si c’est un simple champs et qu’il y a une erreur
if (($error = $sfForm[$id]->getError()))
{
// On ajoute au tableau
$array[$id] = $error->getMessage();
}
}

}

return $array;

}

]]> Comment on Returning your symfony form’s error schema as an array by bux http://www.gerryvandermaesen.com/posts/returning-your-symfony-forms-error-schema-as-an-array/comment-page-1#comment-99 bux Wed, 15 Dec 2010 18:13:24 +0000 http://www.gerryvandermaesen.com/?p=95#comment-99 Pratique! Dommage que ca ne gère pas les erreurs d'embededForms. Pratique!
Dommage que ca ne gère pas les erreurs d’embededForms.

]]> Comment on Sharing layouts cross-application in symfony by GB http://www.gerryvandermaesen.com/posts/sharing-layouts-cross-application-in-symfony/comment-page-1#comment-92 GB Mon, 15 Nov 2010 18:32:37 +0000 http://www.gerryvandermaesen.com/?p=26#comment-92 edit: worked :P edit: worked :P

]]> Comment on Sharing layouts cross-application in symfony by GB http://www.gerryvandermaesen.com/posts/sharing-layouts-cross-application-in-symfony/comment-page-1#comment-91 GB Mon, 15 Nov 2010 18:23:08 +0000 http://www.gerryvandermaesen.com/?p=26#comment-91 Didn't work gives me template doesnt exist in "" error Didn’t work
gives me template doesnt exist in “” error

]]> Comment on Making template vars available in the layout by Gerry http://www.gerryvandermaesen.com/posts/making-template-vars-available-in-the-layout/comment-page-1#comment-58 Gerry Wed, 06 Oct 2010 13:34:51 +0000 http://www.gerryvandermaesen.com/?p=86#comment-58 I agree that you shouldn't resort to this type of solutions for everything. Slots certainly fill a need, and you should stick to them as much as possible. However, sometimes I just want to check certain flags which can be set from inside the controller for rendering different HTML, or just assign a very simple value like an extra CSS class to the body element, and I feel slots are very (too?) verbose for such simple usecases. I would like to revisit this one day and have namespaced parameter holders, in a way you could implement a $this->setGlobalVar('foo', true) in your actions for example. I agree that you shouldn’t resort to this type of solutions for everything. Slots certainly fill a need, and you should stick to them as much as possible.

However, sometimes I just want to check certain flags which can be set from inside the controller for rendering different HTML, or just assign a very simple value like an extra CSS class to the body element, and I feel slots are very (too?) verbose for such simple usecases.

I would like to revisit this one day and have namespaced parameter holders, in a way you could implement a $this->setGlobalVar(‘foo’, true) in your actions for example.

]]>