[tode_st] tODE & GCI in Pharo 5?

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg)

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg) 

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

Cheers,

 

Dale

[1] https://github.com/dalehenrich/Tugrik

On 03/29/2016 08:59 AM, Tudor Girba wrote:

Hi,

Is there a plan to have tODE or at least the GCI library ported to Pharo 5?

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Hi Dale,

Ok, I started with this. I created a baseline, I refactored a bit the session description used for unit testing and added some help to the README (this is temp help notes but I wanted to write them down now while I am at it than later...).

Following the instructions you can find in the README, I managed to run some tests, but only #testGciLogin and #testGetGciErrSType passed. All the rest of the tests are still red. I am still talking on Pharo 3.0, obviously hahahha.

Any idea why would the rest fail? Do they work for you in your Tugrik setup?

On Tue, Mar 29, 2016 at 5:13 PM, Dale Henrichs <[hidden email]> wrote:

Mariano,

Barebones split ... no baseline, but you can look at the Tugrik baseline for load order ... the GemStone-GCI-Server-Tests.package should be loaded into GemStone as it provides a set of methods that are called by the client-side tests ...

I think this should be enough to get you going --- when you have a chance ...

Dale

[1] https://github.com/GsDevKit/GemStone-GCI

On 03/29/2016 12:15 PM, Mariano Martinez Peck wrote:

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg) 

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

Cheers,

 

Dale

[1] https://github.com/dalehenrich/Tugrik

On 03/29/2016 08:59 AM, Tudor Girba wrote:

Hi,

Is there a plan to have tODE or at least the GCI library ported to Pharo 5?

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Do you have some error stacks? AFAIK they all passed .... it has been awhile since I ran the gci tests explicitly as I was working on the server side support ... but running the Tugrik tests excercises most of the GCI ... a stack will job my memory ...

Dale

On 03/29/2016 02:35 PM, Mariano Martinez Peck wrote:

Hi Dale,

Ok, I started with this. I created a baseline, I refactored a bit the session description used for unit testing and added some help to the README (this is temp help notes but I wanted to write them down now while I am at it than later...).

Following the instructions you can find in the README, I managed to run some tests, but only #testGciLogin and #testGetGciErrSType passed. All the rest of the tests are still red. I am still talking on Pharo 3.0, obviously hahahha.

Any idea why would the rest fail? Do they work for you in your Tugrik setup?

On Tue, Mar 29, 2016 at 5:13 PM, Dale Henrichs <[hidden email]> wrote:

Mariano,

Barebones split ... no baseline, but you can look at the Tugrik baseline for load order ... the GemStone-GCI-Server-Tests.package should be loaded into GemStone as it provides a set of methods that are called by the client-side tests ...

I think this should be enough to get you going --- when you have a chance ...

Dale

[1] https://github.com/GsDevKit/GemStone-GCI

On 03/29/2016 12:15 PM, Mariano Martinez Peck wrote:

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg) 

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

Cheers,

 

Dale

[1] https://github.com/dalehenrich/Tugrik

On 03/29/2016 08:59 AM, Tudor Girba wrote:

Hi,

Is there a plan to have tODE or at least the GCI library ported to Pharo 5?

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Do you have some error stacks? AFAIK they all passed .... it has been awhile since I ran the gci tests explicitly as I was working on the server side support ... but running the Tugrik tests excercises most of the GCI ... a stack will job my memory ...

Dale

On 03/29/2016 02:35 PM, Mariano Martinez Peck wrote:

Hi Dale,

Ok, I started with this. I created a baseline, I refactored a bit the session description used for unit testing and added some help to the README (this is temp help notes but I wanted to write them down now while I am at it than later...).

Following the instructions you can find in the README, I managed to run some tests, but only #testGciLogin and #testGetGciErrSType passed. All the rest of the tests are still red. I am still talking on Pharo 3.0, obviously hahahha.

Any idea why would the rest fail? Do they work for you in your Tugrik setup?

On Tue, Mar 29, 2016 at 5:13 PM, Dale Henrichs <[hidden email]> wrote:

