Share this blog
- Morfik Discussion Forums rules and guidelines
- MDA Release: The FacebookLike Package
- MDA Release: The Rating Package
- MDA Release: The HTML5 Video Package
- MDA Release: The Accordion Package
- April 2011 (1)
- January 2011 (4)
- December 2010 (2)
- November 2010 (3)
- October 2010 (5)
- September 2010 (3)
- August 2010 (4)
- July 2010 (5)
- June 2010 (4)
- May 2010 (5)
- April 2010 (4)
- March 2010 (9)
- February 2010 (17)
- January 2010 (19)
Archive for March, 2010
The Amazon Ads Package is designed to display Amazon Product Links and Banners on Morfik-built websites.
Place the widget on the form, then visit Amazon Associates Central website, select the banner or link you want to show on your website, copy the text generated by Amazon, and paste it into the HTMLCode property of a widget. That’s it—you can now run your project and see the ads being displayed.
Recently a developer on our blog site made the following comment: "I’ve been watching and trialing Morfik for about a year now. I still can’t use it because of one simple thing. You haven’t created a properly functioning, bug free, good user experience continuous editable form."
Well, I am about to share with you something that will completely change that!
In Morfik 3 the implementation of Continuous Editable Forms is dramatically enhanced. In fact it will have features of both Continuous and Single Forms; content will be displayed like Continuous Forms but will have the editing capabilities of Single Forms! The best way to get a feel for the improvements in performance and usability is to have a look at the following Continuous Editable Forms demo:
Any new and revolutionary technology will face the dilemma of supply and demand prerequisites for third party support. Generally, third parties will wait until demand for a service reaches a level that ensures profitability before providing such a service. Web hosting is no exception to this rule and Morfik has specifically developed its deployment technology with this in mind.
In search of the ultimate navigation system for Morfik web applications we have come to the realization that just mimicking desktop-like menus on the web is not going to work. The use of desktop-like menus on the web has largely been criticized for its lack of usability, accessibility and scalability. Despite the criticism, desktop-like menus have been high on the list of most requested features for a long time. However, I feel there are merits to the criticism leveled against them that need addressing in order for a successful adaptation of these menus on the Web.
I am very passionate about this feature of Morfik software, but sometimes I wonder if other people can see the benefits too.
The reason I appreciate this feature more than others is that for a long time I used to deploy and update Morfik applications manually. At that stage, we did not have the auto-deployment feature—and it was a real pain. It’s not that Morfik web applications (XApps) were particularly hard to deploy, but this was a general problem when deploying web applications—especially when they needed to use a back-end database.
Nowadays, the deployment process has become so trivial using Morfik software that all the Morfik team deploy their XApps directly from the environment they work in (Morfik IDE) without any knowledge of the back-end or even which files and resources the project needs. They don’t even ask a question about this anymore!
It's been a busy week for the MDA team. We’ve produced four new Packages to help you build high-quality web applications in record time, and we have prepared another five Sample Projects to highlight some of the best features of Morfik. All sample projects are free to download and come with full source code.
First, let's take a look at the new packages we have for you.
This is the second part of the preview of Internationalization Support, and today we are going to take a look at database localization.
Localizing database-driven content is not an easy task, and there is not much choice when it comes to approaches that can be taken. Consider the simple Blog application which uses a very basic table with only two fields: PostDate and Content.
Let’s quickly go through the existing methods of localizing that table: