Hi,
It looks like Pier does not take into account the changes made to the
CSS using the Edit Design command. You can reproduce the error by just:
- Edit Design
- add: body { background: yellow;}
- save and nothing happens.
The strange thing is that the changes are stored, they just do not
affect the rendering.
Cheers,
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"What we can governs what we wish."
I am a bit stuck in a pre-Blueprint world. So I was having a look at it.
I loaded up the current, release of pier, and it is very clean and ready
to be styled. I miss the tree view, has it gone because it doesnt fit in
the layout?
Blueprint looks cool for some applications. I have one site which has a
fairly fixed layout, so blueprint appears to me to be an ideal solution
for that, but not, I fear for pier in general.
This appears to me to be a better fit, for general blogish/corporate sites.
http://www.contentwithstyle.co.uk/Articles/17/a-css-framework/
best regards
Keith
Hi,
I'm trying to use MAOneToManyComponentEditInPlace, and can't realize
how it is supposed to work... what I want to do is add rows and edit
them "InPlace"... now I can add new rows, but empty ones. Is possible
to edit them? how?
Thanks in advance,
Esteban
I'm finally getting around to using Magritte and while I'm only on the
edge of learning what its fully capable of doing, I'm finding that it
appears to work as advertised (which is great!) and that should really
help get rid of a bunch of clutter from my code where I had a bunch of
rendering code + validation handlers. I was trying to do my own
formatting but will back away from that now and focus on content instead
(I've got a short turn-around time).. Once the content and functionality
is working then I'll focus on doing the prettying-up of the forms,etc.
Anyway, I just wanted to write a quick 'Thanks' note to let you know that
your hard work is very appreciated!
-- Rick
Dear list,
This should be an easy answer, I'm just not finding it:
How would I rewrite something like this into descriptions?
(maxAnnualFee > 0) & (fixedAnnualFee > 0)
ifTrue: [InvalidFeeSelection signal].
--
Danie Roux *shuffle* Adore Unix - http://danieroux.com
Lukas et-al,
Is it safe to assume that if I want to port parts of Magritte-Addons
to the VW version of Magritte (which was taken from the LR251 version
of Magritte in Oct 2007), that I should stick with a version that is
dated in about the same period of time (up to perhaps December 2007?)
to avoid issues with the interfaces changing? Just curious.. Thx!
-- Rick
I'm trying to follow "Possibility 3" from the Magritte tutorial (page
54) where I subclass MAContainerComponent and create my own
#renderContentOn: and override #descriptionContainer to point to my
new subclass.. The tutorial didn't really indicate how to get the
component data or other general usage -- so I figured I'd ask..
Also -- for future reference.. Is there an example or two that might
be good to use as references for this sort of questioning that doesn't
require pier since I'm on the VW platform? I'm a Magritte newbie and
examples are very helpful.. Thx!
-- Rick
Richard E. Flower wrote:
> Keith,
>
> Do you mind me asking what sort of method(s) you used to do the
> styling of the form that you were
> showing in this older email thread? Some of what you show is pretty
> much what I'm looking to do
> but I'm totally lost on how to get it going.. Many thanks in advance
> for any pointers you can provide..!
>
> -- Rick
>
Basic packages which you may or may not want to use...
Installer lukas project: 'magritteaddons';
install: 'Magritte-RealMemento';
install: 'Magritte-CustomBuilder';
install: 'Magritte-Scriptaculous.
Magritte-RealMemento package uses a real copy of the object as a
memento, rather than a dictionary of key value pairs. The real object
has behaviour which may relate data items. To use the real memento you
have to override #mementoClass for your model.
"Magritte-CustomBuilder" sets the default builder to use a numeric in
the description selector to set the priority, like so. (I find this very
useful)
description0250Documents
^ MAToManyRelationDescription new
classes: (Array with: DTIExternalFileModel);
"Magritte-Scriptaculous extends the accessors so you can do
things like this...
Where the visibility of this item is determined by
#hasOrderNumber."
accessor: (#documents asAccessor visible: #hasOrderNumber);
componentClass: MAOneToManyDocumentsComponent;
label: 'Documents';
yourself
Accessors augmented in this manner can provide #readonly #visible
#cssClasses #tooltip and #options (for lists)
For rendering, lukas has his MACssRenderer, and I have my MADivsRenderer
(part of Magritte-Scriptaculous).
There is also Magritte-ComponentDecoration another add on that you might
find useful.
best regards
Keith
Hi,
I'd like to have a component that show last edited structure (at leat page).
I think it's not possible yet. Correct me if wrong.
Does adding an inst var timestamp in structure is the way to go ?
Thanks
Cédrick