Mariano,

Barebones split ... no baseline, but you can look at the Tugrik baseline for load order ... the GemStone-GCI-Server-Tests.package should be loaded into GemStone as it provides a set of methods that are called by the client-side tests ...

I think this should be enough to get you going --- when you have a chance ...

Dale

[1] https://github.com/GsDevKit/GemStone-GCI

On 03/29/2016 12:15 PM, Mariano Martinez Peck wrote:

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg) 

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

Cheers,

 

Dale

[1] https://github.com/dalehenrich/Tugrik

On 03/29/2016 08:59 AM, Tudor Girba wrote:

Hi,

Is there a plan to have tODE or at least the GCI library ported to Pharo 5?

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Do you have some error stacks? AFAIK they all passed .... it has been awhile since I ran the gci tests explicitly as I was working on the server side support ... but running the Tugrik tests excercises most of the GCI ... a stack will job my memory ...

Dale

On 03/29/2016 02:35 PM, Mariano Martinez Peck wrote:

Hi Dale,

Ok, I started with this. I created a baseline, I refactored a bit the session description used for unit testing and added some help to the README (this is temp help notes but I wanted to write them down now while I am at it than later...).

Following the instructions you can find in the README, I managed to run some tests, but only #testGciLogin and #testGetGciErrSType passed. All the rest of the tests are still red. I am still talking on Pharo 3.0, obviously hahahha.

Any idea why would the rest fail? Do they work for you in your Tugrik setup?

On Tue, Mar 29, 2016 at 5:13 PM, Dale Henrichs <[hidden email]> wrote:

Mariano,

Barebones split ... no baseline, but you can look at the Tugrik baseline for load order ... the GemStone-GCI-Server-Tests.package should be loaded into GemStone as it provides a set of methods that are called by the client-side tests ...

I think this should be enough to get you going --- when you have a chance ...

Dale

[1] https://github.com/GsDevKit/GemStone-GCI

On 03/29/2016 12:15 PM, Mariano Martinez Peck wrote:

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg) 

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

Cheers,

 

Dale

[1] https://github.com/dalehenrich/Tugrik

On 03/29/2016 08:59 AM, Tudor Girba wrote:

Hi,

Is there a plan to have tODE or at least the GCI library ported to Pharo 5?

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Do you have some error stacks? AFAIK they all passed .... it has been awhile since I ran the gci tests explicitly as I was working on the server side support ... but running the Tugrik tests excercises most of the GCI ... a stack will job my memory ...

Dale

On 03/29/2016 02:35 PM, Mariano Martinez Peck wrote:

Hi Dale,

Ok, I started with this. I created a baseline, I refactored a bit the session description used for unit testing and added some help to the README (this is temp help notes but I wanted to write them down now while I am at it than later...).

Following the instructions you can find in the README, I managed to run some tests, but only #testGciLogin and #testGetGciErrSType passed. All the rest of the tests are still red. I am still talking on Pharo 3.0, obviously hahahha.

Any idea why would the rest fail? Do they work for you in your Tugrik setup?

On Tue, Mar 29, 2016 at 5:13 PM, Dale Henrichs <[hidden email]> wrote:

Mariano,

Barebones split ... no baseline, but you can look at the Tugrik baseline for load order ... the GemStone-GCI-Server-Tests.package should be loaded into GemStone as it provides a set of methods that are called by the client-side tests ...

I think this should be enough to get you going --- when you have a chance ...

Dale

[1] https://github.com/GsDevKit/GemStone-GCI

On 03/29/2016 12:15 PM, Mariano Martinez Peck wrote:

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg) 

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

Cheers,

 

Dale

[1] https://github.com/dalehenrich/Tugrik

On 03/29/2016 08:59 AM, Tudor Girba wrote:

Hi,

Is there a plan to have tODE or at least the GCI library ported to Pharo 5?

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Thanks Dale.

Ok, with your commit, the only failing test is #testSigAbortHandlingNew.

And then, both tests of GsGciTsTest raise "Cannot return the given type" to me. Does this also happen to you?

Cheers,

On Tue, Mar 29, 2016 at 7:10 PM, Dale Henrichs <[hidden email]> wrote:

done ... btw the sigabort tests will fail (after a hang) if you have any gems logged into the test stone ...

Dale

On 03/29/2016 02:57 PM, Dale Henrichs wrote:

Do you have some error stacks? AFAIK they all passed .... it has been awhile since I ran the gci tests explicitly as I was working on the server side support ... but running the Tugrik tests excercises most of the GCI ... a stack will job my memory ...

Dale

On 03/29/2016 02:35 PM, Mariano Martinez Peck wrote:

Hi Dale,

Ok, I started with this. I created a baseline, I refactored a bit the session description used for unit testing and added some help to the README (this is temp help notes but I wanted to write them down now while I am at it than later...).

Following the instructions you can find in the README, I managed to run some tests, but only #testGciLogin and #testGetGciErrSType passed. All the rest of the tests are still red. I am still talking on Pharo 3.0, obviously hahahha.

Any idea why would the rest fail? Do they work for you in your Tugrik setup?

On Tue, Mar 29, 2016 at 5:13 PM, Dale Henrichs <[hidden email]> wrote:

Mariano,

Barebones split ... no baseline, but you can look at the Tugrik baseline for load order ... the GemStone-GCI-Server-Tests.package should be loaded into GemStone as it provides a set of methods that are called by the client-side tests ...

I think this should be enough to get you going --- when you have a chance ...

Dale

[1] https://github.com/GsDevKit/GemStone-GCI

On 03/29/2016 12:15 PM, Mariano Martinez Peck wrote:

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg) 

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

Cheers,

 

Dale

[1] https://github.com/dalehenrich/Tugrik

On 03/29/2016 08:59 AM, Tudor Girba wrote:

Hi,

Is there a plan to have tODE or at least the GCI library ported to Pharo 5?

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

On Tue, Mar 29, 2016 at 8:27 PM, Dale Henrichs <[hidden email]> wrote:

Does the new FFI block the image on function calls? If so, then the thread safe libraries aren't that useful, since they don't currently include non-blocking variants. The point of the thread safe library is allow one to safely make concurrent GCI calls, but if a single FFI calls blocks the image, you can't have more than one in progress anyway ... VW arranges to make FFI calls in a separate os thread, so blocking the thread is not an issue ...

No, threaded callouts are not yet supported. 

 

We can leave the thread safe stuff out of CORE group and not bother with it ...

Yes, that's a good idea. 

 

Dale

On 03/29/2016 04:12 PM, Mariano Martinez Peck wrote:

Thanks Dale.

Ok, with your commit, the only failing test is #testSigAbortHandlingNew.

And then, both tests of GsGciTsTest raise "Cannot return the given type" to me. Does this also happen to you?

Cheers,

On Tue, Mar 29, 2016 at 7:10 PM, Dale Henrichs <[hidden email]> wrote:

done ... btw the sigabort tests will fail (after a hang) if you have any gems logged into the test stone ...

Dale

On 03/29/2016 02:57 PM, Dale Henrichs wrote:

Do you have some error stacks? AFAIK they all passed .... it has been awhile since I ran the gci tests explicitly as I was working on the server side support ... but running the Tugrik tests excercises most of the GCI ... a stack will job my memory ...

Dale

On 03/29/2016 02:35 PM, Mariano Martinez Peck wrote:

Hi Dale,

Ok, I started with this. I created a baseline, I refactored a bit the session description used for unit testing and added some help to the README (this is temp help notes but I wanted to write them down now while I am at it than later...).

Following the instructions you can find in the README, I managed to run some tests, but only #testGciLogin and #testGetGciErrSType passed. All the rest of the tests are still red. I am still talking on Pharo 3.0, obviously hahahha.

Any idea why would the rest fail? Do they work for you in your Tugrik setup?

