>> karl, Could you add your latest css changes to
>> changegov/skin/overlay.css? I think Dietrich designated changegov to be
>> folder for the new extension while the src/ is for the old obamafox
>> extension.
Doh, my bad.
Thanks for merging the changes to overlay.css Abimanyu. I've restored
the obamafox/src/ files back to how they were supposed to be also.
Karl Dearden
w:
http://interclue.com/
e:
ka...@interclue.com
Abimanyu Raja wrote:
> karl, Could you add your latest css changes to
> changegov/skin/overlay.css? I think Dietrich designated changegov to be
> folder for the new extension while the src/ is for the old obamafox
> extension. Why don't we just get rid of src/ ? It only leads to more
> confusion. If we ever need it, we can always get it from the old
> changesets. Or we could start a new repos.
>
> - Abi
>
> 2009/1/10 karl <
ka...@interclue.com <mailto:
ka...@interclue.com>>
>
>
> >> And with regards to the entire project, we should have a bug
> tracker (is
> >> there already one?) so we can assign ourselves things to work on.
>
> I'm in total agreement with Abimanyu here. Whilst setting a bugtracker
> up is a bit of work I've found they are always worth it.
>
> I'd suggest going with a google project hosting
> <
http://code.google.com/hosting/createProject> since we already have the
> main group there and we all have accounts there. I haven't used their
> bugtracker before but from initial impressions I think it would be
> sufficient for our needs.
>
> However it may depend on licencing issues (Joe / Dietrich)?
>
> Karl Dearden
> w:
http://interclue.com/
> e:
ka...@interclue.com <mailto:
ka...@interclue.com>
>
>
> Abimanyu Raja wrote:
> > This sounds like a great idea! I have some free time over the
> weekend. I'll
> > get started on this.
> > I love the idea of event-specific re-skinning. But changing
> default feeds
> > for every event might annoy the user. Just for inauguration (since
> it'll
> > likely be the first time the user uses the extension), we could
> add Chris'
> > feeds as the default one.
> >
> > Besides just converting the ObamaFox extension to
change.gov
> <
http://change.gov> extension, I
> > think a lot more can be done to help
change.gov
> <
http://change.gov> users and people follow news
> > about the new administration. I'll post my thoughts on this soon.
> >
> > And with regards to the entire project, we should have a bug
> tracker (is
> > there already one?) so we can assign ourselves things to work on.
> >
> > Cheers,
> > Abi
> >
> > 2009/1/8 karl <
ka...@interclue.com <mailto:
ka...@interclue.com>>
> >
> >>
> >>> I hope things are well with all of you. For the past two
> months, I've
> >>> been on-and-off brewing ideas for what to do with ObamaFox.
> Inspired
> >>> (or maybe ripped) from a conversation with Dietrich, what if we
> did a
> >>> quick re-skin of ObamaFox as a new (Unofficial) Change.gov Firefox
> >>> Extension?
> >>>
> >>> This is a total out-of-the-blue e-mail and I definitely realize that
> >>> it's very US-centric -- and I should have started this
> conversation two
> >>> months ago. (Yikes)
> >>>
> >>> What do you think, though? are you down?
> >> Things are pretty quiet here right now so I can certainly lend a hand
> >> for a while.
> >>
> >>> Kalib has already created a sleek initial mockup -- attached.
> >>>
> >> Nice
> >>
> >>> Another note: We should host the background images remotely as well.
> >>> That would allow us to do event-specific re-skinning without
> >>> re-releasing.
> >> It we want to be able to re-skin between the current (obamafox)
> skin and
> >> the new (
change.gov <
http://change.gov>) one then we'd need to
> host the css file. But that
> >> introduces security risks (think moz-bindings and man-in-the-middle
> >> attacks) that could run malicious code.
> >>
> >> If we only want to adjust the background image, then I think that's
> >> quite safe to do, but it means we wont be able to adjust the tab
> colours
> >> and such like, unless we use images for everything.
> >>
> >> If we're only going for the background image then I'd suggest
> having two
> >> overlapping boxes with background images. A default one located
> within
> >> the add-on and a box on top containing the remote image. This
> way, the
> >> add-on still looks fine if for some reason the hosted image is
> unavailable.
> >>
> >>
> >> --
> >> Karl Dearden
> >> w:
http://interclue.com/
> >> e:
ka...@interclue.com <mailto:
ka...@interclue.com>
> >>
> >
> > >
> >
>
>
>
>
> >