>> (Object #mementoClass - MACheckedMemento is undeclared)
>> (Class #defaultContainer - MAPriorityContainer is undeclared)
>> (Object class #description - MACachedBuilder is undeclared)
>> (BlockContext #asCondition - MAConditionBuilder is undeclared)
>> (Magritte.MACachedBuilder #register - SystemChangeNotifier is
These should work.
>> (Magritte.MAColorDescription #kind - Color -
>> (Magritte.MAColorDescription #kind - Color is undeclared)
>> (Magritte.MADateDescription #kind - Date - duplicateBindings)
>> (Magritte.MADateDescription #kind - Date is undeclared)
These should work with the right namespace imports to the Squeak
compatibility package that Michel did for Seaside.
>> (Magritte.MADistribution #publish - HTTPSocket is
>> (Magritte.MADistribution #zip - ZipArchive is undeclared)
>> (Magritte.MADistribution #addPackage: - MCWorkingCopy is undeclared)
>> (Magritte.MADistribution #basePackages - MCPackage is undeclared)
>> (Magritte.MADistribution #addPackage:workingCopy: - MCVersion is
These are not needed, they are used to build the SqueakMap packages.
>> (Magritte.MADurationDescription #kind - Duration is
>> (Magritte.MADynamicObject #realSubject - UnhandledError is
>> (Magritte.MATimeDescription #kind - Time - duplicateBindings)
>> (Magritte.MATimeDescription #kind - Time is undeclared)
>> (Magritte.MATimeStampDescription #kind - TimeStamp is undeclared)
Again that should work with the right namespace imports.
> These are all things that you need to fix manually tough an
> in VisualWorks. It is related to platform dependent code that cannot
> be written in a generic way, but the comments should help you
> implement those methods easily.
Are you indicating that I would need to write the appropriate code
whatever the squeak versions do?
Yes, exactly. The tests might also help here.
I'm trying to decide whether or not its worth trying to get
ported over to VW or just ditch the idea altogether and roll my own
forms/reports, etc for each of my domain objects. I was looking at
which has already been ported to VW, but as someone else indicated on
the Seaside list, it has stagnated for several years and may not be
best choice. To that end, if I'm using VW, Seaside & Glorp, can I
expect any gotcha's -- probably specific to Glorp + Magritte that
pose any usability problems?
Mewa does not support to let end users edit the meta-model. Moreover
because it makes heavy use of blocks, it does not work if you want to
make your meta-model persistent. Though, if you just have a few
static forms it might be a good choice, but to give more hints you
need to elaborate your requirements.
Also, how much flexibility can I get with tailoring reports or forms
with Magritte and is the output that is generated XHTML compliant like
that which Seaside spits out (or is Seaside spitting it out as
Yes, it should be XHTML compilant. You can easily plug-in your own
renderer and components.