Squeak-dev January 2017

squeak-dev@lists.squeakfoundation.org

34 participants
77 discussions

The Trunk: Graphics-pre.367.mcz
by commits＠source.squeak.org 20 Jan '17

20 Jan '17

Patrick Rein uploaded a new version of Graphics to project The Trunk: http://source.squeak.org/trunk/Graphics-pre.367.mcz ==================== Summary ==================== Name: Graphics-pre.367 Author: pre Time: 20 January 2017, 5:44:33.081379 pm UUID: 6258ced8-1a7f-5344-914d-5a641a0734cf Ancestors: Graphics-bp.366 Implements HTML colors with 8 characters denoting RGBa colors. Small refactoring of fromString: method. =============== Diff against Graphics-bp.366 =============== Item was added: + ----- Method: Color class>>fromHTMLString: (in category 'other') ----- + fromHTMLString: aColorHex + "Do not call this method directly, call Color>>#fromString: instead as it is more generic" + + | green red blue resultColor | + red := (Integer readFrom: (aColorHex first: 2) base: 16). + green := (Integer readFrom: (aColorHex copyFrom: 3 to: 4) base: 16). + blue := (Integer readFrom: (aColorHex copyFrom: 5 to: 6) base: 16). + resultColor := self r: red g: green b: blue range: 255. + ^ (aColorHex size = 8) + ifTrue: [resultColor alpha: ((Integer readFrom: (aColorHex last: 2) base: 16) / 255)] + ifFalse: [resultColor]! Item was added: + ----- Method: Color class>>fromRGBString: (in category 'other') ----- + fromRGBString: rgb + "Do not call this method directly, call Color>>#fromString: instead as it is more generic" + + | green red blue | + red := (Integer readFrom:(rgb at: 1)) min: 255 max: 0. + green := (Integer readFrom:(rgb at: 2)) min: 255 max: 0. + blue := (Integer readFrom:(rgb at: 3)) min: 255 max: 0. + ^self r: red g: green b: blue range: 255! Item was changed: ----- Method: Color class>>fromString: (in category 'instance creation') ----- fromString: aString "for HTML color spec: #FFCCAA or white/black/red/other name, or an r,g,b triplet string" "Color fromString: '#FFCCAA'. Color fromString: 'white'. Color fromString: 'orange' Color fromString: '126,42,33' " | aColorHex rgb| aString isEmptyOrNil ifTrue: [ ^self white ]. aString first = $# ifTrue: [ aColorHex := aString allButFirst ] ifFalse: [ aColorHex := aString ]. + "is the string a 6 digit hex number?" + ((aColorHex size = 6 or: [aColorHex size = 8]) and: [ - (aColorHex size = 6 and: [ aColorHex allSatisfy: [ :each | '0123456789ABCDEFabcdef' includes: each ] ]) + ifTrue: [^ self fromHTMLString: aColorHex ]. + - ifTrue: [ - | green red blue | - red := (Integer readFrom: (aColorHex first: 2) base: 16). - green := (Integer readFrom: (aColorHex copyFrom: 3 to: 4) base: 16). - blue := (Integer readFrom: (aColorHex last: 2) base: 16). - ^self r: red g: green b: blue range: 255]. "is the string in the form a,b,c ?" rgb := aColorHex findTokens: $, . + rgb size = 3 ifTrue: [^ self fromRGBString: rgb]. + - rgb size = 3 ifTrue: [ - | green red blue | - red := (Integer readFrom:(rgb at: 1)) min: 255 max: 0. - green := (Integer readFrom:(rgb at: 2)) min: 255 max: 0. - blue := (Integer readFrom:(rgb at: 3)) min: 255 max: 0. - ^self r: red g: green b: blue range: 255]. "try to match aColorHex with known named colors, case insensitive" ^self perform: (ColorNames detect: [:colorSymbol | aColorHex sameAs: colorSymbol] ifNone: [ #white ])! Item was added: + ----- Method: TranslucentColor>>asHTMLColor (in category 'conversions') ----- + asHTMLColor + + ^ super asHTMLColor + , (Character digitValue: ((alpha bitShift: -4) bitAnd: 15)) + , (Character digitValue: (alpha bitAnd: 15))!

1 0

The Trunk: GraphicsTests-pre.42.mcz
by commits＠source.squeak.org 20 Jan '17

20 Jan '17

Patrick Rein uploaded a new version of GraphicsTests to project The Trunk: http://source.squeak.org/trunk/GraphicsTests-pre.42.mcz ==================== Summary ==================== Name: GraphicsTests-pre.42 Author: pre Time: 20 January 2017, 5:43:37.520379 pm UUID: 47dbcf43-ff4d-9648-ac3b-36b183918042 Ancestors: GraphicsTests-bp.41 Tests for HTML colors with 8 characters including alpha channel =============== Diff against GraphicsTests-bp.41 =============== Item was changed: ----- Method: ColorTest>>testAsHTMLColor (in category 'testing') ----- testAsHTMLColor | table aColorString | table := #('0' '1' '2' '3' '4' '5' '6' '7' '8' '9' 'A' 'B' 'C' 'D' 'E' 'F'). table do: [ :each | aColorString := '#', each, each, '0000'. + self assert: (Color fromString: aColorString) asHTMLColor equals: aColorString]. - self assert: ((Color fromString: aColorString) asHTMLColor sameAs: aColorString)]. table do: [ :each | aColorString := '#', '00', each, each, '00'. + self assert: (Color fromString: aColorString) asHTMLColor equals: aColorString]. - self assert: ((Color fromString: aColorString) asHTMLColor sameAs: aColorString)]. table do: [ :each | aColorString := '#', '0000', each, each. + self assert: (Color fromString: aColorString) asHTMLColor equals: aColorString]. - self assert: ((Color fromString: aColorString) asHTMLColor sameAs: aColorString)]. table do: [ :each | aColorString := '#', each, each, each, each, each, each. + self assert: (Color fromString: aColorString) asHTMLColor equals: aColorString]. + + table do: [ :each | + aColorString := '#', each, each, each, each, each, each, each, each. + each = 'F' + ifTrue: [self assert: (Color fromString: aColorString) asHTMLColor equals: '#FFFFFF' description: 'For full alpha channel the no alpha color is used'] + ifFalse: [self assert: (Color fromString: aColorString) asHTMLColor equals: aColorString]].! - self assert: ((Color fromString: aColorString) asHTMLColor sameAs: aColorString)].! Item was changed: ----- Method: ColorTest>>testFromString (in category 'testing') ----- testFromString self assert: ((Color fromString: '#FF8800') asHTMLColor sameAs: '#ff8800'); assert: ((Color fromString: 'FF8800') asHTMLColor sameAs: '#ff8800'); + assert: ((Color fromString: '126,42,33') asHTMLColor sameAs: '#7E2A21'); + assert: ((Color fromString: '00000000') asHTMLColor sameAs: '#00000000'); "html with alpha channel" + assert: ((Color fromString: '#8C500BAE') asHTMLColor sameAs: '#8C500BAE'); assert: ((Color fromString: 'white') asHTMLColor sameAs: '#ffffff'); assert: ((Color fromString: 'black') asHTMLColor sameAs: '#000000'); assert: ((Color fromString: nil) asHTMLColor sameAs: '#ffffff'); assert: ((Color fromString: 'inexistent color') asHTMLColor sameAs: '#ffffff'); "should return white" + assert: ((Color fromString: 'XXXXXX') asHTMLColor sameAs: '#ffffff') description: 'Color string should be alphanumeric'; + assert: ((Color fromString: '000000000') asHTMLColor sameAs: '#ffffff') description: 'number string too long'. - assert: ((Color fromString: 'XXXXXX') asHTMLColor sameAs: '#ffffff'); "not alphanumeric" - assert: ((Color fromString: '00000000') asHTMLColor sameAs: '#ffffff'). "too many digits" self assert: (Color fromString: 'DARKGRAY') = Color darkGray description: 'Color can be specified with a case insensitive color name'; assert: (Color fromString: '#blue') = Color blue description: 'Color can be specified with a leading literal sharp'.!

