in reply to Using Win32::GUI::BitmapInline?

This is a really bad idea for several reasons, not least of which is that if you wish to change the design of your buttons you are forced to release new code.

Why do you want to embed images in your code in this way?

Replies are listed 'Best First'.
Re^2: Using Win32::GUI::BitmapInline?
by InfiniteSilence (Curate) on Sep 13, 2005 at 16:08 UTC
    I am not sure this is such a bad idea for two reasons:

  • Software is commonly released with 'resource files' that contain all of the images, sounds, language/locale specific information for the given client that is needed. If you release your code in a modular fashion you can simply send them an 'update' to give them new resource files
  • Images are embedded in e-mail now all of the time. Consider Base 64 Encode/Decode with OpenSSL for instance.

    Celebrate Intellectual Diversity

[reply]

      • The OP didn't mention a resource file, with which I have no problem, he directly referred to embedding images in code, which is an entirely different kettle of wax.
      • What does embedding images in email have to do with embedding images in code?

[reply]
        What does embedding images in email have to do with embedding images in code?

        Embedding an image in e-mail and code basically utilize the same idea. Think __DATA__ segment.

        Celebrate Intellectual Diversity

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom