October 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Spur VM Bug for Chinese Characters?

by Sven Van Caekenberghe

> On 17 Oct 2016, at 21:14, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote >> I copy pasted them from the latest STON package. Thanks. > > Ugh. > > FileLocator home / 'Downloads' / 'myfile.ston' writeStreamDo: [ :s | > STON put: myDB onStream: s]. > > and then > > FileLocator home / 'Downloads' / 'myfile.ston' readStreamDo: [ :s | > STON fromStream: s ] > > resulted in: "STONReaderError: At character 978274: unexpected property name > type" > > Any thoughts on how to debug? That obviously depends on what 'myDB' contains, the basic call is OK though: FileLocator home / 'Downloads' / 'myfile.ston' writeStreamDo: [ :s | STON put: STONTestUser dummy onStream: s ]. FileLocator home / 'Downloads' / 'myfile.ston' readStreamDo: [ :s | STON fromStream: s ]. The error you get basically means that something non-simple was used as property name. You could try doing: FileLocator home / 'Downloads' / 'myfile.ston' readStreamDo: [ :s | (STON reader on: s) allowComplexMapKeys: true; next ]. >From the class comment of STONReader - allowComplexMapKeys <Boolean> default is false if true, any object is allowed as map key if false, only strings, symbols and numbers are allowed as map keys > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883p4919109.… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 17, 2016

Re: [Pharo-dev] Spur VM Bug for Chinese Characters?

by Sean P. DeNigris

Sean P. DeNigris wrote > I copy pasted them from the latest STON package. Thanks. Ugh. FileLocator home / 'Downloads' / 'myfile.ston' writeStreamDo: [ :s | STON put: myDB onStream: s]. and then FileLocator home / 'Downloads' / 'myfile.ston' readStreamDo: [ :s | STON fromStream: s ] resulted in: "STONReaderError: At character 978274: unexpected property name type" Any thoughts on how to debug? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883p4919109.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 17, 2016

Re: [Pharo-dev] Spur VM Bug for Chinese Characters?

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > Hmm, Path (the superclass) is handled, it has custom #stonOn: and > #fromSton: implementations. Do you have them in your image ? They are not included in the stable version from either the Pharo 4.0 MetaC Browser, or Pharo 5.0 Catalog browser, but I copy pasted them from the latest STON package. Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883p4919099.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 17, 2016

Re: [Pharo-dev] Pharo behind ALLSTOCKER marketplace

by Serge Stinckwich

Dear Masahi-san, thank you for your detailed explanations ! This is always great to see that nice tools like that exist in Pharo ecosystem and that people can do business with them. Regards, On Mon, Oct 17, 2016 at 3:05 PM, Masashi UMEZAWA <masashi.umezawa(a)gmail.com> wrote: > Hi all, > > From Torsten, I've received a request to post about some technical > details of ALLSTOCKER (http://pharo.org/success/AllStocker) . > I hope these notes will be interesting to Pharo web developers. > > - Seaside / Teapot > We are using Seaside as a main framework for ALLSTOCKER marketplace. > Seaside's component architecture is great for extending application in > an organized way. > ALLSTOCKER prototype was originally composed of only 3 class > categories. Now these were gradually grown to 70 categories. But we > still feel that they are manageable. > We also use Teapot for building Web-based API in a quick way. Recently > we've built webhook handlers for integration with other services. > > - Templating with Mustaside > We need a lot of responsive-design web pages for supporting various > mobile devices. (It is important especially for Southeast Asian > countries, where tablets are popular than PCs). > We would like to adopt existing Twitter Bootstrap templates for saving > time. So, Mustaside was our choice. > http://smalltalkhub.com/#!/~MasashiUmezawa/Mustaside > Before Mustaside, there were a lot of noisy #div: sends in our code. > Now they are gone. > > - Localization > Our business target is world-wide. So localization is very important > topic. Currently ALLSTOCKER supports 4 languages and we will add > Chinese languages soon. > Translation strings are not only in Smalltalk code, but also in > Mustache templates. So we selected Soup for extracting translatable > strings in those templates. > http://smalltalkhub.com/#!/~PharoExtras/Soup > For managing translations, we use Gettext package. > http://smalltalkhub.com/#!/~PharoExtras/Gettext > > - Databases > For transactional data, we chose Glorp. Although there are mapping > costs, we prefer RDB (Postgres). It is reliable for handling precious > order-related data. > However, for supporting complex search of machines, we use Neo4j - a > graph database. It supports very powerful query language called > Cypher. > We can avoid complex table joins and get aggregated results faster. > http://smalltalkhub.com/#!/~MasashiUmezawa/Neo4reSt > > - Keyword search > ALLSTOCKER supports free keyword search. We selected Elasticsearch for > search-engine. Elasticsearch has elaborated searching facilities and > those are easily accessible via REST API. > We have extended the existing Elasticsearch client for Pharo 5. > https://github.com/newapplesho/elasticsearch-smalltalk > > - Deployment > We are using AWS Elastic Load Balancer and running Nginx as a > front-end web server. Two back-end Pharo images are running and > load-balanced with sticky sessions. > It was sort of difficult to find the appropriate simultaneous number > of database connections and Pharo processes. We feel ALLSTOCKER is > pretty stable for now, but we need to adjust more for expanding our > services. > > Best regards, > -- > [:masashi | ^umezawa] > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Oct. 17, 2016

