Comments on: 13 April 2008 > Squeak Image Updated

By: cdrick

cdrick — Tue, 15 Apr 2008 19:53:19 +0000

ok thanks for both informations :)

While doing my single example, I was looking for a pragma telling the relation like for :

address

…

So actually doing two forms was influenced by Magritte and a bad idea here I think as one is enough. I imagine you’re also thinking on validation of multiple conditions on several models. I particularly appreciated how you dealt with it in Magritte (didn’t found by myself the container trick)

Anyway, thanks for the clarification. Looking forward to hear more on that ;-)…

See you

By: Ramon Leon

Ramon Leon — Tue, 15 Apr 2008 19:23:41 +0000

One of the reasons I haven’t open sourced this just yet is that I haven’t dealt with multiple model editing. It’ll get there, I’ve just been busy. The current solution would be to use the form as it’s own model, give it all the necessary fields, and after successful commit, update your actual model objects manually. Right now it’s pretty much optimized for single model editing, or forms with no model, like login forms or email forms and such.

By: cdrick

cdrick — Tue, 15 Apr 2008 17:24:47 +0000

Sophie,

Yes that could be a good idea. But right now, I won’t use it, as I’m very busy until june at least. So I’m just open an image to relax from time to time :) (I guess I’m addicted really now ! ).

Anyway, I’ll definitly have a closer look at it and I’m sure lots of people will like this as a separate squeaksource project.

Right now, I just wonder how relations are “established” between objects. In other words, what are the equivalents for OneToOne and OneToMany relations in magritte ? Is it possible to express such relations in SSForm ? I tried to implement a simple model,a Person (name adress) and Adress (city code). Do I need to declare two forms, one for person and one for adress and then declare somehow the relation… ?

Thanks

By: Sophie

Sophie — Tue, 15 Apr 2008 14:42:31 +0000

Cdrick,

I’m using SSForm and really like it. If you try it out as well, perhaps we should consider all working off a common project.

Sophie

By: Ramon Leon

Ramon Leon — Tue, 15 Apr 2008 02:45:48 +0000

Yes, I no longer use Magritte for building forms, I build forms with SSForm. SSForm uses meta data from the model in the form of pragmas to render itself. It’s just for entry forms, and its big advantage over Magritte is simplicity and the ability to drop into raw Seaside by overriding the render method for a field to do fancy Ajax stuff when you feel the need. Magritte is too meta, and requires too much brain power to extend and customize. SSForm is much simpler, more straightforward, and is pure Seaside and pragmas, no crazy meta model to learn. SSForm also keeps all fields for a model in a single view making it vastly easier to have field to field or multiple field interactions.

By: cdrick

cdrick — Mon, 14 Apr 2008 18:02:04 +0000

Hi Ramon…

Thanks again for your image. It’s nice to see how a personnal image looks like. It’s a good example to see how people program in smalltalk by gently extending their image.

So I had a closer look to some stuffs, and in particular SSForm (nice example of pragma uses). It seems to me it’s a kind of Magritte framework specialized in forms generation for seaside only, so it’s probably quicker to use. Is it how you see it ? Also, there is no straight viewers or do I miss something ? Anyway viewers are not a problem compared to entry forms…

So is SSForm a new strategy (to replace Magritte) for your editors, an experimentation or you plan to use both magritte and your SSForms (I see SSAdminBase uses magritte for instance but it’s older).

See you, and thanks for all this nice code examples ;)