In cases where there is an MASelectorAccessor, I'd like to make the default
label = `the accessor capitalized unCamelCased`. It seems the overwhelmingly
common use case is `... #accessor: #dateCreated; #label: 'Date Created'`.
The current behavior is
MADescription>>#label
^ self propertyAt: #label ifAbsent: [ self class defaultLabel ]
Is anyone using (or can state a plausible use case for) this
subclass-customizable class-side #defaultLabel?
If no one is relying on the existing behavior, I'll make the change...
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Default-labels-tp4827879.html
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
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
Hi NG,
please help me understand the Pillar Project. Here are my questions and
assumptions:
1) Pillar is a markup language derived from piercms with an wiki-like dsl
language
2) Is it a pharo pendant to markup?
3) Is it possible to import normal markup to generate pillar?
4) What is the goal of Pillar? (at mid- or long-term to establish something
similar like gitbook? maybe pillarbook? )
5) ... something else what is necessary to understand pillars future ;-)
Thanks in advance for your replies.
Best regards,
Damir
-----
--
Damir Majer
... be agile: www.majcon.de
--
View this message in context: http://forum.world.st/Help-me-understanding-Pillar-tp4852071.html
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
Hello,
After my previous question[1] and the pointers given to QCMagritte, I
figured I had to start investigating QCMagritte to see if it will help
for our use case. The one I did not mention was changing screens using
ajax, so I am now trying (inbetween things) to see how QCMagritte
influences work.
It seems the QCMagritte solution is its setters for descriptions, and
the use of, eg. addInfluence:for: in there. Is it possible for me to use
this mechanism without subclassing from QCObject, and in a component
that knows nothing about QCComponent? (Or, alternatively, how can I get
influences to work with as little as possible other QCMagritte stuff
involved?)
If I want to try and use QCMagritte for this goal, I need to be able to
retrofit it bit by bit into an existing application where I cannot just
make existing things inherit from QCMagritte objects.
[1] http://forum.world.st/Understanding-dynamic-descriptions-td4840991.html
Regards
- Iwan
--
Reahl, the Python only web framework: http://www.reahl.org
Alexandre Bergel <alexandre.bergel(a)me.com> writes:
> I use Pillar for AgileVisualization. One problem I have is that the
> book contains many code snippets. How can I run all the code snippet
> in order to spot error? Is there an easy way for that?
something like https://github.com/pillar-markup/pillar/issues/71 ?
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
Hi everyone!
Yes, a new version of Pillar, again!
With this version we removed the old parser of Pillar to introduce
PetitPillar base on PetitParser.
This parser is slower than the previous one but we will be able to
improve his speed.
We will also be able to improve Pillar at the parser level, which was
impossible before. So we will be able to remove some hacks and improve
the experience of the users.
If you are good in parser and you want to contribute to his improvement,
feel free to help, we have a lot of tests to help. This is my first
parser so I am sure it have a lot of rooms for improvement.
--
Cheers
Cyril
Hello guys!
I finished 5 months of internship into the RMoD team. I worked on Pillar
and I am glad to announce the version 1.0.0!
You can find an updated documentation of this version here :
https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l….
We decided with Damien Cassou to use Semetic Versioning from now (see:
http://semver.org/).
I will now explain the main changes I did on Pillar during my internship.
For each new feature I added tests and documentation.
I will begin with the changes of Pillar's structure
- The configuration system is now manage by Cocoon
(http://www.smalltalkhub.com/#!/~PharoExtras/Cocoon)
-- We now use Magritte in Cocoon
- I added Annotations : A syntax extension point
- I added Transformers : A way to transform a document model before an
export (to add a section structure in HTML for example)
- Some small refactoring.
-- Improvement of the template management
-- Improvement of the Pillar model parameters
- Improvement of the document model
-- Now the figures and links are two different entity
- I begun a PetitPillar (with PetitParser) in order to replace the old
parser too complicated.
Now I will talk about new features for the users
- Improvement of the usability of Pillar under Windows
- Beamer and Deck.js exporters
- Annotations :
-- To include a Pillar file into an other (${inputFile:path}$) (Example:
https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/Ente…)
-- To create new slides in Beamer and Deck.js (${slide:My
Title|label=optional}$)
-- To create columns into a Pillar document (currently works in Beamer,
Deck.js and HTML)
-- …
- Transformers
-- You can now add a parameter "lineNumber=true" to a script and Pillar
will transform them to add the line numbers
-- You can now import a script from an other file (see the documentation
of the scripts)
-- …
- Improvement of the errors raised by Pillar
- Addition of the inter-files links
- Improvement of the title configuration for numbering
- No need to make scripts anymore to use Pillar !
-- You can used "defaultExporters" in your configuration to do multiple
export (see documentation)
-- Pillar generate a script for LaTeX compilation (only for Unix for now)
- Possibility to export everything into a different folder (simpler to
clean after)
-- And possibility to copy some support files
For the two previous point you can take example on Enterprise Pharo
(https://github.com/SquareBracketAssociates/EnterprisePharo) and Pharo
Mooc (https://github.com/SquareBracketAssociates/PharoMooc).
This was a really cool internship :)
If you have some questions do not hesitate!
--
Cyril