Re: [Pharo-users] SDL2SpecialCharacterMapping problem
Hi Alvaro, This is not an area I've been involved in, but just a general comment... Can you export a self contained example from your code that can be loaded into a fresh Image that demonstrate the problem? Its always easier if people can see the problem with their own eyes. Also, what version OS/VM/Image are you running? i.e. World Menu > System > System Reporter cheers -ben On 1 April 2018 at 11:45, alvaro piornowrote: > Hi, > > Iam having a problem handling some OSKeywordEvents. These events should > have character associated. > > The mapping is resolved by SDL2SpecialCharacterMapping using a > dictionary(Mappings), it has the mapping, for example, for left arrow and > right arrow. > > It resolve correctly for "left arrow" with key: 1073741904(Integer) , but > it does not found "right arrow" with key: 1073741903(Integer). > > Both keys are present. > Any idea? > >
Re: [Pharo-users] Keeping packages up to date
Thank you! On Sun, Apr 1, 2018, 14:00 Stephane Ducassewrote: > Andrei > > if you need help we can help you. > > Stef > > On Sun, Apr 1, 2018 at 7:59 PM, Stephane Ducasse > wrote: > > use metacello and iceberg or gitfiletree > > > > Stef > > > > On Sun, Apr 1, 2018 at 4:32 PM, Andrei Stebakov > wrote: > >> Exactly! I guess because there are so many ways to navigate around > updating > >> the package, I was lost :) Thank you guys for giving me some pointers, > I'll > >> try to learn them. I wonder, which one is the most promising and > mainstream? > >> > >> On Sun, Apr 1, 2018, 08:58 wrote: > >>> > >>> You can open the repository in the Monticello browser if it’s a > >>> Metacello/Monticello repo, or use Iceberg with git if it’s a git repo > in the > >>> same manner you would with any other git project. You can also open > the > >>> project in Versionner to get the latest version. > >>> > >>> > >>> > >>> As far as scripting it, that’s reasonably obvious if you look at the > >>> Monticello or Versionner code itself. > >>> > >>> > >>> > >>> From: Pharo-users On Behalf Of > >>> Andrei Stebakov > >>> Sent: Saturday, March 31, 2018 7:14 PM > >>> To: Any question about pharo is welcome > >>> Subject: [Pharo-users] Keeping packages up to date > >>> > >>> > >>> > >>> I wonder if there is a generic solution to keeping certain Pharo > project > >>> in sync with development tree. > >>> > >>> For example when I want to get latest Roassal I execute > >>> > >>> Gofer it > >>> > >>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > >>> > >>> package: 'Roassal2'; > >>> > >>> package: 'Roassal2GT'; > >>> > >>> package: 'Trachel'; > >>> > >>> load. > >>> > >>> > >>> > >>> Also I wouldn't know this unless the maintainers (thanks Alexandre!) of > >>> the project told me what script to execute to get the latest version. > >>> > >>> If I went to Project Catalog I can only get the stable version and if > I go > >>> and find Roassal2 it won't give me information how to get its latest > >>> version. > >>> > >>> > >>> > >>> How would I get info about how to update, say Roassal given the script > >>> above from some Roassal project public page? > >>> > >>> Talking about Roassal, if I go to > >>> http://smalltalkhub.com/#!/~ObjectProfile/Roassal2/ page, it offers > the > >>> following script: > >>> > >>> Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > >>> configurationOf: 'Roassal2'; loadDevelopment > >>> > >>> > >>> > >>> Which is probably not exactly equal to the script above (or is it?). > >>> > >>> > >>> > >>> So, is there a generic way to get a latest version of some XYZ package? > >>> > >>> What do I need to learn to be able to get that information about any > Pharo > >>> project (other than asking the community)? Something similar to "git > pull" > >>> when you know the repository. > >
Re: [Pharo-users] Keeping packages up to date
Andrei if you need help we can help you. Stef On Sun, Apr 1, 2018 at 7:59 PM, Stephane Ducassewrote: > use metacello and iceberg or gitfiletree > > Stef > > On Sun, Apr 1, 2018 at 4:32 PM, Andrei Stebakov wrote: >> Exactly! I guess because there are so many ways to navigate around updating >> the package, I was lost :) Thank you guys for giving me some pointers, I'll >> try to learn them. I wonder, which one is the most promising and mainstream? >> >> On Sun, Apr 1, 2018, 08:58 wrote: >>> >>> You can open the repository in the Monticello browser if it’s a >>> Metacello/Monticello repo, or use Iceberg with git if it’s a git repo in the >>> same manner you would with any other git project. You can also open the >>> project in Versionner to get the latest version. >>> >>> >>> >>> As far as scripting it, that’s reasonably obvious if you look at the >>> Monticello or Versionner code itself. >>> >>> >>> >>> From: Pharo-users On Behalf Of >>> Andrei Stebakov >>> Sent: Saturday, March 31, 2018 7:14 PM >>> To: Any question about pharo is welcome >>> Subject: [Pharo-users] Keeping packages up to date >>> >>> >>> >>> I wonder if there is a generic solution to keeping certain Pharo project >>> in sync with development tree. >>> >>> For example when I want to get latest Roassal I execute >>> >>> Gofer it >>> >>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>> >>> package: 'Roassal2'; >>> >>> package: 'Roassal2GT'; >>> >>> package: 'Trachel'; >>> >>> load. >>> >>> >>> >>> Also I wouldn't know this unless the maintainers (thanks Alexandre!) of >>> the project told me what script to execute to get the latest version. >>> >>> If I went to Project Catalog I can only get the stable version and if I go >>> and find Roassal2 it won't give me information how to get its latest >>> version. >>> >>> >>> >>> How would I get info about how to update, say Roassal given the script >>> above from some Roassal project public page? >>> >>> Talking about Roassal, if I go to >>> http://smalltalkhub.com/#!/~ObjectProfile/Roassal2/ page, it offers the >>> following script: >>> >>> Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>> configurationOf: 'Roassal2'; loadDevelopment >>> >>> >>> >>> Which is probably not exactly equal to the script above (or is it?). >>> >>> >>> >>> So, is there a generic way to get a latest version of some XYZ package? >>> >>> What do I need to learn to be able to get that information about any Pharo >>> project (other than asking the community)? Something similar to "git pull" >>> when you know the repository.
Re: [Pharo-users] Keeping packages up to date
use metacello and iceberg or gitfiletree Stef On Sun, Apr 1, 2018 at 4:32 PM, Andrei Stebakovwrote: > Exactly! I guess because there are so many ways to navigate around updating > the package, I was lost :) Thank you guys for giving me some pointers, I'll > try to learn them. I wonder, which one is the most promising and mainstream? > > On Sun, Apr 1, 2018, 08:58 wrote: >> >> You can open the repository in the Monticello browser if it’s a >> Metacello/Monticello repo, or use Iceberg with git if it’s a git repo in the >> same manner you would with any other git project. You can also open the >> project in Versionner to get the latest version. >> >> >> >> As far as scripting it, that’s reasonably obvious if you look at the >> Monticello or Versionner code itself. >> >> >> >> From: Pharo-users On Behalf Of >> Andrei Stebakov >> Sent: Saturday, March 31, 2018 7:14 PM >> To: Any question about pharo is welcome >> Subject: [Pharo-users] Keeping packages up to date >> >> >> >> I wonder if there is a generic solution to keeping certain Pharo project >> in sync with development tree. >> >> For example when I want to get latest Roassal I execute >> >> Gofer it >> >> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >> >> package: 'Roassal2'; >> >> package: 'Roassal2GT'; >> >> package: 'Trachel'; >> >> load. >> >> >> >> Also I wouldn't know this unless the maintainers (thanks Alexandre!) of >> the project told me what script to execute to get the latest version. >> >> If I went to Project Catalog I can only get the stable version and if I go >> and find Roassal2 it won't give me information how to get its latest >> version. >> >> >> >> How would I get info about how to update, say Roassal given the script >> above from some Roassal project public page? >> >> Talking about Roassal, if I go to >> http://smalltalkhub.com/#!/~ObjectProfile/Roassal2/ page, it offers the >> following script: >> >> Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >> configurationOf: 'Roassal2'; loadDevelopment >> >> >> >> Which is probably not exactly equal to the script above (or is it?). >> >> >> >> So, is there a generic way to get a latest version of some XYZ package? >> >> What do I need to learn to be able to get that information about any Pharo >> project (other than asking the community)? Something similar to "git pull" >> when you know the repository.
Re: [Pharo-users] Keeping packages up to date
Exactly! I guess because there are so many ways to navigate around updating the package, I was lost :) Thank you guys for giving me some pointers, I'll try to learn them. I wonder, which one is the most promising and mainstream? On Sun, Apr 1, 2018, 08:58wrote: > You can open the repository in the Monticello browser if it’s a > Metacello/Monticello repo, or use Iceberg with git if it’s a git repo in > the same manner you would with any other git project. You can also open > the project in Versionner to get the latest version. > > > > As far as scripting it, that’s reasonably obvious if you look at the > Monticello or Versionner code itself. > > > > *From:* Pharo-users *On Behalf Of > *Andrei > Stebakov > *Sent:* Saturday, March 31, 2018 7:14 PM > *To:* Any question about pharo is welcome > *Subject:* [Pharo-users] Keeping packages up to date > > > > I wonder if there is a generic solution to keeping certain Pharo project > in sync with development tree. > > For example when I want to get latest Roassal I execute > > Gofer it > > smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > > package: 'Roassal2'; > > package: 'Roassal2GT'; > > package: 'Trachel'; > > load. > > > > Also I wouldn't know this unless the maintainers (thanks Alexandre!) of > the project told me what script to execute to get the latest version. > > If I went to Project Catalog I can only get the stable version and if I go > and find Roassal2 it won't give me information how to get its latest > version. > > > > How would I get info about how to update, say Roassal given the script > above from some Roassal project public page? > > Talking about Roassal, if I go to > http://smalltalkhub.com/#!/~ObjectProfile/Roassal2/ page, it offers the > following script: > > Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > configurationOf: 'Roassal2'; loadDevelopment > > > > Which is probably not exactly equal to the script above (or is it?). > > > > So, is there a generic way to get a latest version of some XYZ package? > > What do I need to learn to be able to get that information about any Pharo > project (other than asking the community)? Something similar to "git pull" > when you know the repository. >
Re: [Pharo-users] Keeping packages up to date
You can open the repository in the Monticello browser if it’s a Metacello/Monticello repo, or use Iceberg with git if it’s a git repo in the same manner you would with any other git project. You can also open the project in Versionner to get the latest version. As far as scripting it, that’s reasonably obvious if you look at the Monticello or Versionner code itself. From: Pharo-usersOn Behalf Of Andrei Stebakov Sent: Saturday, March 31, 2018 7:14 PM To: Any question about pharo is welcome Subject: [Pharo-users] Keeping packages up to date I wonder if there is a generic solution to keeping certain Pharo project in sync with development tree. For example when I want to get latest Roassal I execute Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: 'Roassal2'; package: 'Roassal2GT'; package: 'Trachel'; load. Also I wouldn't know this unless the maintainers (thanks Alexandre!) of the project told me what script to execute to get the latest version. If I went to Project Catalog I can only get the stable version and if I go and find Roassal2 it won't give me information how to get its latest version. How would I get info about how to update, say Roassal given the script above from some Roassal project public page? Talking about Roassal, if I go to http://smalltalkhub.com/#!/~ObjectProfile/Roassal2/ page, it offers the following script: Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadDevelopment Which is probably not exactly equal to the script above (or is it?). So, is there a generic way to get a latest version of some XYZ package? What do I need to learn to be able to get that information about any Pharo project (other than asking the community)? Something similar to "git pull" when you know the repository.
Re: [Pharo-users] PharoLauncher image loading error
Le 31/03/2018 à 16:03, Stephane Ducasse a écrit : And you are on MacOSX? No, I am not. Just some testing on school computers. Can you tell us then on which os? which version? Mentioned earlier on this thread Can you describe what you did? Because with the Launcher you can also I open the "Official distributions" subtree, select Pharo6.1 then click on the icon with the play symbol, on the top of the window. Is the disc where the launcher is located in read write mode? I guess so as it was copied there on the first place, the hard disk, on the dekstop. Stef -- Dr. Geo http://drgeo.eu
Re: [Pharo-users] Namespaces and ASN1 types in Cryptography package
Hi holger we are planning to work again on Module once we release Pillar 70 and Iceberg v2.0. We did not want to let Pillar die so we had to do something to put it in the rails for the future. I hope that by mid may we will get some traction and time to work again on the class infrastructure. Stef On Sat, Mar 31, 2018 at 6:09 PM, Esteban A. Maringolowrote: > Hi Holger, > > Cryptography package lacks a proper modularization, so you could load > only the groups you need, e.g. ASN1 will only be needed if you load > X509 (AFAIR). > > If Nortbert's ASN1 package is more complete than Cryptography's, then > we whould either merge it or discard what's there and load Norbert's > ASN1 package as a dependency instead. > > Regards, > > > Esteban A. Maringolo > > > 2018-03-31 12:11 GMT-03:00 Holger Freyther : >> Hi, >> >> I was debugging some test failures and it turns out that my code defines an >> ASN1IntegerType and the Cryptography package (a dependency of MongoTalk >> which is loaded into my code) has such a class as well. >> >> Thanks to Epicea I could see which package added the method but now I have >> no idea how to resolve the problem. Mongotalk needs PBKDF2 for modern >> authentication... Could Cryptography use "ASN1-Model"[1] instead? This is a >> rather complete[2] ASN1 implementation and used in production for some >> years. Could the classes be prefixed? >> >> If not how can I instruct Metacello to not load a certain package? >> >> holger >> >> >> [1] http://smalltalkhub.com/#!/~NorbertHartl/ASN1/source >> [2] Rather complete parser for ASN1 files but only encoding/decoding for >> DER/BER (none of the modern ones like aper/uper >
Re: [Pharo-users] Keeping packages up to date
Alexandre should publish a version in the catalog browser. Projects should push their configuration once there are stable and updated. On Sun, Apr 1, 2018 at 1:14 AM, Andrei Stebakovwrote: > I wonder if there is a generic solution to keeping certain Pharo project in > sync with development tree. > For example when I want to get latest Roassal I execute > Gofer it > smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > package: 'Roassal2'; > package: 'Roassal2GT'; > package: 'Trachel'; > load. > > Also I wouldn't know this unless the maintainers (thanks Alexandre!) of the > project told me what script to execute to get the latest version. > If I went to Project Catalog I can only get the stable version and if I go > and find Roassal2 it won't give me information how to get its latest > version. > > How would I get info about how to update, say Roassal given the script above > from some Roassal project public page? > Talking about Roassal, if I go to > http://smalltalkhub.com/#!/~ObjectProfile/Roassal2/ page, it offers the > following script: > Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > configurationOf: 'Roassal2'; loadDevelopment > > Which is probably not exactly equal to the script above (or is it?). > > So, is there a generic way to get a latest version of some XYZ package? > What do I need to learn to be able to get that information about any Pharo > project (other than asking the community)? Something similar to "git pull" > when you know the repository.
Re: [Pharo-users] Keeping packages up to date
Hi Andrei 2018-03-31 20:14 GMT-03:00 Andrei Stebakov: > I wonder if there is a generic solution to keeping certain Pharo project in > sync with development tree. > For example when I want to get latest Roassal I execute > Gofer it > smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > package: 'Roassal2'; > package: 'Roassal2GT'; > package: 'Trachel'; > load. > > Also I wouldn't know this unless the maintainers (thanks Alexandre!) of the > project told me what script to execute to get the latest version. > If I went to Project Catalog I can only get the stable version and if I go > and find Roassal2 it won't give me information how to get its latest > version. > > How would I get info about how to update, say Roassal given the script above > from some Roassal project public page? > Talking about Roassal, if I go to > http://smalltalkhub.com/#!/~ObjectProfile/Roassal2/ page, it offers the > following script: > Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > configurationOf: 'Roassal2'; loadDevelopment > > Which is probably not exactly equal to the script above (or is it?). > > So, is there a generic way to get a latest version of some XYZ package? > What do I need to learn to be able to get that information about any Pharo > project (other than asking the community)? Something similar to "git pull" > when you know the repository. Right now the solution AFAIK is to search the web for the most updated installation script. But that's one of the main ideas behind PI https://github.com/hernanmd/pi So tomorrow there could be a Donatello tool and the pi command will be the same for dev and stable. Feel free to contribute or submit issues, propose changes, etc. Cheers, Hernán