Bloc does not have examples yet.
What classes/methods do you need to be commented first to understand the
system?
On Feb 9, 2016 4:46 AM, "Sean P. DeNigris" wrote:
> I realize it's a fast-moving work in progress, but what's the best way to
> try
> to understand the system?
>
> For example, I saw
Sven, just to answer your last question. The UUID generation right now
generates the UUID fields like this:
UUIDGenerator>>generateFieldsVersion4
timeLow := self generateRandomBitsOfLength: 32.
timeMid := self generateRandomBitsOfLength: 16.
timeHiAndVersion := 16r4000 bitOr: (self
I can do the integration too, but I need some people to say go ahead.
I vote for replacing everything, there is no need for a plugin.
> On 09 Feb 2016, at 09:25, Guille Polito wrote:
>
> Sven, just to answer your last question. The UUID generation right now
> generates the UUID fields like this
Beside, you can't make slices ;-)
> On 09 Feb 2016, at 09:58, Sven Van Caekenberghe wrote:
>
> I can do the integration too, but I need some people to say go ahead.
> I vote for replacing everything, there is no need for a plugin.
>
>> On 09 Feb 2016, at 09:25, Guille Polito wrote:
>>
>> Sven
Sad and true... :'(
On Tue, Feb 9, 2016 at 10:01 AM, Sven Van Caekenberghe wrote:
> Beside, you can't make slices ;-)
>
> > On 09 Feb 2016, at 09:58, Sven Van Caekenberghe wrote:
> >
> > I can do the integration too, but I need some people to say go ahead.
> > I vote for replacing everything, t
You want me to do it then ?
I don't want us to do double work ...
> On 09 Feb 2016, at 10:09, Guillermo Polito wrote:
>
> Sad and true... :'(
>
> On Tue, Feb 9, 2016 at 10:01 AM, Sven Van Caekenberghe wrote:
> Beside, you can't make slices ;-)
>
> > On 09 Feb 2016, at 09:58, Sven Van Caekenb
Yes, go on. I think it is the easiest.
Right now, to check if a slice is good or not I have to commit, browse
Smalltalkhub's UI, and if it not good I have to delete the mcz manually...
On 02/09/2016 10:10 AM, Sven Van Caekenberghe wrote:
You want me to do it then ?
I don't want us to do doub
> On 09 Feb 2016, at 09:15, Aliaksei Syrel wrote:
>
> Bloc does not have examples yet.
> What classes/methods do you need to be commented first to understand the
> system?
>
mmm… that’s a bad question because I would answer “all of them”, but I
understand you want to do a step to make easy fo
On Tue, Feb 9, 2016 at 11:39 AM, Esteban Lorenzano
wrote:
> mmm… that’s a bad question because I would answer “all of them”, but I
> understand you want to do a step to make easy for us to understand so my
> answer has to be “the important ones”, but since there is no
> documentation/class commen
>
> The properties visible and locked, somehow they don't fit in the structure
> a BlElement provides, I don't know why but it looks strange.
> zIndex: what defines the order of elements, its zIndex or *are* they in
> different Bloc-Layers and a zIndex would be superfluous?
Don't worry they are d
formerOwner: anElementOrNil
"Set my former or remove property of argument is nil"
anElementOrNil
ifNil: [ self removeProperty: #formerOwner ]
ifNotNil: [ self setProperty: #formerOwner toValue:
anElementOrNil ]
I'd prefer to see a #setProp
On 09/02/16 11:53, Aliaksei Syrel wrote:
So I'm asking: what parts of Bloc do you find especially complicated to
understand. so we could concentrate on them? Root class
BlElement(methods) has good doc, so please use it to start your
exploration journey.
A lot of confusing comes from BlMorphXX t
>
> formerOwner: anElementOrNil
> "Set my former or remove property of argument is nil"
>
> anElementOrNil
> ifNil: [ self removeProperty: #formerOwner ]
> ifNotNil: [ self setProperty: #formerOwner toValue:
> anElementOrNil ]
I hate this method :)
>
> A lot of confusing comes from BlMorphXX things still being around all over
> the place. I prefer good examples as a starting point. Making
> Bloc-DragPanels work again?
Exactly! :) We just physically can't do everything so fast. It will come!
Patience, patience :)
Nevertheless pointing to issu
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 328356dc854a25a48d3fd46972fe68bc410df50e
https://github.com/pharo-project/pharo-core/commit/328356dc854a25a48d3fd46972fe68bc410df50e
Author: Jenkins Build Server
Date: 2016-02-09 (Tue, 09 Feb 2016
Branch: refs/tags/50572
Home: https://github.com/pharo-project/pharo-core
Hi nicolai
I agree. I will have a look at the Calipso experience of Alain.
Because may be Calipso + Spec layout format would be much nicer.
Did you look at it?
Alain just brainstormed but this is interesting for thinking.
Stef
What I hate also is that the
AbstractApdate>>update: aSymbol
> On 09 Feb 2016, at 13:38, Stéphane Ducasse wrote:
>
>>
>> p.s. To all who see this email: Bloc needs more complains
>>
>> :)
>>
>> Some random thoughts:
>> BlWorldElement and BlSpaceElement sounds like this is for elements *in*
>> space or *in* world, not like
>> *the* WorldElement.
>
> I
Le 9/2/16 11:53, Aliaksei Syrel a écrit :
On Tue, Feb 9, 2016 at 11:39 AM, Esteban Lorenzano
mailto:esteba...@gmail.com>> wrote:
mmm… that’s a bad question because I would answer “all of them”,
but I understand you want to do a step to make easy for us to
understand so my answer h
Please add a comment in the method stating it.
People are not reading your mind.
Stef
Le 9/2/16 13:25, Aliaksei Syrel a écrit :
formerOwner: anElementOrNil
"Set my former or remove property of argument is nil"
anElementOrNil
ifNil: [ self remove
>
> Please add a comment in the method stating it.
> People are not reading your mind.
I know :) I'm arguing that some classes/method could wait. We need to
concentrate on most important ones. And then come to the rest.
On Tue, Feb 9, 2016 at 1:52 PM, stepharo wrote:
> Please add a comment in
On Tue, Feb 9, 2016 at 4:15 PM, Aliaksei Syrel wrote:
> Bloc does not have examples yet.
> What classes/methods do you need to be commented first to understand the
> system?
>
> On Feb 9, 2016 4:46 AM, "Sean P. DeNigris" wrote:
>>
>> I realize it's a fast-moving work in progress, but what's the b
NNNDDD! It looks I found the real cause of this!
- I tested an image pre-new session manager, and an image post-new
session manager. The issue only appeared in the latter.
- Checking, it seems that UUIDGenerator is not subscribed to the new
startup list. This means that the UUIDGenerator
--- Begin Message ---
Hello,
yes, #formerOwner: and #formerPosition: are here for compatibility with Morphic.
and it will be like that for a while :)
The bloc drag&drop mechanism is implemented differently with the help of events.
Cheers
Alain
> On 9 févr. 2016, at 13:25, Aliaksei Syrel wrote:
>
--- Begin Message ---
> On 9 févr. 2016, at 13:24, Stephan Eggermont wrote:
>
> On 09/02/16 11:53, Aliaksei Syrel wrote:
>> So I'm asking: what parts of Bloc do you find especially complicated to
>> understand. so we could concentrate on them? Root class
>> BlElement(methods) has good doc, so pl
On Tue, Feb 9, 2016 at 9:12 PM, Guille Polito wrote:
> NNNDDD! It looks I found the real cause of this!
>
> - I tested an image pre-new session manager, and an image post-new session
> manager. The issue only appeared in the latter.
>
> - Checking, it seems that UUIDGenerator is not subscribed
--- Begin Message ---
and please, do not ask too much to Alex.
Alex is doing a pass (great job), and (I guess) he is doing it alone.
I will come back to Pharo and Bloc in two weeks, reimplement examples
and adapt the first Bloc documentation that we did with Stephane.
Then it will be easier for th
--- Begin Message ---
>
> The same for me... Besides SpaceElement there is BlSpace which is a model.
> Doru suggested to rename:
>
> BlWorldElement -> BlWorld
> BlSpace -> BlSpaceModel
> BlSpaceElement -> BlSpace
>
> Would such naming by more self-describing for you?
yes
Alain
--- End Messag
Le 9 févr. 2016 à 14:12, Guille Polito a écrit :
> However, now that we found that something was missing in the startup list, we
> should check for others...
There are currently 3 classes not registered in the startup list:
#SystemSettingsPersistence #MCGitBasedNetworkRepository #UUIDGenerator
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 94b7749d57060689f8e2e88dbf472ce504f15289
https://github.com/pharo-project/pharo-core/commit/94b7749d57060689f8e2e88dbf472ce504f15289
Author: Jenkins Build Server
Date: 2016-02-09 (Tue, 09 Feb 2016
Branch: refs/tags/50573
Home: https://github.com/pharo-project/pharo-core
Hi all,
Since a week, I'm back to using linux (debian) due to a new job. And it
became S evident that the shortcuts are wrongly configured, that I
actually cannot work!
Sometimes windows are closed with ctrl w, sometimes with alt w. Nautilus
is used with alt, playgrounds with ctrl...
S
2016-02-09 15:50 GMT+01:00 Guille Polito :
> Hi all,
>
> Since a week, I'm back to using linux (debian) due to a new job. And it
> became S evident that the shortcuts are wrongly configured, that I
> actually cannot work!
>
> Sometimes windows are closed with ctrl w, sometimes with alt w. Naut
On 09/02/2016 15:50, Guille Polito wrote:
> Hi all,
>
> Since a week, I'm back to using linux (debian) due to a new job. And it
> became S evident that the shortcuts are wrongly configured, that I
> actually cannot work!
>
> Sometimes windows are closed with ctrl w, sometimes with alt w. Na
The widget becomes available only once the UI is built, however when you
are configuring Spec it is not yet built so it's not available and thus the
ugly nil check (well, one of the reasons anyway).
This is a big problem with morphic/spec ui elements. You never know for sure
>> what code this
>> s
Hi guys
I was looking at the Collection chapter and I stumbled upon newFrom: and
I wonder what is the real
difference between newFrom: and withAll:.
I have the impression that there is not much difference. There are only
47 senders of newFrom: in the default Pharo image.
Dictionary class>>wi
Hi guys
I was looking at the Collection chapter and I stumbled upon newFrom:
and I wonder what is the real
difference between newFrom: and withAll:.
I have the impression that there is not much difference. There are
only 47 senders of newFrom: in the default Pharo image.
Dictionary class>>
Le 9/2/16 15:50, Guille Polito a écrit :
Hi all,
Since a week, I'm back to using linux (debian) due to a new job. And
it became S evident that the shortcuts are wrongly configured,
that I actually cannot work!
Sometimes windows are closed with ctrl w, sometimes with alt w.
Nautilus is
I love the class comment!
This is because of such class comment that I love also pharo
Le 8/2/16 20:39, Sven Van Caekenberghe a écrit :
Here is a new version, in preparation of possible integration in the main image:
===
Name: Neo-UUID-SvenVanCaekenberghe.2
Author: SvenVanCaekenberghe
Time: 8 F
Le 9/2/16 09:58, Sven Van Caekenberghe a écrit :
I can do the integration too, but I need some people to say go ahead.
I vote for replacing everything, there is no need for a plugin.
me too.
Less plugin!
On 09 Feb 2016, at 09:25, Guille Polito wrote:
Sven, just to answer your last ques
Hi peter :)
If I recall, one of the key problem is that the state of certain widgets
does not let the adpater do its job nicely and disappear
after the bridging.
Stef
Le 9/2/16 16:31, Peter Uhnák a écrit :
The widget becomes available only once the UI is built, however when
you are configur
Esteban was telling me that he is going to re-integrate the VM fixes to
the shortcuts for windows soon.
On 02/09/2016 04:48 PM, stepharo wrote:
Le 9/2/16 15:50, Guille Polito a écrit :
Hi all,
Since a week, I'm back to using linux (debian) due to a new job. And
it became S evident that
Guille Polito writes:
> So, since today I was able to commit again, I decided to make a couple
> of slices/new configurations fixing the majority of shortcuts in the
> image. Like this, mac shortcuts will remain in cmd, but linux and
> windows shortcuts will be with ctrl, as expected by the va
On Tue, Feb 9, 2016 at 11:53 PM, stepharo wrote:
>
>
> Le 9/2/16 09:58, Sven Van Caekenberghe a écrit :
>>
>> I can do the integration too, but I need some people to say go ahead.
>> I vote for replacing everything, there is no need for a plugin.
>
>
> me too.
> Less plugin!
This is a good genera
> On 09 Feb 2016, at 17:31, Damien Cassou wrote:
>
> Guille Polito writes:
>
>> So, since today I was able to commit again, I decided to make a couple
>> of slices/new configurations fixing the majority of shortcuts in the
>> image. Like this, mac shortcuts will remain in cmd, but linux and
> On 09 Feb 2016, at 17:35, Ben Coman wrote:
>
> On Tue, Feb 9, 2016 at 11:53 PM, stepharo wrote:
>>
>>
>> Le 9/2/16 09:58, Sven Van Caekenberghe a écrit :
>>>
>>> I can do the integration too, but I need some people to say go ahead.
>>> I vote for replacing everything, there is no need for
On 09/02/16 14:12, Guille Polito wrote:
NNNDDD! It looks I found the real cause of this!
- I tested an image pre-new session manager, and an image post-new
session manager. The issue only appeared in the latter.
- Checking, it seems that UUIDGenerator is not subscribed to the new
startup li
Agreed :)
But I was easy to convince :)
Le 9/2/16 19:09, Sven Van Caekenberghe a écrit :
On 09 Feb 2016, at 17:35, Ben Coman wrote:
On Tue, Feb 9, 2016 at 11:53 PM, stepharo wrote:
Le 9/2/16 09:58, Sven Van Caekenberghe a écrit :
I can do the integration too, but I need some people to say
This is great!
Doru
> On Feb 9, 2016, at 7:10 PM, Sven Van Caekenberghe wrote:
>
>
>> On 09 Feb 2016, at 17:31, Damien Cassou wrote:
>>
>> Guille Polito writes:
>>
>>> So, since today I was able to commit again, I decided to make a couple
>>> of slices/new configurations fixing the major
On 09/02/16 15:50, Guille Polito wrote:
Also, I did some changes in Glamour and GTSpotter, but I have no
permissions to commit there. How do we do to commit in those packages?
Should I ask for permissions or is there any other process in place?
There's a magical process by which you complain in
Thanks Stephan :).
@Guille: Stephan just added you to the SmalltalkHub repository.
Could you ping me when you commit so that I can review?
Cheers,
Doru
> On Feb 9, 2016, at 11:25 PM, Stephan Eggermont wrote:
>
> On 09/02/16 15:50, Guille Polito wrote:
>> Also, I did some changes in Glamour a
stepharo wrote
> Hi guys
>
> I was looking at the Collection chapter and I stumbled upon newFrom: and
> I wonder what is the real
> difference between newFrom: and withAll:.
> I have the impression that there is not much difference. There are only
> 47 senders of newFrom: in the default Pharo im
52 matches
Mail list logo