Hi,
is there any photo gallery available for Pier? I mean a widget where I
could upload pictures and they are rendered in a nice way. I started
one 4 years ago but I abandoned it.
Bye
--
Damien Cassou
http://damiencassou.seasidehosting.st
#1.
locationDefinition
^ #( ( 2 '63450af8d9c2e17b' ) ( 30 'iaojv41bw67e0tud5m9rgplqfy8x3cs2kznh' )
)
Why is '63450af8d9c2e17b' all mixed up (as opposed to '012345...')? I'm
cleaning some code and feel like I'm missing something here...
#2. Is anyone using #baseUrl? There are no senders in the image...
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/MAExternalFileModel-Questions-tp4711175.html
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
Dear readers,
I've just extracted Pillar out of Pier (baseline 3.10). Pillar is a
syntax (the good-old Pier syntax), its parser, a document model, and
exporters. Pier now depends on Pillar and provide a CMS (with its
Morph and Seaside views).
https://ci.inria.fr/pharo-contribution/job/Pier3/
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
Are you using Moose to analyse the Magritte system? Moose has its own mailing list.
Magritte uses a lot of the patterns from the gang of four book, and names classes
(and a few packages) after the patterns.
Magritte is a good example of a framework with high essential complexity
and low accidental complexity. It is difficult to understand because it solves
(difficult) problems at a high abstraction level. The elimination of duplication
has been done rather well.
If you want to use Magritte for web development, you might want to take a look
at the extensions in QCMagritte.
MABasicObject overrides GRObject class side basicErrorClass method.
Magritte has to work in multiple Smalltalk implementations. Grease helps with that.
Having Magritte objects inherit from GRObject allows platform-specific overrides
to be applied.
The role of MAAccessorMock isn’t clear to me either. It has no references and removing it
doesn’t make any test fail. It could of course be that references/subclasses are only defined
in packages not loaded by default. More likely is perhaps that it was used in an earlier
version of the framework or tried out at a certain point in time and not removed when no longer
needed. You could find out by browsing earlier versions of the Magritte packages.
Stephan
I’m not aware of any forum for Pier.
You could modify the start of a forum found in
http://ss3.gemstone.com/ss/Forum.html
That contains some code we used in teaching smalltalk
Stephan
Hi all,
I asked this question on the Seaside mailing list, however, this seems like something for Pier :)
Is there a forum for Pier? I don’t mean the one that I’m posting to :) rather is there a smalltalk/seaside/pier framework for adding a forum to a Pier site? It seems like the Pier blog provides much of the required functionality - I’m wondering if anyone has implemented the Blog as a forum, or if there is an add-on that extends the blog to make it more like a forum.
Kind regards,
Jupiter
Hi all,
I'm analysing the Magritte system and I can see that there are many classes
that haven't been declared. Some, I believe, are those are there only to be
abstracted like MABasicObject. Some others, like MAAccessorMock, are there
only for testing purpose? And some other ones, like MAPropertyError, have
blank code but still have some references to themselves.
So are all they code left blank intentionally for future work or for just
testing, or just an incomplete work. Should they be considered bad smells
code as I am analysing those.
Thank you very much!
On Wed, Nov 13, 2013 at 11:18 AM, Stéphane Ducasse
<stephane.ducasse(a)inria.fr> wrote:
>> Is there a plan to extend Pillar to support a book with multiple files?
>
>
> this was not plan but we could
> Now if someone needs that he should have a look and help
I don't really understand the question (and I also don't understand
Steph's answer). Are you talking about sending a set of files to
Pillar so that 1 coherent book is generated?
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
Hi,
On Wed, Nov 13, 2013 at 11:18 AM, Stéphane Ducasse <
stephane.ducasse(a)inria.fr> wrote:
>
>
>> At the moment, Pillar assumes that one file is one chapter. When
>> generating PDF, an index .tex file is required to construct the overall
>> book with table of contents and others such elements.
>>
>> As far as I see, in HTML, there is no possibility of generating this
>>
>> Is there a plan to extend Pillar to support a book with multiple files?
>>
>
> this was not plan but we could
> Now if someone needs that he should have a look and help
>
Ok.
What about references? I saw somewhere that there existed an intention of
>> supporting references, but I did not see an example yet.
>>
>
> do you mean ref{} or cite{}
>
I mean cite{}
> We want to add a kind of generic tagging so that we can express
> cite{}
> comment{}
> …
>
Interesting. I would be very interested in that.
> Are they supported?
>>
>
> I do not think so right now.
>
Ok.
Doru
>
>> Cheers,
>> Doru
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
At the moment, Pillar assumes that one file is one chapter. When generating
PDF, an index .tex file is required to construct the overall book with
table of contents and others such elements.
As far as I see, in HTML, there is no possibility of generating this
Is there a plan to extend Pillar to support a book with multiple files?
What about references? I saw somewhere that there existed an intention of
supporting references, but I did not see an example yet. Are they supported?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
