Object oriented approach to laszlo coding?

[whisperstorm]

It would be great to hear how other laszlo developers approach coding their apps - do you start with an existing app and just port it? Is it more of a discovery of the language approach (oh, it can do this? lemme add that to my app). Recently I discovered one of the more interesting ways to approach developing apps in laszlo -- by creating a bunch of classes with methods, etc. etc. and it seems that this is the "recommended" way to build a laszlo app - have other folks discovered this to be the case?

[cwalker]

My approach varies by what I'm building.

If I'm building a personal app, or just exploring, I really enjoy being able to start in one file, and grow it organically as needed. One of my favorite maneuvers in LZX is renaming a <view/> to a <class/>.

Eventually, if the file grows to be to large, I'll separate the larger classes out into their own Petri dishes.

In other cases, like when working on the components for the 2.0 release, it makes more sense to plan classes out ahead, and work in the more standard OO way, with one file per class in most cases.

Even in that case, I like that I can group related classes in the same file. This is akin to inner-classes in java, except that in LZX, they are still first-class citizens.

I enjoy being able to do either approach based on project or mood.

-christian