Hi,
I am going over Moose Chef. It's quite cool :).
Here are some issues I found:
1. MooseQueryResult currently inherits from Collection. It would be more useful if it would be a MooseGroup because we could directly navigate it in the Moose Finder.
I already played with it and it looks like it is not too problematic to get this working. I got 237 of 240 tests green. The 3 left are due to the Composite not working quite properly due to a small mismatch between the semantics of Group and Collection.
Is there a reason for why we would want a Collection? If not, I will try to get it fully working and then commit.
2. I like the filters, but they would need to be extended for handling groups of entities. For example, now we can say outOfPackage:, but we should also be allowed to specify outOfPackages:. This should not be hard.
3. Right now, we can work with one entity as a starting point (namespace, package, class or method). We should also be able to have Groups as starting point. For this, I guess we would need some other Traits.
4. There are two references to MooseCompositeQueryResult in TScopingEntityQueries and in TDependencyQueries. This class does not exist. First these methods seem to be overridden in the classes. Second, I guess it should be MooseOutgoingCompositeQueryResult. Am I correct?
Cheers,
Doru
--
www.tudorgirba.com
"There are no old things, there are only old ways of looking at them."
I'm trying to parse a negated character with petit parser. I'm trying to parse
[^"]*
but the only thing I came up with is
($" asParser not, #any asParser) star flatten
Is there a better way to parse it or is this just the way to go? The not consuming not parser is indeed useful if I need a combination of negation but the straight forward thing I try to solve looks cumbersome.
thanks,
Norbert
So far no. I have worked with databases, so I cannot recommend anything.
However, if you can extract the data "by hand" and produce a textual file (or even better, an XML file), then the battle will be easily win.
Alexandre
On 28 Apr 2011, at 07:35, Torsten Bergmann wrote:
> Hi Alexandre,
>
> short question about Moose/Mondrian: is there an adaptor
> to visualize PL/SQL (Oracles database language).
>
> Thx
> Torsten
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dear all,
recently I've come across the KDM (Knowledge Discovery Metamodel) on a couple of occasions. KDM is defined by its maker OMG as "a common intermediate representation for existing software systems and their operating environments, that defines common metadata required for deep semantic integration of Application Lifecycle Management tools".
See http://www.omg.org/technology/kdm/index.htm and http://www.omg.org/spec/KDM/1.0/PDF/
Reverse engineering tools are cropping up claiming they're KDM-compatible (whatever that means). I must admit I was not aware of KDM up until very recently, although it seems to have been around since 2008.
My question is: is any Mooser looking into KDM? If not it might be worth a shot, even if only for a Bachelor project, just to understand what is there and what it could mean for Moose.
Cheers
Michele
PS. This is not a "please look into it" message, as I can already anticipate a "why the hell don't you do it yourself" reply. It's a general "heads up" about something that may impact Moose in some way. In any case, I'll try to find a student willing to look into this.
Hi,
I have a small problem related to file line endings and storing the token information of PetitParser.
Sometimes, we parse the sources on Windows and then manipulate the model on Linux or Mac. In this context, if I store the token positions in a string, I encounter problems because CR and LF are considered characters, but the line endings can vary.
('abc', Character cr asString , 'd') findString: 'd'.
==> 5
('abc', Character cr asString , Character lf asString, 'd') findString: 'd'.
==> 6
How would you approach this problem?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow."
Hi,
I am trying to use RoelTyper, but I encountered subscript out of bounds and empty collection errors. It looks like this problem can be reproduced on 29 classes from Pharo 1.2.1. You can test it using:
classes := Dictionary new.
Object withAllSubclassesDo: [:each |
[(TypeCollector typeInstvarsOfClass: each )] on: Error do: [:error | classes at: each put: error ]].
classes inspect
I am not knowledgeable enough to dive into this. Can anyone help?
Cheers,
Doru
--
www.tudorgirba.com
"Value is always contextual."
I sent this msg to Fame-dev but it seems that the list is no more active.
---------- Forwarded message ----------
From: Usman Bhatti <me(a)gmail.com>
Date: Tue, Apr 26, 2011 at 6:22 PM
Subject: Fame C# implementation
To: fame-dev(a)iam.unibe.ch
<https://mail.google.com/>Hi all,
I am working on extracting C# information and import that into Moose. I am
looking to automate the creation of Famix 3.0 entities in C# code to fill in
the information and export those entities into MSE file. I've seen that
there is a C# solution for Fame similar to Java on the fame
page<http://scg.unibe.ch/wiki/projects/fame/>.
However, C# solution does not include code for the generation of Famix 3.0
entities in code as the code does. My question is: does the C# solution for
fame support the import of FAMIX 3.0 entities thru automated code generation
as it does for java?
thanx a lot,
Usman
On Mon, Apr 25, 2011 at 6:37 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote:
> On 04/25/2011 09:12 AM, Mariano Martinez Peck wrote:
>
>> Hi Dale. I guess you are already aware of...but ... SUPPOSE that Glamour
>> is enough for your needs. Glamour can result in plain Morphic but also
>> in seaside. So would be able to have both flavors: image based in
>> Glamour for those who want everything image based, and a web alternative
>> (for example for Gemstone).
>> But...I have no idea how stable/complete the GlamourWeb is, nor if it
>> contains what you need.
>>
>> And finally, did you consider SeasideXUL ? But I guess it may happens
>> what you don't want: spend more time in the framework than in your job :(
>>
>
> I don't have Glamour ported to GemStone (has it been ported to Squeak?) and
> I don't know if I gain in the end ... Can one build a wizard in Glamour ?
> ... I've spent a lot of time trying to bend OmniBrowser to my will, but
> there are some things that are just not easy to do in OmniBrowser ... I
> don't know myself if Glamour can do what i have in mind or how much bending
> to my will it will take:)
>
>
I don't know that neither.
> If someone built a wizard in Glamour for creating a complex configuration
> (like Seaside or Moose) then it might be enough to motivate my to attempt
> the port:)
>
> But if is up to me, I am going to go with something I already know (I just
> don't have enough time to do what I know, let alone what I don't know)
>
> I already pretty much know what I would have to do to do a wizard for a web
> browser ...
>
> I appreciate the suggestions to use framework x, y, or z to solve the
> problem, but I am not an expert in any of the frameworks, and if a framework
> isn't ported to GemStone is it worth porting the framework to GemStone only
> to find that it doesn't fill the bill? Conversely if I build the wizard in
> technology z and then find out that it is very difficult to port to
> GemStone, where am I?
>
>
If fact, what I was thinking is that from Glamour you can generate the
Seaside output, so for Gemstone you don't need to port anything, just use
the seaside components generated from Glamour (be careful, this is how I
think Glamour-seaside works but maybe I am wrong and you need glamour
anyway)
> Using a web framework I am very confident that I could get a model/ui built
> that does the job and is portable to all three platforms ... I can't say
> that (with confidence) for any other approach...
>
>
Sure. But it is realy really bad to see we don't have a single way of
creating portable browsers/wizzard or whatever they are called between 3
dialects.
--
Mariano
http://marianopeck.wordpress.com
Hello Nick,
So then the cut-point is at the level of message sends between the GUI and the model?
How are events handled (messages from the model to the GUI) ... this is the spot where I think that OmniBrowser (in the GLASS implementation) started to falter ... there a large number of event messages that end up with more network round trips than one would like ...
It seems that there is a need for some sort of "message concentrator" that cuts down on network round trips, but this is wandering into "early optimization" territory:)
I think it would definitely be interesting to give this a try with GemStone as it has the potential to provide much more flexibility in terms of which GUI components can be used ....
Dale
On Apr 27, 2011, at 1:27 AM, Nick Papoylias wrote:
Hallo Dale,
In terms of remote tools, we are working with rST which is still kind of unstable but still
useful in many cases. Hopefully in your case too.
http://www.squeaksource.com/@69jY6Xu1NHtRD19j/lOHxDstw
So if your scenario is this:
You already have or you are creating a tool with Model-View architecture
that plays well when tested locally on a client and you want to go remote.
Then with rST (hopefully) you just wrap your model in a network proxy and everything plays out of the box remotely.
At least this is our goal.. we are currently working with remote reflection (in a more theoretical sense) but
we should and will find time to make rST more robust for the community.
I hope this helped, a bit.
Nick
On Wed, Apr 27, 2011 at 3:23 AM, Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com>> wrote:
On Apr 26, 2011, at 5:27 PM, Tudor Girba wrote:
> Hi Dale,
>
> On 27 Apr 2011, at 02:22, Dale Henrichs wrote:
>
>> On 04/26/2011 05:01 PM, Tudor Girba wrote:
>>> Hi Dale,
>>>
>>> Glamour is independent from the rendering, just like Omnibrowser is. Here is a short description:
>>> http://www.themoosebook.org/book/internals/glamour/rendering
>>>
>>> We already have a working Seaside rendering code for the basic widgets of Glamour. For an example, take the following steps:
>>>
>>> 1. download
>>> http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/lastSucces…
>>>
>>> 2. run:
>>> WAKom startOn: 8081
>>>
>>> 3. go to:
>>> http://localhost:8081/moose/metaBrowser
>>>
>>> Cheers,
>>> Doru
>>
>> I'll hold off exploring the scope of the Glamour port until I see if Glamour can be used to construct the configuration wizard:)
>>
>> I'm not skeptical as much as I am very busy...
>>
>> Did I provide you with enough info for the use case?
>
> Not really :).
okay?
Hi,
This is the default way to load the latest version:
Gofer new
squeaksource: 'Glamour';
package: 'ConfigurationOfGlamourSeaside';
load.
(Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault.
Cheers,
Doru
On 27 Apr 2011, at 10:17, Tobias Pape wrote:
>
> Am 2011-04-27 um 09:33 schrieb Tudor Girba:
>
>>> […]
>>> Is it usable in Squeak4.2?
>>
>> I never tried but you are welcome to. If you do, please let us know what happened :)
>>
>> Cheers,
>> Doru
>>
>
> Can you give me some starting points?
>
> So Long,
> -Tobias
>
--
www.tudorgirba.com
"It's not how it is, it is how we see it."
