December 2017 - Pharo-users

Re: [Pharo-users] Zinc JSON parsing error handling

by Norbert Hartl

> Am 13.12.2017 um 11:04 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > >>> On 13 Dec 2017, at 10:54, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>> Am 13.12.2017 um 10:18 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> >>> >>>> On 13 Dec 2017, at 10:14, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>> To make your core a little bit more reliable you should not catch the general error but a NeoJSONParseError. And you need to guard the dictionary access. There is no guarantee you get something back that inlcudes key success and message. >>> >>> Yes, indeed. >>> >>> Also, a better REST API (not something you can change) would not return 200 OK with an error in the payload, but would return a 404 Not Found with a proper error object as payload. >>> >> I must say that the latter is not a good advize. All HTTP status codes refer to the resource that is specified in the uri. REST is resource based but GET and POST are exceptions beacuse they can address processing entities. It means that the result of the operation is not the entity in the uri. Returning a 404 would mean that the >> >> https://bittrex.com/api/v1.1/public/getticker >> >> resource is not available but that is not true and can lead to unwanted behaviour, e.g. that a http stack caches the error and does not try to access that resource again. So the proper status code depends on the definition of the interface. If it is considered to always return an object then the status code needs to be 400 because the specification of the client was invalid. On the other hand you can just return a 200 with an empty result if the search result is optional. >> >> my 2 cents, > > Well, yes, you're right. I was too quick and assumed the resource was properly named. > > That was another remark. The interface does not properly refer to a resource, it is still too procedural, IMHO. > > I would write it as > > https://bittrex.com/api/v1.1/public/tickers/LTC > > A process interface should only be used for, duh, processes that can be identified as such, like a trade that then gets its own unique URI that can be queried for state and so on. > > REST interface design is a subject we can discuss endlessly, no doubt. > No doubt! But with you I might enjoy it ð Nevertheless I think we donât want to live without RPC and that is hard to map on REST. Norbert >> Norbert >> >>> FWIW, there are a couple of more sophisticated examples, like in NeoJSONMappingTests and NeoJSONExamplesTests, with comments that do various special cases. >>> >>>> Norbert >>>> >>>>> Am 13.12.2017 um 09:54 schrieb Ben Coman <btc(a)openinworld.com>: >>>>> >>>>> hi Sven, >>>>> >>>>>> On 13 Dec 2017, at 07:59, Ben Coman <btc(a)openinworld.com> wrote: >>>>>> >>>>>> >>>>>> With... >>>>>> Object subclass: #BittrexResponse >>>>>> instanceVariableNames: 'success message result' >>>>>> classVariableNames: '' >>>>>> package: 'Bittrex' >>>>>> >>>>>> Object subclass: #BittrexMarketSummary >>>>>> instanceVariableNames: 'MarketName High Low Volume Last >>>>>> BaseVolume TimeStamp Bid Ask OpenBuyOrders >>>>>> OpenSellOrders PrevDay Created DisplayMarketName' >>>>>> classVariableNames: '' >>>>>> package: 'Bittrex' >>>>>> >>>>>> this code works great when the response holds good data... >>>>>> ZnClient new >>>>>> url: 'https://bittrex.com/api/v1.1/public/getmarketSummary?market=BTC-LTC'; >>>>>> enforceHttpSuccess: true; >>>>>> accept: ZnMimeType applicationJson; >>>>>> contentReader: [ :entity | |reader| >>>>>> reader := (NeoJSONReader on: entity readStream). >>>>>> reader for: BittrexResponse do: [:m| >>>>>> m mapInstVar: #success. >>>>>> m mapInstVar: #message. >>>>>> (m mapInstVar: #result) valueSchema: #ResultArray]. >>>>>> reader for: #ResultArray customDo: [ :mapping | >>>>>> mapping listOfElementSchema: BittrexMarketSummary ]. >>>>>> reader mapInstVarsFor: BittrexMarketSummary. >>>>>> reader nextAs: BittrexResponse ]; >>>>>> get. >>>>>> >>>>>> i.e. a raw response looking like this.... >>>>>> (ZnClient new >>>>>> url: 'https://bittrex.com/api/v1.1/public/getmarketsummary?market=BTC-LTC'; >>>>>> get) inspect. >>>>>> ==> "'{""success"":true,""message"":"",""result"":[{""MarketName"":""BTC-LTC"",""High"":0.01982450,""Low"":0.01285257,""Volume"":1436429.81313360,""Last"":0.01842000,""BaseVolume"":24841.17217724,""TimeStamp"":""2017-12-13T05:56:25.937"",""Bid"":0.01840001,""Ask"":0.01842000,""OpenBuyOrders"":10140,""OpenSellOrders"":6306,""PrevDay"":0.01439800,""Created"":""2014-02-13T00:00:00""}]}'" >>>>>> >>>>>> >>>>>> But for bad response looking like this... >>>>>> (ZnClient new >>>>>> url: 'https://bittrex.com/api/v1.1/public/getmarketsummary?market=INVALID'; >>>>>> get) inspect. >>>>>> ==> {"success":false,"message":"INVALID_MARKET","result":null} >>>>>> >>>>>> the JSON handling code fails deep in the call stack with an error >>>>>> "NeoJSONParseError: [ expected" >>>>>> which is not so friendly for users of the Bittrex library. >>>>>> >>>>>> What are the different/recommended approaches with Zinc >>>>>> for catching JSON errors such that I can pass "message" >>>>>> as a higher level Error up the stack to the Bittrex user. >>>>>> >>>>>> cheers -ben >>>>> >>>>> >>>>> On 13 December 2017 at 15:37, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> BTW, this is no about Zinc, but about NeoJSON. >>>>> >>>>> This is what I meant with variability that is hard to capture with a simple static type schema. >>>>> >>>>> I have no time to try myself right now, but a custom mapping for ivar result (as in a block) might be able to see the difference and act accordingly. >>>>> >>>>> >>>>> okay. So I played around tracing this through the debugger and for anyone else >>>>> with a similar need later, I ended up with the following... >>>>> >>>>> response := (ZnClient new >>>>> url: 'https://bittrex.com/api/v1.1/public/getticker?market=INVALID'; >>>>> enforceHttpSuccess: true; >>>>> accept: ZnMimeType applicationJson; >>>>> contentReader: >>>>> [ :entity | >>>>> [ |reader| >>>>> reader := (NeoJSONReader on: entity readStream). >>>>> reader for: BittrexResponse do: >>>>> [:m| >>>>> m mapInstVar: #success. >>>>> m mapInstVar: #message. >>>>> (m mapInstVar: #result) valueSchema: BittrexTicker >>>>> ]. >>>>> reader mapInstVarsFor: BittrexTicker. >>>>> reader nextAs: BittrexResponse >>>>> ] on: Error do: >>>>> [ :err | |json| >>>>> json := NeoJSONReader fromString: entity contents. >>>>> (json at: 'success') >>>>> ifFalse: [ self error: (json at: 'message') ] >>>>> ifTrue: [ self error: 'UKNOWN ERROR' ] >>>>> ] >>>>> ]) get. >>>>> >>>>> >>>>> for which I get a nice pre-debug window titled "Error: INVALID_MARKET" >>>>> >>>>> cheers -ben

Dec. 14, 2017

Re: [Pharo-users] P7 image and VM miss matches

by Marcus Denker

> On 14 Dec 2017, at 16:14, Hilaire <hilaire(a)drgeo.eu> wrote: > > Instructions for at http://get.pharo.org were followed, there is no option about 32 or 64 bits VM > Related entry: https://pharo.fogbugz.com/f/cases/20803/http-get-pharo-org-does-not-list-an… It is very high on my todo to add an explanation (this is not that simple, as the page is auto-generated and I need to find out how to do it) Marcus

Dec. 14, 2017

Re: [Pharo-users] P7 image and VM miss matches

by stephan

On 14-12-17 14:21, Ben Coman wrote: > > > On 14 December 2017 at 20:27, Hilaire > <hilaire(a)drgeo.eu > <mailto:hilaire@drgeo.eu>> wrote: > Version: > > ./pharo --version > 5.0-201708271955Â Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production > Spur VM] > CoInterpreter VMMaker.oscog-eem.2265 uuid: > 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: > 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > VM: 201708271955 Yes, that linux 32 bit vm hasn't been build recently and has known crashes. On the opensmalltalk bintray the linux 32 x86 pharo vm is also currently missing https://bintray.com/opensmalltalk/vm/cog/201712121955#files Stephan

Dec. 14, 2017

Re: [Pharo-users] P7 image and VM miss matches

by Hilaire

