This article shows how a web application can easily be transformed into a native application. It uses the Internet Explorer, which is not among the best browsers, but often satisfying. In some aspects it’s probably even the best choice.
The article also contains download links to a tool that easily allows you to create standalone applications containing any HTML5 content as internal resource.
Continue reading
We have done some improvements with v2.1, and we’ve collected these in a new hotfix release.
You can download the installer here:
For other information about other releases, take a look in the release history.
—
Sincerely,
The Smart Mobile Studio Team
We are proud to release Smart Mobile Studio 2.1.
You can download the installer here:
A valid license key (trial or subscription) is required.
NOTE: Since v2.0 isn’t forward compatible, you can’t open v2.1 projects in v2.0. Make sure to always backup your projects case you want to revert to v2.0.
—
Sincerely,
The Smart Mobile Studio Team
This version is actually more like a “release candidate” than a “beta”.
There’s only one issue left, and that’s related to RTTI.
If we mange to fix this issue within the next few days, then we will include that fix in the final release. If not, we’ll postpone the RTTI to the first hotfix and release this version as is.
If you would like to give this a try, you can download the installer here:
A valid license key (trial or subscription) is required.
NOTE: Since v2.0 isn’t forward compatible, you can’t open v2.1 projects in v2.0. Make sure to always backup your projects case you want to revert to v2.0 again.
—
Sincerely,
The Smart Mobile Studio Team
We have received lots of useful feedback from the first beta.
We have addressed most of these, but there are a few more issues we want to implement before the final release. Thus a second beta.
If you would like to give this a try, you can download the installer here:
A valid license key (trial or subscription) is required.
NOTE: Since v2.0 isn’t forward compatible, you can’t open v2.1 projects in v2.0 anymore. Make sure to always backup your projects case you want to revert to v2.0 again.
—
Sincerely,
The Smart Mobile Studio Team
Recently there was a question about how to host Smart project on a dedicated small server to provide access in a sort of a kiosk application way. At the moment there are dozens of examples available as also shown in the Node.js on a RaspberryPi post . In contrast to microcontroller boards, this post will feature an overview over small boards, which are perfect to deliver your Smart application to a small group of clients.
Version 2.1 of Smart Mobile Studio will soon be released.
If you would like to give this a try, you can download the installer here:
A valid license key (trial or subscription) is required.
NOTE: Since v2.0 isn’t forward compatible, you can’t open v2.1 projects in v2.0 anymore. Make sure to always backup your projects case you want to revert to v2.0 again.
—
Sincerely,
The Smart Mobile Studio Team
The next version of Smart Mobile Studio (v2.1) is right around the corner.
We do, however, need a bit more time than first anticipated on testing and quality assurance for this release.
Thus we decided to release another hotfix for v2.0 to support the users who needs these fixes.
You can download Smart Mobile Studio 2.0.2 from the downloads section, which includes this ‘hotfix 2’.
You can download Smart Mobile Studio 2.0.2 from the downloads section.
—
Sincerely,
The Smart Mobile Studio Team
Since version 2.0 there are four different editions available. By knowing what each of these edition offers you can pick what fits the best for your needs to only pay what you need.
Continue reading
While we are hard working on the next release of Smart Mobile Studio (few hints: docking, debugging, HTML projects) we also want to support existing 2.0 users. We have fixed bugs that were reported since version 2.0 and even added few improvements which didn’t make it into the original release.
You can download Smart Mobile Studio 2.0.1 from the downloads section.
You can download Smart Mobile Studio 2.0.1 from the downloads section.
—
Sincerely,
The Smart Mobile Studio Team
We are very proud to release Smart Mobile Studio 2.0!
With version 2.0 a new visual designer is available that finally offers support for event handling right from the designer. Also a package manager allows to extend Smart Mobile Studio with 3rd party components (new chart and grid components are already shipped as packages).
To increase our market we have not only created 4 different editions (see below) tailored around the most popular demands, but also included a new command-line compiler, which is free of any charge! This allows building your projects on non-licensed machines (such as build servers).
Beside this, dozens of smaller changes has been made since the last release. A full change log can be found below.
Oh, this is really a great release 🙂
Continue reading
With the Raspberry Pi a low cost computer is available that can be used for a great variety of different purposes. The credit-card-sized single-board computer is capable to run Linux, which is available in form of different, custom tailored distributions. Most of them can be extended easily to run node.js, which was presented in-depth in the recent posts.
This article will shed a light on how to install node.js on a Raspberry Pi. It will present some nice ideas about how to get the best out of your Raspberry Pi (& alike). Last but not least the article concludes with some benchmarks to show some limits.
We have received lots of useful feedback from the first beta version of v.2.0. Though, there were more issues than expected, which is why we decided to add another beta version that fixes several critical issues. The current beta should now work quite smooth, despite several minor issues that need some fixing until we have a final release (see ‘Known Issues’).
With the new beta version, we also updated the license system, which means that new license files are required. For testing/demoing a beta license is included in the installer. Keep this in mind when you try to run the beta with your old license file (will not work) and use the license file provided by the installer.
The beta is open for everyone, so no registration is required to demo our product.
For a full list of changes for Version 2.0, please see the dedicated post “What’s new in Smart Mobile Studio 2.0”
In addition to that here’s a changelog from the previous beta version.
Download the beta 2 installer [89 MB].
—
Sincerely,
The Smart Mobile Studio Team
With version 2.0 we have spent some precious development time into a new package manager. Similar to other solutions it allows to separate components into packages that can be independently installed in the IDE. Although there is no imminent need for it right now, it opens the IDE for 3rd party and user components that can be integrated into the RAD environment easily.
While there is still some work ahead to iron out some teething problems in the upcoming beta version, it is already used in combination with the new visual designer and its basic set of components, called the “Smart Component Library” (SCL). In addition to the basic set of components, two additional 3rd party packages are shipped with the product TeeChart.spk (by Steema Software) and Grid.spk (by Berg Software). The packages are built to integrate neat-less into the IDE’s component palette.
Furthermore we added an example package called W3Slider.spk with embedded source code. It is designed according to the all-in-one-file approach, that can also be used for the project. With packages designed like this, installation can be as easy as dropping the spk file to the ‘Packages’ folder. In the future we will also add support for encrypted package source code, so that it is possible to build closed source packages.
While the amount of changes (compared to Version 1.x) in this regards seem to be very little, it meant infact to rewrite the entire chain of handling components (in the component palette, visual designer & property inspector) from scratch. Previously all components were “hard coded” in Delphi, which means for every new component we added, we needed to update the component palette, add a dedicated Delphi component for the visual designer & property inspector, convert from Delphi to DWS at compile time and handle property storage in form file. All this code was convoluted in several manners and one couldn’t change one part without affecting other parts in the IDE.
Since we wanted to rewrite the visual designer, we had to rewrite the entire package system as well. Despite the fact that the development of version 2.0 took longer than expected, we now have a system that is perfectly decoupled in the aspects of package manager, visual designer, component palette, property inspector and form handling. It will allow us to maintain and improve each aspect separately. Also it will be possible for us in the future to switch to a JavaScript powered designer, which might allow you to create your layout on the destination device (e.g. iPhone) directly. This allows you to let a designer or even the management redesign the GUI remotely while you can focus on the code…
But let’s stick on what we have now, let’s stay on topic! The packages are basically in a similar XML format as your projects, which means you can – in case of emergencies – edit (and eventually fix) the packages at any time. This can be quite useful, since at the moment the GUI part of the package manager is limited to the essentials. For example it’s not possible at the moment to specify different categories for different components in one package. So far you may only specify one category per package, while the packages would allow an even more detailed specification of categories (per component). Also it’s not yet possible to change/specify icons for a component other than by editing the package files.
But of course you don’t need to know all the details if you only want to work with the packages, so let’s move on to the next chapter.
The installation of packages is very easy. All you need to do is to drop the package to the ‘Packages’ subdirectory.
Note that it might also be necessary to add glyphs for the component palette to the glyphs directory, but that depends whether the icons are specified internally or externally. At the moment a basic set of (external) glyphs is shipped with the product. We decided to make them available externally, so you can change them anytime to your favorite set of icons (the current icons are not always as clear as possible).
Once you have added/removed a package to the package subdirectory you have to restart the IDE in order to get the packages enumerated and listed in the component palette. If you have deleted a package, it will remain in the IDE’s cache until you restart the IDE.
After the packages have been installed, you can use the components in the same manner as you used the components in version 1.x.
This is a list of all changes since the last official release (1.1.2).