Please apologize my "write in Gmail" syntax errors.
The #beFixedHeader was a wrong transcription, it should be #fixedHeader.
And the unimplemented method was because of a missing period at the end.
It should have been:
html render: header.
html mdlLayoutContainer: [ self
Op 2-3-2019 om 19:36 schreef Esteban Maringolo:
renderContentOn: html
html render: header
html mdlLayoutContainer: [ self renderPageContentOn: html ]
Are you sure.
If I do your changes I see these error messages
renderContentOn: html
html mdlLayout
beFixedHeader;
with:
I haven't used MDL before, but moving code around I found that you are
not nesting the MDL tags properly.
The #mdlLayout must contain all the other elements, including the header.
So using your own classes the best way would be to do the following:
TBApplicationRootComponent>>renderContentOn:
Hello,
I try to make my first seaside project.
But I ran into a problem that I do not see how to solve,
The image can be found here :
*https://www.dropbox.com/s/8dt7xj1y6na5jog/Paintings.image?dl=0
*and the changes file here :
*https://www.dropbox.com/s/dnsslrnpxgy0ha8/Paintings.changes?dl=0
Thanks!
Hilaire
Le 02/03/2019 à 14:16, Pierce Ng a écrit :
> I've enhanced the Pharo SQLite library to be even more multilingual. It has
--
Dr. Geo
http://drgeo.eu
Wow! I wasn't aware SQLite supported that.
Thank you from bringing such powerful, yet small, database to Pharo.
Esteban A. Maringolo
El sáb., 2 mar. 2019 a las 10:17, Pierce Ng () escribió:
>
> Hi all,
>
> I've enhanced the Pharo SQLite library to be even more multilingual. It has
> always
Hi all,
I've enhanced the Pharo SQLite library to be even more multilingual. It has
always supported data elements that are Pharo WideString instances, these
being converted to/from UTF8 transparently by the library. Now the library
also handles multilingual table names, column names and default
Cool.
Thx Stef
On Sat, 2 Mar 2019 at 15:27, Stéphane Ducasse
wrote:
> Ok I will contact the editor telling that there are some wishes from the
> community to do something.
> After we can brainstorm on what should be purpose and outline.
>
> Stef
>
> On 1 Mar 2019, at 18:21, Ben Coman wrote:
>
Come on, no it does not. It generates invalid JSON (as it should, but doing so
silently is wrong).
Json render: {
'track' -> 'pharo'.
'language' -> 'smalltalk'.
'exercises' -> {
'slug' -> 'hello'.
'id' -> 55.
'topics' -> #('a' 'b' 'c') }
}.
=>
'["track": "pharo","language":
