Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 951 in moose-technology: Export then Import a MSE Model throws FMSyntaxError

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 951 by v.blonde...(a)gmail.com: Export then Import a MSE Model throws FMSyntaxError http://code.google.com/p/moose-technology/issues/detail?id=951 Hi, I wanted to export and import a MSE file of a Moose Model. The export works perfectly but the import which throws an FMSyntaxError. You can reproduce from the Moose Panel by creating a Model from Smalltalk, export it (Import/export / Export to MSE), and import it. The pragma in FAMIXMethod>>clientClasses : <MSEProperty: 'Client classes' type: #FAMIXType> <multivalued> seems to be the problem. Indeed 'Client Classes' contains a space character which is not recognize by the MSE parser. I resolved by deleting the space. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years, 11 months

Issue 955 in moose-technology: GTInspector should install methods in the selected class

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 955 by tu...(a)tudorgirba.com: GTInspector should install methods in the selected class http://code.google.com/p/moose-technology/issues/detail?id=955 Right now, the inspector installs methods in the class of the current object. Instead, it should install the methods in the selected class (from the drop down). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years, 11 months

Re: UI stuff in parsing

by Vincent Blondeau

Hi, > Le 11/07/2013 17:53, Stephan Eggermont a écrit : >> Hi Vincent, >> >> FMMSEParser basicRun should do the trick Indeed, but I send the message MooseModel importFromMSEStream, which call many methods before FMMSEParser basicRun included FMMSEParser run containing the UIstuff. I don't want to rewrite them just for remove that. >> What's your end goal for this? Because most of what you can do with >> moose >> is going to perform pretty bad over high latency slow bandwidth >> connections. >> >> http://sealedabstract.com/rants/why-mobile-web-apps-are-slow/ The goal of the Moose on web project is sharing project analyses. We want to deploy a moose platform on a server and accesses it from computers. So the developers would be able to consult the models and see the improvements they have to make on the code. We don't want to use mobile platforms to see the models. The technology is too slow for this. However, what we do is synthesize the information. The moose is accessible by blocks and, this, shorten the delay. Have you seen the website in demo : http://37.139.2.203/client/ and the API : http://37.139.2.203/API ? > > >> Stephan >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > Vincent

11 years, 11 months

Re: [Pharo-users] New win32 VM available (was: More than 500MB for windows)

by Stéphane Ducasse

Thanks igor. On Jul 11, 2013, at 4:07 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > So, after spending unproportionally huge time (2days) dealing with > jenkins config idiosyncrasies, > it finally managed to build it. > > http://files.pharo.org/vm/pharo/win/latest.zip > > This VM should react properly on > AddressSpaceLimit=<number of MBytes> > setting in .ini file. > The ini file is located in same directory as VM executable. > If it doesn't exists, you can run VM once and it will create it automatically. > > Thanks for patience. > > -- > Best regards, > Igor Stasenko. >

11 years, 11 months

Re: PetitJava AST model status

by Stephan Eggermont

Sounds like a good idea, if you have the time. How do you build the AST incrementally and iteratively, so you can show (end-user) results every day? Stephan

11 years, 11 months

Hierarchical Bundle Edges

by Alexandre Bergel

Hi! Some of you may have heard about Hierarchical Bundle Edges. If no, then use google to find their cool papers. We will soon have a working implementation :-) Cheers, Hernan & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 years, 11 months

PetitJava AST model status

by Chris Cunningham

So, it looks like everyone that wanted to speak up has spoken up. From a strictly numeric standpoint it looks like the consensus is tied - 3 for strict grammar adherence, and 3 for allowing it to be looser (maybe significantly). But, popular vote isn't really the best way to solve technical problems. After reviewing the arguments again, the case for following the published grammar does make a lot of sense, especially since there is one. For my purposes, I'll either subclass that grammar or figure out how to use it directly (probably by extended it in my image as necessary). I still like a more focused AST, but given that I am not a Java expert, I definitely shouldn't be the one creating it - at least not the general one. So, how/when should I/we go about converting the current AST over? I will be interested in converting at least the parts that I want - which is more than there is now, but not the entire grammar. Note that this will change any Visitors using the AST, meaning that the Fast build will probably continue to fail as work is progressing. Might I suggest that a symbolic version be made against PetitJava that the Fast job uses - that uses a static version of PetitJava. This would stop the job from failing; the static version can be updated when you are ready to incorporate the changes in. Thanks, Chris

11 years, 11 months

Re: UI stuff in parsing

by Stephan Eggermont

Hi Vincent, FMMSEParser basicRun shoudl do the trick What's your end goal for this? Because most of what you can do with moose is going to perform pretty bad over high latency slow bandwidth connections. http://sealedabstract.com/rants/why-mobile-web-apps-are-slow/ Stephan

11 years, 11 months

UI stuff in parsing

by Vincent Blondeau

Hi, In developing moose on web, I wanted to use the MSE parsing to import by the web an moose model. Guillaume and I discover that the parsing trigs a job showing a progress bar. This UI stuff is directly implemented in the parser (FMMSEParser>>run) what is not really the way to do it according Guillaume.... and I can't disable it easily for running the parsing on a server... What do you think ? Cheers, Vincent

11 years, 11 months

[ANN] Moose On Web

by Vincent Blondeau

Hi, Moose on Web is on the Web ! The purpose of this project is to access the moose image across the web through a Rest Api I let you discover ... You can try it at: http://37.139.2.203 And access directly to the API at: http://37.139.2.203/API Cheers, Vincent

11 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev