I understand that it makes a lot of sense to reuse the functions
implemented in the FossilRepo.
Installation of the Fossil version control system seems to be very
simple, just put a single executable file into the pharo folder for
example
https://fossil-scm.org/index.html/doc/trunk/www/index.wi
So at the moment I am fine to get it up and running using a FossilRepo.
Later on I will work on replacing it with a JSON data store.
On 9/6/17, H. Hirzel wrote:
> I understand that it makes a lot of sense to reuse the functions
> implemented in the FossilRepo.
>
> Installation of the Fossil vers
We are looking for new developers at ZWEIDENKER (the company formerly known as
2denker :) ). So if you are at ESUG right now and you are interested please
either contact me in person or reply to this email and I will get in contact
with you.
See you,
Norbert
Hi Tim.
Sorry for late response. During Esug I am a bit out of mails.
About saving method problem it is definitely a bug. Thank's for the report.
About source code refactoring:
Supporting source code commands was easy to do with suggestions. In fact
text editor menu is still working old way. Tha
Hey Denis - I didn't mean to interrupt your ESUG (I should have mentioned it
was something to follow up on afterwards). Enjoy it and help lots of ideas.
Should I raise a bug for the saving issue in fogbugz?
I'll have to look at how you add define shortcuts in Calypso as I'm not
familiar with th
Hi everyone,
I built a little syntax highlighting extension for the Nautilus source code
pane, which puts a background color behind blocks, so that nested blocks are
easily recognizable.
Install with:
Metacello new
baseline: 'BlockStyler';
repository: 'github://maenu/BlockSty
Hello Pharo-ers !
On behalf of the community, I would like to thank each one of you for their
significant contribution in the recently concluded *Google Summer of Code
2017* with *Pharo Consortium*. We aspire to take-off on a long flight after
this successful stint. In this spirit, I proposed at E
Hi,
On 06/09/17 02:12, H. Hirzel wrote:
> So at the moment I am fine to get it up and running using a FossilRepo.
> Later on I will work on replacing it with a JSON data store.
Please let me know if you need any permissions into the repository to
make JSON data store available in Brea.
>
> On 9
It isn't only #changeDirectory: method that is missing. Method
#workingDirectoryPath: and instance variable workingDirectory are also
missing.
FileSystem >> changeDirectory: aPath
self workingDirectoryPath: (self resolve: aPath)
FileSystem >> workingDirectoryPath: aPath
aPath isAbsolute
i
On Wed, Sep 06, 2017 at 10:50:05AM -0700, Andreas Sunardi wrote:
> It isn't only #changeDirectory: method that is missing. Method #
> workingDirectoryPath: and instance variable workingDirectory are also
> missing.
>
> FileSystem >> changeDirectory: aPath
> self workingDirectoryPath: (self res
Hi Stef,
I think you are correct and you would still always perform actions like:
initializeWidgets (to create components and sub-components)
initializePresenter (to define interactions between components)
But, there could also be a third initialization step like
initializeSubject: aSubjectMod
Hi Alistair,
I found fogbugz #19717 where this was discussed.
https://pharo.fogbugz.com/f/cases/19717/FileSystem-workingDirectory-wrong-after-image-moved-to-a-new-folder
The issue seems to be the current working directory is saved in instance
variable workingDirectory. When the image is moved to
Hi Manuel
This is coool.
How linked to nautilus it is?
Stef
On Wed, Sep 6, 2017 at 1:52 PM, Manuel Leuenberger wrote:
> Hi everyone,
>
> I built a little syntax highlighting extension for the Nautilus source
> code pane, which puts a background color behind blocks, so that nested
> blocks
> Hi Stef,
>
> I think you are correct and you would still always perform actions like:
>
> initializeWidgets (to create components and sub-components)
> initializePresenter (to define interactions between components)
>
>
> But, there could also be a third initialization step like
>
> initializeSub
Thanks a lot andreas!!
On Thu, Sep 7, 2017 at 1:53 AM, Andreas Sunardi wrote:
> Hi Alistair,
>
> I found fogbugz #19717 where this was discussed.
>
> https://pharo.fogbugz.com/f/cases/19717/FileSystem-workingDirectory-wrong-after-image-moved-to-a-new-folder
>
> The issue seems to be the curre
Tim
Oh yes. There are still part of Pharo that we did not clean.
Stef
On Fri, Sep 1, 2017 at 1:39 PM, Tim Mackinnon wrote:
> Thanks Thierry - this is proving an interesting problem domain ...
>
> I too am using #bestNodeFor: although I don't find it always gives the best
> node (it does if you
Hi Andreas,
On Wed, Sep 06, 2017 at 04:53:27PM -0700, Andreas Sunardi wrote:
> Hi Alistair,
>
> I found fogbugz #19717 where this was discussed.
>
> https://pharo.fogbugz.com/f/cases/19717/
> FileSystem-workingDirectory-wrong-after-image-moved-to-a-new-folder
>
> The issue seems to be the curre
17 matches
Mail list logo