1 0

<Programming> 2017: Final call for workshop, symposium, demo & poster submissions
by Tim Molderez 20 Jan '17

20 Jan '17

----------------------------------------------------------------------- <Programming> 2017 : The Art, Science, and Engineering of Programming April 3-6, 2017, Brussels, Belgium http://2017.programming-conference.org ----------------------------------------------------------------------- Final call for submissions to all co-located events at the <Programming> 2017 conference: - ELS 2017 - 10th European Lisp Symposium - Modularity 2017 Invited talks - International Symposium on Modularity - **Updated** ACM Student Research Competition / <Programming> 2017 Posters - **NEW** <Programming> 2017 Demos - **NEW** CoCoDo 2017 - Raincode Labs Compiler Coding Dojo - LASSY 2017 - 2nd Workshop on Live Adaptation of Software SYstems - **NEW** MiniPLoP 2017 - Mini Pattern Languages of Programs writers' workshop - **Updated** MOMO 2017 - 2nd Workshop on Modularity in Modelling - MoreVMs 2017 - 1st Workshop on Modern Language Runtimes, Ecosystems, and VMs - PASS 2017 - 1st Workshop on Programming Across the System Stack - PX 2017 - 2nd Workshop on Programming Experience - ProWeb 2017 - 1st Workshop on Programming Technology for the Future Web - Salon des Refusés 2017 - 1st edition of the Salon des Refusés workshop All co-located events will take place during April 3-4 2017. CFPs for each of these events are listed below. (apart from Modularity 2017, which is invitation-based) **************************************************************** ELS 2017 - 10th European Lisp Symposium Submissions: Mon 30 Jan 2017 Notifications: Mon 27 Feb 2017 Symposium date: Mon Apr 3 - Tue Apr 4 2017 http://2017.programming-conference.org/track/els-2017 **************************************************************** The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The 10th European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: * Context-, aspect-, domain-oriented and generative programming * Macro-, reflective-, meta- and/or rule-based development approaches * Language design and implementation * Language integration, inter-operation and deployment * Development methodologies, support and environments * Educational approaches and perspectives * Experience reports and case studies ******************************************************************** ACM Student Research Competition / <Programming> 2017 Posters Submissions **extended** : Mon 30 Jan 2017 http://2017.programming-conference.org/track/programming-posters ******************************************************************** 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. See our website for requirements and further details. Please note that, while the SRC involves a poster session, there also is a regular poster session that isn't part of a competition. Submissions for this regular session are due March 3rd. *********************************************************************** ‹Programming› 2017 Demos Submissions: Fri 3 Mar 2017 http://2017.programming-conference.org/track/programming-2017-Demos *********************************************************************** Demonstrations will be selected on the basis of technical merit, relevance, and novelty of presentation at <Programming>. They can include work in progress, commercial or in-house applications, proofs of concept, results of academic or industrial research, or any other innovative programming tools or systems. We encourage authors of accepted papers to co-located workshops and main conferences also submit a demo proposal. We hope that this will give them the opportunity to show their work in action, and increase the visibility of their results. We suggest to cite the paper in the demo abstract. **************************************************************** CoCoDo 2017 - Raincode Labs Compiler Coding Dojo Coding dojo date: Tue 4 Apr 2017 https://cocodo.github.io **************************************************************** CoCoDo is a coding dojo where you can enjoy an entire day of compiler programming under gentle guidance of field experts. Compiler construction comprises, but is not limited to, lexical analysis, syntactic analysis, preprocessing, context handling, code generation, code optimisation, virtual machines, interpreters, smell detection, clone management, portability, migration, refactoring, domain-specific language design, linking and loading, assembling and disassembling, generics and reflection, numerous paradigms and so much more. If you are interested in participating, please contact Vadim Zaytsev: vadim(a)raincodelabs.com ****************************************************************** LASSY 2017 - 2nd Workshop on Live Adaptation of Software SYstems Submissions: Fri 3 Feb 2017 Notifications: Fri 3 Mar 2017 Workshop date: Mon 3 Apr 2017 http://2017.programming-conference.org/track/LASSY-2017-papers ****************************************************************** When developing current-day software systems, their deployment and usage environments should be considered carefully, in order to understand the adaptations those systems might need to undergo to interact with other systems and with their environment. Moreover, due to the portability, mobility and increasingly evolutionary nature of software systems, such adaptations should be enacted even while the system is running. Developing such software systems can prove challenging, and many seemingly different techniques to address this concern have been proposed over the last couple of years. The intention of the LASSY workshop is to congregate all topics relevant to dynamic adaptation and run-time evolution of software systems, ranging from a computer science perspective covering the domains of programming languages, model-driven software development, software and service composition, context-aware databases, software variability, requirements engineering, UI adaptation and other domains, to a human perspective covering sociological or ethical implications of dynamic software systems. The 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. Topics of Interest: * Design and Implementation of Live Adaptive Software Systems * Context-, aspect-, feature-, role- and agent-oriented programming * Context representation and discovery * Context-aware model-driven software development * Context-aware data management * Software variability and dynamic product lines * Self-adaptive, self-explanatory systems * Inconsistency management, verification, and validation * Middleware and Runtime of Live Adaptive Software Systems * Dynamic software evolution, upgrades and configuration * Dynamic software and service composition mechanisms * Dynamic software architecture and middleware approaches * Dynamic user interface adaptation and multimodal user interfaces * Impact and Assessment of Live Adaptive Software Systems * User acceptance and usability issues * Human, sociological, ethical and legal aspects * Privacy and security aspects of dynamic adaptability * Live adaptation in smart environments (e.g. smart rooms, smart robot cells, smart factories, smart cities) * Self-adaptation and emergence in SoS and CPSoS ********************************************************************** MiniPLoP 2017 - Mini Pattern Languages of Programs writers' workshop Workshop date: Mon 3 Apr 2017 http://2017.programming-conference.org/track/MiniPLoP-2017-papers ********************************************************************** Software developers and those involved with programming have long observed that certain patterns recur and endure across different applications and systems. The growing interest in Design Patterns, Architectural Patterns, Analysis Patterns, Pedagogical Patterns, Agile Patterns, and so on, represents an effort to catalog and better communicate knowledge, providing handbooks of proven solutions to common problems. The MiniPLoP writers' workshop brings together researchers, educators, and practitioners whose interests span a remarkably broad range of topics and who share an interest in exploring the power of the pattern form. MiniPLoP invites you to add your expertise to the growing corpus of patterns. MiniPLoP focuses on improving the expression of patterns. You will have the opportunity to refine and extend your patterns or pattern ideas with the help from knowledgeable and sympathetic fellow pattern enthusiasts. You will also be able to discuss applications of patterns in industry and academia. Techniques for Pattern Mining will also be presented. Highlights include group discussions on patterns, an introduction to pattern writing, an international keynote, and the writers’ workshop. This MiniPLoP at <Programming> 2017 has the goal to help beginners learn more about the pattern community. If you have some patterns or pattern ideas you would like to have brainstormed or workshopped, please contact the organizers at: miniplop2017(a)hillside.net **************************************************************** MOMO 2017 - 2nd Workshop on Modularity in Modelling Abstract submissions (optional) **extended** : Sun Feb 5 2017 Paper submissions **extended** : Sun Feb 12 2017 Notifications: Wed Feb 22 2017 Workshop date: Mon 3 Apr 2017 http://www.momo2017.ece.mcgill.ca/cfp.htm **************************************************************** Extending the time-honored practice of separation of concerns, Model-Driven Engineering (MDE) promotes the use of separate models to address the various concerns in the development of complex software-intensive systems. The main objective is to choose the right level of abstraction to modularize a concern, specify its properties and reason about the system under development depending on stakeholder and development needs. While some of these models can be defined with a single modelling language, a variety of heterogeneous models and languages are typically used in the various phases of software development. Furthermore, Domain-Specific Modelling Languages designed to address particular concerns are also increasingly used. 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. As a result, many (standard) modelling notations have been extended with aspect-oriented mechanisms and advanced composition operators to support advanced separation of concerns, to combine (possibly heterogeneous) models modularizing different concerns, to execute an application based on modularized models, and to reason over global properties of modularized models. The Second International Modularity in Modelling Workshop brings together researchers and practitioners interested in the theoretical and practical challenges resulting from applying modularity, advanced separation of concerns, and advanced 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. We are interested in submissions on all topics related to modularity and modelling including but not limited to: * Modularization Support in Modelling Languages and Tools * Model Interfaces * Homogeneous Model Composition Operators * Heterogeneous Model Composition Operators * Visualization of Modularized and Composed Models * Effects of Using Modularization and Composition in Modelling * On Verification and Validation * On Reuse * On the Model-Driven Software Development Process (Requirements Engineering, Software Architecture, Software Design, Implementation) * On Maintenance * Experience Reports / Empirical Evaluations of Applying Modularization and Composition in Modelling * Feature-Oriented, Aspect-Oriented and Concern-Oriented Modelling * Modularization support and composition operators for specific modelling notations * Modelling essential characteristics of specific (crosscutting) concerns * Multi-View Modelling: avoiding inconsistencies, avoiding Redundancies * Support for Detecting and/or Resolution of Feature Interactions * Domain-Specific Modelling * Modularization for Domain-Specific Languages * Composition for Domain-Specific Languages * Domain-specific Aspect Models ****************************************************************************** MoreVMs 2017 - 1st Workshop on Modern Language Runtimes, Ecosystems, and VMs Submissions: Wed 15 Feb 2017 Notifications: Wed 1 Mar 2017 Workshop date: Mon 3 Apr 2017 http://2017.programming-conference.org/track/MoreVMs-2017-papers ****************************************************************************** The main goal of the workshop is to bring together both researchers and practitioners and facilitate effective sharing of their respective experiences and ideas on how languages and runtimes are 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 the academic as well as industrial perspective. Relevant topics include, but are definitely not limited to, the following: * Extensible VM design (compiler- or interpreter-based VMs) * Reusable runtime components (e.g. interpreters, garbage collectors, intermediate representations) * Static and dynamic compiler techniques * Techniques for compilation to high-level languages such as JavaScript * Runtimes and mechanisms for interoperability between languages * Tooling support (e.g. debugging, profiling, etc.) * Programming language development environments and virtual machines * Case studies of existing language implementations, virtual machines, and runtime components (e.g. design choices, tradeoffs, etc.) * Language implementation challenges and trade-offs (e.g. performance, completeness, etc.) * Surveys and applications usage reports to understand runtime usage in the wild * Surveys on frameworks and their impact on runtime usage * New research ideas on how we want to build languages in the future ************************************************************************** PASS 2017 - 1st Workshop on Programming Across the System Stack Submissions: Mon 13 Feb 2017 Notifications: Mon 27 Feb 2017 Workshop date: Tue 4 Apr 2017 http://2017.programming-conference.org/track/PASS-2017#Call-for-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. Current methodologies and software development technologies should be revised in order to produce software to meet system-oriented goals, while preserving high internal code quality. The role of the Software Engineer is essential, having to be aware of the implications that each design, architecture and implementation decision has on the application system ecosystem. 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. Areas of interest include but are not limited to: * Energy-aware software engineering (e.g. energy efficiency models, energy efficiency as a quality attribute) * Modularity support (e.g., programming language design, development tools or verification) for applications in resource-constrained or real-time systems * Emerging platforms (e.g., Internet of Things and wearable devices) * Security support (e.g., compositional information flow, compositional program analysis) * Software architecture for reusability and adaptability in systems and their interactions with applications * Empirical studies (patterns and anti-patterns) on the relationship between internal code quality and system-oriented goals * Software engineering techniques to balance the trade-off between internal code quality and efficiency * Memory bloats and long-tail performance problems across modular boundaries * Program optimization across modular boundaries * Internal code quality in systems software * Reasoning across applications, compilers, and virtual machines **************************************************************** PX 2017 - 2nd Programming Experience Workshop Submissions: Sat 4 Feb 2017 Notifications: Mon 27 Feb 2017 Workshop date: Mon 3 Apr 2017 http://programming-experience.org/px17 **************************************************************** Imagine a software development task: some sort of requirements and specification including performance goals and perhaps a platform and programming language. A group of developers head into a vast workroom. In that room they discover they need to explore the domain and the nature of potential solutions—they need exploratory programming. The Programming Experience Workshop is about what happens in that room when one or a couple of programmers sit down in front of computers and produce code, especially when it’s exploratory programming. Do they create text that is transformed into running behavior (the old way), or do they operate on behavior directly (“liveness”); are they exploring the live domain to understand the true nature of the requirements; are they like authors creating new worlds; does visualization matter; is the experience immediate, immersive, vivid and continuous; do fluency, literacy, and learning matter; do they build tools, meta-tools; are they creating languages to express new concepts quickly and easily; and curiously, is joy relevant to the experience? Correctness, performance, standard tools, foundations, and text-as-program are important traditional research areas, but the experience of programming and how to improve and evolve it are the focus of this workshop, and in this edition we would like to focus on exploratory programming. The technical topics include: * Exploratory programming * Live programming * Authoring * Representation of active content * Visualization * Navigation * Modularity mechanisms * Immediacy * Literacy * Fluency * Learning * Tool building * Language engineering ************************************************************************* ProWeb 2017 - 1st Workshop on Programming Technology for the Future Web Submissions: Wed 15 Feb 2017 Notifications: Wed 1 Mar 2017 Workshop date: Tue 4 Apr 2017 http://2017.programming-conference.org/track/proweb-2017-papers ************************************************************************* Full-fledged web applications have become ubiquitous on desktop and mobile devices alike. Whereas “responsive” web applications already offered a more desktop-like experience, there is an increasing demand for “rich” web applications (RIAs) that offer collaborative and even off-line functionality —Google docs being the prototypical example. Long gone are the days that web servers merely had to answer incoming HTTP request with a block of static HTML. Today’s servers react to a continuous stream of events coming from JavaScript applications that have been pushed to clients. As a result, application logic and data is increasingly distributed. Traditional dichotomies such as “client vs. server” and “offline vs. online” are fading. The 1st International Workshop on Programming Technology for the Future Web, or ProWeb17, 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: * Quality on the new web: static and dynamic program analyses; code, design test and process metrics; development and migration tools; automated testing and test generation; contract systems, type systems, and web service API conformance checking; … * Hosting languages on the web: new runtimes; transpilation or compilation to JavaScript, WebAssembly, asm.js, … * Designing languages for the web: multi-tier (or tierless) programming; reactive programming; frameworks for multi-tier or reactive programming on the web; … * Distributed data sharing, replication and consistency: cloud types, CRDTs, eventual consistency, offline storage, peer-to-peer communication, … * Security on the web: client-side and server-side security policies; policy enforcement; proxies and membranes; vulnerability detection; dynamic patching, … * Surveys and case studies using state-of-the-art web technology (e.g., WebAssembly, WebSocket, LocalStorage, AppCache, ServiceWorkers, Meteor, deepstream.io, Angular.js, React and React Native, Swarm.js, Caja, TypeScript, Proxies, ClojureScript, Amber Smalltalk, Scala.js, …) * Ideas on and experience reports about: how to reconcile the need for quality with the need for agility on the web; how to master and combine the myriad of tier-specific technologies required to develop a web application, … * Position statements on what the future of the web will look like **************************************************************** Salon des Refusés 2017 Submissions: Wed 1 Feb 2017 Notifications: Fri 17 Feb 2017 Workshop date: Tue 4 Apr 2017 https://refuses.github.io **************************************************************** Salon des Refusés (“exhibition of rejects”) was an 1863 exhibition of artworks rejected from the official Paris Salon. The jury of Paris Salon required near-photographic realism and classified works according to a strict genre hierarchy. Paintings by many, later famous, modernists such as Édouard Manet were rejected and appeared in what became known as the Salon des Refusés. This workshop aims to be the programming language research equivalent of Salon des Refusés. We provide a venue for exploring new ideas and new ways of doing computer science. Many interesting ideas about programming might struggle to find space in the modern programming language research community, often because they are difficult to evaluate using established evaluation methods (be it proofs, measurements or controlled user studies). As a result, new ideas are often seen as “unscientific”. This workshop provides a venue where such interesting and thought-provoking ideas can be exposed to critical evaluation. Submissions that provoke interesting discussion among the program committee members will be published together with an attributed review that presents an alternative position, develops additional context or summarizes discussion from the workshop. This means of engaging with papers not just enables explorations of novel programming ideas, but also encourages new ways of doing computer science. Topics of interest The scope of the workshop is determined more by the format of submissions than by the specific area of programming language or computer science research that we are interested in. We welcome submissions in a format that makes it possible to think about programming in a new way, including, but not limited to: * Thought experiments – we believe that thought experiments, analogies and illustrative metaphors can provide novel insights and inspire fruitful programming language ideas. * Experimentation – we find prejudices in favour of theory, as far back as there is institutionalized science, but programming can often be seen more as experimentation than as theorizing. We welcome interesting experiments even if there is yet no overarching theory that explains why they happened. * Paradigms – all scientific work is rooted in a scientific paradigm that frame what questions can be asked. We encourage submissions that reflect on existing paradigms or explore alternative scientific paradigms. * Metaphors, myths and analogies – any description of formal, mathematical, quantitative or even poetical nature still represents just an analogy. We believe that fruitful ideas can be learned from less common forms of analogies as well as from the predominant, formal and mathematical ones. * From jokes to science fiction – a story or an artistic performance may explore ideas and spark conversations that provide crucial inspiration for development of new computer science thinking.

