[Seaside] OSCON "contest"
cdrick65 at gmail.com
Fri Jul 25 08:29:03 UTC 2008
Are there Pragma in Gemstone ? If yes I'll suggest looking at
SSFormand SSFormTest in Ramon image
Otherwise, I think one could publish in a repository a small table
component that add/edit/remove collection entries (based on
conventions on object accessors) having a simple validate function
;)... There's a need anyway for such a component. It could even be a
project in itself to expose several variations of tables... without
any apriori relation to the oscon app :)
My 2 cents
>> On Jul 24, 2008, at 5:54 PM, Ramon Leon wrote:
>>>> And if you were invited to a Ruby event and asked whether Seaside/
>>>> they were wrong for asking?
>>> Nope, but I wouldn't be showing them Magritte either, that's a mistake,
>>> be showing them Seaside and Scriptaculous. Magritte is complex in the
>>> way Glorp is complex, building all those metadata descriptions is complex
>>> and error prone and takes way too much time to use in a demo, especially
>>> time limited one. Whipping up something in raw Seaside would be much
>>> unless you've rigged up some code generators to write the mappings
>>> automatically for you.
>> I did try it both ways and building the editor by hand seemed to be more
>> lines of code and I thought I'd go for something that might seem more
>> familiar for the domain definition. Also, since I was building one component
>> by hand trying the other as meta data seemed like reasonable variety. On the
>> other hand, since I don't consider the whole experience a great success I
>> certainly won't insist that I made the right choice.
>>> Rails guys are accustomed to ActiveRecord and scaffolding which
>>> them up to a running system very quickly using code generation and a
>>> generate and modify philosophy (this is also how they learn Rails).
>>> Gemstone might eliminate the need for ActiveRecord, but Magritte is not
>>> all equivalent to scaffolding. Scaffolding is much easier to hack and
>>> customize because it's not a framework, it's just a bunch of generated
>>> template code. To compete against Rails in a time limited demo, you'll
>>> something like a scaffolder, or a form builder you have a very deep
>>> knowledge of so it can be highly customized on the fly. To sell newbs,
>>> need the scaffolder, because scaffolding code is an excellent way to
>>> them how to write Seaside code, they don't need yet another framework
>>> (Magritte) to learn.
More information about the seaside