Instructions for at http://get.pharo.org were followed, there is no option about 32 or 64 bits VM Installed P6 VM seems too old for git, got some complains/errors on that. http://files.pharo.org did not help either for lates 64bits P7 VM. Will try with a newer P6 VM in case... Le 14/12/2017 Ã 14:21, Ben Coman a Ã©critÂ : > You have is a 32-bit VM ^^^^ (four digit vers.) > and a 64-bit Image (five digit vers.) vvvvvv > > Â Â cannot read image file (vers. 68021). > > > > The https://pharo.org/download shows how to one flavour of 64-bit VM > Â Â curl https://get.pharo.org/64/ | bash > > but I can't guess how that interfaces with getting a 64-bit vmTLatest70 > I wonder if rather than squeezing "64" onto the path side of url, > it would be easier to squeeze it into the host name... get64.pharo.org > <http://get64.pharo.org> > and all existing url-paths remain unchanged?(?) -- Dr. Geo http://drgeo.eu

Dec. 14, 2017

Re: [Pharo-users] P7 image and VM miss matches

by Ben Coman

On 14 December 2017 at 20:27, Hilaire <hilaire(a)drgeo.eu> wrote: > With latest VM for P7 fetched with get.pharo.org/vmTLatest70 < > http://get.pharo.org/vmTLatest70> > > Then when using the VM with a P7 image: > > ./pharo ../../../DrGeoII/Dev-pharo7/Pharo7.0-64bit-f82fc36.image > > This error shows up: > > This interpreter (vers. 6521) You have is a 32-bit VM ^^^^ (four digit vers.) and a 64-bit Image (five digit vers.) vvvvvv > cannot read image file (vers. 68021). > The https://pharo.org/download shows how to one flavour of 64-bit VM curl https://get.pharo.org/64/ | bash but I can't guess how that interfaces with getting a 64-bit vmTLatest70 I wonder if rather than squeezing "64" onto the path side of url, it would be easier to squeeze it into the host name... get64.pharo.org and all existing url-paths remain unchanged?(?) cheers -ben P.S. it would be useful if --version more prominently displayed whether it was 32bit or 64bit something like... "[Production Spur VM 64bit]" > Version: > > ./pharo --version > 5.0-201708271955 Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production Spur > VM] > CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a > Aug 27 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: > 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Sun Aug 27 21:55:26 2017 +0200 $ > Plugins: 201708271955 https://github.com/OpenSmallta > lk/opensmalltalk-vm.git $ > Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 3.13.0-115-generic > #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 i686 i686 i386 > GNU/Linux > > -- > Dr. Geo > http://drgeo.eu > > > >

Dec. 14, 2017

<Programming> 2018: Call for workshop, symposium & poster submissions

by Sylvia Grewe

