Le 13/8/15 11:38, H. Hirzel a écrit :
http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.52.mcz
47 test run, 37 passes.
Nice :)
Currently I have a fixed string
TabularXSLXExport>>sharedStrings_xml
^'
http://schemas.openxmlformats.org/spreadsheetml/2006/main";
count="1" uniqueC
Hi pablo
I always considered Magma as a good idea/system. Now Chris always
thought that
Pharo was not good for him because we were supported by Gemstone. I
never really understood.
So a port could be good but if Chris is not interested it may be
difficult. Now may be you should
contact him and
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 wi
Found the information on page 1600 of
http://standards.iso.org/ittf/PubliclyAvailableStandards/c061750_ISO_IEC_29500-1_2012.zip
18.3.1.4
c (Cell)
On 8/14/15, H. Hirzel wrote:
> On 8/13/15, Blondeau Vincent wrote:
>> Hi,
>>
>> Look at TabularCell>>extractFromXml: to have some hint about the st
On 8/13/15, Blondeau Vincent 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.
Magma is a very valuable tools!
I have no idea of the complexity to deal with that. For example we have
trait in Pharo, I guess it have implication.
Hilaire
Le 14/08/2015 00:15, Pablo R. Digonzelli a écrit :
> FYI. Is it interesting for pharo comunity migrate magma from squeak to pharo?.
> Anyone
Indeed that is better idea!
Thanks Ben,
Vincent
-Message d'origine-
De : Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] De la part de Ben
Coman
Envoyé : jeudi 13 août 2015 19:13
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] Tabular: XLSX import
On Thu, Aug
On Thu, Aug 13, 2015 at 10:37 PM, Blondeau Vincent
wrote:
>
> > -Message d'origine-
> > De : Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] De la
> part
> > de H. Hirzel
> > Envoyé : jeudi 13 août 2015 15:06
> > À : Any question about phar
> -Message d'origine-
> De : Pharo-users [mailto:pharo-users-boun...@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 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/Tabu
Hi,
Look at TabularCell>>extractFromXml: to have some hint about the standard
values of the parameters.
Don't hesitate to put some comments in the code with the discoveries you made.
Vincent
> -Message d'origine-
> De : Pharo-users [mailto:pharo-users-boun...@lists.phar
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.
I think the access to an empty cell should be nil.
To answer generally to all the other questions, you
Answering my own question:
Another value for t is
t="inlineStr"
abcdefghijklmnopqrstuvwxyz 1234567890
So for the export I will ignore the construction of a file
sharedStrings.xml
at the moment.
On 8/13/15, H. Hirzel wrote:
> The attribute t="s" of a cell c seems to indicate that the con
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|
For the shared strings in sheet1.xml for example
what do the attributes s and t stand for?
0
1
On 8/13/15, H. Hirzel wrote:
> http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.52.mcz
> 47 test run, 37 passes.
>
>
> Currently I have a fixed string
>
> TabularXSLXExport>>
http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.52.mcz
47 test run, 37 passes.
Currently I have a fixed string
TabularXSLXExport>>sharedStrings_xml
^'
http://schemas.openxmlformats.org/spreadsheetml/2006/main";
count="1" uniqueCount="1">
'.
How far can I safely ignore constructi
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 wrote:
> http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.50.mcz
>
> Another question
I think the priority at the moment is to get the non-GUI operations
working fine.
Export currently only works for one sheet and more tests are needed,
see other thread.
Excel and LibreOffice Calc are the spreadsheet editors! The focus is
to get Pharo interacting nicely with this ubiquitous data
http://ss3.gemtalksystems.com/ss/Tabular/Tabular-HannesHirzel.50.mcz
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
19 matches
Mail list logo
