- Pharo-users - lists.pharo.org

Re: [Pharo-users] Fwd: Debris' Quuve - Technologies used
by Brad April 15, 2015

April 15, 2015

I'd love to know more about your architecture. It seems like you've built an architecture very similar to what I've dreamed of building. Is there any possibility of asking questions or of you providing examples of some of the features from time to time? Brad Selfridge 913-269-2385 > On Apr 15, 2015, at 4:30 PM, Cameron Sanders via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > <mime-attachment>

1 0

Re: [Pharo-users] Fwd: Debris' Quuve - Technologies used
by Luc Fabresse April 15, 2015

April 15, 2015

Hi, Thanks for this email. It is really nice to read that all these frameworks are used in yet another successful commercial app such as Quuve. Best, #Luc 2015-04-15 23:30 GMT+02:00 Cameron Sanders via Pharo-users < pharo-users(a)lists.pharo.org>: > > > ---------- Message transfÃ©rÃ© ---------- > From: Cameron Sanders <camsanders(a)aol.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: > Date: Wed, 15 Apr 2015 17:30:24 -0400 > Subject: Fwd: Debris' Quuve - Technologies used > Several people inquired as to how Quuve was built. Mariano wrote up a nice > description of the various tools that were used to build Quuve -- see > below. Note also that DebrisPublishing.com website is now up; we are still > working on videos, but the site is very lean at present. > > -Cam > > Quuve Technologies Used > > Quuve has been and still is developed with Pharo. We try to use the most > up to date stable version of Pharo. Quuve is deployed in GemStone. > > Package dependencies are managed via Metacello. Not only do we have many > dependencies but also multiple Smalltalk environments: Pharo and GemStone. > We also use Metacello to correctly load the needed packages and versions > for each of the platforms. > > We use Seaside as our web framework and Twitter Bootstrap for Seaside for > the layout and design of the app. While some parts are still using the > full-request approach, most of the app is done with AJAX and only > refreshing the needed part of the screen. > > We use JQuery a lot and some external JS libraries such a DataTables (for > our table/reports), floatThead, HighCharts (for making charts), TinyMCE (to > edit notes and a few other things), etc. > > We have a full-featured CRUD system based on Magritte. Actually, we have > extended Magritte so much that all our descriptions and components are > actually subclasses of the original Magritte classes. We have our own > descriptions, components, report column classes, mementos, table layouts, > etc. All our framework is Twitter Bootstrap integrated, fully AJAX and with > lots of rich features. We can make a full CRUD report/form out of Magritte > descriptions in no time. > > For persistency we have a library/layer which gives a unified way of > saving and querying objects using a Glorp-like interface; it differs in > that the where clauses are straight Smalltalk blocks. So far, when we work > on Pharo we use Fuel as the "database", while for production we use > GemStone. We have developed some compatibility packages so that same code > would work in both Smalltalks in the way we expect. Quuve briefly used > Oracleâs relational DB for persistence of its securities DB, connecting to > it via the Glorp toolkit; because many mature financial DBâs are delivered > in relational form, we may need to do so more extensively in the future. > Although the need for this may subside as more data becomes available over > REST-server interfaces. > > We use NeoCSV for parsing CSV, XMLParser, Zinc-REST and STON for providing > REST web services, and SIXX for moving data between Pharo and GemStone. > > As to the web server, in Pharo we use Zinc, and in GemStone we use nginx + > FastCGI. Quuve clients could be for example, an individual or a large > advisory firm. In each case, Quuve is deployed as a "site/instance" for > each customer. Each site is a fully isolated and secured instance of Quuve. > > Quuve is hosted in a cloud virtual hosting which allows us to scale as > much as we need and we can have as many nodes as required. The operating > system is CentOS Linux. We correctly perform backups, cleanings and > maintenance of our sites. We have scripts to automatically create new sites > very easily. > > >

1 0

Fwd: Debris' Quuve - Technologies used
by Cameron Sanders April 15, 2015

April 15, 2015

