Problems using java code importer with inFusion under windows

Hi,

i was using moose in windows and i had an error trying to use the function "import from Java source with inFusion". Seems that OSProcess doesn't work properly. To reproduce the error just try to import java code using this function in the Moose panel in windows. In Mac i never had problem using that cool function.

Anybody can help me to figure out where the problem is?

Thanks in advance for the support,

Fabrizio

PS: Here the stack trace: 

--- The full stack ---

UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll:

ExternalWindowsOSProcess>>value

ExternalWindowsOSProcess class>>command:

WindowsProcess>>command:

WindowsProcess>>waitForCommand:

OSProcess class>>waitForCommand:

MooseImportFromJavaSourceFilesWizard>>validateImportation

[] in MooseImportFromJavaSourceFilesWizard>>performTerminateButtonAction

[] in ProgressInitiationException>>defaultAction

BlockClosure>>ensure:

ProgressInitiationException>>defaultAction

UndefinedObject>>handleSignal:

MethodContext(ContextPart)>>handleSignal:

ProgressInitiationException(Exception)>>signal

ProgressInitiationException>>display:at:from:to:during:

ProgressInitiationException class>>display:at:from:to:during:

PSUIManager(MorphicUIManager)>>displayProgress:at:from:to:during:

MooseImportFromJavaSourceFilesWizard>>performTerminateButtonAction

WizardLastPane>>terminateButtonAction

PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction

PluggableButtonMorphPlus>>performAction

[] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp:

Array(SequenceableCollection)>>do:

PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp:

PluggableButtonMorphPlus>>mouseUp:

PluggableButtonMorphPlus(Morph)>>handleMouseUp:

MouseButtonEvent>>sentTo:

PluggableButtonMorphPlus(Morph)>>handleEvent:

PluggableButtonMorphPlus(Morph)>>handleFocusEvent:

[] in HandMorph>>sendFocusEvent:to:clear:

[] in PasteUpMorph>>becomeActiveDuring:

BlockClosure>>on:do:

PasteUpMorph>>becomeActiveDuring:

HandMorph>>sendFocusEvent:to:clear:

HandMorph>>sendEvent:focus:clear:

HandMorph>>sendMouseEvent:

HandMorph>>handleEvent:

HandMorph>>processEvents

[] in WorldState>>doOneCycleNowFor:

 - - - - - - - - - - - - - - -  

- - - - - - - - - - - - - - - - - -

Array(SequenceableCollection)>>do:

WorldState>>handsDo:

WorldState>>doOneCycleNowFor:

WorldState>>doOneCycleFor:

PasteUpMorph>>doOneCycle

[] in Project class>>spawnNewProcess

[] in BlockClosure>>newProcess

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Because the discussion about this topic happened on the moose mailing list i just update also the pharo mailing list. To summarize:

I had problems using the importer of java code with inFusion on Windows, at the end i discovered that the primitives into WindowsOSProcessAccessor just fails during the initialization and that the process is not able to access the OS. There is also a bug report here:

http://code.google.com/p/moose-technology/issues/detail?id=321&q=OSProcess&colspec=ID%20Status%20Summary%20Owner%20Type%20Opened%20Modified%20Milestone%20Component%20Reporter 

Is it possible to debug primitives? 

Cheers,

Fabrizio

2010/2/18 Cyrille Delaunay <[hidden email]>

The command send to OSProcess is a Unix-specific command .This command generate the mse file usimg the '.sh' file from inFusion. The solution add a condition, and use the .bat file (and the command line that come with ) if the OS is windows.

2010/2/18 Fabrizio Perin <[hidden email]>

Hi,

i was using moose in windows and i had an error trying to use the function "import from Java source with inFusion". Seems that OSProcess doesn't work properly. To reproduce the error just try to import java code using this function in the Moose panel in windows. In Mac i never had problem using that cool function.

Anybody can help me to figure out where the problem is?

Thanks in advance for the support,

Fabrizio

PS: Here the stack trace: 

--- The full stack ---

UndefinedObject(Object)>>doesNotUnderstand: #nextPutAll:

ExternalWindowsOSProcess>>value

ExternalWindowsOSProcess class>>command:

