[Pharo-users] Chip-8
Hi, I just read an fun article about Chip-8. Someone has worked on an emulator of this with Pharo? http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interpreter/ http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ Best regards
Re: [Pharo-users] Chip-8
Wow it would be a fun project! I know there was GameBoy [1] emulator but I don't know if it is still working. Julien Links: [1]: http://smalltalkhub.com/#!/~jeanbaptistearnaud/GameBoyEmulator On 16/11/16 11:21, olivier auverlot wrote: Hi, I just read an fun article about Chip-8. Someone has worked on an emulator of this with Pharo? http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interpreter/ http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ Best regards
[Pharo-users] Chip8
I would like to know if one of you implemented chip8 in Pharo? http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interpreter/ https://github.com/miguelduarte42/Jhip8
Re: [Pharo-users] Chip-8
Le 16/11/16 à 11:40, Julien Delplanque a écrit : Wow it would be a fun project! Yes I want to play with that :) I know there was GameBoy [1] emulator but I don't know if it is still working. Julien Links: [1]: http://smalltalkhub.com/#!/~jeanbaptistearnaud/GameBoyEmulator On 16/11/16 11:21, olivier auverlot wrote: Hi, I just read an fun article about Chip-8. Someone has worked on an emulator of this with Pharo? http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interpreter/ http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ Best regards
Re: [Pharo-users] Chip-8
very interesting article thanks for sharing. I was actually wondering about bytecodes and emulation lately with my shared memory bridge. I will definitely keep this around as a guide. On Wed, Nov 16, 2016 at 12:22 PM olivier auverlot < olivier.auver...@gmail.com> wrote: > Hi, > > I just read an fun article about Chip-8. Someone has worked on an emulator > of this with Pharo? > > > http://www.multigesture.net/articles/how-to-write-an-emulator-chip-8-interpreter/ > http://miguelduarte.pt/2012/07/09/chip-8-emulator-in-javascript/ > > Best regards >
Re: [Pharo-users] Pier3 with latest Pillar?
Hey Stephane, >> It would be nice to see Pillar return to being a cross platform project as >> well. One of the beautiful things about Seaside/Magritte/Pier was it’s >> compatibility across many dialects of Smalltalk. The “develop in Pharo and >> deploy in GemStone” was a big draw for me :) One of my clients uses VW so it >> was great to have these projects there as well. > Yes but at the end of the day. You see we cannot work for free and in > addition got constraints that are dragging us behind. Absolutely! Luckily the hard work of cross-compatability has already been done for Pier. I’m just hoping we can keep the parts of Pillar on which Pier is reliant working across dialects - Pharo and GemStone at least. From memory, the only thing that made it hard was PRTParametrizable. I imagine very few of us are being paid for the contributions we make. In my case, it’s only when I have a paid project that allows me to work in Smalltalk, that I can invest some of that paid time in contributing towards the packages I’m using for that project. I also feel my smalltalk-ability isn’t up to the standard of so many of the amazing people contributing, which makes me a little reticent to get involved in the more complex projects. > I will see if the trait usage make sense and can be removed. But you see if > everything we do has to be compatible better be dead. Maybe not a matter of code or die, but certainly a matter of style and most likely a commitment to more pain. it is (sometimes much) harder working with community projects since it takes working with that community - and everyone has their own use case, and at least three opinions. :) I’ve experienced this many time in non-software projects. It may take a little longer to get there, but it’s definitely worth the extra pain it in the end. > I would prefer to see GS having an infrastructure to load Pharo kernels. We > are pushing the bootstrap for this reasons. Dale and the GemStone team are doing a great job moving towards that ideal. Their constraints are even greater since they have a large commercial install base supporting many platforms. We should be able to be more flexible and dynamic > Because you see Pharo will use more and more slots because they are really > really cool and powerful. > What do you do with Pillar? Because I write books, slides, and websites so > this is an important piece of software for me. For me, Pillar was a package in Pier, and Pier was a tool that I used for all my presentations, prototyping, and small or short-lived community and not-for-profit projects. >> I’d like to see Pier get some love - it’s an awesome tool. How can I help? > Join and hack. I’d love to! I noticed that the issue tracker and other Pillar related stuff is now on GitHub which is awesome. Is there any chance that the Smalltalk project could also move there? It would make it easier to fork and hack and make versions available to test before deciding what might be valuable pushed back to the core project. Thanks for all your excellent work with Pillar - not to mention everything else! Have fun! Jupiter
Re: [Pharo-users] Pier3 with latest Pillar?
It would be nice to see Pillar return to being a cross platform project as well. One of the beautiful things about Seaside/Magritte/Pier was it’s compatibility across many dialects of Smalltalk. The “develop in Pharo and deploy in GemStone” was a big draw for me :) One of my clients uses VW so it was great to have these projects there as well. Yes but at the end of the day. You see we cannot work for free and in addition got constraints that are dragging us behind. Absolutely! Luckily the hard work of cross-compatability has already been done for Pier. I’m just hoping we can keep the parts of Pillar on which Pier is reliant working across dialects - Pharo and GemStone at least. From memory, the only thing that made it hard was PRTParametrizable. I imagine very few of us are being paid for the contributions we make. In my case, it’s only when I have a paid project that allows me to work in Smalltalk, that I can invest some of that paid time in contributing towards the packages I’m using for that project. Which packages? I also feel my smalltalk-ability isn’t up to the standard of so many of the amazing people contributing, which makes me a little reticent to get involved in the more complex projects. You see fixing a comment or adding a test should be possible. Don't hide yourself behind this argument. I will see if the trait usage make sense and can be removed. But you see if everything we do has to be compatible better be dead. Maybe not a matter of code or die, but certainly a matter of style and most likely a commitment to more pain. it is (sometimes much) harder working with community projects since it takes working with that community - and everyone has their own use case, and at least three opinions. :) I’ve experienced this many time in non-software projects. It may take a little longer to get there, but it’s definitely worth the extra pain it in the end. I would prefer to see GS having an infrastructure to load Pharo kernels. We are pushing the bootstrap for this reasons. Dale and the GemStone team are doing a great job moving towards that ideal. Their constraints are even greater since they have a large commercial install base supporting many platforms. Come on. Pharo too and we have far less ressources!!! We should be able to be more flexible and dynamic Because you see Pharo will use more and more slots because they are really really cool and powerful. What do you do with Pillar? Because I write books, slides, and websites so this is an important piece of software for me. For me, Pillar was a package in Pier, and Pier was a tool that I used for all my presentations, prototyping, and small or short-lived community and not-for-profit projects. Ok then you can still use an old version of Pier and hope that others will do what you want. I’d like to see Pier get some love - it’s an awesome tool. How can I help? Join and hack. I’d love to! I noticed that the issue tracker and other Pillar related stuff is now on GitHub which is awesome. Is there any chance that the Smalltalk project could also move there? It would make it easier to fork and hack and make versions available to test before deciding what might be valuable pushed back to the core project. Why easier? You cannot produce a slice? Seriously I will not move pillar to github before Pharo has a fully working solution. And I will maintain pillar but I need time. Thanks for all your excellent work with Pillar - not to mention everything else! Have fun! Jupiter
Re: [Pharo-users] Pier3 with latest Pillar?
For me, Pillar was a package in Pier, and Pier was a tool that I used for all my presentations, prototyping, and small or short-lived community and not-for-profit projects. I do not get why you cannot use Pharo for that. Le 17/11/16 à 02:04, Jupiter Jones a écrit : Hey Stephane, It would be nice to see Pillar return to being a cross platform project as well. One of the beautiful things about Seaside/Magritte/Pier was it’s compatibility across many dialects of Smalltalk. The “develop in Pharo and deploy in GemStone” was a big draw for me :) One of my clients uses VW so it was great to have these projects there as well. Yes but at the end of the day. You see we cannot work for free and in addition got constraints that are dragging us behind. Absolutely! Luckily the hard work of cross-compatability has already been done for Pier. I’m just hoping we can keep the parts of Pillar on which Pier is reliant working across dialects - Pharo and GemStone at least. From memory, the only thing that made it hard was PRTParametrizable. I imagine very few of us are being paid for the contributions we make. In my case, it’s only when I have a paid project that allows me to work in Smalltalk, that I can invest some of that paid time in contributing towards the packages I’m using for that project. I also feel my smalltalk-ability isn’t up to the standard of so many of the amazing people contributing, which makes me a little reticent to get involved in the more complex projects. I will see if the trait usage make sense and can be removed. But you see if everything we do has to be compatible better be dead. Maybe not a matter of code or die, but certainly a matter of style and most likely a commitment to more pain. it is (sometimes much) harder working with community projects since it takes working with that community - and everyone has their own use case, and at least three opinions. :) I’ve experienced this many time in non-software projects. It may take a little longer to get there, but it’s definitely worth the extra pain it in the end. I would prefer to see GS having an infrastructure to load Pharo kernels. We are pushing the bootstrap for this reasons. Dale and the GemStone team are doing a great job moving towards that ideal. Their constraints are even greater since they have a large commercial install base supporting many platforms. We should be able to be more flexible and dynamic Because you see Pharo will use more and more slots because they are really really cool and powerful. What do you do with Pillar? Because I write books, slides, and websites so this is an important piece of software for me. For me, Pillar was a package in Pier, and Pier was a tool that I used for all my presentations, prototyping, and small or short-lived community and not-for-profit projects. I’d like to see Pier get some love - it’s an awesome tool. How can I help? Join and hack. I’d love to! I noticed that the issue tracker and other Pillar related stuff is now on GitHub which is awesome. Is there any chance that the Smalltalk project could also move there? It would make it easier to fork and hack and make versions available to test before deciding what might be valuable pushed back to the core project. Thanks for all your excellent work with Pillar - not to mention everything else! Have fun! Jupiter
Re: [Pharo-users] QCMagritte question- does it have undo?
Paul there is an undo framework inside Pharo I imagine that you can use it to build your ideas. Stef Le 11/11/16 à 18:31, Paul DeBruicker a écrit : Thanks Norbert. I'm not sure of the feasibility/value but I think it would be nice to be able to undo back to a clean slate and redo all the way to a fully fleshed out system. Or at least some sane way in a multi-user environment. I wonder how etherpad.org has their undo structured. I'll go check it out. Paul NorbertHartl wrote Am 11.11.2016 um 06:03 schrieb PAUL DEBRUICKER < pdebruic@ >: I've never used magritte or QC magritte and was wondering whether with the momento it qas also possible to get multi step undo cheaply if it didn't already exist. I don't know if it exists. But you just need to save the current memento, copy it (make sure the dictionary inside is another instance) and use that. This would work before a commit has been done. Do you want to undo even commited stuff? Norbert -- View this message in context: http://forum.world.st/QCMagritte-question-does-it-have-undo-tp4922643p4922740.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