----------------------------------------------------------------------- Â <Programming> 2018 : The Art, Science, and Engineering of Programming Â Â April 9-12, 2018, Nice, France https://2018.programming-conference.org/ ----------------------------------------------------------------------- The associated journal for <Programming> already published two exciting issues this year (openly accessible at http://programming-journal.org/2018/) a third one is being prepared at the moment. All of the papers from this yearâs volume will be presented at <Programming> 2018 in Nice in April. Are you still looking for a good opportunity to contribute to the event? We are excited to announce that there will be 11 co-located events at the <Programming> 2018 conference: Â - ACM Student Research Competition / <Programming> 2018 Posters Â - Bx 2018 - 7th International Workshop on Bidirectional Transformations Â -Â CoCoDo 2018 â Raincode Labs Compiler Coding Dojo Â - LASSY 2018 - 3rdÂ Workshop on Live Adaptation of Software SYstems Â - MOMO 2018 - 3rd Workshop on Modularity in Modelling Â - MoreVMs 2018 - 2nd Workshop on Modern Language Runtimes, Ecosystems, and VMs Â -Â PASS 2018 - 2nd Workshop on Programming Across the System Stack Â - Programming for the Large 2018 Workshop Â - ProWeb 2018 - 2nd International Workshop on Programming Technology for the Future Web Â - PX/18 - 3rd Workshop on Programming Experience Â - Salon des RefusÃ©s 2018 - 2nd edition of the Salon des RefusÃ©s workshop All co-located events will take place during April 9-10 2018. Below, we list short descriptions and important dates for each event. We are looking forward to your contributions! ******************************************************************** Â ACM Student Research Competition / <Programming> 2018 Posters Â Â Â Submissions: Mon 22 Jan 2018 https://2018.programming-conference.org/track/programming-2018-src ******************************************************************** The ACM Student Research Competition (SRC), sponsored by Microsoft Research, offers a unique forum for ACM student members at the undergraduate and graduate levels to present their original research before a panel of judges and conference attendees. The SRC gives visibility to up-and-coming young researchers, and offers them an opportunity to discuss their research with experts in their field, get feedback, and to help sharpen communication and networking skills. ACMâs SRC program covers expenses up to $500 for all students invited to an SRC. Please see our website for requirements and further details. **************************************************************** Â Bx 2018 - 7th International Workshop on Bidirectional Transformations Â Â Â Paper submissions: Fri 19 Jan 2018 Â Â Â Notifications: Sat 17 Feb 2018 https://2018.programming-conference.org/track/bx-2018-papers **************************************************************** Bidirectional transformations (bx) are a mechanism for maintaining the consistency of at least two related sources of information. Such sources can be relational databases, software models and code, or any other document following standard or ad-hoc formats. Bx are an emerging topic in a wide range of research areas, with prominent presence at top conferences in several different fields (namely databases, programming languages, software engineering, and graph transformation), but with results in one field often getting limited exposure in the others. Bx 2018 is a dedicated venue for bx in all relevant fields, and is part of a workshop series that was created in order to promote cross-disciplinary research and awareness in the area. As such, since its beginning in 2012, the workshop has rotated between venues in different fields. **************************************************************** Â CoCoDo 2018 â Raincode Labs Compiler Coding Dojo Â Â Â No submission deadlines! https://cocodo.github.io **************************************************************** If you ever studied any computing discipline, you must have learnt something about compilers as well, and you probably think you forgot everything about it since. Yet, almost every time you develop a non-trivial piece of software, you end up converting data between formats, traversing hierarchical structures, analysing and representing dependences and doing many other things that are at the heart of compiler design and implementation. Whether you are applying a Visitor design pattern or emulating a state machine with a switch/case statement, you are programming a little part of a compiler for your own language. Participating in CoCoDo will give you a chance to immerse in the marvels of compiler technologies for one day â and if you like it, you are welcome to stay in this field! Our coding dojo will be split into sessions, each dedicated to one aspect of compilation, with brief explanations and supervision by leading field experts. There will be several technologies, mainstream and otherwise, laid out at your disposal. Better yet, you can bring your own workbench and show us how itâs done. **************************************************************** Â LASSY 2018 - 3rdÂ Workshop on Live Adaptation of Software SYstems Â Â Â Paper submissions: Fri 12 Jan 2018 Â Â Â Notifications: Fri 12 Feb 2018 https://2018.programming-conference.org/track/LASSY-2018-papers **************************************************************** The LASSY workshop provides a space for discussion and collaboration between researchers working on the problem of enabling live adaptations to software systems, across the development stack. The workshop encourages theoretical work on programming models and techniques to adapt software systems at the programming language, database, or user interface levels; application and practice to adaptive systems to a particular domain; and empirical studies on the impact and assessment of adaptive systems from a societal point of view. **************************************************************** Â MOMO 2018 - 3rd Workshop on Modularity in Modelling Â Â Abstract submissions (optional): Fri 2 Feb 2018 Â Â Paper submissions: Thu 8 Feb 2018 Â Â Notifications: Thu 1 Mar 2018 http://www.momo2018.ece.mcgill.ca/index.htm **************************************************************** Despite the power of abstraction of modelling, models of real-world problems and systems quickly grow to such an extent that managing the complexity by using proper modularization techniques becomes necessary. The Third International Modularity in Modelling Workshop (MoMoâ18) will bring together researchers and practitioners interested in the theoretical and practical challenges resulting from applying modularity, advanced separation of concerns, and composition at the modelling level. It is intended to provide a forum for presenting new ideas and discussing the impact of the use of modularization in the context of (MDE) at different levels of abstraction. MoMoâ18 will bring together researchers and practitioners interested in exploring modularization techniques for modelling, such as but not limited to aspect-oriented mechanisms to support advanced separation of concerns, advanced composition operators for possibly heterogeneous models, and techniques for execution and reasoning over global properties of modularized models. ****************************************************************************** Â MoreVMs 2018 - 2nd Workshop on Modern Language Runtimes, Ecosystems, and VMs Â Â Submissions: Fri 26 Jan 2018 Â Â Notifications: Fri 23 Feb 2018 https://2018.programming-conference.org/track/MoreVMs-2018 ****************************************************************************** The MoreVMs'18 workshop aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. This includes aspects such as reuse of language runtimes, modular implementation, language design and compilation strategies. The workshop aims to enable a diverse discussion on how languages and runtimes are currently being utilized, and where they need to improve further. We welcome presentation proposals in the form of extended abstracts discussing experiences, work-in-progress, as well as future visions, from either an academic or industrial perspective. ************************************************************************** Â PASS 2018 - Workshop on Programming Across the System Stack Â Â Submissions: Mon 5 Feb 2018 Â Â Notifications: Mon 26 Feb 2018 Â Â Poster Submissions: Tue 6 Mar 2018 https://2018.programming-conference.org/track/PASS-2018-papers ************************************************************************** The landscape of computation platforms has changed dramatically in recent years. Emerging systems - such as wearable devices, smartphones, unmanned aerial vehicles, Internet of things, cloud computing servers, heterogeneous clusters, and data centers - pose a distinct set of system-oriented challenges ranging from data throughput, energy efficiency, security, real-time guarantees, to high performance. In the meantime, code quality, such as modularity or extensibility, remains a cornerstone in modern software engineering, bringing in crucial benefits such as modular reasoning, program understanding, and collaborative software development. This workshop is driven by one fundamental question: How does internal code quality interact with system-oriented goals? We welcome both positive and negative responses to this question. An example of the former would be modular reasoning systems specifically designed to promote system-oriented goals, whereas an example of the latter would be anti-patterns against system-oriented goals during software development. ************************************************************************* Â Programming for the Large 2018 Workshop Abstract submissions: Fri 26 Jan 2018 Â Â Submissions (full papers): Â Fri 2 Feb 2018 Â Â Position paper and work-in-progress paper submission: Tue 13 Feb 2018 Â Â Notifications: Â Fri 23 Feb 2018 https://2018.programmingconference.org/track/PftL-2018-papers ************************************************************************* In the last decade we have witnessed a new kid on the block in the programming (language) community: programming âlarge computersâ. Such computers include many-core machines, clusters of raspberry-pies, industry-scale cluster machines, cloud infrastructure, CUDA and MPI-based supercomputers etc. This workshop seeks to gather researchers that contribute to the simplification of the software stack that will be used to program such machinery in the near future. The main focus of the workshop is "Programming for the Large". Nonetheless, this workshop aims to bring together researchers from many disciplines: distributed programming, big data processing, distributed database engineering, etc. This workshop welcomes any contribution that advances the state-of-the-art in the design, implementation and engineering of runtime systems for cluster architectures. ************************************************************************* Â ProWeb 2018 - 2nd International Workshop on Programming Technology for the Future Web Â Â Submissions: Â Mon 15 Jan 2018 Â Â Notifications: Mon 12 Feb 2018 https://2018.programming-conference.org/track/proweb-2018-papers ************************************************************************* Web applications have become ubiquitous on desktop and mobile devices alike. Whereas âresponsiveâ web applications already offered a desktop-like experience, there is an increasing demand for ârichâ web applications (RIAs) that offer collaborative and even off-line functionality. ProWeb18, the 2nd International Workshop on Programming Technology for the Future Web, is a forum for researchers and practitioners to share and discuss new technology for programming these and future evolutions of the web. We welcome submissions introducing programming technology (i.e., frameworks, libraries, programming languages, program analyses and development tools) for implementing web applications and for maintaining their quality over time, as well as experience reports about the use of state-of-the-art programming technology. Relevant topics include, but are not limited to: program analysis and testing for the web; design and implementation of languages for the web; distributed technology for data sharing, replication and consistency; and security technology for the web. **************************************************************** PX/18 - 3rd Workshop on Programming Experience Â Â Submissions: Sat 3 Feb 2018 Â Â Notifications: Mon 26 Feb 2018 https://2018.programming-conference.org/track/px-2018-papers/ http://programming-experience.org/px18/ **************************************************************** PX is a workshop that explores the act of programming, in particular what programmers and programming teams do to create software. Do they type in source text and compile; do they modify running programs; what kinds of tools are available for error detection, correction, and prevention; what collaboration tools are available; what language features make some things easier (or harder); what constitutes programming; etc? The workshop is run as a writersâ workshop. **************************************************************** Â Salon des RefusÃ©s 2018 Â Â Submissions: Thu 1 Feb 2018 Â Â Notifications: Sat 17 Feb 2018 https://www.shift-society.org/salon/2018/ **************************************************************** Salon des RefusÃ©s ("exhibition of rejects") was an 1863 exhibition of artworks rejected from the official Paris Salon. It displayed works by later famous modernists such as Ãdouard Manet, whose paintings were rejected by the conservative jury of the Paris Salon. A similar space is needed to explore new ways of doing computer science. Many interesting ideas about programming struggle to find space in the modern programming language research community, often because they are difficult to evaluate. To provide space for unorthodox thought provoking ideas, we take inspiration from literary criticism. Papers that spark an interesting debate among the program committee are presented together with an attributed critique that discusses the merits of the work.

Dec. 14, 2017

P7 image and VM miss matches

by Hilaire

With latest VM for P7 fetched with get.pharo.org/vmTLatest70 <http://get.pharo.org/vmTLatest70> Then when using the VM with a P7 image: ./pharo ../../../DrGeoII/Dev-pharo7/Pharo7.0-64bit-f82fc36.image This error shows up: This interpreter (vers. 6521) cannot read image file (vers. 68021). Version: ./pharo --version 5.0-201708271955Â Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production Spur VM] CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 i686 i686 i386 GNU/Linux -- Dr. Geo http://drgeo.eu

Dec. 14, 2017

Re: [Pharo-users] Iceberg is cool!

by Sean P. DeNigris

NorbertHartl wrote > Well done and thank youâ¦ You broke the rule!!! We never say anything positive about Iceberg - only complaints - because we want to keep Esteban on his toes ha ha ;) Seriously though, it just keeps getting better and better over a very short timeâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 13, 2017

Re: [Pharo-users] Iceberg is cool!

by Norbert Hartl

> Am 13.12.2017 um 13:06 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Well, I am enjoying it too even if I still would need more features :) > BTW, how can I update a Pharo 6.1 that came with 0.6.2 to 0.6.5 ? Can I simply run the update script listed here [1] ? > I use <script> MetacelloPharoPlatform select. #( 'BaselineOfTonel' 'BaselineOfLibGit' 'BaselineOfIceberg' 'Iceberg-UI' 'Iceberg-Plugin-GitHub' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration' 'Iceberg-Libgit-Tonel' 'Iceberg-Libgit-Filetree' 'Iceberg-Libgit' 'Iceberg' 'LibGit-Core' 'MonticelloTonel-Tests' 'MonticelloTonel-Core' 'MonticelloTonel-FileSystem' ) do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem ]. latestRelease := ZnClient new url: 'https://api.github.com/repos/pharo-vcs/iceberg/releases/latest'; contentReader: [ :entity | (STON fromString: entity contents) at: 'tag_name' ]; get. Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:',latestRelease; load. </script> > Thanks in advance > > [1] https://github.com/pharo-vcs/iceberg#for-pharo-6 <https://github.com/pharo-vcs/iceberg#for-pharo-6> > > > > On Wed, Dec 13, 2017 at 8:42 AM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > I just got back from vacation and prepared a new image to work on the current project. Well, I upgraded iceberg to 0.6.5 and everything works like expected. I can see nicely what my colleagues have done while I was away. I can update everything easily. And most important I can do changes and then cherry pick and commit. > > So even if people are complaining about missing features (they always do!) I can say that for a basic workflow (for me about 95% of my work) everything seems to be in place. So everyone should feel invited to add the missing pieces. > > Well done and thank you, > > Norbert > > > > > -- > Mariano > http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>

Dec. 13, 2017

Re: [Pharo-users] Iceberg is cool!

by Mariano Martinez Peck

Well, I am enjoying it too even if I still would need more features :) BTW, how can I update a Pharo 6.1 that came with 0.6.2 to 0.6.5 ? Can I simply run the update script listed here [1] ? Thanks in advance [1] https://github.com/pharo-vcs/iceberg#for-pharo-6 On Wed, Dec 13, 2017 at 8:42 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > I just got back from vacation and prepared a new image to work on the > current project. Well, I upgraded iceberg to 0.6.5 and everything works > like expected. I can see nicely what my colleagues have done while I was > away. I can update everything easily. And most important I can do changes > and then cherry pick and commit. > > So even if people are complaining about missing features (they always do!) > I can say that for a basic workflow (for me about 95% of my work) > everything seems to be in place. So everyone should feel invited to add the > missing pieces. > > Well done and thank you, > > Norbert > > -- Mariano http://marianopeck.wordpress.com

Dec. 13, 2017