On Wed, Aug 31, 2016 at 9:16 PM, stepharo wrote:
> In squeak by example
>
> we could tag in the document code snippet as text and a perl script
>
> turn the expression into Sunit method and run the tests
>
> We lost that.
Yes I remember this was very nice.
We should have a look to the org-babel
In squeak by example
we could tag in the document code snippet as text and a perl script
turn the expression into Sunit method and run the tests
We lost that.
Stef
Le 31/8/16 à 12:21, Peter Uhnak a écrit :
On Wed, Aug 31, 2016 at 12:00:30PM +0200, Yuriy Tymchuk wrote:
Ok, now I know what I
On Wed, Aug 31, 2016 at 12:00:30PM +0200, Yuriy Tymchuk wrote:
> Ok, now I know what I want.
>
> I want a better way to document. Because I’m trying to write a documentation
> about my stuff, but there are too many disconnected ways to do that. I’m
> trying to always have reasonable class commen
Ok, now I know what I want.
I want a better way to document. Because I’m trying to write a documentation
about my stuff, but there are too many disconnected ways to do that. I’m trying
to always have reasonable class comments. But sometimes you need a more general
description, so you write help
Additionally I would like to see:
- investigation in the Win Pharo VM for being able to run again as
a Windows Service
(as it was possible for Squeak) to be able to easily provide,
deploy and administrate a web
app on Windows
Definitively. Thanks for mentionning it. It will be don
Thanks
we are currently brainstorming with esteban on the pharo pro offer and
this is nice to have your feedback.
Stef
Le 28/8/16 à 15:33, Torsten Bergmann a écrit :
what are the points you are working on and that would deserve more focus and
help from the community?
I once started with a
> what are the points you are working on and that would deserve more focus and
> help from the community?
I once started with a refactored version of GetText, covered with tests and
tools.
Code status I reached so far is here:
http://www.smalltalkhub.com/#!/~TorstenBergmann/Gettext
Idea was
Hi,
The answer was that Spotter is not different in any way than any other global
shortcut. This means that if we want to have an interactive solution, we should
do it at the level of the Keymapping framework not at the level of individual
tools.
In the meantime, how do we manage this? Inspect
> On 28 Aug 2016, at 00:55, Cyril Ferlicot D. wrote:
>
> Le 27/08/2016 à 14:32, Esteban Lorenzano a écrit :
>> yes, some years ago I made a package for this.
>> later Ben tried something similar with the user manager.
>> none of those approaches worked as general approach because you need to
>
Thanks Cyril
Now we have to check what is synectique specific from what should be
pushed to Pharo.
Since we moved to a Seaside application not so long after I joined
Synectique we only disable some basic things.
If I don't say anything wrong here is what we did:
- Remove repositories contain
Le 27/08/2016 à 14:32, Esteban Lorenzano a écrit :
> yes, some years ago I made a package for this.
> later Ben tried something similar with the user manager.
> none of those approaches worked as general approach because you need to
> “close” a lot of things… (not just the spotter… which by the
Le 27/08/2016 à 14:39, stepharo a écrit :
> Cyril what would be good is to share what you are disabling and to tunr
> such points into points that can be turned
> but inside Pharo like that you push the logic to the system.
>
Since we moved to a Seaside application not so long after I joined
Syne
> On 27 Aug 2016, at 14:40, stepharo wrote:
>
> Hi esteban
>
> I think that we should identify the main hook points and slowly prepare them.
>
> The system should be prepared for that so that we just need to pass a context
> to configure it.
.. I should have that old package somewhere… it wi
Hi esteban
I think that we should identify the main hook points and slowly prepare
them.
The system should be prepared for that so that we just need to pass a
context to configure it.
Stef
Le 27/8/16 à 14:32, Esteban Lorenzano a écrit :
yes, some years ago I made a package for this.
late
Cyril what would be good is to share what you are disabling and to tunr
such points into points that can be turned
but inside Pharo like that you push the logic to the system.
Now this is important to see that if people for which the value is high
do not work on something
why others would do i
yes, some years ago I made a package for this.
later Ben tried something similar with the user manager.
none of those approaches worked as general approach because you need to “close”
a lot of things… (not just the spotter… which by the way, NEEDS to have a
setting, no idea who answered you tha
Le 27/08/2016 à 13:18, stepharo a écrit :
>
>
> YES!!!
>
> Do you know how Settings works?
> We can adapt it this way.
When I improved the deployment of Synectique Tools I asked to get a
simple way to disable Spotter via a setting but I got as answer "No
because you can do it by removing a glob
Hi!
There is one thing I would like, but maybe not for Pharo6 since there is
a lot to do, but I would like people to have this in mind: A way to
deploy commercials apps.
YES!!!
I would like to be able to say something like "Smalltalk
lockForDeployment" and "Smalltalk prepareForDeployment"
Le 24/08/2016 à 06:59, stepharo a écrit :
> Hi
>
> We have some ideas (because people are working on items) for the Pharo 6
> roadmap
>
> and we will consolidate them soon and propose them to you.
>
> but I would like to know two kinds of points
>
> - what are the points you are working on
My Christmas list is divided to 2 sections a) What I want from you b) What
I am going to deliver
*What I want from you*
The things I want from Pharo are centered on the high priorities
a) 64 bit version
b) Bloc /SDL
c) FFI documentation / stabilization
Its f
Le 26/8/16 à 14:40, Norbert Hartl a écrit :
Hi,
the things I want to have are 64bit, bootstrap and vector graphic
backend because these are so disruptive that it takes some time to
stabilize the whole system. But there is a roadmap for this which is
ok for me.
For me we really need to foc
List:
* image size management under control
Yes it requires to write a new GC so I hope that the VM team with get
the ressources.
* no more gradients in that UI (even in the light theme)
* modern "Material style" UI
* FASTER Nautilus
what is the problem?
* better console support (in/out)
Hi,
the things I want to have are 64bit, bootstrap and vector graphic backend
because these are so disruptive that it takes some time to stabilize the whole
system. But there is a roadmap for this which is ok for me.
For me we really need to focus on stabilizing a few things which are (to me)
List:
* image size management under control
* no more gradients in that UI (even in the light theme)
* modern "Material style" UI
* FASTER Nautilus
* better console support (in/out)
* Pharo VM as something I can embed in other programs
* something like npm.js for the packages list along with exter
Thanks Peter
I cannot find the list, but there were some things we discussed during
consortium call a month or so ago. Maybe Esteban can find it?
I want for Christmas
* Better Spec
* Roadmap so we know where we are going,
* with clean API,
* so we can build really live UIs (where you ca
I cannot find the list, but there were some things we discussed during
consortium call a month or so ago. Maybe Esteban can find it?
I want for Christmas
* Better Spec
* Roadmap so we know where we are going,
* with clean API,
* so we can build really live UIs (where you can drag windows ar
Hi
We have some ideas (because people are working on items) for the Pharo 6
roadmap
and we will consolidate them soon and propose them to you.
but I would like to know two kinds of points
- what are the points you are working on and that would deserve
more focus and help from the commun
27 matches
Mail list logo