Right, in my eyes 4.2 was a major release with the SWF10 runtime
support. :-) I'm aware of the great improvements the platform has seen
in the past years. A bit of marketing would be good, though.

http://visualrinse.com/2011/01/25/what-flash-needs-to-remain-relevant-in-5-years/
" Laszlo‘s a bit of a fringe player (geeks love it, but your mom
doesn’t know Laszlo), but it is solid technology. Why doesn’t Adobe
have this capability?"

On Tue, Feb 1, 2011 at 2:38 PM, Amy Muntz <[email protected]> wrote:
> Hi Raju,
> Yes - please contact the Laszlo Systems management team.
>
> One quick correction - the last major release was actually OpenLaszlo 4.2,
> which added the SWF10 run time platform. While the number scheme could be
> better, this release was in 2009. Since then, we've continued to push out
> new features to the community as fast as we can, with OpenLaszlo 4.9 being
> released in October, 2010.  We are due for another community release soon. I
> agree that publishing a target would be helpful and I will look into this.
>
> Thanks, as always, for your insightful comments and technical contributions!
>
> Amy
>
>
> On Tue, Feb 1, 2011 at 8:26 AM, Raju Bitter
> <[email protected]> wrote:
>>
>> Thank you, Amy. I will contact the Laszlo Systems management team.
>> Though I think it would be good for Laszlo Systems as a company to be
>> able to publish the release date for the next major release of the
>> platform (not specifying a month, but at least to be able to say: we
>> expect to release OpenLaszlo 5.0 by Q?/Year?). The last major release
>> of OpenLaszlo (4.0) was in March 2007. That's almost 4 years without a
>> major release, and I can imagine that I'm not the only one waiting for
>> 5.0.
>>
>> Let's see if I can get an answer from Laszlo Systems.
>>
>> On Tue, Feb 1, 2011 at 3:13 AM, Amy Muntz <[email protected]>
>> wrote:
>> > Hi Raju,
>> > Unfortunately, I do not know the answer to these questions. I would
>> > suggest
>> > to anyone using OpenLaszlo that they explore new features as they are
>> > added
>> > by downloading the OpenLaszlo nightly trunk builds. Right now,
>> > OpenLaszlo
>> > remains as it always has with the CPL license and any change would
>> > certainly
>> > only affect future versions of OpenLaszlo and not the current software.
>> >
>> > I understand from your email that you have requirements for upcoming
>> > work,
>> > so it might be best to talk directly with the management team at Laszlo
>> > Systems about licensing, etc..
>> >
>> > Sorry that I couldn't be more helpful in this matter,
>> > Amy
>> >
>> > On Mon, Jan 31, 2011 at 7:24 AM, Raju Bitter
>> > <[email protected]> wrote:
>> >>
>> >> I might be starting a new project using OpenLaszlo in the  next weeks,
>> >> and have a few questions on the future of the project:
>> >>
>> >> 1) When will OpenLaszlo 5.0 be released?
>> >> 2) Under which license will OpenLaszlo 5.0 be released? Will the
>> >> software still be open source for commercial usage? I've heard rumors
>> >> that there are plans to use a dual license for future versions of
>> >> OpenLaszlo?
>> >>  a) If there are plans for a commercial version of OpenLaszlo, how
>> >> much are the license costs going to be? Similar to ExtJS
>> >> http://www.sencha.com/store/, charging around $ 900-1000/developer
>> >> seat?
>> >>  b) Will there be license costs for non-commercial use of the software?
>> >>  c) Will contributors/committers get a free version of the software
>> >> for commercial development? Or do we have to pay the full price in
>> >> case of a release under a dual license?
>> >> 3) Will the 5.0 release include the new component set?
>> >> 4) Will the new components be compatible with the old components (can
>> >> you mix old and new components)?
>> >> 5) Can custom components be migrated to the new component set
>> >> infrastructure (e.g. having components extending base components)?
>> >>
>> >> My recommendations for OpenLaszlo as a future-proof development
>> >> platform will much depend on answers to these questions.
>> >>
>> >> Thanks,
>> >> Raju
>> >
>> >
>>
>
>

Reply via email to