Blogs : Latest entries
|
|
|
This has mainly been a release with bug-fixes and minor convenience changes. Thanks to the great feedback we've received from users on the previous release, we're confident that the 1.0 mark has almost been reached. Since there were still a couple of new features added, we're first releasing this interim release candidate. Below are the highlights of this release. You can also read the full changelog for more details. Full declaration of elements in the site structureIn prior versions you were forced to declare each element in a separate file if you chose to use XML for the definition of your site structure. The XML site structure now supports all the element declaration statements in-line. So if it doesn't make sense for you to have re-usable declarations, you can just centralize everything in one file. For example, this is the new Hello World site structure: <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE site SYSTEM "/dtd/site.dtd">
<site>
<element id="HELLOWORLD" implementation="tutorial.helloworld.HelloWorld" url="/home"/>
</site>New asynchronous mail queueWe've extracted the mail queue from our Bamboo forums project and ported it to all the databases that RIFE supports. This allows you to
create mails with simple POJOs and just put them into the queue. At
regular intervals, the queue will process them and send them. To be able
to use the mail queue, you need to have the The queue is stored in a database and you install the structure as follows: DatabaseMailQueueFactory.getInstance(datasource).install(); To
make the queue run at regular intervals, you have to activate the RIFE's
scheduler. It's the easiest to use the in-memory scheduler. You do this by
adding the following line to your <participant param="rep/scheduler.xml">ParticipantMemoryScheduler</participant> The
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE scheduler SYSTEM "/dtd/scheduler.dtd">
<scheduler>
<task classname="com.uwyn.rife.mail.executors.DatabaseMailQueueExecutor" frequency="*/3 * * * *">
<option name="datasource">postgresql</option>
<option name="smtp_server">localhost</option>
</task>
</scheduler>The format of the To send a mail all you have to do is this, for example: DatabaseMailQueueFactory.getInstance(datasource).queue(new Email()
.to("customer@theircompany.com")
.from("info@yourcompany.com")
.cc("billing@yourcompany.com")
.bcc("themanager@yourcompany.com")
.subject("this is the subject")
.body("and the body of the mail")); |
|
I just stumbled into PhotoBlox.
It is an image viewing application that can be embedded into a personal blog template or Web page. It totally relies on Flash's multi-media capabilities and Laszlo's ease to dynamically fetch external data and display it. The application loads fast, works in almost every browser and looks great in multiple sizes. For applications like this, none of the other RIA solutions that I know would fit the bill. Well, maybe Flex would, but I doubt that anyone would pay at least 14400 € in licensing to be able to run a photo blogging tool |
|
A new version of Laszlo has just been released.
It contains a number of important feature additions that make the platform a lot more viable (compared against 2.2.1):
The detailed release notes are here and here. I tried it out with an application that I developed for version 2.2.1, and I found a number of problems:
I have to say that I'm impressed by the dedication of the Laszlo people. After my previous posts, I got contacted directly by Adam Wolff, the director or Laszlo Systems. He's really devoted to try finding out how to reduce the gripes people have with Laszlo and to lower the adoption barrier. Also, I managed to get hold of a 3.0b2 version early by peeking around where I was not supposed to look and I mailed him about the problems I encountered. He immediately forwarded my mail to three developers, asking to investigate! It's good to see that they are so actively and dynamically supporting users. |