1 0

Swiss speed page is a bit out of date...
by tim Rowledge 20 Jan '17

20 Jan '17

It’s not been updated since may ’09. Somebody could have a lot of fun updating that and comparing numbers... tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Useful random insult:- Doesn't just know nothing; doesn't even suspect much.

4 7

Support for LP64 & LLP64 in FFI Kernel
by Eliot Miranda 19 Jan '17

19 Jan '17

Hi All, currently the FFI has support for 8, 16, 32 & 64 bit integers, but no support for C's long type. In almost all C implementations byte is 8 bits, short is 16 bits, int is 32 bits and long long is 64 bits. But long may be either 32 or 64 bits depending on programming model. In LP32 long is 32 bits, which is used in 32-bit unix, mac os and windows. In LP64 long is 64 bits, which is used in 64-bit unix and mac os. In LLP64 long is 32 bits, which is used in 64-bit windows. So having a type which is either 32 or 64 bits depending on platform is useful in modeling C's long type across platforms. Esteban and I propose adding such a type to FFI kernel, actually two types, one unsigned, one signed. So we propose extending the below (these constants are used to define signatures for FFI calls and the contents of structs) FFIConstants class>>#initializeTypeConstants "type void" FFITypeVoid := 0. "type bool" FFITypeBool := 1. "basic integer types. note: (integerType anyMask: 1) = integerType isSigned" FFITypeUnsignedByte := 2. FFITypeSignedByte := 3. FFITypeUnsignedShort := 4. FFITypeSignedShort := 5. FFITypeUnsignedInt := 6. FFITypeSignedInt := 7. "64bit types" FFITypeUnsignedLongLong := 8. FFITypeSignedLongLong := 9. "special integer types" FFITypeUnsignedChar := 10. FFITypeSignedChar := 11. "float types" FFITypeSingleFloat := 12. FFITypeDoubleFloat := 13. "type flags" FFIFlagAtomic := 16r40000. "type is atomic" FFIFlagPointer := 16r20000. "type is pointer to base type" FFIFlagStructure := 16r10000. "baseType is structure of 64k length" FFIStructSizeMask := 16rFFFF. "mask for max size of structure" FFIAtomicTypeMask := 16r0F000000. "mask for atomic type spec" FFIAtomicTypeShift := 24. "shift for atomic type" to add to "special integer types" FFITypeUnsignedChar := 10. FFITypeSignedChar := 11. FFITypePlatformUnsignedLong := 14. FFITypePlatformSignedLong := 15. This is backward compatible, even if it complicates the marshaling a little since it used to be that all integer types were less than FFITypeSingleFloat. But breaking backward compatibility would be a bad idea. Then in ByteArray et al we could add accessors for platformLongAt: platformUnsignedLongAt:. Comments, thoughts, objections? _,,,^..^,,,_ best, Eliot

