|
|
Tim,
You open a good theme to improve Aida. I propose to do:
- #internalCSS in AIDASite settings, default true
- #externalCSSFilename: in AIDASite settings
macta wrote:
> Another piece that has caught my attention is how CSS styles are stored
> as methods in the WebStyle class.
>
> Is there any way to have them in a seperate CSS file? This makes it much
> easier to work with a web designer - you give them the style sheet and
> they mess around with making it look good (potentially usingdreamweaver
> or NVU) and just checkin the new style sheet.
I usualy make first my web site using default CSS in WebStyle then send
some example html pages and CSS to web designer. After he made a design
(that is, CSS), I put it manually back to css methods in a subclass of
WebStyle. Later I as a developer change CSS by myself if needed. For
Smalltalker this is easier than to change one big fat CSS file and also
easier to maintain with versioning systems.
> It seems like your current approach is quite developer focused - or your
> designer has to use a smalltalk image to make and view changes.
I could say that it is focuses for one time web design and then design
improvements from piece to piece
> Of course your approach does put all the "code" in one place - in
> smalltalk where it is versioned together.
That's a big plus, said from experience
> Presumably it can't be hard to have different policies for how style
> information is served?
One fast patch would be to create an another css method (say
#css99External), which just read some external css file.
Best regards
JAnko
|
Locked