Several people inquired as to how Quuve was built. Mariano wrote up a nice description of the various tools that were used to build Quuve -- see below. Note also that DebrisPublishing.com website is now up; we are still working on videos, but the site is very lean at present. -Cam Quuve Technologies Used Quuve has been and still is developed with Pharo. We try to use the most up to date stable version of Pharo. Quuve is deployed in GemStone. Package dependencies are managed via Metacello. Not only do we have many dependencies but also multiple Smalltalk environments: Pharo and GemStone. We also use Metacello to correctly load the needed packages and versions for each of the platforms. We use Seaside as our web framework and Twitter Bootstrap for Seaside for the layout and design of the app. While some parts are still using the full-request approach, most of the app is done with AJAX and only refreshing the needed part of the screen. We use JQuery a lot and some external JS libraries such a DataTables (for our table/reports), floatThead, HighCharts (for making charts), TinyMCE (to edit notes and a few other things), etc. We have a full-featured CRUD system based on Magritte. Actually, we have extended Magritte so much that all our descriptions and components are actually subclasses of the original Magritte classes. We have our own descriptions, components, report column classes, mementos, table layouts, etc. All our framework is Twitter Bootstrap integrated, fully AJAX and with lots of rich features. We can make a full CRUD report/form out of Magritte descriptions in no time. For persistency we have a library/layer which gives a unified way of saving and querying objects using a Glorp-like interface; it differs in that the where clauses are straight Smalltalk blocks. So far, when we work on Pharo we use Fuel as the "database", while for production we use GemStone. We have developed some compatibility packages so that same code would work in both Smalltalks in the way we expect. Quuve briefly used Oracleâs relational DB for persistence of its securities DB, connecting to it via the Glorp toolkit; because many mature financial DBâs are delivered in relational form, we may need to do so more extensively in the future. Although the need for this may subside as more data becomes available over REST-server interfaces. We use NeoCSV for parsing CSV, XMLParser, Zinc-REST and STON for providing REST web services, and SIXX for moving data between Pharo and GemStone. As to the web server, in Pharo we use Zinc, and in GemStone we use nginx + FastCGI. Quuve clients could be for example, an individual or a large advisory firm. In each case, Quuve is deployed as a "site/instance" for each customer. Each site is a fully isolated and secured instance of Quuve. Quuve is hosted in a cloud virtual hosting which allows us to scale as much as we need and we can have as many nodes as required. The operating system is CentOS Linux. We correctly perform backups, cleanings and maintenance of our sites. We have scripts to automatically create new sites very easily.

1 0

Re: [Pharo-users] Zinc, servicing a full website
by Sven Van Caekenberghe April 14, 2015

April 14, 2015

Hi Leo, > On 14 Apr 2015, at 14:28, Leo Paniceres <lpaniceres(a)gmail.com> wrote: > > Hi Sven, > > Thanks very much for your excellent Zinc package. > > Excuse me for contacting to your email, I couldnât find the official support email list. I much prefer answering question on the pharo-users ML, in CC. > My problem is that I could not find a way to solve simultaneously file servicing and services. > > I have a small app that responds to a request via a GET, and I also need to include in the response a lot of static files in a directory. > > How can I integrate two delegates? > > (ZnStaticFileServerDelegate and ZnDefaultServerDelegate) This is from an older answer, it should be applicable: Multiple handlers can be combined in one server. For example, http://zn.stfx.eu serves static content and serves all Zinc demos, with the following config (part of the startup script): | id logFile staticFileServerDelegate | id := 1. logFile := 'transcript.{1}.log' format: { id }. (NonInteractiveTranscript onFileNamed: logFile) install. (ZnServer defaultOn: 8080 + id) logToTranscript; route: 'r', id printString; start. (staticFileServerDelegate := ZnStaticFileServerDelegate new) prefixFromString: 'zn'; directory: '/home/ubuntu/zn' asFileReference. ZnServer default delegate prefixMap at: 'zn' put: [ :request | staticFileServerDelegate handleRequest: request ]; at: 'redirect-to-zn' put: [ :request | ZnResponse redirect: '/zn/index.html' ]; at: '/' put: 'redirect-to-zn'. HTH, Sven > -- > > Afectuosamenteâ desde Argentinaâ, (de corazÃ³n por mas que lo tenga automatico) > Leo

