Skip to main content
This topic has been closed for replies.

1 reply

BenPleysier
Community Expert
BenPleysierCommunity Expert
Community Expert
June 28, 2018

I have been using all of the lastest versions of WebAssist's extensions using MySQLi, specifically when I have had occasion to use eCart. It brings back memories of the golden past when Dreamweaver was at its height with the inclusion of the server behaviours panels. Ray has also been very helpful when I have had to use different payment gateways, sometimes spending 4 hours and charging for one. All in all, thumbs up.

Having said that, I have fallen in love with client-side processing of data. It allows for very fast data manipulation without having to traffic back and forth to the server. An added feature is that page refresh is a thing of the past. In this regard, large database tables of more than 3K records are better processed on the server-side.

I guess that in the end it's all a matter of taste.

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
    O
    osgood_
    Legend
    June 28, 2018

    Not sure why a page refresh should be a thing of the past, its still relevant if you're processing a product details page, which uses a different page template. On the other hand if your processing some kind of form data or simple search app using client side processing is a smoother experience. I think its more a question of where to use which one rather than one being a better solution than the other.

    Impressive_play01AC
    Impressive_play01ACAuthor
    Inspiring
    June 29, 2018

    Hello!

    I agree with Michele that it is good news. Using dreamweaver CC Next together with the webassist beta again we have an updated product.

    Currently it is the combination I am using to build very complex websites, backends, and intranets.

    I have to say that from the Mysqli extension although the updates have been scarcer have been, in my opinion, very accurate, with an updated code simple and easy to handle and updating just the modules (like ckeditor and its file manager or phpmailer) that were necessary.

    I'm very interested in Ben's opinion about the use of Dmxzone (Since I've seen that you have experience with him). I am sure that I will acquire the webassist extension as soon as it goes on sale. I have become accustomed to the system of templates, to the use of plugins with framework builder, and to the code that it generates (now very simple and elegant to edit it by hand) and it would be impossible for me to live without it.

    I am not so clear whether to acquire or not a subscription to wrappler as a complement. Whenever I bought dmxzone extensions in the end I ended up never using them. Now more than ever they are products that can be complementary, and not exclusive.

    PROS WEBASSIST:

    - Simple and easy to read, understand and edit code.

    - Very friendly for SEO and construction of frontends.

    - When i have to build complex intranets, helping me with code by hand. It is very easy to combine the extension of webassit with code by hand.

    - The system of templates and pluging. I am simply in love with him.

    AGAINST WEBASSIST:

    - It is also a dreamweaver counter. The ajax capacities are few and simple. In the end I ended up programming in ajax by hand, which I have gotten used to using jquery, but it would not be any extra capacity. (The only functionality that you have to load plugins in divs).

    - It works within dreamweaver, and for me it is a counter because Adobe has it very forgotten. Every time you have to update something because this obsolete Adobe simply deletes it. It is not also an agile program in terms of speed. This together with the elimination of fireworks means that if it were not for webassist, it would be out of the Adobe ecosystem.

    PROS DMXZONE

    - Very innovative, and excellent ajax capabilities.

    - They certainly have components for many things. With a subscription you now have a good "arsenal" of components.

    AGAINST DMXZONE:

    - I am worried about the SEO issue regarding the construction of the frontend. I mean, I know that Google is able to read the javascript code, but the same site built with Wrappler would compete in Google on an equal footing with that same site in Dreamweaver? It's something that disturbs me.

    - Hand code. As I have said many times I have to build intranets that can be complex. It is common to find actions that can not be performed with extensions. It is easy to write code by hand with dreamweaver and webassist. With the dmxzone framework, I feel completely lost. This is something I wanted to ask Ben since he has more experience. Is it possible once you learn to use it to combine it with programming by hand?

    Thanks greetings!


    As you said, Ben is most qualified person here to answer about your questions.

    For me, server-side solutions give me a feeling of greater security... to understand what I mean see this post:

    https://community.wappler.io/t/hide-secure-data-connection/1412

    It's easy for those who are at first to commit serious data management errors.

    Another "little" problem is that the DMXzone's client-side solutions are proprietary (I mean the framework), which means that if they close, your business is over (e.g. remember InterAKT with PHAkt).

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices