- Pharo-users - lists.pharo.org

[ANN] Pharo Consortium New Gold Member: <Anonymous>

by Marcus Denker

The Pharo Consortium is very happy to announce that <Anonymous> has joined the Consortium as an Gold Member. About - Pharo Consortium: http://consortium.pharo.org <http://consortium.pharo.org/> <http://consortium.pharo.org/> The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org <http://association.pharo.org/>

Aug. 14, 2015

Re: [Pharo-users] Tabular: XLSX import

by H. Hirzel

Problem solved so far http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.63.mcz Now found out how to parse inline strings with the SAX parser I had to include t in registeredElements ^ #(row c v t) and add a method t_characters: aString self cell data: aString. This parses XML code snippets like this <row r="1" spans="1:1"> <c r="A1" t="inlineStr"> <is><t>This is inline string example</t></is> </c> </row> Just hope that t is always a string and not dependent on being surrounded by <is>....</is>. Now two tests more work. But I have to do more to get the data types of the cell correct (number, strings). In the round trip parsing numbers are given back as strings. This seems to be unrelated to the string parsing. I'll have to check. On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > P.S. Code in > http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.59.mcz > > On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> I am now looking for the place in the SAX parser where the cell >> content is assigned. >> >> >> Test script (debug it) >> >> |wbk wsheet wimported cell fname4| >> fname4 := 'TabularConstructed4Exported.xlsx'. >> wbk := TabularWorkbook new. >> self assert: (wbk worksheets isEmpty). >> >> wsheet := TabularWorksheet new. >> wsheet >> at: 1 @ 1 putData: 'abc 11'; >> at: 2 @ 1 putData: 'def 21'; >> at: 3 @ 1 putData: 'ghi 31'. >> wbk worksheets add: wsheet. >> TabularXSLXExport workbook: wbk fileName: fname4. >> >> wimported := XLSXImporter import: (FileLocator home / fname4 ) . >> cell := ((wimported worksheetNamed: 'Sheet1') at: 1@1). >> >> Put a halt into >> TabularWorksheet>>at:putCell: >> >> to come near the place. The cell attributes are there (inline string >> in this case) >> >> But I did not find the exact place where the cell content 'abc 11' is >> assigned. >> >> Any help? >> >> --Hannes >> >> On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> On 8/2/15, Ben Coman <btc(a)openinworld.com> wrote: >>>> Cool. I might have a use for this soon. >>>> cheers -ben >>> >>> Hello Ben >>> >>> The standard to implement is huge. We are dealing with a subset. >>> >>> Example test documents I consider using are here >>> >>> http://www.openoffice.org/sc/testdocs/index.html >>> >>> (all which are labeled 'XML') >>> >>> What we have so far in the tabular package is quite usable, depending >>> on the project. >>> >>> My interest for next steps are >>> >>> a. get round trip : >>> 1. create tabular model >>> 2. export workbook >>> 3. import workbook >>> working fine. >>> (the issue is inline string parsing currently but I will soon be >>> there) >>> >>> b. cell styles >>> >>> c. multiple worksheets on export (currently limited to one with a fix >>> name; import >>> can deal with several worksheets in a workbook) >>> >>> -- Hannes >>> >>> >>> >>> >>>> On Sun, Aug 2, 2015 at 2:58 AM, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> >>>> wrote: >>>>> Hello. >>>>> Some time ago I announced Tabular, some effort to make a tool for >>>>> spreadsheets import/export. >>>>> >>>>> This is short notice: Vincent Blondeau have added XLSX import >>>>> functionality! >>>>> It's also mostly proof-of-concept now, but even at this stage it's >>>>> quite >>>>> usable. >>>>> >>>>> Thanks, Vincent! >>>> >>>> >>> >> >

Aug. 14, 2015

Re: [Pharo-users] Tabular: https://ci.inria.fr/pharo-contribution/job/Tabular/lastCompletedBuild/testReport/

by H. Hirzel

Thank you. Build 4 is now done. Where can I see which http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.nn.mcz file it picked? Hannes On 8/14/15, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > Hi, > > The job is built every one hour if a commit has been made. So you have to > wait a bit. > > Regards, > > Vincent > > -----Message d'origine----- > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de > H. Hirzel > EnvoyÃ© : vendredi 14 aoÃ»t 2015 10:22 > Ã : vincent.blondeau > Cc : Any question about pharo is welcome > Objet : [Pharo-users] Tabular: > https://ci.inria.fr/pharo-contribution/job/Tabular/lastCompletedBuild/testR… > > Hello Vincent > > The integration server does not seem to pick my latest committed versions of > today. > > What needs to be done to fix this? > > Regards > > Hannes > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended solely > for the addressee; it may also be privileged. If you receive this e-mail in > error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be > triggered for the message content. Although the sender endeavours to > maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. >

Aug. 14, 2015

[Tutorial] CI Automated Build for your Pharo Application

by Jigyasa Grover

