[Pharo-users] Sharing data between images

[Dimitris Chloupis]

Just wondering what my options are about sharing data between images,
should I use Ston ? A database ? something else ?

I would prefer options that have as few dependencies as possible and
something that does not require from my users to install external stuff.

For now Ston looks like a good option but I am very new to all this so I
would welcome any advice from the pharo experts.

Re: [Pharo-users] Sharing data between images

[Johan Fabry]

Hi,

have a look at Fuel, It’s included in the image. See 
http://files.pharo.org/books/enterprisepharo/book/Fuel/Fuel.html 
 for more 
info.

> On Nov 29, 2015, at 11:57, Dimitris Chloupis  wrote:
> 
> Just wondering what my options are about sharing data between images, should 
> I use Ston ? A database ? something else ?
> 
> I would prefer options that have as few dependencies as possible and 
> something that does not require from my users to install external stuff. 
> 
> For now Ston looks like a good option but I am very new to all this so I 
> would welcome any advice from the pharo experts. 



---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
Chile

Re: [Pharo-users] Sharing data between images

[Sven Van Caekenberghe]

Fuel is binary, faster and store more special kinds of objects. STON is 
textual, you can read and edit it, better suited for model objects.

> On 29 Nov 2015, at 16:35, Johan Fabry  wrote:
> 
> Hi,
> 
> have a look at Fuel, It’s included in the image. See 
> http://files.pharo.org/books/enterprisepharo/book/Fuel/Fuel.html for more 
> info.
> 
>> On Nov 29, 2015, at 11:57, Dimitris Chloupis  wrote:
>> 
>> Just wondering what my options are about sharing data between images, should 
>> I use Ston ? A database ? something else ?
>> 
>> I would prefer options that have as few dependencies as possible and 
>> something that does not require from my users to install external stuff. 
>> 
>> For now Ston looks like a good option but I am very new to all this so I 
>> would welcome any advice from the pharo experts. 
> 
> 
> 
> ---> Save our in-boxes! http://emailcharter.org <---
> 
> Johan Fabry   -   http://pleiad.cl/~jfabry
> PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
> Chile
> 

Re: [Pharo-users] Sharing data between images

[Sebastian Heidbrink]

I used message pack before.
Nice thing is that you can easily also integrate to other environments.

https://github.com/msgpack/msgpack-smalltalk
http://smalltalkhub.com/#!/~MasashiUmezawa/MessagePack

Seabstian


On 2015-11-29 6:57 AM, Dimitris Chloupis wrote:
Just wondering what my options are about sharing data between images, 
should I use Ston ? A database ? something else ?


I would prefer options that have as few dependencies as possible and 
something that does not require from my users to install external stuff.


For now Ston looks like a good option but I am very new to all this so 
I would welcome any advice from the pharo experts.

Re: [Pharo-users] [Pharo5] Semantic Warnings as icons in the editor

[stepharo]

I'm happy to see all the pieces coming together. It was thinking about 
it that we worked with frank and alain on putting rubric in place and 
now it pays off :).


Stef

Le 28/11/15 23:01, Marcus Denker a écrit :

Hi,

One result of Friday’s Pharo Sprint in Chile: Use the nice icons of 
the new text editor
to display some of the semantic errors nicely (instead of breaking 
flow with a intrusive dialog):


This was done by Johan based on the prototype Miguel did in September:

1) unused temps:


(the “drag the crosshair”r is an artefact of the snapshot tool)

2) temps used that are not initialised:



In a next step, we need to integrate that with the QA tool… no need to 
have this reported

twice.

What is nice is that this simplified the Compiler: instead of having 
an Exception and raising

it, we now just annotate the AST:

unusedVariable: variableNode

variableNode propertyAt: #semanticWarning put: 'unused variable’

(this is very simple for now, with a node just being able to have one 
kind of semanticWarning).


SemanticWarningIconStyler is what adds the icon. It has 4 methods with 
one line each.


Marcus

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

[stepharo]

What I would like for Pharo is to avoid to be bound to a given back-end 
for its versionning.

This master is a step in the right direction

http://www.hpi.uni-potsdam.de/fileadmin/hpi/source/Technische_Berichte/HPI_54.pdf

Stef

Re: [Pharo-users] Sharing data between images

[Dimitris Chloupis]

" have a look at Fuel, It’s included in the image. See
http://files.pharo.org/books/enterprisepharo/book/Fuel/Fuel.html for more
info."



FUEL !!! Lol how I forgot about it ? Nice , I think its exactly what I was
looking for , thanks.

"Fuel is binary, faster and store more special kinds of objects. STON is
textual, you can read and edit it, better suited for model objects."

Yeah both options look very good, I think I may need something fast because
I may end up with a lot of data (3d graphics data). So I will go with Fuel.

The nice thing about STON is that because is JSON it will be easier to move
between different languages. But then nothing stops me from choosing Fuel
and making also a JSON exporter with STON.

"I used message pack before.
Nice thing is that you can easily also integrate to other environments."

Thanks will take a look at this as well.

Re: [Pharo-users] Spec: Binding widgets how to

[Nicolai Hess]

2015-11-26 19:36 GMT+01:00 Offray Vladimir Luna Cárdenas 
:

> Hi,
>
> I had tried that before and didn't work. Passing information between
> widgets and back in this spec interface seems my stop point now... If
> someone could help me with some kind of minimalist example that uses
> treeModel, that would be greatly appreciated.
>

Find attached a minimal example. (I use Morph and its subclasses for
generating some tree data, these are just names, renaming a node does not
rename the class :))

