I made all the necessary Magritte3 changes to the example in the Seaside
Book, pages 358-361.
The scripts on page 360 ran OK which seems to suggest that I got all the
Magritte3 changes correct.
But when I tried to create a Seaside Editor as per the bottom half of
page 360, a method, asComponent, was called for. I searched for
asComponent, but it isn't in my image.
So, when I ran the example in Seaside, I got "MessageNotUnderstood:
Address>>asComponent"
I'm running Seaside 3.1 and Magritte3 on Pharo3. Has something replaced
asComponent?
Hi all,
I tried to load Pier3 into a fresh Pharo image using:
Gofer new
url: 'http://smalltalkhub.com/mc/Pier/Pier3/main';
package: 'ConfigurationOfPier3';
load.
(Smalltalk at: #ConfigurationOfPier3) load
Note that this does not load Pier-Seaside.
This loading failed due to the following error: (while loading: 'Pier-Pharo-Persistency')
'This package depends on the following classes:
PRWidget
You must resolve these dependencies before you will be able to load these definitions:
PRExportImportWidget
groupLabel
isAbstract
label
export:
exporterImporter
exporterImporter:
exporterImporterClass
exporterImporterClass:
import:into:
initialize
renderContentOn:
renderExportOn:
renderImportOn:
renderSelectOn:
replace
replace:
'
When I take a Pier3 image from the build server, it appears that PRWidget is in Pier-Seaside. Also this stuff is not loaded (the warning is ignored somewhere!). So this should be moved to a different package, with a dependency on Pier-Seaside and Pier-Pharo-Persistency.
Cheers,
Diego
Hi all,
Pier3Addons now successful loads in pharo3.0 and pharo2.0. There is only an issue in Pharo3.0 that gives a warning: the link checker uses HTTPSocket. So I guess this needs to be moved to Grease (as Zinc is not part of Squeak).
Diego
Diego and I are looking at migrating the moose site to a newer pier.
We use the PierCodeExporter for that.
The moose site is a pretty old pier (Pier1 on Pharo 1.0rc1 10492). It doesn’t have grease loaded.
The exporter doesn’t use a lot of grease functionality.
We could have tried loading Grease, but decided to just copy paste
the functionality needed.
http://smalltalkhub.com/mc/Pier/Pier3Addons/main/Pier-Exporter1-DiegoLont.1…
Then the compilation fails because there are too many news entries,
resulting in a method that is too large to compile.
In PRKernelCodeExporter>>writeCodeFor: structure
we changed the repeated
structure addChild: (self newsABCD: aKernel).
to an array of selectors with a perform: loop.
+ stream << ' #('.
+ structure enumerator do: [ :each | stream << ' #''' << (each asSelector) << ':''' ] separatedBy: [ stream cr ].
+ stream << ' ) do: [ :each | ' << String cr << ' structure addChild: (self perform: each with: aKernel) ].' << String cr.
-
- structure enumerator do: [ :each |
- stream << ' structure addChild: (self ' << (each asSelector) << ': aKernel).' << String cr ].
This was enough for moose, but needs method splitting for larger sites.
http://smalltalkhub.com/mc/Pier/Pier3Addons/main/Pier-Exporter-Code-DiegoLo…
With this we are able to generate the code. Next step is loading in a newer Pier.
to be continued.
Stephan
On 01.02.2014, at 01:19, Tobias Pape <Das.Linux(a)gmx.de> wrote:
> Hay,
>
>
> On 31.01.2014, at 16:10, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote:
>
>> I need to download the contents of a html table generated with Seaside as a file (actually the whole contents if the table is paginated).
>>
>> I wonder if somebody already implemented the feature to generate an Excel file programatically?
>>
>> I'm using CSV files, but the customer prefers Excel (it can be XLSX).
>>
>> Any thoughts? Command line converters? (linux)
>>
>
> I've done an excel 2003 xml-exporter for seaside/magritte.
> and since excel can open http/https urls, you can even serve it directly
>
> If y’all are interested, I can dig it out of the pit.
-- which I just did:
have a look at:
http://ss3.gemtalksystems.com/ss/Sheet.html
Needs Magritte3 and seaside.
Have fun!
Best
-Tobias
