Hey,
I concur with James on the points he made.
The approach taken would make more sense if SMW was a plug in to PS, as
this is what the code makes it out to be. I'd rather see the code be part
of PS, and have it only be registered there is SMW is loaded.
Cheers
--
Jeroen De Dauw
On 08/08/13 13:18, Jeroen De Dauw wrote:
Hey,
I concur with James on the points he made.
The approach taken would make more sense if SMW was a plug in to PS, as
this is what the code makes it out to be. I'd rather see the code be
part of PS, and have it only be registered there is SMW is
Hey,
I'm not sure what the use for the newly introduced ArrayAccessor class is.
It seems to not be providing a lot of functionality on top of ArrayObject.
And I found that one rarely actually needs the functionality ArrayObject
provides. And when one does not need it, it is better to not have it,
Wow... I don't know if there's ever been such quick consensus on a topic on
this list. Evidently that Page Schemas class has been bugging people for a
long time. :)
Yury wrote:
I remember Yaron have explained that it's a legacy remained from some
kind of global
plan of making PageSchemas the
Hey,
Wow... I don't know if there's ever been such quick consensus on a topic
on this list.
Yes, you have won of badge of some sorts :)
I'm not even sure what a global plan is. :)
Ah, of course you would deny your secret plans to take over the world, and
then install SMW everywhere.
But on
Hi,
ArrayAccessor is used in several classes[1] to conveniently access an
array through object methods. Of course one could make use of the
ArrayObject directly but one would need to implement the expectation
handling individually for when an expected element is not accessible.
Accessing an
Hi,
On Thu, Aug 8, 2013 at 9:48 AM, Jeroen De Dauw jeroended...@gmail.comwrote:
Hey,
Wow... I don't know if there's ever been such quick consensus on a topic
on this list.
Yes, you have won of badge of some sorts :)
I'm not even sure what a global plan is. :)
Ah, of course you would
Hi Yaron,
If we look from a point where we see SMW core being assigned to tasks
like data storage, data access, or querying then the implementation of
SMWPageSchemas feels a bit sidetracked to the point where:
For example having code like [1] where $psTemplateField is some kind
of an object but
Hi,
Well, I think you've reached the crux of the issue, which is the question
of what exactly SMW should be in charge of doing and what it shouldn't. If
you view SMW as essentially a library that provides data storage, data
access, or querying for MediaWiki - sort of a MySQL for MediaWiki - then