2 1

Re: [squeak-dev] Squeak 4.6: MultilingualTests-fbs.18.mcz
by H. Hirzel 19 Jan '17

19 Jan '17

Reactivating an old thread ... Taking the test above just gives a question mark for the fallback font case | text font bb destPoint | text := (Character value: 257) asString asText. font := TextStyle default fontOfSize: 21. text addAttribute: (TextFontReference toFont: font). bb := (Form extent: 100 @ 30) getCanvas privatePort. bb combinationRule: Form paint. font installOn: bb foregroundColor: Color black backgroundColor: Color white. destPoint := font displayString: text asString on: bb from: 1 to: 1 at: 0@0 kern: 1. bb destForm asMorph openInHand. Is there another fallback font readily available which gives for small hex numbers for the missing characters? --Hannes On Fri, 5 Jun 2015 20:20:36.139 0000, commits(a)source.squeak.org <commits(a)source.squeak.org> wrote: > Chris Muller uploaded a new version of MultilingualTests to project Squeak > 4.6: > http://source.squeak.org/squeak46/MultilingualTests-fbs.18.mcz > > ==================== Summary ==================== > > Name: MultilingualTests-fbs.18 > Author: fbs > Time: 6 November 2013, 6:35:02.811 pm > UUID: 07e26018-8455-3349-9b44-9ecb4aaeefb2 > Ancestors: MultilingualTests-nice.17 > > More #shouldnt:raise: Error fixes. > > ==================== Snapshot ==================== > > SystemOrganization addCategory: #'MultilingualTests-TextConversion'! > SystemOrganization addCategory: #'MultilingualTests-Display'! > > TestCase subclass: #FontTest > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'MultilingualTests-Display'! > > !FontTest commentStamp: 'tak 3/11/2005 14:31' prior: 0! > I am mainly a test for fallback font. > FontTest buildSuite run! > > ----- Method: FontTest>>testDisplay (in category 'testing') ----- > testDisplay > "self debug: #testDisplay" > | text font bb destPoint width | > text := 'test' asText. > font := TextStyle default fontOfSize: 21. > text addAttribute: (TextFontReference toFont: font). > bb := (Form extent: 100 @ 30) getCanvas privatePort. > bb combinationRule: Form paint. > > font installOn: bb foregroundColor: Color black backgroundColor: Color > white. > destPoint := font displayString: text asString on: bb from: 1 to: 4 at: 0@0 > kern: 1. > > width := text inject: 0 into: [:max :char | max + (font widthOf: char)]. > self assert: destPoint x = (width + 4). > "bb destForm asMorph openInHand." > ! > > ----- Method: FontTest>>testFallback (in category 'testing') ----- > testFallback > "self debug: #testFallback" > | text font bb destPoint | > text := (Character value: 257) asString asText. > font := TextStyle default fontOfSize: 21. > text addAttribute: (TextFontReference toFont: font). > bb := (Form extent: 100 @ 30) getCanvas privatePort. > bb combinationRule: Form paint. > > font installOn: bb foregroundColor: Color black backgroundColor: Color > white. > destPoint := font displayString: text asString on: bb from: 1 to: 1 at: 0@0 > kern: 1. > > "bb destForm asMorph openInHand." > self assert: destPoint x = ((font widthOf: $?) + 1). > ! > > ----- Method: FontTest>>testMultistringFallbackFont (in category 'testing') > ----- > testMultistringFallbackFont > "self debug: #testMultistringFallbackFont" > | text p style height width | > [(TextStyle default fontArray at: JapaneseEnvironment leadingChar) > ifNil: [^ self]] > ifError: [:err :rcvr | ^ self]. > text := ((#(20983874 20983876 20983878 ) > collect: [:e | e asCharacter]) > as: String) asText. > p := NewParagraph new. > style := TextStyle new leading: 0; newFontArray: {Preferences > standardFlapFont}. > p > compose: text > style: style > from: 1 > in: (0 @ 0 corner: 100 @ 100). > "See CompositionScanner>>setActualFont: & > CompositionScanner>>composeFrom:inRectangle:firstLine:leftSide:rightSide:" > height := style defaultFont height + style leading. > width := text > inject: 0 > into: [:tally :next | tally > + (style defaultFont widthOf: next)]. > p adjustRightX. > self assert: p extent = (width @ height). > "Display getCanvas > paragraph: p > bounds: (10 @ 10 extent: 100 @ 100) > color: Color black"! > > ----- Method: FontTest>>testMultistringFont (in category 'testing') ----- > testMultistringFont > "self debug: #testMultistringFont" > | text p style height width | > [(TextStyle default fontArray at: JapaneseEnvironment leadingChar) > ifNil: [^ self]] > ifError: [:err :rcvr | ^ self]. > text := ((#(20983874 20983876 20983878 ) > collect: [:e | e asCharacter]) > as: String) asText. > p := NewParagraph new. > style := TextStyle default. > p > compose: text > style: style > from: 1 > in: (0 @ 0 corner: 100 @ 100). > "See CompositionScanner>>setActualFont: & > CompositionScanner>>composeFrom:inRectangle:firstLine:leftSide:rightSide:" > height := style defaultFont height + style leading. > width := text > inject: 0 > into: [:tally :next | tally > + (style defaultFont widthOf: next)]. > p adjustRightX. > self assert: p extent = (width @ height). > "Display getCanvas > paragraph: p > bounds: (10 @ 10 extent: 100 @ 100) > color: Color black"! > > ----- Method: FontTest>>testParagraph (in category 'testing') ----- > testParagraph > "self debug: #testParagraph" > | text p style height width | > text := 'test' asText. > p := NewParagraph new. > style := TextStyle default. > p > compose: text > style: style > from: 1 > in: (0 @ 0 corner: 100 @ 100). > "See CompositionScanner>>setActualFont: & > CompositionScanner>>composeFrom:inRectangle:firstLine:leftSide:rightSide:" > height := style defaultFont height + style leading. > width := text > inject: 0 > into: [:tally :next | tally > + (style defaultFont widthOf: next)]. > p adjustRightX. > self assert: p extent = (width @ height)! > > ----- Method: FontTest>>testParagraphFallback (in category 'testing') ----- > testParagraphFallback > "self debug: #testParagraphFallback" > | text p style height width e expect | > e := (Character value: 257) asString. > text := ('test' , e , e , e , e , 'test') asText. > expect := 'test????test'. > p := NewParagraph new. > style := TextStyle default. > p > compose: text > style: style > from: 1 > in: (0 @ 0 corner: 100 @ 100). > "See CompositionScanner>>setActualFont: & > CompositionScanner>>composeFrom:inRectangle:firstLine:leftSide:rightSide:" > height := style defaultFont height + style leading. > width := expect > inject: 0 > into: [:tally :next | tally > + (style defaultFont widthOf: next)]. > p adjustRightX. > self assert: p extent = (width @ height). > "Display getCanvas > paragraph: p > bounds: (10 @ 10 extent: 100 @ 100) > color: Color black"! > > ----- Method: FontTest>>testResetAfterEmphasized (in category 'testing') > ----- > testResetAfterEmphasized > "self debug: #testResetAfterEmphasized" > | normal derivative | > normal := TextStyle defaultFont. > derivative := normal emphasized: 3. > self assert: (normal derivativeFonts at: 3) == derivative. > normal reset. > self assert: (normal derivativeFonts select:[:any| any isSynthetic]) > isEmpty > ! > > TestCase subclass: #MultiByteFileStreamTest > instanceVariableNames: 'fileName' > classVariableNames: '' > poolDictionaries: '' > category: 'MultilingualTests-TextConversion'! > > ----- Method: MultiByteFileStreamTest>>tearDown (in category 'running') > ----- > tearDown > > fileName ifNotNil: [ > FileDirectory default deleteFileNamed: fileName ]! > > ----- Method: MultiByteFileStreamTest>>testAsciiBackChunk (in category > 'testing') ----- > testAsciiBackChunk > > fileName := 'foobackchunk.txt'. > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > file > lineEndConvention: #cr; > converter: UTF8TextConverter new; > cr; nextChunkPut: 'test1' printString; > cr; nextChunkPut: 'test2' printString. > self > assert: file backChunk = (String cr , 'test2' printString); > assert: file backChunk = (String cr , 'test1' printString) ]! > > ----- Method: MultiByteFileStreamTest>>testBinaryUpTo (in category > 'testing') ----- > testBinaryUpTo > "This is a non regression test for bug > http://bugs.squeak.org/view.php?id=6933" > > fileName := 'foobug6933'. > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > file > binary; > nextPutAll: #[ 1 2 3 4 ] ]. > MultiByteFileStream oldFileNamed: fileName do: [ :file | > file binary. > self assert: (file upTo: 3) = #[ 1 2 ] ]! > > ----- Method: MultiByteFileStreamTest>>testByteTextConverter (in category > 'testing') ----- > testByteTextConverter > | strings converterClasses | > strings := { > String newFrom: ((0 to: 255) collect: [:e | e asCharacter]). > }. > > converterClasses := ByteTextConverter allSubclasses. > converterClasses do: [:converterClass | > strings do: [:string | | converter stream encoded decoded encoded2 | > converter := converterClass new. > stream := string readStream. > encoded := string select: [:e | (converter nextFromStream: stream) > notNil]. > stream := encoded readStream. > decoded := encoded collect: [:e | converter nextFromStream: stream]. > self assert: stream atEnd. > stream := String new writeStream. > converter nextPutAll: decoded toStream: stream. > encoded2 := stream contents. > self assert: (encoded2 collect: [:e | e charCode] as: Array) = (encoded > collect: [:e | e charCode] as: Array). > stream := String new writeStream. > decoded do: [:e | converter nextPut: e toStream: stream]. > encoded2 := stream contents. > self assert: (encoded2 collect: [:e | e charCode] as: Array) = (encoded > collect: [:e | e charCode] as: Array)]]! > > ----- Method: > MultiByteFileStreamTest>>testLineEndConvention:withConverter:ifFail: (in > category 'helpers') ----- > testLineEndConvention: lineEndConvention withConverter: textConverterClass > ifFail: failBlock > > | expectedResult result | > [ > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > file > converter: textConverterClass new; > lineEndConvention: lineEndConvention; > cr; > nextPut: Character cr; > nextPutAll: String cr; > nextPutAll: String cr asWideString ]. > result := StandardFileStream oldFileNamed: fileName do: [ :file | > file contents ]. > expectedResult := String streamContents: [ :stream | > 4 timesRepeat: [ stream perform: lineEndConvention ] ]. > result = expectedResult ifFalse: [ > failBlock value: expectedResult asByteArray value: result asByteArray ] > ] > on: Error > do: [ :err | failBlock value: err messageText value: err messageText ]! > > ----- Method: MultiByteFileStreamTest>>testLineEndConversion (in category > 'testing') ----- > testLineEndConversion > > | failures | > fileName := 'foolinendconversion.txt'. > failures := OrderedCollection new. > TextConverter allSubclassesDo: [ :textConverterClass | > textConverterClass encodingNames ifNotEmpty: [ > #(cr lf crlf) do: [ :lineEndConvention | > self > testLineEndConvention: lineEndConvention > withConverter: textConverterClass > ifFail: [ :expectedResult :result | > failures add: { > textConverterClass. > lineEndConvention. > expectedResult. > result } ] ] ] ]. > self assert: failures isEmpty! > > ----- Method: MultiByteFileStreamTest>>testLineEnding (in category > 'testing') ----- > testLineEnding > > fileName := 'foolinend.txt'. > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > file > wantsLineEndConversion: false; > nextPutAll: 'line 1'; cr; > nextPutAll: 'line 2'; crlf; > nextPutAll: 'line 3'; lf; > nextPutAll: 'line 4' ]. > { > {#cr. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String cr > , 'line 4'}. > {#lf. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String cr > , 'line 4'}. > {#crlf. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String > cr , 'line 4'}. > {nil. 'line 1' , String cr , 'line 2' , String crlf , 'line 3' , String > lf , 'line 4'} > } do: [:lineEndingResult | > MultiByteFileStream oldFileNamed: fileName do: [ :file | > file lineEndConvention: lineEndingResult first. > self assert: file upToEnd = lineEndingResult last ] ]! > > ----- Method: MultiByteFileStreamTest>>testLineEndingChunk (in category > 'testing') ----- > testLineEndingChunk > > fileName := 'foolinend.txt'. > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > file > wantsLineEndConversion: false; > nextPutAll: 'line 1'; cr; > nextPutAll: 'line 2'; crlf; > nextPutAll: 'line 3'; lf; > nextPutAll: 'line 4'; nextPut: $!! ]. > { > {#cr. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String cr > , 'line 4'}. > {#lf. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String cr > , 'line 4'}. > {#crlf. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String > cr , 'line 4'}. > {nil. 'line 1' , String cr , 'line 2' , String crlf , 'line 3' , String > lf , 'line 4'} > } do: [:lineEndingResult | > MultiByteFileStream oldFileNamed: fileName do: [ :file | > file lineEndConvention: lineEndingResult first. > self assert: lineEndingResult last equals: file nextChunk ] ]! > > ----- Method: MultiByteFileStreamTest>>testLineEndingWithWideStrings (in > category 'testing') ----- > testLineEndingWithWideStrings > > | cr lf crlf | > fileName := 'foolinend.txt'. > cr := String cr asWideString. > lf := String lf asWideString. > crlf := String crlf asWideString. > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > file > wantsLineEndConversion: false; > nextPutAll: 'line 1'; nextPutAll: cr; > nextPutAll: 'line 2'; nextPutAll: crlf; > nextPutAll: 'line 3'; nextPutAll: lf; > nextPutAll: 'line 4' ]. > { > {#cr. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String cr > , 'line 4'}. > {#lf. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String cr > , 'line 4'}. > {#crlf. 'line 1' , String cr , 'line 2' , String cr , 'line 3' , String > cr , 'line 4'}. > {nil. 'line 1' , String cr , 'line 2' , String crlf , 'line 3' , String > lf , 'line 4'} > } do: [ :lineEndingResult | > MultiByteFileStream oldFileNamed: fileName do: [ :file | > file lineEndConvention: lineEndingResult first. > self assert: file upToEnd = lineEndingResult last ] ]! > > ----- Method: MultiByteFileStreamTest>>testMultiByteTextConverter (in > category 'testing') ----- > testMultiByteTextConverter > | strings converterClasses | > strings := { > String newFrom: ((0 to: 255) collect: [:e | Unicode value: e]). > String newFrom: ((0 to: 1023) collect: [:e | Unicode value: e]). > }. > > converterClasses := { > UTF8TextConverter . UTF16TextConverter . > "CompoundTextConverter ." > "EUCJPTextConverter . CNGBTextConverter . ShiftJISTextConverter . > EUCKRTextConverter"}. > converterClasses do: [:converterClass | > strings do: [:string | > | converter stream | > converter := converterClass new. > stream := String new writeStream. > converter nextPutAll: string toStream: stream. > stream := stream contents readStream. > string do: [:e | | decoded | > decoded := converter nextFromStream: stream. > self assert: e charCode = decoded charCode]. > self assert: stream atEnd. > > stream := String new writeStream. > string do: [:e | converter nextPut: e toStream: stream]. > stream := stream contents readStream. > string do: [:e | | decoded | > decoded := converter nextFromStream: stream. > self assert: e charCode = decoded charCode]. > self assert: stream atEnd]]! > > ----- Method: MultiByteFileStreamTest>>testNextLine (in category 'testing') > ----- > testNextLine > > fileName := 'foonextline.txt'. > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > file > wantsLineEndConversion: false; > nextPutAll: 'line 1'; cr; > nextPutAll: 'line 2'; crlf; > nextPutAll: 'line 3'; lf; > nextPutAll: 'line 4' ]. > #(cr lf crlf nil) do: [:lineEnding | > MultiByteFileStream oldFileNamed: fileName do: [ :file | > file lineEndConvention: lineEnding. > self > assert: file nextLine = 'line 1'; > assert: file nextLine = 'line 2'; > assert: file nextLine = 'line 3'; > assert: file nextLine = 'line 4'; > assert: file nextLine = nil ] ]! > > ----- Method: MultiByteFileStreamTest>>testNextPutAllStartingAt (in category > 'testing') ----- > testNextPutAllStartingAt > > | result | > fileName := 'foonextputallstartingat.txt'. > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > { 'abcde' asWideString. 'abcde' } do: [ :string | > file > next: 1 putAll: string startingAt: 5; > next: 3 putAll: string startingAt: 2; > next: 1 putAll: string startingAt: 1 ] ]. > result := StandardFileStream readOnlyFileNamed: fileName do: [ :file | > file binary; contents ]. > self assert: #[101 98 99 100 97 101 98 99 100 97] equals: result > ! > > ----- Method: MultiByteFileStreamTest>>testNonAsciiBackChunk (in category > 'testing') ----- > testNonAsciiBackChunk > "Note: this is an expected failure: MultiByteFileStream is not equipped to > read back non ASCII String... (no comment) > As a consequence, never use non ASCII in method category nor in your > initials. That would make a few tools blind..." > > fileName := 'foobackchunk.txt'. > MultiByteFileStream forceNewFileNamed: fileName do: [ :file | > file > lineEndConvention: #cr; > converter: UTF8TextConverter new; > cr; nextChunkPut: 'testé' printString; > cr; nextChunkPut: 'test' printString. > self assert: file backChunk = (String cr , 'test' printString). > self assert: file backChunk = (String cr , 'testé' printString) ]! > > TestCase subclass: #UTF16TextConverterTest > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'MultilingualTests-TextConversion'! > > ----- Method: UTF16TextConverterTest>>testByteOrders (in category 'testing') > ----- > testByteOrders > |converter originalText bytes decodedText | > originalText := 'test'. > converter := UTF16TextConverter new. > > "Default (ie useLittleEndian instvar nil)" > bytes := (originalText convertToWithConverter: converter). > decodedText := bytes convertFromWithConverter: converter. > > self assert: originalText equals: decodedText. > > "Little-endian" > converter useLittleEndian: true. > > bytes := (originalText convertToWithConverter: converter). > decodedText := bytes convertFromWithConverter: converter. > > self assert: originalText equals: decodedText. > > "Big-endian" > converter useLittleEndian: false. > > bytes := (originalText convertToWithConverter: converter). > decodedText := bytes convertFromWithConverter: converter. > > self assert: originalText equals: decodedText. > > ! > > ClassTestCase subclass: #UTF8TextConverterTest > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'MultilingualTests-TextConversion'! > > ----- Method: UTF8TextConverterTest>>testLazyConversion (in category > 'tests') ----- > testLazyConversion > "Ensure the lazy conversions do what they should" > > | strict result | > strict := UTF8TextConverter strictUtf8Conversions. > [UTF8TextConverter strictUtf8Conversions: false. > result := 'Grüß Gott' utf8ToSqueak. > ] ensure:[UTF8TextConverter strictUtf8Conversions: strict]. > > self assert: result = 'Grüß Gott'. > ! > > ----- Method: UTF8TextConverterTest>>testSqueakToUtf8 (in category 'tests') > ----- > testSqueakToUtf8 > "Ensure proper encoding" > > self assert: '' squeakToUtf8 equals: ''. > self assert: 'Hello World' squeakToUtf8 equals: 'Hello World'. > self assert: 'Grüß Gott' squeakToUtf8 asByteArray > equals: #[71 114 195 188 195 159 32 71 111 116 116]! > > ----- Method: UTF8TextConverterTest>>testStrictConversion (in category > 'tests') ----- > testStrictConversion > "Ensure the strict conversions do what they should" > > | strict | > strict := UTF8TextConverter strictUtf8Conversions. > [UTF8TextConverter strictUtf8Conversions: true. > self should:[ 'Grüß Gott' utf8ToSqueak ] raise: Error. > ] ensure:[UTF8TextConverter strictUtf8Conversions: strict].! > > ----- Method: UTF8TextConverterTest>>testUtf8ToSqueak (in category 'tests') > ----- > testUtf8ToSqueak > "Ensure proper encoding" > > self assert: '' utf8ToSqueak equals: ''. > self assert: 'Hello World' utf8ToSqueak equals: 'Hello World'. > self assert: #[71 114 195 188 195 159 32 71 111 116 116] asString > utf8ToSqueak > equals: 'Grüß Gott' > > ! > > >

