Very Important Suggestions

QAAF Tech
10 Posts
QAAF Tech posted this 16 October 2016

I've few suggestions which are actually very important for end users and overall functionality of Themler itself.

  1. When themler asks for upgrade (beta or stable) it only gives an option for Backup and Upgrade. There should be another option for Upgrade only. Because when user creates a blank theme in themler, it asks for upgrade and untitled theme is the one that is being updated while user have committed no changes to that untitled theme, therefore it is useless to backup that theme.

  2. At this moment current stable version available for desktop is v319. while stable version for upgrade is v349. and here comes the interesting part beta version for upgrade is v352, so if i upgrade a blank theme from v319 to v349 and then it gives me option to upgrade again for beta update and I opt in. now it creates 02 backups of theme, which was not even touched. Therefore, while upgrading, Themler should give us the option to upgrade to latest stable release or latest beta release. It will save time and issues relating to multiple upgradation process.

  3. Themler wordpress and other CMS based development structure has a major flaw which needs to be addressed at highest priority. Let me explain it with a practical example.

    • Let's say I create a theme in Themler for Wordpress and this is my first ever theme.
    • Now if i want to create another theme, Themler gives me the CMS data of previous theme which is only good if my theme is relating to previous type of business. But if my previous theme was about a medical institute and my next theme is about a resturant, how would it fit in?

    • What should be done then? When user creates very first wordpress theme, themler should ask for few options like

      • Create a Theme from scratch (if yes, then themler should install separate wordpress under the new proejct name, which is definitely provided by the user)

      • Clone a Theme Without Data (it means user want to modify the previously created theme but wants to use new data, in this case another worpdress installation will be done under the newly created project name)

      • Create a theme with previous data (it is the case which is currently working in themler, but it can be enhanced like you give us the option which project data we want to use in our new project/theme)

  4. Instead of just creating a theme, we should be able to create a themler project (any cms), Themler will create a folder named as that project and in it Themler will install chosen CMS along with other details i.e. Project Name, Database Name, Admin, Email, Password and theme name etc. These database should be select able if someone wants to use those databases with new themes (current case)

  5. When We download images/sections from billion digital network, these sections/images should be downloaded to Themler desktop main directory (local library instead of online library), so in future we don't have to download each type of images/sections again and again. This will drastically improve Themler performance and will also lessen the load on Themler servers.

  6. Upon each change, and let me say upon selecting and modifying any control properties themler goes online and comes back after verification, which is totally ridiculous and is the main reason of slowness of Themler. I've practically tested that when i am working on Themler desktop, and only doing changes in a theme (means designing) and my net signals goes down, it gives me Retry Blue Button, which never goes off untill i am connected back. It should not be the case, it should give me errors only when i am going to save or export the theme (like Artisteer). You should check for valid license upon launching of Themler, Saving and Exporting of themes and remove the checks while modifying/designing themes/contents. if you implement this, 99% of your users will be happy.

  7. Add a global setting to Themler which will then be applied to all Themler sub sections i.e. for html, wordpress, joomla etc.
    In these global settings let user fill in and opt in what they want and then apply these to themlers. i.e.
    Let user type his/her name for Author/Web Developer, let user opt in to show backword links of turn them off.
    These settings will also be available to all mini-themlers as they are now available, for changing per theme/project base (if required)

  8. In suggest background, also add the color pickers/color choices (currently available in design tab)

  9. In layout tab, add the layouts as they were in Artisteer, instead of showing widths, these widths controls should be moved to Sheet Width tab/section.

  10. Generated code (CSS, JavaScript etc) are messy, kindly remove the unnecessary code when user exports. It will make themes loading time faster. i.e. in a simple wordpress theme, remove code/settings for woocommerce.

  11. After finalizing a theme online, add an option to remove themler core so end user (client) may not get confused. for example. I've created a wordpress theme, uploaded it and finalized it on client's website and handed over all passwords to client. Now client see edit in themler, run themler options. upon clicking these links, themler loads and client modifies theme but can't save because themler asks for email and password, which i can't share with the client. so it would be better to remove themler after finalizing (option but very handy feature)

  12. Add a basic theme customizer for end users (clients) so they can edit basic settings i.e. font styles, font sizes, some background colors, images of their own choice without the need of Themler.

Thank for reading.

I've few suggestions which are actually very important for end users and overall functionality of Themler itself. 1. When themler asks for upgrade (beta or stable) it only gives an option for Backup and Upgrade. There should be another option for Upgrade only. Because when user creates a blank theme in themler, it asks for upgrade and untitled theme is the one that is being updated while user have committed no changes to that untitled theme, therefore it is useless to backup that theme. 2. At this moment current stable version available for desktop is v319. while stable version for upgrade is v349. and here comes the interesting part beta version for upgrade is v352, so if i upgrade a blank theme from v319 to v349 and then it gives me option to upgrade again for beta update and I opt in. now it creates 02 backups of theme, which was not even touched. Therefore, while upgrading, Themler should give us the option to upgrade to latest stable release or latest beta release. It will save time and issues relating to multiple upgradation process. 3. Themler wordpress and other CMS based development structure has a major flaw which needs to be addressed at highest priority. Let me explain it with a practical example. - Let's say I create a theme in Themler for Wordpress and this is my first ever theme. - Now if i want to create another theme, Themler gives me the CMS data of previous theme which is only good if my theme is relating to previous type of business. But if my previous theme was about a medical institute and my next theme is about a resturant, how would it fit in? - What should be done then? When user creates very first wordpress theme, themler should ask for few options like * Create a Theme from scratch (if yes, then themler should install separate wordpress under the new proejct name, which is definitely provided by the user) * Clone a Theme Without Data (it means user want to modify the previously created theme but wants to use new data, in this case another worpdress installation will be done under the newly created project name) * Create a theme with previous data (it is the case which is currently working in themler, but it can be enhanced like you give us the option which project data we want to use in our new project/theme) 4. Instead of just creating a theme, we should be able to create a themler project (any cms), Themler will create a folder named as that project and in it Themler will install chosen CMS along with other details i.e. Project Name, Database Name, Admin, Email, Password and theme name etc. These database should be select able if someone wants to use those databases with new themes (current case) 5. When We download images/sections from billion digital network, these sections/images should be downloaded to Themler desktop main directory (local library instead of online library), so in future we don't have to download each type of images/sections again and again. This will drastically improve Themler performance and will also lessen the load on Themler servers. 6. Upon each change, and let me say upon selecting and modifying any control properties themler goes online and comes back after verification, which is totally ridiculous and is the main reason of slowness of Themler. I've practically tested that when i am working on Themler desktop, and only doing changes in a theme (means designing) and my net signals goes down, it gives me Retry Blue Button, which never goes off untill i am connected back. It should not be the case, it should give me errors only when i am going to save or export the theme (like Artisteer). You should check for valid license upon launching of Themler, Saving and Exporting of themes and remove the checks while modifying/designing themes/contents. if you implement this, 99% of your users will be happy. 7. Add a global setting to Themler which will then be applied to all Themler sub sections i.e. for html, wordpress, joomla etc. In these global settings let user fill in and opt in what they want and then apply these to themlers. i.e. Let user type his/her name for Author/Web Developer, let user opt in to show backword links of turn them off. These settings will also be available to all mini-themlers as they are now available, for changing per theme/project base (if required) 8. In suggest background, also add the color pickers/color choices (currently available in design tab) 9. In layout tab, add the layouts as they were in Artisteer, instead of showing widths, these widths controls should be moved to Sheet Width tab/section. 10. Generated code (CSS, JavaScript etc) are messy, kindly remove the unnecessary code when user exports. It will make themes loading time faster. i.e. in a simple wordpress theme, remove code/settings for woocommerce. 11. After finalizing a theme online, add an option to remove themler core so end user (client) may not get confused. for example. I've created a wordpress theme, uploaded it and finalized it on client's website and handed over all passwords to client. Now client see edit in themler, run themler options. upon clicking these links, themler loads and client modifies theme but can't save because themler asks for email and password, which i can't share with the client. so it would be better to remove themler after finalizing (option but very handy feature) 12. Add a basic theme customizer for end users (clients) so they can edit basic settings i.e. font styles, font sizes, some background colors, images of their own choice without the need of Themler. Thank for reading.