Re: [Pharo-dev] Pharo behind ALLSTOCKER marketplace

by Esteban A. Maringolo

Thank you for sharing all your experience. I wasn't aware of many of the packages you're using. And I like the Mustaside approach for certain parts of a Seaside app. It still surprises me how these packages can fly so low under the radar. What version of Glorp are you using? Best regards! Esteban A. Maringolo

Oct. 17, 2016

Pharo behind ALLSTOCKER marketplace

by Masashi UMEZAWA

Hi all, >From Torsten, I've received a request to post about some technical details of ALLSTOCKER (http://pharo.org/success/AllStocker) . I hope these notes will be interesting to Pharo web developers. - Seaside / Teapot We are using Seaside as a main framework for ALLSTOCKER marketplace. Seaside's component architecture is great for extending application in an organized way. ALLSTOCKER prototype was originally composed of only 3 class categories. Now these were gradually grown to 70 categories. But we still feel that they are manageable. We also use Teapot for building Web-based API in a quick way. Recently we've built webhook handlers for integration with other services. - Templating with Mustaside We need a lot of responsive-design web pages for supporting various mobile devices. (It is important especially for Southeast Asian countries, where tablets are popular than PCs). We would like to adopt existing Twitter Bootstrap templates for saving time. So, Mustaside was our choice. http://smalltalkhub.com/#!/~MasashiUmezawa/Mustaside Before Mustaside, there were a lot of noisy #div: sends in our code. Now they are gone. - Localization Our business target is world-wide. So localization is very important topic. Currently ALLSTOCKER supports 4 languages and we will add Chinese languages soon. Translation strings are not only in Smalltalk code, but also in Mustache templates. So we selected Soup for extracting translatable strings in those templates. http://smalltalkhub.com/#!/~PharoExtras/Soup For managing translations, we use Gettext package. http://smalltalkhub.com/#!/~PharoExtras/Gettext - Databases For transactional data, we chose Glorp. Although there are mapping costs, we prefer RDB (Postgres). It is reliable for handling precious order-related data. However, for supporting complex search of machines, we use Neo4j - a graph database. It supports very powerful query language called Cypher. We can avoid complex table joins and get aggregated results faster. http://smalltalkhub.com/#!/~MasashiUmezawa/Neo4reSt - Keyword search ALLSTOCKER supports free keyword search. We selected Elasticsearch for search-engine. Elasticsearch has elaborated searching facilities and those are easily accessible via REST API. We have extended the existing Elasticsearch client for Pharo 5. https://github.com/newapplesho/elasticsearch-smalltalk - Deployment We are using AWS Elastic Load Balancer and running Nginx as a front-end web server. Two back-end Pharo images are running and load-balanced with sticky sessions. It was sort of difficult to find the appropriate simultaneous number of database connections and Pharo processes. We feel ALLSTOCKER is pretty stable for now, but we need to adjust more for expanding our services. Best regards, -- [:masashi | ^umezawa]

Oct. 17, 2016

[JOB][Research] Postdoc "'Higher level IDEs for BlockChain Technologies"

by Marcus Denker

