"John A. Palmieri" wrote:
>
> Hi Frank,
>
> I started SOMELib. Right now I play a minor role in the development
> though I keep an eye on design and such and put in my $.02 now and
> again. Thomas does the bulk of the development right now. When you
> talk about having knowledge that goes "way back to SOM" are you talking
> about my original releases of SOMlib(simple object model) or IBM's
> SOM(system object model)?
System Object Model
> I had changed the name to SOMELib to avoid
> confusion. Ours is a simple inprocess object model for extending
> dynamic object loading on Linux and now Windows systems. The new
> codebase is completely rewritten and is currently in its alpha stage.
> It in fact does not even have Makefiles for Linux yet.
>
> SOMELib is meant to be a simple library with not much higher level
> functionality and almost no dependencies other than standard
> components. In other words a person can drop in SOMELib and use it just
> as if they were using c's dynamic loading facilities (at bit more
> complex than that but you get the idea). Theoretically you should be
> able to create a CoreLinux++ loadable object that has the ability to
> load SOMELib objects very easily and with little overhead.
>
> As for collaboration on a standard for metaclasses/metatype classes for
> reflection/introspection. I think this would be great. Having a
> standard for such a task would alleviate the pains of developers and
> would allow people to chose what implementation they wish to use. For
> crossplatformability alacart SOMELib and for full linux standards with
> many backup classes CoreLinux++. So it sounds like fun. Is there a
> mailing list setup for this yet?
>
> Our main concern with SOMELib is to not sacrifice simplicity and as long
> as this does not I am all for it.
>
> -Quinticent
>
> SOMELib
> http://sourceforge.net/projects/somelib/
> C++ object loading
>
> The Snaglepuss Project
> http://sourceforge.net/projects/snaglepuss/
> Multimedia development engine
Yes, I can understand that, and as CoreLinux++ is not targeted to other
platforms, it makes sense.
Well, if anyone wants to throw in their $0.02 we have a
corelinux-develop mailing list. There is some information in the archive
concerning meta-types.
There is also the (in progress) MetaClass functional requirement:
http://corelinux.sourceforge.net/doc/requirements/req10658.php
and the Library Load abstraction design (although a Function Library
Load theoretical specialization is shown as well):
http://corelinux.sourceforge.net/doc/design/4865.php
--
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
>
> "Frank V. Castellucci" wrote:
> >
> > I am the project admin for CoreLinux++. I have experience in declarative
> > object modeling, knowledge representation, meta-models, and way back to
> > SOM.
> >
> > Our objectives were to create a core library (90% complete) and then
> > develop common framework abstractions (libclfw++) which we have just
> > begun.
> >
> > For example, we have already put in the Library Load abstraction with
> > the intent to construct specialized derivations (such as Function
> > Library Load, Image Library Load, etc.). It was obvious that the
> > metaclass/metatype objects would be very useful in this and many other
> > framework plans for reflection, reasoning, and reification.
> >
> > So my reason for posting to this list is to see if there is any interest
> > in joining forces in CoreLinux++ with the intent to extend
> > metaclass/metatype/meta-attribute paradigm to further specialize the
> > libraries.
> >
> > This has immediate applications in our plans for Persistence, Class
> > Loading, Toolbox function reasoning, and type ontology management.
> >
> > Looking forward to your response.
> >
> > --
> > Frank V. Castellucci
> > http://corelinux.sourceforge.net
> > OOA/OOD/C++ Standards and Guidelines for Linux
> > _______________________________________________
> > somelib-devel mailing list
> > som...@li...
> > http://lists.sourceforge.net/mailman/listinfo/somelib-devel
> _______________________________________________
> somelib-devel mailing list
> som...@li...
> http://lists.sourceforge.net/mailman/listinfo/somelib-devel
|
