JooseX.Type status?

[John Mark Hawley]

I know that JooseX.Type hasn't been ported over to Joose3 yet, but I
can't find the current status of it. Is it being worked on? It's
probably the biggest win for me with Joose2.

It looks like there has been a LOT of thought on Types, and I'd like
to know the consensus on what JooseX.Type should support.

[Nickolay Platonov]

There is no progress on this item for now.

My very preliminary thoughts on it:
1) "type" means that objects of that "type" provides certain interface.
thus
2) Each Class is (or rather "has") a Type.
3) Each Role is a Type also.

Regards, Nickolay

--
You received this message because you are subscribed to the Google Groups "Joose" group.
To post to this group, send email to joos...@googlegroups.com.
To unsubscribe from this group, send email to joose-js+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/joose-js?hl=en.

[John Mark Hawley]

That sounds pretty close to the Joose2 Type system. Do you think the port is basically adapting the old system to the JooseX idioms, or are you looking to have them implemented via the reflection API or other existing Joose sub-systems?

--
John Mark Hawley
Design Technologist, Nilbog Group
http://www.nilbog.com
AIM: jmhnilbog
Twitter: johnmarkhawley

[Nickolay Platonov]

On Mon, Nov 22, 2010 at 8:54 PM, John Mark Hawley <john.mar...@gmail.com> wrote:

That sounds pretty close to the Joose2 Type system. Do you think the port is basically adapting the old system to the JooseX idioms, or are you looking to have them implemented via the reflection API or other existing Joose sub-systems?

The old system definitely should be taken for basis, and adapted to new API along with some refactoring. It should be also coupled with additional progress on JooseX.Attribute (the whole purpose of the type system).