Issue 4130 in pharo: Zinc should be added to core

Status: FixToInclude
Owner: [hidden email]
Labels: Milestone-1.3

New issue 4130 by [hidden email]: Zinc should be added to core
http://code.google.com/p/pharo/issues/detail?id=4130

We should add Zinc to Core


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 4130 by [hidden email]: Zinc should be added to  
core
http://code.google.com/p/pharo/issues/detail?id=4130

Gofer it
   squeaksource: 'ZincHTTPComponents';
   package: 'Zinc-HTTP';
   package: 'Zinc-Tests';
   load
If you also want to destructively replace all existing HTTP client  
functionality in your Smalltalk image, execute the following script:

Gofer it
   squeaksource: 'ZincHTTPComponents';
   package: 'Zinc-HTTP';
   package: 'Zinc-Tests';
   package: 'Zinc-Patch-HTTPSocket';
   load
Warning: loading of 'Zinc-Patch-HTTPSocket' is a bit harder to undo, you  
have to reload the package containing the class  
HTTPSocket, 'Network-Protocols' from its original source.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 4130 by [hidden email]: Zinc should be added to  
core
http://code.google.com/p/pharo/issues/detail?id=4130

Hi Stef,

We talked about this during the Pharo sprint in Brussels.

Zn was written explicitely in the hope that it could become the default  
http client and server functionality in Pharo. So yes, let's do this. I  
think that the current state of Zn is many times better than what is  
available now in HTTPSocket. For that reason alone, this is worth doing.

My only concern is that I would like to keep on evolving Zn independently  
as well. I want to be able to move faster with more experimental stuff,  
while the version in Pharo Core would track only stable releases that are  
proven a bit in the field. I would also like to maintain compatibility with  
Gemstone and to a lesser degree Squeak and maybe other Smalltalks.

Is is conceiveable to leave Zn in its current namespace ? I think that  
would be easiest, no ? That way, I and others who want to track the  
bleeding edge version can just load over what is already present in Core  
and be done.

What do you and the other think ?

Sven



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 4130 by marianopeck: Zinc should be added to core
http://code.google.com/p/pharo/issues/detail?id=4130

THere are a couple of "external maintained" packages that are in the core  
already: Gofer, HelpSystem, etc....So you will one more. Right now, I agree  
to what you said. You follow your development in your repository and then  
just for stable releases you move it to pharo core.

In a fure we can use Metacello...


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 4130 by [hidden email]: Zinc should be added to  
core
http://code.google.com/p/pharo/issues/detail?id=4130

We did that some some years and even now with polymorph.
You push versions you like in the system and you can be experimenting on  
your branch.
This is working well for us.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #5 on issue 4130 by [hidden email]: Zinc should be added to  
core
http://code.google.com/p/pharo/issues/detail?id=4130

OK, these could be considered released versions (they were marked as such  
in SqueakSource):

Zinc-HTTP-SvenVanCaekenberghe.150.mcz
Zinc-Tests-SvenVanCaekenberghe.77.mcz
Zinc-Patch-HTTPSocket-SvenVanCaekenberghe.1.mcz

I guess someone of the main integrators should do this, there is not much  
point in making a slice I guess.

Sven


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #6 on issue 4130 by [hidden email]: Zinc should be added to  
core
http://code.google.com/p/pharo/issues/detail?id=4130

Ok I will do that.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #7 on issue 4130 by [hidden email]: Zinc should be added to  
core
http://code.google.com/p/pharo/issues/detail?id=4130

in 13196


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #8 on issue 4130 by [hidden email]: Zinc should be added to  
core
http://code.google.com/p/pharo/issues/detail?id=4130

Thank you.

This gives me a nice feeling.

I guess, it comes with some future responsabilities as well ;-)

Sven


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker