Extreme expectations – avoiding frustration

I had an interesting chat with a fellow developer who was frustrated because he had to do a lot of programming work, in order to create a business application with Morfik. At first I was a bit puzzled, but as we continued to discuss this issue, I started to understand why he was so frustrated.

Morfik AppsBuilder 2.0 has a very slick look. It allows you to do some amazing things, very quickly, with its built-in control effects, thus making it really easy for you to create an impressive looking website quite quickly. This has a side effect. People that start to work with Morfik AppsBuilder (be it FX or BX) start to believe that whatever they want to do, it will always be possible to do it visually and easily. Well, that is not really true.

The fact that AppsBuilder gives you a compiler and an IDE, and not just a framework makes it possible for you to implement pretty much anything with it, but not everything you might want or need is ready built for you. Many times, speacially in areas which are more directly related to your business, you will need to engage in some serious programing and not just screen/page design.

Sure, Morfik’s visually oriented design environment and RAD qualities will help non-experienced programmers to create web applications. They will, also, allow experienced developers to create sloppy applications due to their ease of use. This is a temptation that should be resisted, at all costs. It is fine to try to do as much visually as possible, for prototyping, for example, where you are not sure if you are going to keep what you are designing and need to get the prototype out quickly,

It is essential, on starting a new and serious Morfik project, to consider good programming practices and design and plan for it from the start. As with all development tools, when building complex systems, good design and architecture is much more important then the tool itself.

Morfik is a RAD, high productivity tool, but that doesn’t mean that you will not be putting in some quility programming time when building a new system. What it does mean, we all hope, is that the tool will be continuously evolving and offering new ways to help you design the best pages and create the best quality code, with the least effort.

If you are new to Morfik and just about to begin your first project, set your expectations to a realistic level. Remember, your application is only going to be as good as you make it.

This entry was posted in Architecture, M2, Visual Design. Bookmark the permalink.

4 Responses to Extreme expectations – avoiding frustration

  1. mocte says:


    I thought you were talking about me ;-)

    But setting apart application architecture and best practices, the morfik marketing makes you think that way too, for example, I still can’t find a way to link 2 comboboxes, let’s say Country and States, I want to refresh the States combobox when the selection of country has been changed, in Delphi I had each combo linked to one query and in the OnChange event of the country combo I can do a refresh on the States query and that’s all. Do you know how can I re-populate the second (states) combobobox in a Morfik form? This task should be very trivial and easy but I wasn’t able to find any sample on this. Do you have any sample? I will be very grateful if you can send something.

    Best regards,

    P.S. You were right it was very easy to delete a record in a single data form.

  2. Mauricio Longo says:

    I wasn’t talking about you. :-)

    I’m pretty sure that Morfik itself has an example of how to do this. Drop a line to Shah and ask him if he doesn’t a sample of this.

  3. mocte says:

    Thank you Mauricio,

    I posted the issue on the forum, in fact he gave a solution but doesn’t fit my needs, I think that may be you have been there and had a better answer or a sample


  4. mocte says:

    Never mind,

    I have received a sample from Shah :-D

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>