2 3

testing...
by tim Rowledge 19 Jan '17

19 Jan '17

Is this thing on? There seems to be some sort of blockage somewhere.. tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Any program that runs right is obsolete.

4 3

Unable to save project in Squeak 5.1
by Benjamin L. Russell 19 Jan '17

19 Jan '17

Upon installing Squeak 5.1 (both 32-bit and 64-bit) on Windows 7.1, customizing the user interface, and attempting to save the project, I received a popup window entitled with the following error message: > Error: subscript is out of bounds: 53 Closing the window with this title resulted in a list of the following error messages on the left side of the main Squeak window: ----- error messages follow immediately after this line ----- ***System error handling failed*** MessageNotUnderstood: UndefinedObject>>form Project class>>tryEmergencyEvaluatorForRecovery: Project class>>handlePrimitiveError: MorphicProject(Object)>>primitiveError: MorphicProject(Project)>>handleFatalDrawingError: [] in WorldState>>displayWorldSafely: BlockClosure>>cull: [] in MethodContext(ContextPart)>>handleSignal: MessageNotUnderstood(Exception)>>signal UndefinedObject(Object)>>doesNotUnderstand: #form [] in WorldState>>drawWorld:submorphs:invalidAreasOn: Array(SequenceableCollection)>>do: WorldState>>drawWorld:submorphs:invalidAreasOn: WorldState>>drawWorld:submorphs: PasteUpMorph>>displayWorld [] in WorldState>>displayWorldSafely: BlockClosure>>on:do: WorldState>>displayWorldSafely: WorldState>>doOneCycleNowFor: ----------------- Type CR to enter an emergency evaluator. Type any other character to restart. ----- error messages end immediately before this line ----- Attempting to close Squeak by clicking on the close button of the Squeak main window did nothing; I was forced to use Task Manager to quit the process. A similar error message also occurred when I attempted to save the project in Squeak 4.6; however, I was able to save the project normally in Squeak 3.9. How can I tweak Squeak 5.1 to save the project normally? -- Benjamin L. Russell