On Tue, Mar 29, 2016 at 5:13 PM, Dale Henrichs <[hidden email]> wrote:

Mariano,

Barebones split ... no baseline, but you can look at the Tugrik baseline for load order ... the GemStone-GCI-Server-Tests.package should be loaded into GemStone as it provides a set of methods that are called by the client-side tests ...

I think this should be enough to get you going --- when you have a chance ...

Dale

[1] https://github.com/GsDevKit/GemStone-GCI

On 03/29/2016 12:15 PM, Mariano Martinez Peck wrote:

On Tue, Mar 29, 2016 at 3:58 PM, Dale Henrichs <[hidden email]> wrote:

Yes, there is a plan ...

I have been waiting for Pharo 5.0 to stabilize before jumping in ... also I am assuming that the FFI api has changed significantly -- is that true? If so, the hard work will be porting to the new FFI ...

I have recently started work on Tugrik[1] (for Pharo 4.0) and part of the project is to do a cleaner implementation of the GCI libraries, so for Pharo 5.0, I would probably start with the GCI libraries from Tugrik, port them to Pharo5.0 and then port tODE to using the new GCI libraries ...

wow... is Tugrik the idea you talked to me years ago with Martin? (In Edinburg) 

 

With all of the other work I am doing, I don't know when I will get around to Pharo5.0, but if you are interested in helping, I would be willing to split the GCI library work out from Tugrik into a separate project and help with the sticky bits in the port of the GCI libraries to Pharo5.0 ... then tODE would follow on once the GCI libraries were ported ...

Dale, I personally think that having the CGI libs in a separate repository makes A LOT OF SENSE, wether we will gonna give it a try right now or not. See...GemTools needed them. Then you copy them and put them inside tODE. Now you need it too for Tugrik. And now we may want to fork it and make it work in Pharo 5.0 ;)

As part of my work with the Pharo Consortium and OSSubprocess I did work with the new FFI. So I can give a hand here. You even have tests for it:  https://github.com/dalehenrich/Tugrik/tree/master/repository/GemStone-GCI-Tests.package/GsGciTest.class/instance

So... I think it's a matter of defining a new home for CGI lib, fork it, and start giving it a try in Pharo 5.0 with new FFI. 

If you move these guys into a separate repository (on github) that I can load them into a fresh Pharo 5.0, I will do my best to do the first try when time allows me. Note that that doesn't mean you have to remove them from Tugrik, updates it ConfigurationOf etc...we can do that later. Just copy them to a new repo and once we have tests working in Pharo 3/4 then we start with 5.0. 

Cheers,

 

Dale

[1] https://github.com/dalehenrich/Tugrik

On 03/29/2016 08:59 AM, Tudor Girba wrote:

Hi,

Is there a plan to have tODE or at least the GCI library ported to Pharo 5?

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Next time you see your life passing by, say 'hi' and get to know her."

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--

Mariano
http://marianopeck.wordpress.com

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

On Tue, Mar 29, 2016 at 8:36 PM, Dale Henrichs <[hidden email]> wrote:

Cool!

I am working on trying to figure out a way to make smalltalkCI run gemstone and pharo, so that travis/smalltalkCI can be used to run the Pharo-based GCI tests ...

Yes, that would be nice!!!

BTW, I just pushed the missing bit in the readme of copying the libcgi* libs.

Those steps would be the requiered ones for Travis. 

BTW2... it would be nice if:

1) You can also build the custom todeClient so that you know from where to copy the libcgi. Or even better... call your download script from gsDevKit_home to put the cgilibs in the pharo 3.0 vm.

2) You can replace my instructions on how to load cgi into gemstone with a todeIt script :)

I know how do to it for Pharo ;)   

That way we can also automate all that.

BTW3 In my original tode vm image I have a very large hierarchy of GciLibrary (GciLibrary allSubclasses size -> 7) for all combinations of of Gemstone 3.2, 2.2. etc etc. But with the project we are working now, we ONLY have GsGci32xLibrary. So....that means that this new CGI wrapper will only work for 3.2..... do we agree??