Last edited 16 October 2016 by QAAF Tech

Vote to pay developers attention to this features or issue.
5 Comments
Order By: Standard | Newest
QAAF Tech
10 Posts
QAAF Tech posted this 17 October 2016

seems like nothing important in my post?

seems like nothing important in my post?
Linkebel
125 Posts
Linkebel posted this 03 November 2016

Hi,

it to look interesting but too long

Maybe make separate post for each suggestion

Hi, it to look interesting but too long Maybe make separate post for each suggestion
Support Team
Support Team posted this 08 November 2016

QAAF Tech,

We already added your suggestions to our wish list.
If you want to receive our comments for each request please let us know.

Thank you,
Themler team

**QAAF Tech**, We already added your suggestions to our wish list. If you want to receive our comments for each request please let us know. Thank you, Themler team
QAAF Tech
10 Posts
QAAF Tech posted this 08 November 2016

Dear Team
It sounds good that you have added those suggestions to wish-list.
If you keep us updated with the progress, that would be a healthy response and definitely we (the users) will assist you with our testing and valuable feedback for the improvement of Themler.

Dear Team It sounds good that you have added those suggestions to wish-list. If you keep us updated with the progress, that would be a healthy response and definitely we (the users) will assist you with our testing and valuable feedback for the improvement of Themler.
QAAF Tech
10 Posts
QAAF Tech posted this 09 January 2017

Dear Team

It's been two months and no update/comments from your side.
Can you please spare some time to share updates/progress/road map?

Further I've two other suggestions. (which are quite easy to implement)

  1. When we insert image control, it shows a grey image icon/thumbnail by default, which is fine. But the problem is, that thumbnail/icon is loaded from your server (http://cstatic.billiondigital.com/themler/354/images/defaultImage.jpg).

Now let's suppose.
If 10,000 users are using themler (online/desktop) at the same time, and also suppose that 10,000+ websites developed with themler are online, it means that image is being served to at least 20,000+ times from your server.

  1. When we insert separator, in separator's short code the above link is also inserted, which doesn't make any sense to me, because if i remove that link from separator's short code, nothing happens, means no visual changes etc.
    If you apply above assumption, then above image is being called 20,000+ times in browser (though not visible on page, but being loaded in background).

If you solve these issues, I'm sure you may lessen load on your servers and it can have impact on overall performance of Themler and its generated code.

Regards
Qaiser Ikram

Dear Team It's been two months and no update/comments from your side. Can you please spare some time to share updates/progress/road map? Further I've two other suggestions. (which are quite easy to implement) 1. When we insert image control, it shows a grey image icon/thumbnail by default, which is fine. But the problem is, that thumbnail/icon is loaded from your server (http://cstatic.billiondigital.com/themler/354/images/defaultImage.jpg). Now let's suppose. If 10,000 users are using themler (online/desktop) at the same time, and also suppose that 10,000+ websites developed with themler are online, it means that image is being served to at least 20,000+ times from your server. 2. When we insert separator, in separator's short code the above link is also inserted, which doesn't make any sense to me, because if i remove that link from separator's short code, nothing happens, means no visual changes etc. If you apply above assumption, then above image is being called 20,000+ times in browser (though not visible on page, but being loaded in background). If you solve these issues, I'm sure you may lessen load on your servers and it can have impact on overall performance of Themler and its generated code. Regards Qaiser Ikram
You must log in or register to leave comments