XML mapping DSL (SimpleXO)
by Steffen Märcker
Hi,
I am currently working on an XML to object mapping library. I came up with
an early version for a project, since I had to map weird/complex/poor XML
files. I'm in contact with Stephané Ducasse about a planned Pharo port.
He suggested to ask here for your opinions and ideas on this DSL/library.
SimpleXO consists of two parts, a Smalltalk Builder API that constructs a
parser object and a non-Smalltalk syntax meant for external binding
configuration. This post is on the API.
SimpleXO uses two concepts: types and mappings. A type describes how to
construct an object. It is configured with a class, a constructor and
mappings. A mapping defines which type a set of nodes is mapped to. The
nodes are given by a expression similar to XPath.
Short Example:
<geo id="1">
<rect>
<pos x="2" y="3" />
<width>4</width>
<height>5</height>
</rect>
</geo>
"Smalltalk'ish way:"
builder := SimpleXOParserBuilder new.
(builder defineElement: 'Rect')
class: 'Rectangle'; "given as string to postpone resolving"
mapPath: ('pos' /@ 'x') toType: 'Int';
mapPath: ('pos' /@ 'y') toType: 'Int';
mapPath: ('width') toType: 'Int';
mapPath: ('height') toType: 'Int';
mapPath: (AnyNodeTest /@ 'id') toType: 'Int'.
(builder defineCData: 'Int')
class: 'Integer';
constructor: #fromString:.
parser := builder buildParser: 'rect'.
parser mapNode: xmlNode.
"this gives the following object:"
(Rectangle new)
x: 2; y: 2;
width: 4; height: 5.
Actually we see two kinds of types: element and cdata. The only difference
is that elements are constructed using an unary constructor and cdata with
a one-argument message that is sent with the string-value of the current
node. Of course, SimpleXO supports id resolving, collecting values and
tokenizing attribute values. You can find further information on
https://wiki.aleturo.com/alpha/simplexo:start
I am really interested in your impressions, questions and ideas so far?
Regards,
Steffen
12 years
Getting the source code of a FAMIXClass
by Alberto Bacchelli
Hi,
I've parsed a Java system by using Verveine-J (pretty fast :) and imported
the resulting MSE file in the Moose Suite 4.6 Development I downloaded from
the moose website. Everything went fine.
I saw that each non-stub FAMIXClass has a FAMIXFileAnchor that correctly
points to the java source code file that contains the class declaration.
However, I cannot find the right way to directly access this declaration
(even though the FAMIXFileAnchor contains also
startLine,startColumn,endLine, and endColumn). I tried to call the method
FAMIXFileAnchor>>sourceText, but I only get an empty string.
Is there a way to access the source code?
Thanks.
Cheers,
Alberto
--
View this message in context: http://moose-dev.97923.n3.nabble.com/Getting-the-source-code-of-a-FAMIXCl...
Sent from the moose-dev mailing list archive at Nabble.com.
12 years
Issue 742 in moose-technology: smalltalkClass and compiledMethod extensions should be covered by tests
by moose-technology＠googlecode.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 742 by usman.bh...(a)gmail.com: smalltalkClass and compiledMethod
extensions should be covered by tests
http://code.google.com/p/moose-technology/issues/detail?id=742
especially when the mporter semantics is to distinguish or not metaclasses.
Right now
FamixClass>>smalltalkClass
"Returns the associated smalltalk class if it exist in the system."
^ FAMIXNameResolver smalltalkClassFromFamixClassName:
self name ifAbsent: [nil]
FamixMethod>>compiledMethod
"Return the compiled method associated to the receiver or nil"
| realClass |
realClass := self parentType smalltalkClass.
self hasClassScope
ifTrue: [realClass := realClass class].
^ realClass isNil
ifFalse: [realClass compiledMethodAt: self name asSymbol]
ifTrue: [nil]
It is strange that we have to do the test hasClassScope in the
compiledMethod method since normally smalltalk should correctly handle it.
12 years
An analysis of the MooseTask hierarchy
by Usman Bhatti
Hi guys
here are some notes we wrote when browsing the MooseTask
- It would be good to rename MooseTask should be renamed because it has
nothing to do in Moose.t
- MooseTask and MooseOperator should be in the same package: Moose-Core
since MooseOperator has nothing to do with Smalltalk.
- the hierarchy of MooseCompositeImporterTask is really dealing only with
Smalltalk importing logic.
so we should rename it:
SmalltalkCompositeExtractorTask or at least
SmalltalkCompositeImporterTaskcolle
- MooseImportClassesTask should be renamed SmalltalkImportClassesTask
or SmalltalkExtractClassesTask
since it only create entity extracted from Smalltalk.
( Importer vs extractor
I would like to keep the term importer to the action of populating a model
and the action to extract model from source code.
In java, c3 we have extractor and in Moose importers and extractors)
- I would rename SmalltalkImporter as SmalltalkExtractor like that we have
a clear line.
- Nobody is referencing PackageDescription?
- Now our problem is that we would like to run tasks when a
a Smalltalk model is extracted and imported and when a mse file is
imported.
We should probably introduce the logic of the plugin login somewhere
in a superclass and (MSEImporter should be a subclass of MooseTask - not
verified if make sense)
- I have no clue about the contents of the Moose-GenericImporter. It looks
like we stopped in the middle of something (which is probably true).
- MooseImportingTask is still Smalltalk specific so I would move to
the Moose-SmalltalkImporter.
- MooseFileStructureImporter looks really broken but it can be a nice
example of a subclass of MooseImporterTask (not MooseExtractorTask)
Doru it would be fun to do some pair programming to address these changes.
Do you have time this evening?
12 years
An analysis of MooseTask hierarchy
by Usman Bhatti
Hi guys
here are some notes we wrote when browsing the MooseTask
- It would be good to rename MooseTask should be renamed because it has
nothing to do in Moose.t
- MooseTask and MooseOperator should be in the same package: Moose-Core
since MooseOperator has nothing to do with Smalltalk.
- the hierarchy of MooseCompositeImporterTask is really dealing only with
Smalltalk importing logic.
so we should rename it:
SmalltalkCompositeExtractorTask or at least
SmalltalkCompositeImporterTaskcolle
- MooseImportClassesTask should be renamed SmalltalkImportClassesTask
since it only create entity extracted from Smalltalk.
( Importer vs extractor
I would like to keep the term importer to the action of populating a model
and the action to extract model from source code.
In java, c3 we have extractor and in Moose importers and extractors)
- Nobody is referencing PackageDescription?
- Now our problem is that we would like to run tasks when a
a Smalltalk model is extracted and imported
12 years
Attributes and Properties
by Usman Bhatti
I would like to know the difference between an attribute and a property of
a FamixEntity.
thanx,
Usman
12 years
MooseId vs MooseName
by Usman Bhatti
Hi guys
We are adding Author to Moose as an experience to learn how to extend moose.
In the past, for a moose entity with a unique name we were using the
uniqueName as mooseID
What is the status now?
For example we would to make sure that author can be retrieved by their
name
mooseModel entityNamed: 'me'
and that we do not have conflict with other Moose entity.
Stef
12 years
Is there an update button for moose
by Stéphane Ducasse
Hi
I would like to know how I can get the latest version from a given version.
Because I do not want to have to merge back.
So how do I get all the latest versions of packages? and does it work?
Stef
12 years
what is the pattern to add a custom importer performing action after default import?
by Stéphane Ducasse
Doru
long time ago :) there were importer post action plugin that we could register to Moose.
I reread my comment on Tasks and friends (I hate hate all the classes with not a single comment - so I will take some time
when I can to see what I can write but this is really terrible) - this were the comments I wrote when I wanted to build the new importer.
Now they do not describe the API and how to plug a new Task.
So how do we declare to an importer that a task should be run automatically after a model is created?
May be by creating a compositeTask but I want it to run after the main model is created.
Stef
12 years
