Re: [Fofredux-devel] CSS expert?

[Andrew T. <ajt...@hi...>]

I recommend TortoiseSVN for simple SVN activity. It has an Explorer
plug-in to give you right-click contextual interface to Subversion
folders you have checked out. That should prevent you from having to
"learn" subversion. It's what I *have* to use at work, since I can't
be on a Mac. ;)


Andrew

On 4/22/06, Evan Roth <eva...@gm...> wrote:
> hey khaled,
>
> i'm not sure what you prefer to use for development.  if you have no
> preference yet, i can highly recommend eclipse (http://www.eclipse.org/).=
  i
> use it at home for php/web apps, and we use it at work for all our java
> related stuff...super flexible.  in any case, it has built in SVN support=
,
> which makes it really easy via plugin.  there are probably plenty of othe=
r
> options...perhaps asking google might help.  (if you want full dev suite =
on
> a windows pc, grab XAMPP for apache, php and mysql at
> www.apachefriends.org...)
>
> In any case, the SVN book can be found at
> http://svnbook.red-bean.com/nightly/en/index.html
> that's more info than anyone sanely needs to get started with svn.
>
> /evan
>
>
> On 4/22/06, Khaled Abou Alfa <kha...@gm...> wrote:
> > I'm completely with Evan on this one. CSS layout all the way. Tables
> > should really only be used for tabular data. I'll start hacking through
> > and giving how I think we should be going down, and then everyone can
> > pitch in with ideas etc.
> >
> > But before I do that, I'll need a bit of a leg up on the whole SVN
> > thing. I'm a windows user so if you've got anything to ease my
> > progression into this world would be much appreciated :). Also since I'=
m
> > currently coding my latest redesign I'm in a bit of a coding mood right
> > now which is a good thing.
> >
> > Evan Roth wrote:
> > > yeh ignore my colors and layout in that screenshot.  it's what i did
> > > in about 10 mins to get something to show what fields we had to deal
> > > with.  we could easily add a <p> to each <div> with text as a
> > > description of what the user needs to fill in there.  I originally ha=
d
> > > it, but thought it seemed to be too much text for such trivial info.
> > > a better option may be to do something with a mouseover
> > >
> > > i would also suggest, if we are beginning to redo the layout, that we
> > > move away from tabled layout and into all css/div stuff.  first, it's
> > > web 2.0 friendly.  but most importantly, it allows users to generate
> > > their own layouts (skins) down the road...which would be inline with
> > > the plugin culture you want to aim for.  and it's always better to
> > > look at it that way from the ground up, rather than have to change it
> > > all later.  (if you haven't seen it before, check out
> > > http://blog.html.it/layoutgala/ --- 1 simple tableless layout in 40
> > > different stylesheets kind of shows endless possibilities.
> > >
> > > On 4/22/06, *Andrew Turner* <ajt...@hi...
> > > <mailto:ajt...@hi... >> wrote:
> > >
> > >     On 4/22/06, Evan Roth <eva...@gm...
> > >     <mailto:eva...@gm...>> wrote:
> > >     > ok, then here you go.  a screenshot of what i am aiming for, as
> > >     well as the
> > >     > html markup.
> > >
> > >     As I mentioned in my other email, I like the layout. Perhaps just
> > >     splitting up the help info so it's next to the appropriate fields=
.
> > >
> > >     > 1 thing i left out, since i'm not quite that far yet...when the
> > >     user submits
> > >     > back, of course we need to run through and check for errors.  i=
f
> > >     an error is
> > >     > found, the <div> encasing a label and input/select will have a
> > >     border of
> > >     > some color (red usually is good for errors) and we insert a
> > >     short error text
> > >     > <p> in the <div> above the input field, so the user can correct
> it.
> > >
> > >     Well, we can do on the fly error checking via JS (valid email, va=
lid
> > >     hostnames, etc.) and then do actual "can I write to the db" testi=
ng
> > >     and return like you  said.
> > >
> > >     >
> > >     > feel free to change colors, fonts, layout or even the markup as
> > >     needed.  i
> > >     > can fix the code later.  I'd also imagine that this does not
> > >     need to fit
> > >     > into the redesign of the site, since the script is run once, an=
d
> > >     then
> > >     > hopefully moved or deleted.  (although keeping with our color
> > >     scheme is
> > >     > always a good idea)
> > >     >
> > >
> > >     Definitely color scheme/style.
> > >
> > >     >
> > >     > On 4/22/06, Broken Kode <kha...@gm...
> > >     <mailto:kha...@gm...>> wrote:
> > >     > > I wouldn't call myself an expert on anything :), however I
> > >     dabble and I
> > >
> > >     He's lying. :)
> > >
> > >     Khaled, you mentioned about doing the code of the layout or the C=
SS
> of
> > >     the layout first. I think it would be better if you created the
> > >     prototype CSS for the site. When you come to things like tables,
> just
> > >     put a single row and then we/I will go back and insert the PHP to
> fill
> > >     in the table for each row. You can also put in any comments <!-- =
-->
> > >     or just <p class=3D"design_comment"></p> for 'how' something shou=
ld
> > >     work
> > >     if you have any ideas. e.g.
> > >
> > >     <table id=3D"feeds_table">
> > >     <tr class=3D"feeds_row even"><td>Example
> > >     title</td><td>View</td><td>Delete</td></tr>
> > >     </table>
> > >     <p class=3D"design_comment">The row should fade away when the use=
r
> hits
> > >     delete. When the user presses "view" there should be a cool
> flyout</p>
> > >
> > >     I think doing the CSS/Layout first will allow you to work with a
> > >     clean
> > >     slate and implement exactly what you have designed/pictured. Then
> we,
> > >     as programmers, can just fill in the underlying nitty-gritty.
> > >
> > >
> > >     > > know enough people who are experts if I hit a brick wall, so
> > >     if you want
> > >     > > I can jump in to play around with the CSS and then people can
> > >     see what
> > >     > > I'm trying to do and either code it in a cleaner fashion or
> > >     streamline
> > >     > > it as they see fit or whatever?
> > >     > >
> > >     > > I'm going to have to wait and see what happens with the whole
> > >     SVN change
> > >     > > and whatever before I jump into that area though..
> > >
> > >     Do you have, or know how to run SVN? It's rather straight forward=
.
> > >
> > >
> > >     --
> > >     Andrew Turner
> > >     ajt...@hi...
> > >     <mailto:ajt...@hi...>        42.4266N x 83.4931W
> > >     http://highearthorbit.com              Northville, Michigan, USA
> > >
> > >
> >
> >
>
>


--
Andrew Turner
ajt...@hi...        42.4266N x 83.4931W
http://highearthorbit.com              Northville, Michigan, USA