1 0

DoubleLinkedList vs LinkedList vs Collection
by Peter UhnÃ¡k April 14, 2015

April 14, 2015

I was surprised to learn that DoubleLinkedList is descendant of Object, while LinkedList is descendant of SequencableCollection. Is there a particular reason behind this? Are they really so conceptually different that DLL is not even considered a collection? Thanks, Peter

6 10

Gitfiletree unstable on Windows
by Jan B. April 14, 2015

April 14, 2015

Hello This is me again with problems with gitfiletree. In general it works just fine, but in about 50 % cases it crashes VM. It happens to me when loading via Gofer new url: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo40/main'; configurationOf: 'GitFileTree'; loadDevelopment. Metacello new baseline:...; repository:'gitfiletree:///...'; load. or when opening repository in Monticello. Sometimes the crash is handled and dmp file is generated, but sometimes just Pharo.exe stops. Using Windows 7 64-bit, VM tried 420 (latest) from 2015-03-26 and stable from 2014-05-15, images tried multiple between 40546 to 40588 and also 30864. Here are links for dmp files: http://www.mediafire.com/download/txbxi77a4nthyxg/Pharo_dmp.zip crash1 and 2 are from stable VM and 3 and 4 from latest VM, all from image 40588. Using git from http://git-scm.com/ . Would be glad to help any further if you need. Jan -- View this message in context: http://forum.world.st/Gitfiletree-unstable-on-Windows-tp4816354.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

6 10

ZnUrl directory
by Christophe Demarey April 13, 2015

April 13, 2015

Hi, I just tried to evaluate: (ZnUrl fromString: 'file:///tmp/') directory and got 'tmp/' as result. I'm a bit suprised. Shouldn't it be '/tmp/' ? Be fore trying to fix I would like to be sure what is the expected behavior. Thanks, Christophe.

3 3

pillar internal link
by Peter UhnÃ¡k April 13, 2015

April 13, 2015

Hi, how does one add an internal link? I have chapter 'Framework' (and file 'Framework/Framework.pillar') and 'Palette' (and file 'Palette/Palette.pillar') Can I in Framework.pillar write something like *Palette/Palette* to create a link? Currently it fails at *** Warning: PRReferenceNotFound: Can't find anchor named 'Palette/Palette' Thanks, Peter

4 11

[ANN] MorphicDoc : A project to document Morphic
by kilon alios April 12, 2015

April 12, 2015

One of the frequent questions we get asked is how to use Morphic. Unfortunately there is very little documentation for Morphic around and barely touches the most interesting concepts. I decided to start my own project called MorphicDoc . MorphicDoc is very easy to install with Configuration Browser and it works in 2 ways. a) open the Help tool (World Menu => Help => Help Browser ) and there you will find a new section called "Morphic Doc by Kilon" b) open System Browser go to MorphicDoc package and look at the class side of MorphicDocExamples class , each method is an example taken from the tutorial in help tool and you can easily execute by clicking the green arrow next to its name. Right now only 3 pages have been added but slowly and steadily more will be added. To get new pages and even new chapters make sure you reinstall the same very simple way like installing just open Configuration Browser and click "Install Stable Version" after you selected MorphicDoc. I will try to add 1 page per day and at least 1 page per week depending on my free time. So make sure you update at least once per week to get the latest version of MorphicDoc. You can report issues , advice and requests at the project page in https://github.com/kilon/MorphicDoc. Of course pull requests are more than welcomed.

7 13

Dictionary and sorting
by Hilaire April 11, 2015

April 11, 2015

Dear all, >From a dictionary, I want the keys sorted according to the values (string). I came with this method: keysSortedByValue ^ (self associations sort: [ :assoc1 :assoc2 | assoc1 value < assoc2 value ]) collect: [ :assoc | assoc key ] Is there better way to deal with it, in term of efficiency? Thanks Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

1 1