Hi Folks ! I have been working throughout the summers on *searchQuick*, an application to enable a user to search a set of books or texts, like an encyclopedia, or some other topical book collection offline. ( https://github.com/jig08/sQuick_new ) On my mentors suggestion, I have put up my application for automated build on *CI Inria*. While undergoing the process of configuring my application for automated build, I have jotted down and compiled important steps/information in my post namely '*[Tutorial] CI Automated Build for your Pharo Application*' [*LINK*: https://jigyasagrover.wordpress.com/2015/08/08/ci-automated-build-for-your-…] on my blogspot *jigyasagrover.wordpress.com <http://jigyasagrover.wordpress.com>.* Kindly give it a read. I look forward to all your comments and suggestions. Regards Jigyasa

Aug. 14, 2015

Re: [Pharo-users] Tabular: https://ci.inria.fr/pharo-contribution/job/Tabular/lastCompletedBuild/testReport/

by Blondeau Vincent

Hi, The job is built every one hour if a commit has been made. So you have to wait a bit. Regards, Vincent -----Message d'origine----- De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de H. Hirzel EnvoyÃ© : vendredi 14 aoÃ»t 2015 10:22 Ã : vincent.blondeau Cc : Any question about pharo is welcome Objet : [Pharo-users] Tabular: https://ci.inria.fr/pharo-contribution/job/Tabular/lastCompletedBuild/testR… Hello Vincent The integration server does not seem to pick my latest committed versions of today. What needs to be done to fix this? Regards Hannes Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Aug. 14, 2015

Tabular: https://ci.inria.fr/pharo-contribution/job/Tabular/lastCompletedBuild/testReport/

by H. Hirzel

Hello Vincent The integration server does not seem to pick my latest committed versions of today. What needs to be done to fix this? Regards Hannes

Aug. 14, 2015

Re: [Pharo-users] Tabular: XLSX import

by H. Hirzel

P.S. Code in http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.59.mcz On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > I am now looking for the place in the SAX parser where the cell > content is assigned. > > > Test script (debug it) > > |wbk wsheet wimported cell fname4| > fname4 := 'TabularConstructed4Exported.xlsx'. > wbk := TabularWorkbook new. > self assert: (wbk worksheets isEmpty). > > wsheet := TabularWorksheet new. > wsheet > at: 1 @ 1 putData: 'abc 11'; > at: 2 @ 1 putData: 'def 21'; > at: 3 @ 1 putData: 'ghi 31'. > wbk worksheets add: wsheet. > TabularXSLXExport workbook: wbk fileName: fname4. > > wimported := XLSXImporter import: (FileLocator home / fname4 ) . > cell := ((wimported worksheetNamed: 'Sheet1') at: 1@1). > > Put a halt into > TabularWorksheet>>at:putCell: > > to come near the place. The cell attributes are there (inline string > in this case) > > But I did not find the exact place where the cell content 'abc 11' is > assigned. > > Any help? > > --Hannes > > On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> On 8/2/15, Ben Coman <btc(a)openinworld.com> wrote: >>> Cool. I might have a use for this soon. >>> cheers -ben >> >> Hello Ben >> >> The standard to implement is huge. We are dealing with a subset. >> >> Example test documents I consider using are here >> >> http://www.openoffice.org/sc/testdocs/index.html >> >> (all which are labeled 'XML') >> >> What we have so far in the tabular package is quite usable, depending >> on the project. >> >> My interest for next steps are >> >> a. get round trip : >> 1. create tabular model >> 2. export workbook >> 3. import workbook >> working fine. >> (the issue is inline string parsing currently but I will soon be >> there) >> >> b. cell styles >> >> c. multiple worksheets on export (currently limited to one with a fix >> name; import >> can deal with several worksheets in a workbook) >> >> -- Hannes >> >> >> >> >>> On Sun, Aug 2, 2015 at 2:58 AM, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> >>> wrote: >>>> Hello. >>>> Some time ago I announced Tabular, some effort to make a tool for >>>> spreadsheets import/export. >>>> >>>> This is short notice: Vincent Blondeau have added XLSX import >>>> functionality! >>>> It's also mostly proof-of-concept now, but even at this stage it's >>>> quite >>>> usable. >>>> >>>> Thanks, Vincent! >>> >>> >> >

Aug. 14, 2015

Re: [Pharo-users] Tabular: XLSX import

by H. Hirzel

I am now looking for the place in the SAX parser where the cell content is assigned. Test script (debug it) |wbk wsheet wimported cell fname4| fname4 := 'TabularConstructed4Exported.xlsx'. wbk := TabularWorkbook new. self assert: (wbk worksheets isEmpty). wsheet := TabularWorksheet new. wsheet at: 1 @ 1 putData: 'abc 11'; at: 2 @ 1 putData: 'def 21'; at: 3 @ 1 putData: 'ghi 31'. wbk worksheets add: wsheet. TabularXSLXExport workbook: wbk fileName: fname4. wimported := XLSXImporter import: (FileLocator home / fname4 ) . cell := ((wimported worksheetNamed: 'Sheet1') at: 1@1). Put a halt into TabularWorksheet>>at:putCell: to come near the place. The cell attributes are there (inline string in this case) But I did not find the exact place where the cell content 'abc 11' is assigned. Any help? --Hannes On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > On 8/2/15, Ben Coman <btc(a)openinworld.com> wrote: >> Cool. I might have a use for this soon. >> cheers -ben > > Hello Ben > > The standard to implement is huge. We are dealing with a subset. > > Example test documents I consider using are here > > http://www.openoffice.org/sc/testdocs/index.html > > (all which are labeled 'XML') > > What we have so far in the tabular package is quite usable, depending > on the project. > > My interest for next steps are > > a. get round trip : > 1. create tabular model > 2. export workbook > 3. import workbook > working fine. > (the issue is inline string parsing currently but I will soon be there) > > b. cell styles > > c. multiple worksheets on export (currently limited to one with a fix > name; import > can deal with several worksheets in a workbook) > > -- Hannes > > > > >> On Sun, Aug 2, 2015 at 2:58 AM, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> >> wrote: >>> Hello. >>> Some time ago I announced Tabular, some effort to make a tool for >>> spreadsheets import/export. >>> >>> This is short notice: Vincent Blondeau have added XLSX import >>> functionality! >>> It's also mostly proof-of-concept now, but even at this stage it's quite >>> usable. >>> >>> Thanks, Vincent! >> >> >

Aug. 14, 2015

Re: [Pharo-users] Tabular: XLSX import

by H. Hirzel

On 8/2/15, Ben Coman <btc(a)openinworld.com> wrote: > Cool. I might have a use for this soon. > cheers -ben Hello Ben The standard to implement is huge. We are dealing with a subset. Example test documents I consider using are here http://www.openoffice.org/sc/testdocs/index.html (all which are labeled 'XML') What we have so far in the tabular package is quite usable, depending on the project. My interest for next steps are a. get round trip : 1. create tabular model 2. export workbook 3. import workbook working fine. (the issue is inline string parsing currently but I will soon be there) b. cell styles c. multiple worksheets on export (currently limited to one with a fix name; import can deal with several worksheets in a workbook) -- Hannes > On Sun, Aug 2, 2015 at 2:58 AM, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> > wrote: >> Hello. >> Some time ago I announced Tabular, some effort to make a tool for >> spreadsheets import/export. >> >> This is short notice: Vincent Blondeau have added XLSX import >> functionality! >> It's also mostly proof-of-concept now, but even at this stage it's quite >> usable. >> >> Thanks, Vincent! > >

Aug. 14, 2015

Re: [Pharo-users] Tabular: XLSX import

by H. Hirzel

On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Vicent > > It seems that there are two importing methods implemented in the subpackage > > Tabular-Importers > > TabularCell>>extractFromXml: aXMLElement > > and above it > > TabularWorksheet>>extractContentsFromXml: aXMLDocument > > is actually never called. > > So actually I was fixing the wrong method for dealing with inline strings. > > XLSXImporter>>import: > > takes another road > > import: aStream > archive := ZipArchive new readFrom: aStream. > workbook := TabularWorkbook new. > "self extractStyles." > self extractSharedStrings. > self extractWorksheets. > > self resolveSharedStrings. > ^ workbook > > Through XLSXSheetParser, which seems to be independant. > > > > Is this correct? > > --Hannes CONFIRMED: there are two import methods. The currently in use is extractWorksheetsList | list | list:=XLSXWorkbookParser parse: (archive memberNamed: 'xl/workbook.xml') contentStream. sheetsToExtract ifNotNil:[list := list associationsSelect: [:assoc| sheetsToExtract includes: assoc value] ]. ^list. And the XLSXWorkbookParser uses the XLSXSheetParser with the main method where the cell parsing activity happens XLSXSheetParser>>c_start: properties |cell coord| cell := TabularCell new. properties at: #s ifPresent:[:styleId| cell style: styleId]. "Should be substituted by actual style upon finalisation" properties at: #t ifPresent:[:type| cell attributeAt: 'xlsx:t' put: type]. properties at: #r ifPresent: [:r| coord := r asPoint]. coord ifNil: [ coord := colCounter @ rowCounter ] ifNotNil: [ colCounter := coord x ]. "It's expected that row of r attribute is always points to current row. If it is not - have no idea how to manage this" self worksheet cells at: coord put: cell. parsingStack push: cell. So the fix for inline string parsing has to be around here somewhere. Adding inline string parsing to the importer is important because then we can do round trips. Create Tabular Model / Export / Import. Of course the alternative is to add the sharedString.xml generation to the export function which I might do later. But I'd like to avoid that for the moment as space efficiency for storing strings is not so much an issue if the file is put into a zip file. What counts more is the readability of the generated code for visual checks. We are dealing with a specification which has several thousand pages! --Hannes > > On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Found the information on page 1600 of >> http://standards.iso.org/ittf/PubliclyAvailableStandards/c061750_ISO_IEC_29… >> >> 18.3.1.4 >> c (Cell) >> >> >> >> On 8/14/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> On 8/13/15, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: >>>> Hi, >>>> >>>> Look at TabularCell>>extractFromXml: to have some hint about the >>>> standard >>>> values of the parameters. >>> >>> I factores out self extractDataFromXml: aXMLElement. >>> >>> extractFromXml: aXMLElement >>> >>> self style: (aXMLElement attributeAt: 's') asString. >>> self type: ((aXMLElement attributeAt: 't') asString ifEmpty: [ nil ]). >>> self extractDataFromXml: aXMLElement. >>> self formula: ((aXMLElement elementAt: 'f') ifNotNil: [ :e | e >>> firstNode asString ]) >>> >>> >>> >>> >>> extractDataFromXml: aXMLElement >>> self >>> data: >>> (self type = 's' >>> ifTrue: [ (self stringAt: ((aXMLElement elementAt: 'v') ifNotNil: >>> [ :e | e firstNode ifNotNil: [ :s | s asString ] ])) asString ] >>> ifFalse: [ (aXMLElement elementAt: 'v') ifNotNil: [ :e | e >>> firstNode ifNotNil: [ :s | s asString ] ] ]) >>> >>> >>> type may be 's' (for shared string) or 'inline' for inline string. >>> But what is 'v'? >>> >>> In the case of a inline string I have for example >>> >>> <row r="1"> >>> <c r="A1" t="inlineStr"> >>> <is><t>abcdefghijklmnopqrstuvwxyz 1234567890</t></is> >>> </c> >>> >>> I'd like to compile a short summary of the meaning of these one-letter >>> tags. >>> >>> >>> >>>> Don't hesitate to put some comments in the code with the discoveries >>>> you >>>> made. >>> >>> Sure >>> >>> >>>> Vincent >>>> >>>> > -----Message d'origine----- >>>> > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] >>>> De >>>> la part >>>> > de H. Hirzel >>>> > EnvoyÃ© : jeudi 13 aoÃ»t 2015 12:39 >>>> > Ã : Any question about pharo is welcome >>>> > Objet : Re: [Pharo-users] Tabular: XLSX import >>>> > >>>> > Answering my own question: >>>> > >>>> > Another value for t is >>>> > >>>> > t="inlineStr" >>>> > >>>> > <row r="1"> >>>> > <c r="A1" t="inlineStr"> >>>> > <is><t>abcdefghijklmnopqrstuvwxyz 1234567890</t></is> </c> >>>> </row> >>>> > >>>> > So for the export I will ignore the construction of a file >>>> > >>>> > sharedStrings.xml >>>> > >>>> > at the moment. >>>> > >>>> > On 8/13/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> > > The attribute t="s" of a cell c seems to indicate that the >>>> content has >>>> > > to be interpreted as a shared string. >>>> > > >>>> > > XLSXImporter>>resolveSharedStrings >>>> > > "Replace shared strings pointers to real strings" >>>> > > workbook worksheets do:[:worksheet| >>>> > > worksheet cells do:[:cell| >>>> > > ((cell attributeAt: #xlsx:t) = 's') >>>> > > ifTrue:[cell data: >>>> (sharedStrings >>>> at: (cell data >>>> > asNumber + 1))] >>>> > > "XLSX uses 0-based arrays" >>>> > > ] >>>> > > ] >>>> > > >>>> > > On 8/13/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> > >> For the shared strings in sheet1.xml for example >>>> > >> >>>> > >> <c r="A1" s="1" t="s"> >>>> > >> >>>> > >> what do the attributes s and t stand for? >>>> > >> >>>> > >> >>>> > >> <row r="1" customFormat="false" ht="35.05" hidden="false" >>>> > >> customHeight="false" outlineLevel="0" collapsed="false"> >>>> <c >>>> r="A1" >>>> > >> s="1" t="s"> <v>0</v> </c> </row> >>>> > >> >>>> > >> <row r="5" customFormat="false" ht="79.85" hidden="false" >>>> > >> customHeight="false" outlineLevel="0" collapsed="false"> >>>> <c >>>> r="B5" >>>> > >> s="1" t="s"> <v>1</v> </c> </row> >>>> > >> >>>> > >> >>>> > >> On 8/13/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> > >>> http://ss3.gemtalksystems.com/ss/Tabular/Tabular- >>>> > HannesHirzel.52.mcz >>>> > >>> 47 test run, 37 passes. >>>> > >>> >>>> > >>> >>>> > >>> Currently I have a fixed string >>>> > >>> >>>> > >>> TabularXSLXExport>>sharedStrings_xml >>>> > >>> ^'<?xml version="1.0" encoding="UTF-8" standalone="yes"?> >>>> <sst >>>> > >>> >>>> > >>>> xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main" >>>> > >>> count="1" uniqueCount="1"> >>>> > >>> <si><t> </t></si> >>>> > >>> </sst>'. >>>> > >>> >>>> > >>> How far can I safely ignore constructing a proper >>>> > >>> xl/sharedStrings.xml in the archive? >>>> > >>> >>>> > >>> >>>> > >>> >>>> > >>> On 8/13/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> > >>>> Found a useful summary about for generating XLSX files >>>> > >>>> >>>> > >>>> >>>> http://stackoverflow.com/questions/6055430/how-to-create-xlsx- >>>> > file- >>>> > >>>> without-using-any-excel-library-php/18820405#18820405 >>>> > >>>> >>>> > >>>> On 8/13/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> > >>>>> http://ss3.gemtalksystems.com/ss/Tabular/Tabular- >>>> > HannesHirzel.50.m >>>> > >>>>> cz >>>> > >>>>> >>>> > >>>>> Another question is about the >>>> > >>>>> >>>> > >>>>> #colspan: property of a cell >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> (wsheet cells at: 1 @ 1) colspan: 1. >>>> > >>>>> >>>> > >>>>> actually makes cell A1 span 2 columns. >>>> > >>>>> >>>> > >>>>> Is this OK according to the standard? >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> TabularXLSXExportTest>>testExport7 >>>> > >>>>> >>>> > >>>>> | wbk wsheet | >>>> > >>>>> wbk := TabularWorkbook new. >>>> > >>>>> self assert: (wbk worksheets isEmpty). >>>> > >>>>> >>>> > >>>>> wsheet := TabularWorksheet new. >>>> > >>>>> wsheet >>>> > >>>>> at: 1 @ 1 putData: 'aaa'; >>>> > >>>>> at: 3 @ 1 putData: 'ccc'. >>>> > >>>>> (wsheet cells at: 1 @ 1) colspan: 1. >>>> > >>>>> >>>> > >>>>> wbk worksheets add: wsheet. >>>> > >>>>> TabularXSLXExport workbook: wbk fileName: >>>> fname7. >>>> > >>>>> >>>> > >>>>> "manual inspection shows that the exported file >>>> is >>>> fine" >>>> > >>>>> "But is the colspan command fine? Add a colspan >>>> test >>>> to TabularCell" >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> On 8/13/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> > >>>>>> Hello Jurij and Vincent >>>> > >>>>>> >>>> > >>>>>> I am working on extending the export function (export >>>> of >>>> several >>>> > >>>>>> worksheets). >>>> > >>>>>> >>>> > >>>>>> For this I am adding some more tests currently and I'd >>>> like >>>> to >>>> > >>>>>> have your feedback on some of the basic functions >>>> regarding >>>> > >>>>>> initial values. >>>> > >>>>>> >>>> > >>>>>> http://ss3.gemtalksystems.com/ss/Tabular/Tabular- >>>> > HannesHirzel.49. >>>> > >>>>>> mcz >>>> > >>>>>> (41 tests run, 32 passes) >>>> > >>>>>> >>>> > >>>>>> in particular on class TabularWorksheetTest (3 tests) >>>> > >>>>>> >>>> > >>>>>> We have for example >>>> > >>>>>> >>>> > >>>>>> >>>> > >>>>>> Test which passes >>>> > >>>>>> >>>> > >>>>>> testCellsReadingEmptyCell0 >>>> > >>>>>> "accessing a cell without data" >>>> > >>>>>> >>>> > >>>>>> ws col: 1 row: 1 putData: 11. >>>> > >>>>>> ws col: 2 row: 1 putData: 21. >>>> > >>>>>> >>>> > >>>>>> self assert: (ws col: 1 row: 1) data equals: >>>> 11. >>>> > >>>>>> self assert: (ws col: 2 row: 1) data equals: >>>> 21. >>>> > >>>>>> >>>> > >>>>>> self assert: ((ws col: 3 row: 1) isNil). "Is >>>> this >>>> OK to have >>>> > >>>>>> nil returned?" >>>> > >>>>>> >>>> > >>>>>> >>>> > >>>>>> >>>> > >>>>>> Test which does not pass >>>> > >>>>>> >>>> > >>>>>> testCellsReadingEmptyCell >>>> > >>>>>> >>>> > >>>>>> self assert: ((ws col: 100 row: 100) data =''). >>>> > >>>>>> >>>> > >>>>>> "probably should return an empty string" >>>> > >>>>>> >>>> > >>>>>> >>>> > >>>>>> Comments of others are invited as well. >>>> > >>>>>> >>>> > >>>>>> -- Hannes >>>> > >>>>>> >>>> > >>>>>> On 8/9/15, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> >>>> wrote: >>>> > >>>>>>> If your are using at least Pharo 4.0, you can use the >>>> catalog >>>> > >>>>>>> browser to load the ConfigurationOfTabular directly. >>>> > >>>>>>> >>>> > >>>>>>> You have only publish it for MetaRepoForPharo50, so >>>> it >>>> didn't >>>> > >>>>>>> work for Pharo 4. >>>> > >>>>>>> BUt, thanks to your explanations, I just have >>>> published >>>> in >>>> > >>>>>>> MetaRepoForPharo40 as well - works like charm! >>>> > >>>>>>> >>>> > >>>>>>> 2015-08-08 12:45 GMT+03:00 Vincent BLONDEAU < >>>> > >>>>>>> vincent.blondeau(a)polytech-lille.net>: >>>> > >>>>>>> >>>> > >>>>>>>> Hi, >>>> > >>>>>>>> >>>> > >>>>>>>> I added the dependencies to PharoExtras/XMLWriter >>>> and >>>> > XMLParser. >>>> > >>>>>>>> I didn't add the dependencies before because I used >>>> Tabular >>>> > >>>>>>>> with Moose, and Moose already loads these >>>> dependencies... >>>> > >>>>>>>> >>>> > >>>>>>>> Now it should work. I created the new 0.2 release >>>> with >>>> the >>>> > >>>>>>>> required dependencies. >>>> > >>>>>>>> >>>> > >>>>>>>> By the way, I used Versionner to create the >>>> configuration. I >>>> > >>>>>>>> don't know if there is a documentation but there is >>>> a >>>> video: >>>> > >>>>>>>> https://www.youtube.com/watch?v=cFRJDuWL-Q0 >>>> > >>>>>>>> >>>> > >>>>>>>> It is a very fast tool to manage your projects! >>>> > >>>>>>>> >>>> > >>>>>>>> If your are using at least Pharo 4.0, you can use >>>> the >>>> catalog >>>> > >>>>>>>> browser to load the ConfigurationOfTabular directly. >>>> > >>>>>>>> >>>> > >>>>>>>> Best, >>>> > >>>>>>>> Vincent >>>> > >>>>>>>> >>>> > >>>>>>>> -----Message d'origine----- >>>> > >>>>>>>> De : Pharo-users >>>> [mailto:pharo-users-bounces@lists.pharo.org] >>>> > >>>>>>>> De la part de H. Hirzel EnvoyÃ© : samedi 8 aoÃ»t 2015 >>>> 10:34 >>>> Ã : >>>> > >>>>>>>> Any question about pharo is welcome Objet : Re: >>>> [Pharo-users] >>>> > >>>>>>>> Tabular: XLSX import >>>> > >>>>>>>> >>>> > >>>>>>>> If I do >>>> > >>>>>>>> >>>> > >>>>>>>> ConfigurationOfXMLWriter load >>>> > >>>>>>>> >>>> > >>>>>>>> then >>>> > >>>>>>>> >>>> > >>>>>>>> TabularExperimentalExport writeTestFile >>>> > >>>>>>>> >>>> > >>>>>>>> is fine generating an Excel file. >>>> > >>>>>>>> >>>> > >>>>>>>> >>>> > >>>>>>>> http://ss3.gemtalksystems.com/ss/Tabular/Tabular- >>>> > HannesHirzel.2 >>>> > >>>>>>>> 7.mcz >>>> > >>>>>>>> >>>> > >>>>>>>> I am currently exploring the code and trying to >>>> figure >>>> out how >>>> > >>>>>>>> it works. >>>> > >>>>>>>> >>>> > >>>>>>>> --Hannes >>>> > >>>>>>>> >>>> > >>>>>>>> On 8/8/15, H. Hirzel <hannes.hirzel(a)gmail.com> >>>> wrote: >>>> > >>>>>>>> > I understand that Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ asks how to >>>> construct >>>> his >>>> > >>>>>>>> > ConfigurationOfTabular file >>>> > >>>>>>>> > >>>> > >>>>>>>> > http://ss3.gemtalksystems.com/ss/Tabular.html >>>> > >>>>>>>> > >>>> > >>>>>>>> > So I pointed him to the Pharo By Examples book 2 >>>> Chapter 9 >>>> > >>>>>>>> > Managing Projects with Metacello >>>> > >>>>>>>> > >>>> > >>>>>>>> > >>>> > >>>>>>>> > The Tabular project needs a XMLWriter class. I >>>> assume >>>> the >>>> > >>>>>>>> > regular pharoExtras is fine. I do not know. >>>> > >>>>>>>> > >>>> > >>>>>>>> > I am just looking at the code to see how the >>>> reading >>>> and >>>> > >>>>>>>> > writing of MSOffice files, Excel in this >>>> particular >>>> case, is >>>> > >>>>>>>> > done so far. >>>> > >>>>>>>> > >>>> > >>>>>>>> > For reading a TabularSAXParser is included in the >>>> package. >>>> > >>>>>>>> > Probably >>>> > >>>>>>>> > not necessary. >>>> > >>>>>>>> > >>>> > >>>>>>>> > I moved it out here >>>> > >>>>>>>> > http://ss3.gemtalksystems.com/ss/Tabular/Tabular- >>>> > HannesHirzel >>>> > >>>>>>>> > .26.mcz >>>> > >>>>>>>> > >>>> > >>>>>>>> > Hannes >>>> > >>>>>>>> > >>>> > >>>>>>>> > >>>> > >>>>>>>> > >>>> > >>>>>>>> > On 8/8/15, stepharo <stepharo(a)free.fr> wrote: >>>> > >>>>>>>> >> >>>> > >>>>>>>> >> >>>> > >>>>>>>> >> Le 8/8/15 09:11, H. Hirzel a Ã©crit : >>>> > >>>>>>>> >>> What about >>>> > >>>>>>>> >>> >>>> http://rmod.lille.inria.fr/deepIntoPharo/index.html >>>> > >>>>>>>> >>> >>>> > >>>>>>>> >>> p. 163 depending on a project without Metacello >>>> description >>>> > p. >>>> > >>>>>>>> >>> 164, >>>> > >>>>>>>> >>> depending on a project with a Metacello >>>> configuration >>>> > >>>>>>>> >>> >>>> > >>>>>>>> >>> In the mean time just a note that Tabular needs >>>> XMLParser >>>> > >>>>>>>> >>> and XMLWriter packages on >>>> > >>>>>>>> >>> http://ss3.gemtalksystems.com/ss/Tabular.html. >>>> > >>>>>>>> >> >>>> > >>>>>>>> >> are you implying that there is no expression of >>>> dependencies >>>> > >>>>>>>> >> and that in addition it depend on a different XML >>>> > >>>>>>>> >> Parser/Writer than pharoExtras ones? >>>> > >>>>>>>> >> >>>> > >>>>>>>> >> Stef >>>> > >>>>>>>> >>> >>>> > >>>>>>>> >>> Some class comments are welcome as well :-) >>>> > >>>>>>>> >>> >>>> > >>>>>>>> >>> I understand that I can read Excel files and >>>> that >>>> you >>>> just >>>> > >>>>>>>> >>> started to check out how to write them? >>>> > >>>>>>>> >>> >>>> > >>>>>>>> >>> --Hannes >>>> > >>>>>>>> >>> >>>> > >>>>>>>> >>> On 8/4/15, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ >>>> <assargaddon(a)gmail.com> >>>> > wrote: >>>> > >>>>>>>> >>>> Thank you Vincent. >>>> > >>>>>>>> >>>> Some things is much clearer for me now. >>>> > >>>>>>>> >>>> >>>> > >>>>>>>> >>>> *It's shame on me that I lost all this >>>> Metacello >>>> progress, >>>> > >>>>>>>> >>>> especially taking into account I was on the >>>> ESUG >>>> > >>>>>>>> >>>> conference where it was presented. >>>> > >>>>>>>> >>>> It >>>> > >>>>>>>> >>>> was my only conference unfortunately.* >>>> > >>>>>>>> >>>> >>>> > >>>>>>>> >>>> I see that you already started this job: you >>>> added >>>> > >>>>>>>> >>>> ConfigurationOfTabular. >>>> > >>>>>>>> >>>> What I really want to do with this >>>> configuration: >>>> add >>>> > >>>>>>>> >>>> dependencies to XMLParser and XMLWriter >>>> packages. >>>> Can >>>> > you >>>> > >>>>>>>> >>>> help with this, please? >>>> > >>>>>>>> >>>> >>>> > >>>>>>>> >>>> 2015-08-04 17:19 GMT+03:00 Blondeau Vincent >>>> > >>>>>>>> >>>> <vincent.blondeau(a)worldline.com> >>>> > >>>>>>>> >>>> : >>>> > >>>>>>>> >>>> >>>> > >>>>>>>> >>>>> Hi, >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> To add a configuration in the catalog, first >>>> you >>>> should >>>> > >>>>>>>> >>>>> have a configuration for your project. You can >>>> create it >>>> > >>>>>>>> >>>>> with the versionner if needed. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Second, you have to add some methods adding >>>> > >>>>>>>> >>>>> meta-description to your project. The >>>> versionner >>>> do >>>> it >>>> > >>>>>>>> >>>>> for you: in the configuration list, select >>>> your >>>> project, >>>> > >>>>>>>> >>>>> do a right click and select add catalog >>>> methods. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> It creates all the mandatory methods for the >>>> catalog. You >>>> > >>>>>>>> >>>>> now have to fill them (look at the class side >>>> of >>>> the >>>> > >>>>>>>> >>>>> configuration). >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Finally, commit your configuration on your >>>> repo >>>> and >>>> on >>>> > >>>>>>>> >>>>> the >>>> > >>>>>>>> >>>>> MetaRepoForPharo30/40/50 depending where your >>>> > project is >>>> > >>>>>>>> >>>>> working. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> The link is here: >>>> > >>>>>>>> >>>>> >>>> > http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo50 >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Once published, your project will be in the >>>> catalog >>>> in >>>> > >>>>>>>> >>>>> the image (Tools>catalog browser) and on the >>>> web >>>> > >>>>>>>> >>>>> http://catalog.pharo.org/. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Tell me if you need help to do it, >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Cheers, >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Vincent >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> *De :* Pharo-users >>>> > >>>>>>>> >>>>> [mailto:pharo-users-bounces@lists.pharo.org] >>>> > >>>>>>>> >>>>> *De la part de* ???? ????????? >>>> > >>>>>>>> >>>>> *EnvoyÃ© :* dimanche 2 aoÃ»t 2015 10:25 *Ã :* >>>> Any >>>> > question >>>> > >>>>>>>> >>>>> about pharo is welcome *Objet :* Re: >>>> [Pharo-users] >>>> > >>>>>>>> >>>>> Tabular: XLSX import >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> It looks like I need some guidance to >>>> understand >>>> > >>>>>>>> >>>>> contemporary packaging/deployment/versioning >>>> system. >>>> > I >>>> > >>>>>>>> >>>>> know it exists, but I don't know details. Can >>>> you >>>> kick me >>>> > >>>>>>>> >>>>> in the right direction? >>>> > >>>>>>>> >>>>> Maybe >>>> > >>>>>>>> >>>>> some link? >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> 2015-08-02 11:21 GMT+03:00 Esteban Lorenzano >>>> > >>>>>>>> >>>>> <estebanlm(a)gmail.com>: >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Hi, >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> it would be sooo cool to have a configuration >>>> in >>>> the >>>> > >>>>>>>> >>>>> catalogâ¦ >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Esteban >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> On 01 Aug 2015, at 20:58, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ >>>> > >>>>>>>> >>>>> <assargaddon(a)gmail.com> >>>> > >>>>>>>> >>>>> wrote: >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Hello. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Some time ago I announced Tabular >>>> > >>>>>>>> >>>>> >>>> <http://ss3.gemtalksystems.com/ss/Tabular.html>, >>>> some >>>> > >>>>>>>> >>>>> effort to make a tool for spreadsheets >>>> import/export. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> This is short notice: Vincent Blondeau have >>>> added >>>> XLSX >>>> > >>>>>>>> >>>>> import functionality! >>>> > >>>>>>>> >>>>> It's also mostly proof-of-concept now, but >>>> even >>>> at >>>> this >>>> > >>>>>>>> >>>>> stage it's quite usable. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Thanks, Vincent! >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> ------------------------------ >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> Ce message et les piÃ¨ces jointes sont >>>> confidentiels >>>> et >>>> > >>>>>>>> >>>>> rÃ©servÃ©s Ã l'usage exclusif de ses >>>> destinataires. >>>> Il peut >>>> > >>>>>>>> >>>>> Ã©galement Ãªtre protÃ©gÃ© par le secret >>>> professionnel. >>>> Si >>>> > >>>>>>>> >>>>> vous recevez ce message par erreur, merci d'en >>>> avertir >>>> > >>>>>>>> >>>>> immÃ©diatement l'expÃ©diteur et de le dÃ©truire. >>>> L'intÃ©gritÃ© >>>> > >>>>>>>> >>>>> du message ne pouvant Ãªtre assurÃ©e sur >>>> Internet, >>>> la >>>> > >>>>>>>> >>>>> responsabilitÃ© de Worldline ne pourra Ãªtre >>>> recherchÃ©e >>>> > >>>>>>>> >>>>> quant au contenu de ce message. Bien que les >>>> meilleurs >>>> > >>>>>>>> >>>>> efforts soient faits pour maintenir cette >>>> transmission >>>> > >>>>>>>> >>>>> exempte de tout virus, l'expÃ©diteur ne donne >>>> aucune >>>> > >>>>>>>> >>>>> garantie Ã cet Ã©gard et sa responsabilitÃ© ne >>>> saurait Ãªtre >>>> > >>>>>>>> >>>>> recherchÃ©e pour tout dommage rÃ©sultant d'un >>>> virus >>>> > >>>>>>>> >>>>> transmis. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>>>> This e-mail and the documents attached are >>>> confidential >>>> > >>>>>>>> >>>>> and intended solely for the addressee; it may >>>> also >>>> be >>>> > privileged. >>>> > >>>>>>>> >>>>> If >>>> > >>>>>>>> >>>>> you receive this e-mail in error, please >>>> notify >>>> the >>>> > >>>>>>>> >>>>> sender immediately and destroy it. >>>> > >>>>>>>> >>>>> As >>>> > >>>>>>>> >>>>> its integrity cannot be secured on the >>>> Internet, >>>> the >>>> > >>>>>>>> >>>>> Worldline liability cannot be triggered for >>>> the >>>> message >>>> > >>>>>>>> >>>>> content. >>>> > >>>>>>>> >>>>> Although >>>> > >>>>>>>> >>>>> the sender endeavours to maintain a computer >>>> virus-free >>>> > >>>>>>>> >>>>> network, the sender does not warrant that this >>>> > >>>>>>>> >>>>> transmission is virus-free and will not be >>>> liable >>>> for any >>>> > >>>>>>>> >>>>> damages resulting from any virus transmitted. >>>> > >>>>>>>> >>>>> >>>> > >>>>>>>> >>> >>>> > >>>>>>>> >> >>>> > >>>>>>>> >> >>>> > >>>>>>>> >> >>>> > >>>>>>>> > >>>> > >>>>>>>> >>>> > >>>>>>>> >>>> > >>>>>>>> >>>> > >>>>>>>> >>>> > >>>>>>> >>>> > >>>>>> >>>> > >>>>> >>>> > >>>> >>>> > >>> >>>> > >> >>>> > > >>>> >>>> >>>> >>>> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >>>> l'usage >>>> exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le >>>> secret >>>> professionnel. Si vous recevez ce message par erreur, merci d'en >>>> avertir >>>> immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne >>>> pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne >>>> pourra >>>> Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs >>>> efforts soient faits pour maintenir cette transmission exempte de tout >>>> virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa >>>> responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >>>> d'un >>>> virus transmis. >>>> >>>> This e-mail and the documents attached are confidential and intended >>>> solely >>>> for the addressee; it may also be privileged. If you receive this >>>> e-mail >>>> in >>>> error, please notify the sender immediately and destroy it. As its >>>> integrity >>>> cannot be secured on the Internet, the Worldline liability cannot be >>>> triggered for the message content. Although the sender endeavours to >>>> maintain a computer virus-free network, the sender does not warrant >>>> that >>>> this transmission is virus-free and will not be liable for any damages >>>> resulting from any virus transmitted. >>>> >>> >> >

Aug. 14, 2015