I need a module for, in the product description, the customer to choose and preview how a certain text (that the customer have typed in) is looking using diffrent fonts. (Its for vinyl stickers, wall art - texts).
Contact me if you can help me.
/I
Contact me if you can help me.
/I
Hello,
yes this should be possible...
Please send me more information via PM
Thanks
yes this should be possible...
Please send me more information via PM
Thanks
Hand Dryers
Bookstore Mod
QuickShop Module
Restricted Access - Compulsory Login
Template Override - Category Specific (vQmod)
Template Override - Brand Specific (vQmod)
How did you find out about us register question mod
Compulsory Login vQmod
Brands In Top Menu
zoom - Product Image - Auto on hover
Active Member
Hi
i can help you with the work. contact me on skype : webmeastro
Thanks
i can help you with the work. contact me on skype : webmeastro
Thanks
OpenCart Development partner and Solutions provider
www.Iweballey.com
skype : webmeastro
Hello- I too need an extension like this for OC V1.5.5.1 - is anything available?
My client sells lettered plaques and signs. Her customers need to see how their specific text will look before ordering.
Thanks I look forward to your reply.
Lisa
Sedona AZ
My client sells lettered plaques and signs. Her customers need to see how their specific text will look before ordering.
Thanks I look forward to your reply.
Lisa
Sedona AZ
Assuming you have the necessary libraries available on your server (usually not a problem), I can do this for you. Created similar utilities for Zen Cart a while back for a promotional products storefront. Send me a PM if you haven't already chosen someone.
Thank you..yes.. I did already have a couple bids. Now I am just waiting for the client to "go for it"- thanks again.
Having someone develop the thing is an obvious alternative to using what you already have at hand in front of you. One or more of the extensions in the store might do the trick, depending upon what is there at a given time.
You can replicate in its own page or frame an edit box to bring up ckeditor, force that instance to be in wysiwyg mode (most customers will have no idea what Source mode is all about), and then they can type text and choose fonts and whatnot. You can equip that with an incremental Save (of successive records in database) so that you can get back to each one, unless you could trust customers to submit the font name, size, etc, along with text, another way.
You can also separate a copy of ckeditor for that alone from ckeditor for OC itself.
You can replicate in its own page or frame an edit box to bring up ckeditor, force that instance to be in wysiwyg mode (most customers will have no idea what Source mode is all about), and then they can type text and choose fonts and whatnot. You can equip that with an incremental Save (of successive records in database) so that you can get back to each one, unless you could trust customers to submit the font name, size, etc, along with text, another way.
You can also separate a copy of ckeditor for that alone from ckeditor for OC itself.
Showing someone what their message will look like for decoration purposes, requires more than simply applying the style to a visual element. The purchaser usually will not have all the available fonts installed on their system. Furthermore, all fonts are not available for all operating systems. You can't just assume web-fonts will work in all situations 

To some extent no matter what you do you can't win.
Most fonts you see on the web are actually installed on your and other visitors' own machines. Code usually gives fallbacks, all the way to simply serif or non-serif so that the machines can find "something" that works. For the most part visitors will have no idea whether they are seeing a preferred or a fallback font, or a locally installed or a server called font.
If for customers' product choices you expect them to see fixed known fonts, then you will need to make those available via the server. Some fonts are called nowadays from Google. You can call your own, from your own tree. You will notice that stock ckeditor has very few font choices, all of which are currently installed on most machines. You would need to provide fonts that the software can call from the server.
You would also need to be able to use the same fonts in producing products. A Google or other called font or a given locally installed font may not be available for silkscreening or whatever (serious primary fonts are actually copyrighted and licensed). There are, of course, virtually look-alike fonts copycatted to circumvent those restrictions.
If you stick with the fonts that are prevalent in standardized file formats, then most customers will get by with that. If you supply the fonts, then there will still be some few customers whose operating systems or devices, big or little, cannot deal with the world as it is. Even in a given font format, such as truetype or the classic Adobe formats, there are versions of those -- early truetype won't run on current machines, current truetype won't run on Grandma's 95 machine. There are quite a few folks out there still using quite a few kinds of old machines and operating systems. Those machines or operating systems older than certain age cutoffs cannot even go on-line or cannot see more than 256 colors or cannot handle JavaScript or whatever. Their owners are not likely to spend much.
Most fonts you see on the web are actually installed on your and other visitors' own machines. Code usually gives fallbacks, all the way to simply serif or non-serif so that the machines can find "something" that works. For the most part visitors will have no idea whether they are seeing a preferred or a fallback font, or a locally installed or a server called font.
If for customers' product choices you expect them to see fixed known fonts, then you will need to make those available via the server. Some fonts are called nowadays from Google. You can call your own, from your own tree. You will notice that stock ckeditor has very few font choices, all of which are currently installed on most machines. You would need to provide fonts that the software can call from the server.
You would also need to be able to use the same fonts in producing products. A Google or other called font or a given locally installed font may not be available for silkscreening or whatever (serious primary fonts are actually copyrighted and licensed). There are, of course, virtually look-alike fonts copycatted to circumvent those restrictions.
If you stick with the fonts that are prevalent in standardized file formats, then most customers will get by with that. If you supply the fonts, then there will still be some few customers whose operating systems or devices, big or little, cannot deal with the world as it is. Even in a given font format, such as truetype or the classic Adobe formats, there are versions of those -- early truetype won't run on current machines, current truetype won't run on Grandma's 95 machine. There are quite a few folks out there still using quite a few kinds of old machines and operating systems. Those machines or operating systems older than certain age cutoffs cannot even go on-line or cannot see more than 256 colors or cannot handle JavaScript or whatever. Their owners are not likely to spend much.
Maybe it helps to have run a business in the past that had similar needs. No sense explaining how simple it really can be and why it speeds up the production process. The original poster is likely already aware of this 

Who is online
Users browsing this forum: paulfeakins and 5 guests