Introducing Morfik technical blogs

After a long development cycle and a series of maintenance releases, Morfik 2 has reached a level of stability and strength that has allowed us to look beyond the horizon ahead and consider new possibilities.

In line with our goal to have a greater level of engagement with the wider developer community in 2010 we have decided to use Morfik’s blog site (rather than our existing technical support forums) for communicating our ideas and plans for the product and its future development. Using this site, Morfik’s key developers will blog about the upcoming features and significant architectural changes that are necessary to support their implementation. From time to time we might preview new features through screenshots or live demos and invite you to comment and provide feedback to ensure we’re heading in the right direction. This should also make our blogs more interesting to read!

I would like to make a disclaimer right from the outset that previewing a feature on this site is not a commitment by Morfik to the inclusion of that feature in its future product upgrades. You should make your purchasing decision purely on the value proposition that is offered on the day and not any potential future feature. There are many factors that can result in the feature being modified in its final implementation or even being fully removed from future product upgrades. Another closely related issue is that any indication of timing, express or implied, is purely speculative and as such should not be used as a deciding factor in any purchasing or product development decision.

Morfik 2 in its current form represents the blueprint for the next generation of Rapid Application Development tools on the web. Within the constraints imposed by its long term design objectives, it already delivers a level of productivity that is currently unmatched on the web. While we are busy working on a number of tasks such as updating the documentation and enhancing our controls, we are looking ahead and making plans to significantly improve the productivity of the web developers in meeting the manifold challenges of modern day web applications.

In 2010 we will be making significant strides forward with a number of key development threads already in motion. You will see the outcome of these activities in terms of new product upgrades and a series of downloadable packages from our website.

Next week in our first tech blog we will be previewing our new Menu control!

3 Responses to “Introducing Morfik technical blogs”

May 29th, 2017
Carlos Ramirez says:

En la seccion tecnica creo que seria importante explicar en forma detallada y con codigo la forma de hacer cosas de progamacion, pero desde una forma basica a la mas elaborada. Por ejemplo: El usuario ingresa en la pantalla tres (3) datos codigo de Cliente, codigo de Producto, codigo de Proveedor el cual debe ser validado con las tablas Clientes, Productos, Vendedores, otros datos a validar son fecha de entrada, cantidad entrada sea mayor que cero, esto ayuda que los programadores encuentren la herramienta mas facil y se entusiamen con ella. Saludos desde Colombia suramerica

[Morfik]
Translated by Google translate:

In the technical section I think it would be important to explain in detail and with code how to do things Progamacion, but from a basic shape to the more elaborate. For example: The user enters the screen three (3) data client code, product code, vendor code which must be validated with the tables customers, products, vendors, other data are to validate entry, number entry is greater than zero, this helps programmers find the tool easier and is enthusiastic about it. Greetings from Colombia South America
[/Morfik]

get tips says:

ah at last, I found your article once again. You have few useful tips for my school project. Now, I won’t forget to bookmark it. 🙂

Darryl says:

Aram,
Thanks for starting the blogs. I look forward to many interesting and informative articles from you and the Morfik team.

Best wishes and a successful 2010 for Morfik.

Darryl

Leave a Reply

Fields marked by an asterisk (*) are required.