> -----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 15:06 > à : Any question about pharo is welcome > Objet : Re: [Pharo-users] Tabular: XLSX import > > On 8/13/15, Blondeau Vincent <vincent.blondeau@worldline.com> wrote: > > Hello, > > > > As preface, I would like to announce that I created a job for the > > project on > > Jenkins: https://ci.inria.fr/pharo-contribution/job/Tabular/. This you > > can check all your tests are green. > > Excellent! > > https://ci.inria.fr/pharo- > contribution/job/Tabular/lastCompletedBuild/testReport/ > > Thank you. > > At the moment I do not mind so much if there are yellow and red tests. > > I'd like to get more tests to demonstrate what works and what does not. > It better to make tests on what is working instead of what is not. But if you want to add failing tests for next features, you can add the pragma <expectedFailure> to put it green and have a better view of what is broke on the Jenkins. > The package is useful as is at the moment but only for a certain subset of > cases. > > Next thing is to get the export of several worksheets working and round trip > testing of it. > > As well some cell styles. For example the attached case. > > > > I think the access to an empty cell should be nil. > > OK > > But what about > > aCell data > > (aCell being nil) > > should it still give nil or the empty string? It should give nil. The string is not an expected representation of an empty cell. You can put formula or strings in a cell, but nil represent the lack of content. BTW, the cell can be not nil but the content can be... It is the case where the cell has a style defined. > > > > > > > To answer generally to all the other questions, you can found the > > standards of the Spreadsheet here: > > http://standards.iso.org/ittf/PubliclyAvailableStandards/c061750_ISO_I > > EC_29500-1_2012.zip > > Thanks for the link. > > I had added > > http://www.ecma- > international.org/news/TC45_current_work/TC45_available_docs.htm > > to the comment of > > TabularObject > > > As well a link to a very short summary > > http://stackoverflow.com/questions/151005/create-excel-xls-and-xlsx-file- > from-c-sharp > Nice! > > Is it OK to keep this general documentation in the class comment of > TabularObject? > For me it is, as you have a pointer in the ConfigurationOfTabular that is saying that TabularObject is the main class. At least, you know where is the doc ;) Regards, Vincent > > > Regards > > Hannes > > > > > > -----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 08:51 > > > à : Any question about pharo is welcome > > > Objet : Re: [Pharo-users] Tabular: XLSX import > > > > > > 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@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@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.27.mcz > > > >> > > > >> I am currently exploring the code and trying to figure > > out how it works. > > > >> > > > >> --Hannes > > > >> > > > >> On 8/8/15, H. Hirzel <hannes.hirzel@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.mc > > > >> > z > > > >> > > > > >> > Hannes > > > >> > > > > >> > > > > >> > > > > >> > On 8/8/15, stepharo <stepharo@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@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@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@gmail.com>: > > > >> >>>>> > > > >> >>>>> Hi, > > > >> >>>>> > > > >> >>>>> > > > >> >>>>> > > > >> >>>>> it would be sooo cool to have a configuration in > > the catalog⦠> > > >> >>>>> > > > >> >>>>> > > > >> >>>>> > > > >> >>>>> Esteban > > > >> >>>>> > > > >> >>>>> > > > >> >>>>> > > > >> >>>>> On 01 Aug 2015, at 20:58, ЮÑий ÐиÑоненко > > > >> >>>>> <assargaddon@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. > > 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.