Re: frysk-gui/frysk gui/FryskGui.javain gui/Change ...

Re: frysk-gui/frysk gui/FryskGui.javain gui/Change ...

[Phil Muldoon]

mcvet@sourceware.org wrote:
> 	* Gui.java (gui): Added a new overloaded gui() method, used to
> 	directly instantiate a new SourceWindow.
> 	
>   
Given this change, I'm wondering if we even need the menu option that 
currently exists in the session manager as it is right now. Not sure of 
the reason for this change (though I agree, tis a nice one). Could be 
room for rearranging of that first session manager window?

Regards

Phil

Re: frysk-gui/frysk gui/FryskGui.javain gui/Change ...

[Phil Muldoon]

Phil Muldoon wrote:
> mcvet@sourceware.org wrote:
>>     * Gui.java (gui): Added a new overloaded gui() method, used to
>>     directly instantiate a new SourceWindow.
>>     
>>   
> Given this change, I'm wondering if we even need the menu option that 
> currently exists in the session manager as it is right now. Not sure 
> of the reason for this change (though I agree, tis a nice one). Could 
> be room for rearranging of that first session manager window?
>
> Regards
>
> Phil

Oops a little quick on the sending this morning.

Does this represent a new work-flow, replacement of an existing one? 
Experimental? Should we update the work-flow section of the website 
accordingly?

Regards

Phil

Re: frysk-gui/frysk gui/FryskGui.javain gui/Change ...

[Mike Cvet]

On Mon, 2007-01-15 at 09:47 -0600, Phil Muldoon wrote:
> > Given this change, I'm wondering if we even need the menu option that 
> > currently exists in the session manager as it is right now. Not sure 
> > of the reason for this change (though I agree, tis a nice one). Could 
> > be room for rearranging of that first session manager window?
> >
> > Regards
> >
> > Phil
> 
> Oops a little quick on the sending this morning.
> 
> Does this represent a new work-flow, replacement of an existing one? 
> Experimental? Should we update the work-flow section of the website 
> accordingly?


I think that that menu option in the session manager is still important.
Frysk is for the most part a graphical program; these new flags for
directly bringing up the source window are there for convenience, but
the graphical link to the SW should always be there. That's not to say
that the Session Manager couldn't use a tune-up when we get some spare
time =)

I think that this impacts our workflows in two ways; the first simply
re-enforces the way we use the SW in the first place; but just steps
over the session manager window and attaches to a requested process
directly from the command line. The second I suspect is an entirely new
one - asking Frysk to execute a program from scratch and debugging it
from the start. In that case... /workflows should probably get a poke.

- Mike

Re: frysk-gui/frysk gui/FryskGui.javain gui/Change ...

[Sami Wagiaalla]

This is interesting, if you as the programmer are finding the current 
pathway too long maybe the user will feel the same way. I think it is 
something to consider next time we review our work flows, which is not 
the top thing on my list right now :)

Re: frysk-gui/frysk gui/FryskGui.javain gui/Change ...

[Andrew Cagney]

Yes.

Something currently being drilled into me is that, for a UI, the 
addition of an option and choice, is often an indicator that its time to 
review the original scenario.

Andrew

Sami Wagiaalla wrote:
> This is interesting, if you as the programmer are finding the current 
> pathway too long maybe the user will feel the same way. I think it is 
> something to consider next time we review our work flows, which is not 
> the top thing on my list right now :)