You can listen on tree node selection by registering with
#whenSelectedChanged, on the TreeNode(!)

"create the node"
t :=  TreeNodeModel new
content: aClass name;
hasChildren: [ aClass subclasses notEmpty ];
children: [ subItems ifNil:[subItems:=aClass subclasses collect: [
:s | self buildNodeFor: s ] ]];
yourself.

"listen on selection"
t whenSelectedChanged: [ :bool | bool ifTrue:[self field text: t content] ].

this will change the text field content with the content of the node (the
default label).

Changing the label node *Morph* on accepting the text field text is somehow
impossible or difficult.
I would have expected that Spec would create a MorphicTreeNodeAdapter that
represents some Morph, for which the adapter would update/change the state,
if you change
the TreeNodeModel content.
Instead, it creates some strange SpecTreeNodeModel. And the only way to
update the NodeLabel and make this change visible is to
rebuild the whole tree:

tree roots: tree roots.

Yes, I did not find another way.

Luckily MorphTreeMorph is smart enough to remember the selection and path
expansion state, so this works quite well.



>
> Cheers,
>
> Offray
>
>
> On 26/11/15 12:47, webwarrior wrote:
>
>> Try #whenHighlightedItemChanged: method.
>>
>> I remember that distinction between selection/highlight is not very clear
>> in
>> TreeModel.
>>
>>
>>
>> --
>> View this message in context:
>> http://forum.world.st/Spec-Binding-widgets-how-to-tp4863742p4863757.html
>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>>
>>
>>
>
>


Tree-TextField-Demo-NicolaiHess.2.mcz
Description: Binary data

Re: [Pharo-users] Basic versioning of GitHub repositories from within Pharo

[Dimitris Chloupis]

And there lies the trap.

If you end up making something that works with everything, you will create
something that just works with everything instead of something that works
very well with one thing. Right now Git is by very far the undisputed king
of version control and has completely dethroned SVN.

Ironically the things that make git integration in pharo so hard is all the
thing that are there to decouple it from git , like filetree metadata , or
continuous support for mcz and monticello.

In the end you cant have your cake and eat it too. We will have to choose
between very good integration with git or average / mediocre integration
with multiple backends.

On Sun, Nov 29, 2015 at 8:15 PM stepharo  wrote:

> What I would like for Pharo is to avoid to be bound to a given back-end
> for its versionning.
> This master is a step in the right direction
>
>
> http://www.hpi.uni-potsdam.de/fileadmin/hpi/source/Technische_Berichte/HPI_54.pdf
>
> Stef
>
>
>

[Pharo-users] graph library in Pharo

[Peter Uhnak]

Hi,

is there any graph library for pharo with algorithms for planarity
testing, spanning trees, flow costs, etc.?

Thanks,
-- 
Peter

Re: [Pharo-users] graph library in Pharo

[Alexandre Bergel]

There are a few algorithms in the moose distribution. Maybe you can check them.
Which algo do you really need?

Cheers,
Alexandre


> On Nov 29, 2015, at 5:29 PM, Peter Uhnak  wrote:
> 
> Hi,
> 
> is there any graph library for pharo with algorithms for planarity
> testing, spanning trees, flow costs, etc.?
> 
> Thanks,
> -- 
> Peter
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-users] graph library in Pharo

[Peter Uhnák]

I need at least (mixed/upward)-planarity testing, embedding, spanning
tree, flow, assignment, ...

I've seen the Moose-Algos, but from what I need it contains only
Kruskal (spanning tree).

So ideally I would like to just load a project instead having to
implement them all by myself, because most of them are very complex.

Peter

On Sun, Nov 29, 2015 at 11:35 PM, Alexandre Bergel
 wrote:
> There are a few algorithms in the moose distribution. Maybe you can check 
> them.
> Which algo do you really need?
>
> Cheers,
> Alexandre
>
>
>> On Nov 29, 2015, at 5:29 PM, Peter Uhnak  wrote:
>>
>> Hi,
>>
>> is there any graph library for pharo with algorithms for planarity
>> testing, spanning trees, flow costs, etc.?
>>
>> Thanks,
>> --
>> Peter
>>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>

Re: [Pharo-users] Pharo RDBMS Support Survey

[EuanM]

I completed it.

(There was one question that I found hard to understand - so I
commented my response heavily.  I can't remember what my issue was -
but my comments would remind me)

On 26 November 2015 at 03:02, Esteban A. Maringolo  wrote:
> Hello all,
>
> I just created this survey (https://goo.gl/pcc9u8) to collect
> information about the users of RDBMS in Pharo.
>
> Please promote it in the social networks, so I can get as many
> responses as possible.
>
> URL: https://goo.gl/pcc9u8
>
> I'll share the results in a month or before if I get 100 responses. :)
>
>
> Thank you!
>
>
>
> Esteban A. Maringolo
>

Re: [Pharo-users] Pharo Consortium New Gold Member: Thales

[EuanM]

That's great news.

It would be really interesting, and really useful to
community-enlargement works, to know:
  Which part of Thales drove this?
  What is their specific interest in Pharo?  Or what is their current
(or proposed) use of Pharo?





On 26 November 2015 at 13:42,   wrote:
> The Pharo Consortium is very happy to announce that Thales
> has joined the Consortium as an Gold Member.
>
> About
> - Thales: https://www.thalesgroup.com
> - Pharo Consortium: http://consortium.pharo.org
>
> The goal of the Pharo Consortium is to allow companies and institutions to
> support the ongoing development and future of Pharo.
>
> Individuals can support Pharo via the Pharo Association:
>
>   http://association.pharo.org
>