28 Mar
2014
28 Mar
'14
3:48 p.m.
Thanks, Yuriy. We need to invent these tools dramatically. This is a huge
opportunity both for Pharo and for Moose. The road will not be smooth all
the time, but I think that the most difficult things are now a thing of the
past.
Doru
On Fri, Mar 28, 2014 at 3:31 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:
On 28 Mar 2014, at 15:17, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi,
On Fri, Mar 28, 2014 at 3:04 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote;wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
I'm not used to a gt debugger. Debugging
buttons have icons that are not
easily understandable, they are located fa from another things that i
access.
What do you mean by being far from what you access?
At the moment it's hard to say. Las time I just notices that it took me
more time to use debugger buttons
Also I like the idea that you don't have to
spawn a new inspector when
drilling down, but I like to have a small workspace to test out something
and close rather than big window of gt-playground.
Playground should behave like the Workspace, too. What prevents you from
having small playgrounds open without previewing?
The thing is that I was using Moose itself about a year ago. After that I
was working only in Pharo. Now when I needed to
do something in Moose fast,
I found myself in the middle of dark technology :).
That is because you are not using the white theme :)
I really don't think that my issue is
something serious, but it's a
religious point of view, that if user wants to use Moose he shouldn't be
forced to become a beta-tester of gt-toolkit and so on.
Careful ... you are touching a sensitive coord ... GT is not a beta thing
:)). Seriously, Moose will focus on a full experience. You can still choose
to setup your image the way you want, but Moose will be a full image
covering the entire development cycle.
Makes sense. It was just disturbing when I wanted to do something fast and
everything was different. Well, ok let's try to understand the whole
philosophy more and then I can talk in a more confident way.
I dislike belief-driven-policies because they prevent learning. If you do
not say what the issue is, it is hard to get it addressed. It can cost a
bit of effort at times, but overall everyone benefits.
Cheers,
Doru
Uko
On 28 Mar 2014, at 14:45, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi Yuriy,
Please let's get concrete because only like that we can improve and learn
from each other. Up to now, you listed:
- Autocompletion being turned off - I agree that this should be on, but
as it is now it is a bit buggy - I did not yet raise my voice loudly
because I did not have a chance of looking into it in more details.
- White theme
What other things don't you like and why?
Doru
On Fri, Mar 28, 2014 at 2:08 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote;wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
It works. Just that I prefer it the other way
around. I get suggestions
disabled I can enable them, but it takes some time. I get a white theme, I
can switch to original one, but it takes time. And so on. Also when I try
to introduce someone who knows Pharo to Moose I have also to introduce him
to whole new tools.
I'm not insisting on keeping it there, this is just a thing that saves
time because Moose is loaded by CI
Uko
Sent from my iPhone
On 28 Mar 2014, at 13:38, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Apparently, it contains the code without having the Moose image setup
being triggered.
@Yuriy: Could you let us know what exactly does not work for you?
Cheers,
Doru
On Fri, Mar 28, 2014 at 1:35 PM, Alexandre Bergel <
alexandre.bergel(a)me.com> wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
What Moose-less contains then?
Alexandre
On Mar 28, 2014, at 7:25 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>
wrote:
> Hi guys.
>
> I've created a "Moose-less" version
https://ci.inria.fr/moose/job/moose-5.0/1006/artifact/moose-5.0-less.zipbec… some
people (including me of course) don't want to have all IDE
revamped to use the features of Moose. It's created during a main Mosse
build as it's already there anyway. But if you don't like it, I can move it
to somewhere else.
>
> Uko
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev