Comments for Adam Fairholm's Internet Superworld http://blog.adamfairholm.com Wed, 18 Jan 2012 20:11:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Dynamic Pages with PyroCMS and PyroStreams by Jitse http://blog.adamfairholm.com/dynamic-pages-with-pyrocms-and-pyrostreams/comment-page-1/#comment-534 Jitse Wed, 18 Jan 2012 20:11:00 +0000 http://blog.adamfairholm.com/?p=157#comment-534 I want to use PyroStreams to display specific images on the pages. I'm trying to use the following code in PyroCMS 2.0 Professional: {{ streams:cycle stream="images" where="page_number=={{ page:id }}" }} With this where syntax, I can't get it to work... {{ streams:cycle stream="images" where="page_number==2" }} This does work, but thats not how I want it... Any suggestions? I want to use PyroStreams to display specific images on the pages.
I’m trying to use the following code in PyroCMS 2.0 Professional:

{{ streams:cycle stream=”images” where=”page_number=={{ page:id }}” }}
With this where syntax, I can’t get it to work…

{{ streams:cycle stream=”images” where=”page_number==2″ }}

This does work, but thats not how I want it…

Any suggestions?

]]> Comment on FuelPHP for CodeIgniter Developers by Ricky http://blog.adamfairholm.com/fuelphp-for-codeigniter-developers/comment-page-1/#comment-532 Ricky Sun, 08 Jan 2012 16:41:00 +0000 http://blog.adamfairholm.com/?p=104#comment-532 TL;DR: Use Symfony2 TL;DR: Use Symfony2

]]> Comment on FuelPHP for CodeIgniter Developers by Ricky http://blog.adamfairholm.com/fuelphp-for-codeigniter-developers/comment-page-1/#comment-531 Ricky Sun, 08 Jan 2012 16:40:00 +0000 http://blog.adamfairholm.com/?p=104#comment-531 Static classes are bad. You can't pass them around as data. They make unit testing more difficult and less beautiful. Static classes are bad. You can’t pass them around as data. They make unit testing more difficult and less beautiful.

]]> Comment on FuelPHP for CodeIgniter Developers by Dauren Dauletov http://blog.adamfairholm.com/fuelphp-for-codeigniter-developers/comment-page-1/#comment-530 Dauren Dauletov Mon, 05 Dec 2011 11:09:00 +0000 http://blog.adamfairholm.com/?p=104#comment-530 Nice article, thanks. Nice article, thanks.

]]> Comment on Getting Your Add-ons ready for PyroCMS 2 by Osvaldo Brignoni http://blog.adamfairholm.com/getting-your-add-ons-ready-for-pyrocms-2/comment-page-1/#comment-529 Osvaldo Brignoni Fri, 11 Nov 2011 03:10:00 +0000 http://blog.adamfairholm.com/?p=195#comment-529 Hello Adam, I'm updating the the Flash widget and had problem with how the Workless theme is styling select elements by default. Anywhere you use form_dropdown() without the filter fieldset tags the select elements are hidden. The css inspector shows... select {    min-width: 260px;    visibility: hidden;}the css selector should be more specific like .filter select {} and not hiding all select elements.I could not get the filter to work with the Flash widget. I figured is not essential to use the filter. Y overrode the css with visibility:visible to show the plain select element for now.You should check if this affects widgets in general.Another problem with the Widgets admin is that the code text is styled with white color and is hardly readable...Other than that Pyrocms 2.0 is looking awesome and i know you took part in that. I'll be developing a new simple plugin that i'll be revealing soon...Hey, and kudos for helping me learn some PHP/CI back then... Hello Adam, I’m updating the the Flash widget and had problem with how the Workless theme is styling select elements by default. Anywhere you use form_dropdown() without the filter fieldset tags the select elements are hidden. The css inspector shows…

select {    min-width: 260px;    visibility: hidden;}the css selector should be more specific like .filter select {} and not hiding all select elements.I could not get the filter to work with the Flash widget. I figured is not essential to use the filter. Y overrode the css with visibility:visible to show the plain select element for now.You should check if this affects widgets in general.Another problem with the Widgets admin is that the code text is styled with white color and is hardly readable…Other than that Pyrocms 2.0 is looking awesome and i know you took part in that. I’ll be developing a new simple plugin that i’ll be revealing soon…Hey, and kudos for helping me learn some PHP/CI back then…

]]> Comment on FuelPHP for CodeIgniter Developers by Oubliez CakePHP, Codeigniter, Symfony… voici FuelPHP | Trois Point Zéro - webdesign, développement et actualité autour du web par Grégory BABONAUX, concepteur web freelance http://blog.adamfairholm.com/fuelphp-for-codeigniter-developers/comment-page-1/#comment-528 Oubliez CakePHP, Codeigniter, Symfony… voici FuelPHP | Trois Point Zéro - webdesign, développement et actualité autour du web par Grégory BABONAUX, concepteur web freelance Tue, 01 Nov 2011 17:32:19 +0000 http://blog.adamfairholm.com/?p=104#comment-528 [...] Pour vous convaincre un peu plus : http://blog.adamfairholm.com/fuelphp-for-codeigniter-developers/ [...] [...] Pour vous convaincre un peu plus : http://blog.adamfairholm.com/fuelphp-for-codeigniter-developers/ [...]

]]> Comment on FuelPHP for CodeIgniter Developers by Adam Fairholm http://blog.adamfairholm.com/fuelphp-for-codeigniter-developers/comment-page-1/#comment-527 Adam Fairholm Thu, 20 Oct 2011 14:41:00 +0000 http://blog.adamfairholm.com/?p=104#comment-527 Thanks Travis! I appreciate it. I have no experience with Kohana, but I'd say that CI is not really coming from a corporate environment anymore - it's currently being pushed and pulled like nobody's business on GitHub. There are truly solid fantastic devs on both projects (some even work on both). So if you haven't seen it I'd recommend checking out the CI repo: https://github.com/EllisLab/CodeIgniter Thanks Travis! I appreciate it. I have no experience with Kohana, but I’d say that CI is not really coming from a corporate environment anymore – it’s currently being pushed and pulled like nobody’s business on GitHub. There are truly solid fantastic devs on both projects (some even work on both). So if you haven’t seen it I’d recommend checking out the CI repo: https://github.com/EllisLab/CodeIgniter

]]> Comment on FuelPHP for CodeIgniter Developers by Travis Watson http://blog.adamfairholm.com/fuelphp-for-codeigniter-developers/comment-page-1/#comment-526 Travis Watson Thu, 20 Oct 2011 13:43:00 +0000 http://blog.adamfairholm.com/?p=104#comment-526 Adam, this is a very well written article on the topic, and I appreciate your insight and wit.  I have a project I'm pursuing with colleagues that are all very open minded, but have a strict OO background in C#, and I'm looking for a good OO MVC framework to ease the boundary. I originally suggested CI, but both Kohana and FuelPHP are looking great.  My only hesitation at this point would be the development cycles.  CI comes from a corporate environment, so I think Ellis understands the importance of backwards compatibility persistence through security and performance updates. From your article, and some things I've seen 'round the tubes, Fuel seems to have a better foundation, better developers, more cohesion, and a firmer direction than Kohana. Adam, this is a very well written article on the topic, and I appreciate your insight and wit.  I have a project I’m pursuing with colleagues that are all very open minded, but have a strict OO background in C#, and I’m looking for a good OO MVC framework to ease the boundary.

I originally suggested CI, but both Kohana and FuelPHP are looking great.  My only hesitation at this point would be the development cycles.  CI comes from a corporate environment, so I think Ellis understands the importance of backwards compatibility persistence through security and performance updates.

From your article, and some things I’ve seen ’round the tubes, Fuel seems to have a better foundation, better developers, more cohesion, and a firmer direction than Kohana.

]]> Comment on Getting Your Add-ons ready for PyroCMS 2 by Adam Fairholm http://blog.adamfairholm.com/getting-your-add-ons-ready-for-pyrocms-2/comment-page-1/#comment-524 Adam Fairholm Tue, 18 Oct 2011 17:09:00 +0000 http://blog.adamfairholm.com/?p=195#comment-524 Hey Mark, I definitely agree with you that the hrs should go from the forms and be replaced with a simple border-bottom like you have there. I know Scott Parry is working on forms, so those should be gone in the final 2.0 version. For the special case, I think it comes down to personal preference. I like a lot of color in a UI, but I realize most listings just need to be plain. Blog posts are major pieces of content (unlike smaller chunks like variables), so that's why they've got the color buttons. I've also used it on PyroStreams to list streams (but not entries) since Streams are large datasets. So I suppose the real definition is use the colored buttons in a list where the data list is important, if that makes any sense. No piece of content is really more important when you think that one missing piece will break a site, but there are certain pieces of content that users spend a lot more time managing on the back end. Adam Hey Mark,

I definitely agree with you that the hrs should go from the forms and be replaced with a simple border-bottom like you have there. I know Scott Parry is working on forms, so those should be gone in the final 2.0 version.

For the special case, I think it comes down to personal preference. I like a lot of color in a UI, but I realize most listings just need to be plain. Blog posts are major pieces of content (unlike smaller chunks like variables), so that’s why they’ve got the color buttons.

I’ve also used it on PyroStreams to list streams (but not entries) since Streams are large datasets.

So I suppose the real definition is use the colored buttons in a list where the data list is important, if that makes any sense. No piece of content is really more important when you think that one missing piece will break a site, but there are certain pieces of content that users spend a lot more time managing on the back end.

Adam

]]> Comment on Getting Your Add-ons ready for PyroCMS 2 by Mark http://blog.adamfairholm.com/getting-your-add-ons-ready-for-pyrocms-2/comment-page-1/#comment-523 Mark Tue, 18 Oct 2011 09:33:00 +0000 http://blog.adamfairholm.com/?p=195#comment-523 Didn't realise hr tags were going to be rendered! Where there is a line it's meant to be a hr tag! Didn’t realise hr tags were going to be rendered! Where there is a line it’s meant to be a hr tag!

]]>