1 0

The Trunk: System-tfel.923.mcz
by commits＠source.squeak.org 18 Jan '17

18 Jan '17

Tim Felgentreff uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-tfel.923.mcz ==================== Summary ==================== Name: System-tfel.923 Author: tfel Time: 18 January 2017, 10:05:39.926932 am UUID: d9dcb1e9-52fe-435e-9d88-96f921f9fd20 Ancestors: System-ul.922 add methods to quickly increase/decrease fonts =============== Diff against System-ul.922 =============== Item was added: + ----- Method: Preferences class>>changeFontSize: (in category 'prefs - fonts') ----- + changeFontSize: delta + | theme base fonts | + delta = 0 ifTrue: [self restoreDefaultFonts]. + (UserInterfaceTheme current name beginsWith: 'Demo') + ifFalse: [ + "Create DEMO version of current theme." + theme := UserInterfaceTheme named: 'Demo'. + theme merge: UserInterfaceTheme current overwrite: true. + theme apply]. + + base := (TextStyle defaultFont name beginsWith: 'Darkmap') + ifTrue: ['Darkmap DejaVu Sans'] ifFalse: ['Bitmap DejaVu Sans']. + + fonts := { + {#SystemFont. base}. + {#FixedFont. 'BitstreamVeraSansMono'}. + {#ListFont. base}. + {#FlapFont. base}. + {#EToysFont. base}. + {#PaintBoxButtonFont. base}. + {#MenuFont. base}. + {#WindowTitleFont. base, ' B'}. + {#BalloonHelpFont. base}. + {#CodeFont. base}. + {#ButtonFont. base}. + } collect: [:ary || newPtSize | + newPtSize := (self perform: ('standard', ary first) asSymbol) pointSize + delta. + {('set', ary first, 'To:') asSymbol. ary second. newPtSize} + ]. + self setDefaultFonts: fonts. + ! Item was added: + ----- Method: Preferences class>>decreaseFontSize (in category 'prefs - fonts') ----- + decreaseFontSize + + self changeFontSize: -3. + ! Item was added: + ----- Method: Preferences class>>increaseFontSize (in category 'prefs - fonts') ----- + increaseFontSize + + self changeFontSize: 3. + ! Item was added: + ----- Method: Preferences class>>setFlapFontTo: (in category 'prefs - fonts') ----- + setFlapFontTo: aFont + + UserInterfaceTheme current + set: #standardFlapFont + to: aFont; + apply. + + "FlapTab allSubInstancesDo: + [:aFlapTab | aFlapTab reformatTextualTab]"! Item was added: + ----- Method: Preferences class>>standardWindowTitleFont (in category 'prefs - fonts') ----- + standardWindowTitleFont + "Answer the standard font to use for window titles" + + ^ (UserInterfaceTheme current get: #windowTitleFont) + ifNil: [TextStyle defaultFont]!

2 2

What is the squeak equivalent of VA Smalltalk's ObjectLoader and ObjectDumper?
by Louis LaBrunda 18 Jan '17

18 Jan '17

Hi, What is the squeak equivalent of VA Smalltalk's ObjectLoader and ObjectDumper? Lou -- Louis LaBrunda Keystone Software Corp. SkypeMe callto://PhotonDemon

5 10