I would like to propose a new feature which would add two new xml tags for profiles,
Using an image url could be open to abuse of tracking people's IP using your profiles, maybe this could be controlled by forcing people to use an imagehost (for example, imgur) which doesn't allow tracking on an individual level, or alternatively not allowing image downloading at all and only embedded images. On second thoughts, it would probably be best not to have this, at least initially. The other negative is people could get crazy with embedding large images and you would end up putting more pressure on your db with potentially large attachments - not a huge concern but something to keep in mind.
Ideas? Thoughts? Comments? If this isn't something the devs aren't willing to invest any time in I could probably whip up a quick plugin to override the load profile button (if they haven't restrained reflection) and the plugin button could also be the one used to show current profile image - also a good way to enable/disable this feature.
HTML:
<image></image> and <imagedata></imagedata>- Both tags would obviously be optional.
- image takes either a direct url to an image (not a web page/html, this is too open to abuse) or a string 'data'
- if image is data, the imagedata tag must be provided and contains base64 encoded image data (or something easy to have in text)
- If present, the image should be displayed in the openfiledialog when loading a new profile using the ofd HookProc to add a panel with an image/picturebox and when a new xml file is highlighted, read the profile and load+display any image
- Maybe a checkbox in the OpenFileDialog to enable/disable image preview
- Once a profile is loaded, maybe a small button to display the image of the loaded profile
- Images loaded from a url should be cached somehow, and maybe clear the cache on a fresh load of HB (ie, no other HB copies open)
- When clicking on the preview, launch a browser to that image?
Using an image url could be open to abuse of tracking people's IP using your profiles, maybe this could be controlled by forcing people to use an imagehost (for example, imgur) which doesn't allow tracking on an individual level, or alternatively not allowing image downloading at all and only embedded images. On second thoughts, it would probably be best not to have this, at least initially. The other negative is people could get crazy with embedding large images and you would end up putting more pressure on your db with potentially large attachments - not a huge concern but something to keep in mind.
Ideas? Thoughts? Comments? If this isn't something the devs aren't willing to invest any time in I could probably whip up a quick plugin to override the load profile button (if they haven't restrained reflection) and the plugin button could also be the one used to show current profile image - also a good way to enable/disable this feature.