We are looking to fill a Postdoc position. The candidate should : - hold a PhD degree in Computer Science - be fluent in English (French is an advantage but not required) - have good programming skills Experience with DSLs, IDEs, Models, compilers, code analysis... is a plus. Topic: Higher level IDEs for BlockChain Technologies ==================================================== With Ethereum, BlockChain technology moves from being an implementation technology for virtual currency to being the basis for developing new kinds of software with smart contracts. The goal of this project is to analyse and improve high-level development and analysis tools for this new kind of software. Users like banks and insurance companies need tools that model their processes and level of confidentiality of the information shared though blockchain technology, especially on public blockchains. For this, users need a solution that provides a higher level way to model systems than solidity code or even low-level byte-code. In addition, blockchain based solutions often use multiple programming languages. Especially the later poses a risk for later software maintenance. The goal of this Postdoc is to work on high level IDE / modelling tools for blockchain technology like Ethereum. The plan is to - Analyse the current state of tools and languages in the context of blockchain technologies. - Analyse the current state: modelling tools and processes with a focus in decision processes both in communities and commercial use. - Explore how to improve the state of the art, with a focus on how tools can support users of blockchain solutions. - Realize prototypes for IDEs/modelling tools for Ethereum, possibly using Pharo. Directions to explore will be both related to generating and analysing solidity code as well as complete solutions for users in an industrial setting. - Results will be submitted to be publish in international conferences and journals. The work is a collaboration between Inria Lille (RMOD) and Utocat SAS. Duration : 2 years Salary: 31 644â¬ brut Employer: Inria More information: contact marcus.denker(a)inria.fr Utocat: ====== Utocat was created in October 2014 by ClÃ©ment Francomme to help merchants accepting bitcoin payments and converting it directly in euros. In 2015, Utocat joined the EuraTechnologies acceleration program and pivoted to propose Blockchainiz : the dedicated access platform for Banks and Insurance companies. Laurent Koszyczek and Alexis MÃ©vellec partnered with ClÃ©ment Francomme to improve the technical and commercial aspects. As a Platform As A Service (PAAS), Blockchainiz accompanies projects up to the production stage. Blockchainiz connects the functional processes to the blockchain. Data is not replicated on different IT systems anymore. Blockchain is used as a common repository for every part of the process. Hence, it enables to limit the typing errors, to optimize the costs and delays while the customer experience is improved. More information at: https://www.blockchainiz.io Inria Lille =========== Inria is a research institute dedicated to promoting âscientific excellence in the service of technology transfer and society as a wholeâ. Inria employs a staff of 2700, drawn from the worldâs most prestigious universities, to address the latest challenges in computer science and mathematics. The Institute operates eight Research Centres throughout France. The Inria Lille - Nord Europe Research Centre was founded in 2008 and employs a staff of 360, including 300 scientists working in sixteen research teams. Recognised for its outstanding contribution the socio-economic development of the Nord - Pas-de-Calais Region, the Inria Lille - Nord Europe Research Centre undertakes research in the field of computer science in collaboration with a range of academic, institutional and industrial partners. The strategy of the Centre is to develop an internationally renowned centre of excellence with a significant impact on the City of Lille and its surrounding area. It works to achieve this by pursuing a range of ambitious research projects in such fields of computer science as the intelligence of data and adaptive software systems. Building on the synergies between research and industry, Inria is a major contributor to skills and technology transfer in the field of computer science. https://www.inria.fr/centre/lille RMOD ==== The goal of RMoD is to support remodularization and development of modular object-oriented applications. We tackle this objective from two complementary perspectives: reengineering, and constructs for dynamic languages. In the context of languages, we revisit language concepts such as modules and composition; we are also working on a new generation of reflective systems. We experiment with these programming constructs using Pharo, an open source, reflective, object-oriented language. http://rmod.inria.fr

Oct. 17, 2016

Re: [Pharo-dev] [ANN] New release of iceberg

by Aliaksei Syrel

Diff has inverted colors (Red <-> Green) Almost every time have to stop and think why new code I just wrote will be removed ;) GitHub: (new content is green) [image: Inline images 1] Iceberg: (new content is red, note also that last E character in LINE is not highlighted, but it should): [image: Inline images 2] Cheers, Alex On 16 October 2016 at 20:28, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi > > I use Iceberg to load project in non-interactive mode and this is what I > get with latest stable: > > RETRY->BaselineOfIceberg An attempt to use interactive tools detected, > while in non-interactive mode > > Is there any reason that prevents Iceberg to be used in non-interactive > mode, from command line for example? > > Cheers, > Alex > > On 15 October 2016 at 13:59, stepharo <stepharo(a)free.fr> wrote: > >> + 1 >> >> This is on my todo :) >> >> >> Le 13/10/16 Ã 20:37, Tudor Girba a Ã©crit : >> >> Hi Nicolas, >>> >>> Great work! >>> >>> I will test it again. I kindly ask everyone else to follow the call and >>> test this release. Ideally, create a repository on GitHub and play with it. >>> >>> It is important to get this piece as stable as possible to make Git part >>> of the default Pharo experience. >>> >>> Cheers, >>> Doru >>> >>> >>> On Oct 13, 2016, at 2:25 PM, Nicolas Passerini <npasserini(a)gmail.com> >>>> wrote: >>>> >>>> Hi, we are releasing a new version of Iceberg, with several new >>>> features and bugfixes. I would't yet say that is 100% production ready, but >>>> it is close, so I want to invite you to test it and provide feedback. >>>> >>>> You can install it by doing: >>>> >>>> Metacello new >>>> baseline: 'Iceberg'; >>>> repository: 'github://npasserini/iceberg'; >>>> load. >>>> >>>> More installation instructions and documentation can be found at >>>> https://github.com/npasserini/iceberg. >>>> >>>> Some of the new features in this version are: >>>> - Allow to commit several packages together in the same commit. >>>> - Show diffs for incoming and outgoing commits (i.e. before push/pull >>>> you can browse the difference between the remote and the local versions). >>>> - New History view allows to see any commit in any branch and compare >>>> it to the current loaded version. >>>> - Better support for interacting code loaded outside Iceberg >>>> (smaltalkhub, filetree, gitfiletree, etc). >>>> - From the diff view, revert changes or browse them (i.e. open a >>>> Nautilus on the changed class/method). >>>> - Automatically update presentations on code / repository changes. >>>> - Integration with Metacello, i.e. after installing Iceberg you do >>>> something like >>>> >>>> Metacello new >>>> >>>> baseline: 'TaskIt' >>>> ; >>>> repository: 'github://sbragagnolo/taskit' >>>> ; >>>> load. >>>> >>>> >>>> (By default) it will be loaded using iceberg (there is a setting to >>>> avoid it if you prefer traditional behavior. >>>> >>>> - Improved handling of git errors. >>>> - Improved performance for several operations. >>>> - Improved documentation. >>>> - ... and several bug fixes and other minor improvements (please look >>>> at https://github.com/npasserini/iceberg/milestone/7?closed=1 for more >>>> details). >>>> >>>> >>>> Please do not hesitate to contact me if you have any doubts. >>>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Reasonable is what we are accustomed with." >>> >>> >>> >>> >> >> >

Oct. 17, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60261 Home: https://github.com/pharo-project/pharo-core

Oct. 17, 2016

[pharo-project/pharo-core] 3107e3: 60261

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 3107e30982d85e81af5460e05d7622823c451f39 https://github.com/pharo-project/pharo-core/commit/3107e30982d85e81af5460e0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-17 (Mon, 17 Oct 2016) Changed paths: A Polymorph-Widgets.package/MorphicUIManager.class/instance/services/confirm_label_trueChoice_falseChoice_cancelChoice_default_.st M Polymorph-Widgets.package/MorphicUIManager.class/instance/services/confirm_trueChoice_falseChoice_cancelChoice_default_.st R ScriptLoader60.package/ScriptLoader.class/instance/accessing/inboxRepository50.st R ScriptLoader60.package/ScriptLoader.class/instance/accessing/repository50.st M ScriptLoader60.package/ScriptLoader.class/instance/cleaning/addHomeRepositoryToAllPackagesExcept_.st M ScriptLoader60.package/ScriptLoader.class/instance/mc related utils/addHomeRepositoryToAllPackages.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60260.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60261.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60260.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60261.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Shout.package/SHRBTextStyler.class/instance/private/styleTempBars_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitBlockNode_.st A Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitCascadeNode_.st M Shout.package/SHRBTextStyler.class/instance/visiting rb nodes/visitSequenceNode_.st M System-Support.package/SmalltalkImage.class/instance/miscellaneous/metacelloPlatformAttributes.st A UIManager.package/CommandLineUIManager.class/instance/ui requests/confirm_label_trueChoice_falseChoice_cancelChoice_default_.st A UIManager.package/DummyUIManager.class/instance/ui requests/confirm_label_trueChoice_falseChoice_cancelChoice_default_.st A UIManager.package/NonInteractiveUIManager.class/instance/ui requests/confirm_label_trueChoice_falseChoice_cancelChoice_default_.st A UIManager.package/UIManager.class/instance/ui requests/confirm_label_trueChoice_falseChoice_cancelChoice_default_.st Log Message: ----------- 60261 19210 Add styler support for period / semicolon / double colon / temp bar https://pharo.fogbugz.com/f/cases/19210 19206 UIManager confirm does not allow to set true/false button labels and window title at the same time https://pharo.fogbugz.com/f/cases/19206 18811 remove pharo 5.0 inbox and metacello platform attributes https://pharo.fogbugz.com/f/cases/18811 http://files.pharo.org/image/60/60261.zip

Oct. 17, 2016