My best experiences have been when the designer has full reign to do
what they need on the CSS/HTML front on a blank canvas-- obviously after
doing wireframes with something like OmniGraffle, Balsamiq or Fireworks.
It helps if they add things like static error messages or a highlighted
I would just give the artist the freedom to do what ever he wants...
and then just refactor what's necessary afterwards.
**
Martin
2009/10/27 Ashley Aitken mrhat...@mac.com:
Hi All,
Just a quick question.
Can someone please provide some pointers to Wicket-specific or general CSS
I wouldn't do it. The churn of implementing a UI before its designed is huge.
In my opinion your better off watching cartoons for the month it takes
the UI to be developed because you'll most likely waste that month
trying to adapt your UI implementation to the reality of what is
developed by the
Thanks Martin and John.
I realise that most projects start with Web/GUI storyboards and
perhaps even fully graphically designed pages and then add the dynamic
stuff. However, I think my situation is somewhat the reverse. I want
to design the logical interface myself, header, footers,
It makes sense what you are asking and it can be done. If you
logically construct your div structure and liberally apply divs/spans
so that your eventually CSS implementor can uniquely address any
element on the page.
More spans/divs will be better. For example, if you have an area of
the page
Oh and don't use an automated tool. It'll add far too much extraneous
noise to your files that will complicate the CSS skinning you are
after later. Hand code it and then move it around in CSS by hand.
This is my opinion. I know our CSS team hates it when someone sends
them something done in a
to this question, its what works
best for you and your company.
Regards,
J.D.
-Original Message-
From: Ashley Aitken [mailto:mrhat...@mac.com]
Sent: Tuesday, October 27, 2009 11:10 AM
To: users@wicket.apache.org
Subject: Re: Wicket HTML before graphics design with CSS ...
Thanks Martin
Thank you all.
So it seems what I am trying to do is not completely impractical.
Perhaps though I could let them edit the HTML files as well (as long
as they maintain the logical / hierarchical structure I guess). I
just wanted to make it easier for them to do things consistently
thought CSS styles would be the way to go.
Oh, you should definitely use CSS and web standards based markup. You
should be able to apply the most basic style to it yourself so you can
get the functionality going. Google 3 column layout or something
similar for a basic css based layout.
While
Its amazing what designers can screw up :)
Design can have a huge impact on code. This peaceful co-existence can
really only occur if you let the designers go first. If you start with
wicket you will either A) tell your designers to go to h*ll daily or
B) spend hours and hours re-factoring to
really? because we have quiet the opposite experience.
we take a wireframe prototype, build it, and have the designer go in
afterwards and pretty it up. with only a couple of hours of
wicket-related training the designers know what to touch and what not
to touch.
-igor
On Tue, Oct 27, 2009 at
Totally divergent now but its an interesting topic.
We segment our Designers, HTML implementors and Java developers. Thats
probably the key difference.
Our designers work in photoshop or illustrator to pretty exacting
requirements. This lets us contract out design work to a variety of
firms
On Tue, Oct 27, 2009 at 9:36 PM, Ashley Aitken mrhat...@mac.com wrote:
Hi Igor (et al.),
On 28/10/2009, at 12:21 PM, Igor Vaynberg wrote:
we take a wireframe prototype, build it, and have the designer go in
afterwards and pretty it up.
Great, that is what I was hoping for.
Any tips on
13 matches
Mail list logo