WindowsProcess>>command:

WindowsProcess>>waitForCommand:

OSProcess class>>waitForCommand:

MooseImportFromJavaSourceFilesWizard>>validateImportation

[] in MooseImportFromJavaSourceFilesWizard>>performTerminateButtonAction

[] in ProgressInitiationException>>defaultAction

BlockClosure>>ensure:

ProgressInitiationException>>defaultAction

UndefinedObject>>handleSignal:

MethodContext(ContextPart)>>handleSignal:

ProgressInitiationException(Exception)>>signal

ProgressInitiationException>>display:at:from:to:during:

ProgressInitiationException class>>display:at:from:to:during:

PSUIManager(MorphicUIManager)>>displayProgress:at:from:to:during:

MooseImportFromJavaSourceFilesWizard>>performTerminateButtonAction

WizardLastPane>>terminateButtonAction

PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction

PluggableButtonMorphPlus>>performAction

[] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp:

Array(SequenceableCollection)>>do:

PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp:

PluggableButtonMorphPlus>>mouseUp:

PluggableButtonMorphPlus(Morph)>>handleMouseUp:

MouseButtonEvent>>sentTo:

PluggableButtonMorphPlus(Morph)>>handleEvent:

PluggableButtonMorphPlus(Morph)>>handleFocusEvent:

[] in HandMorph>>sendFocusEvent:to:clear:

[] in PasteUpMorph>>becomeActiveDuring:

BlockClosure>>on:do:

PasteUpMorph>>becomeActiveDuring:

HandMorph>>sendFocusEvent:to:clear:

HandMorph>>sendEvent:focus:clear:

HandMorph>>sendMouseEvent:

HandMorph>>handleEvent:

HandMorph>>processEvents

[] in WorldState>>doOneCycleNowFor:

 - - - - - - - - - - - - - - -  

- - - - - - - - - - - - - - - - - -

Array(SequenceableCollection)>>do:

WorldState>>handsDo:

WorldState>>doOneCycleNowFor:

WorldState>>doOneCycleFor:

PasteUpMorph>>doOneCycle

[] in Project class>>spawnNewProcess

[] in BlockClosure>>newProcess

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Wed, Mar 03, 2010 at 04:51:25PM +0100, Levente Uzonyi wrote:
> On Wed, 3 Mar 2010, Simon Denier wrote:
>
> >
> > On 3 mars 2010, at 03:34, David T. Lewis wrote:
> >
> >> On Tue, Mar 02, 2010 at 02:18:20PM +0100, Fabrizio Perin wrote:
> >>> Because the discussion about this topic happened on the moose mailing list i
> >>> just update also the pharo mailing list. To summarize:
> >>>
> >>> I had problems using the importer of java code with inFusion on Windows, at
> >>> the end i discovered that the primitives into WindowsOSProcessAccessor just
> >>> fails during the initialization and that the process is not able to access
> >>> the OS. There is also a bug report here:
> >>>
> >>> http://code.google.com/p/moose-technology/issues/detail?id=321&q=OSProcess&colspec=ID%20Status%20Summary%20Owner%20Type%20Opened%20Modified%20Milestone%20Component%20Reporter
> >>
> >> Hi Fabrizio,
> >>
> >> The failure that you are seeing is because the OSProcessPlugin is not
> >> present in your VM, and therefore the primitives are not there (so really
> >> there is nothing to debug).
> >>
> >> OSProcess is not fully implemented on Windows. You can find some information
> >> about OSProcess at http://wiki.squeak.org/squeak/708
> >>
> >> If you have the option to use Unix/Linux or Mac, you should get better results.
> >
> >
> > Hi David
> >
> > Is there other means to launch a command line (and external tools) form a Windows VM then?
>
> You can give this a try: http://www.squeaksource.com/ProcessWrapper.html .
> Don't know if it works in Pharo or not.

You can also run a Windows exe using FFI, and if you are comfortable
building your on VM you can build the OSProcessPlugin for Windows.
Both of these will allow you to run an external program, but will
not allow you to directly read the output of the external program
as you can do on unix systems with OSProcess.

I think that ProcessWrapper will do what you need, so I suggest to
try that first for Windows.

Dave

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project