Anyone done that before?

public static $SmtpServer = 'localhost';

       /**
        * Port of the SMTP Service on the SmtpServer, usually 25
        *
        * @var integer SmtpPort
        */
       public static $SmtpPort = 25;

I assume I would need to change it in the core?  But what happens if I upgrade?  Is there a config file I could use instead?

So QCodo supports i18n (translation), but not l10n (formatting).

I am looking at the I18 support in QCODO and using that to Internationalize an application built using QCODO. I know internally QCODO uses that for localization support.

Zend looks great and may use it. Right now I am looking to see the pro's and cons of leveraging the QCODO I18N support for internationalization. Will it require extending whats already there within QCODO for I18N.

Appreciate any input. New to QCodo and figuring out how we can leverage it to the maximum.

It may also be a nicer approach to dynamically resize the QImageControl itself so that the ratio matches and no background is necessary.

In QImageControlBase, in RenderImage, after imagefilledrectangle is called (line 433 in my copy), you can call:
imagecolortransparent($objFinalImage, $clrBackground);

That's it. Now, any image you upload will have a transparent background.

Note that if your image contains the same color as the background, that portion of the image may be transparent as well. To avoid this, set your image control's BackColor property to something that doesn't show up in the image itself.

Having this behavior controlled by a boolean property of QImageControl would be a worthwhile addition to the framework, I think.

Cheers,
tronics

Thank you very much.

Note: This is very important to me

I receive the email with the <img /> code (I did view the source), but I literally can't see the image in my email client (using Gmail and Mac Mail).  When I send the same exact email (as shown in the example) via the PHP mail function and manually set my HTML headers, I'm able to see the image just fine in the same email client.

Are you able to send HTML formatted emails with Qcodo without an issue?  Something seems to be wrong with the headers or something.  For now, I'll just have to go with the PHP mail function.

Thanks for any help,
Chris

• Status changed from Fixed to Closed
• Resolution changed from none to Fixed

• Status changed from Fixed to Closed
• Resolution changed from none to Fixed

Great ! thank you !

Have you “view sourced” the email in your client to see if it is properly formatted HTML?

Lastly, remember that some email clients block image downloads from remote servers on email reads... have you ensured that this isn't the cause of the issue?

It looks like you and folks at qcubed have thought through some stuff as well, I'd love any input (either higher level suggestions or even lower level code contributions, if you have them) that you'd be willing to provide.

I know that you say for some of those items you need some “seed” ideas/input from me -- I think the best way to go about it (as is the best way I seem to be operating at the moment) is, are there specific questions you have about any of those items (e.g. roadmap, QPM vs. GitHub vs. whatever documentation, etc.) that can help you to understand it better... and then you could write or you could delegate someone to structure and write documentation (e.g. up in the wiki) in a format that is clear and makes sense to the average user?

let me know if that makes sense...

Qcodo plays very nicely with ZF, and in fact, there is already a QPM package which allows you to one-line install ZF into your Qcodo application.

See http://www.qcodo.com/qpm/package.php/zend_framework for more info