I just uploaded a Spaz theme called 'urchin' to the file storage area
of this group - please try it out. Just unzip into the themes folder
and restart Spaz.
It has a few limitations in that it's designed for a fixed-width main
tweet list as the posts appear on non-tiled bitmap backgrounds, but
there's no apparent way to stop the main window from being resized to
any width (is there?). It also has the drawback that postings that use
large amounts of glyph characters (e.g. chinese / japanese) could
potentially wrap onto more lines than will fit onto the tweet
background, and so I have limited height of the main text block for
each tweet because i'm not interested in reading the full text of
these chinese / japanese tweets.
First off, you can put themes like this in the "userthemes" directory, which is in the same location as your preferences.json file. On OS X, it's someplace like this:
You'd make a directory in here for the theme (like "urchin") and then put the theme files inside it.
The advantage of putting it here is that this directory does *not* get overwritten when you install a new version. The standard "themes" directory does.
These directories may be too hard to find. I'm not sure I'm 100% happy with the current location. Maybe we should put these in the user's Documents directory? It isn't quite as good a fit semantically, but semantics don't matter if people can't use them.
On Mon, Jul 7, 2008 at 10:14 AM, urchino <nick.sturr...@googlemail.com> wrote:
> I just uploaded a Spaz theme called 'urchin' to the file storage area > of this group - please try it out. Just unzip into the themes folder > and restart Spaz.
> It has a few limitations in that it's designed for a fixed-width main > tweet list as the posts appear on non-tiled bitmap backgrounds, but > there's no apparent way to stop the main window from being resized to > any width (is there?). It also has the drawback that postings that use > large amounts of glyph characters (e.g. chinese / japanese) could > potentially wrap onto more lines than will fit onto the tweet > background, and so I have limited height of the main text block for > each tweet because i'm not interested in reading the full text of > these chinese / japanese tweets.
On Mon, Jul 7, 2008 at 11:30 AM, Ed Finkler <funkat...@gmail.com> wrote: > This is totally awesome.
> First off, you can put themes like this in the "userthemes" directory, > which is in the same location as your preferences.json file. On OS X, > it's someplace like this:
> You'd make a directory in here for the theme (like "urchin") and then > put the theme files inside it.
> The advantage of putting it here is that this directory does *not* get > overwritten when you install a new version. The standard "themes" > directory does.
> These directories may be too hard to find. I'm not sure I'm 100% happy > with the current location. Maybe we should put these in the user's > Documents directory? It isn't quite as good a fit semantically, but > semantics don't matter if people can't use them.
> On Mon, Jul 7, 2008 at 10:14 AM, urchino <nick.sturr...@googlemail.com> wrote:
>> I just uploaded a Spaz theme called 'urchin' to the file storage area >> of this group - please try it out. Just unzip into the themes folder >> and restart Spaz.
>> It has a few limitations in that it's designed for a fixed-width main >> tweet list as the posts appear on non-tiled bitmap backgrounds, but >> there's no apparent way to stop the main window from being resized to >> any width (is there?). It also has the drawback that postings that use >> large amounts of glyph characters (e.g. chinese / japanese) could >> potentially wrap onto more lines than will fit onto the tweet >> background, and so I have limited height of the main text block for >> each tweet because i'm not interested in reading the full text of >> these chinese / japanese tweets.
>> So it's far from perfect, but aren't we all? ;)
I moved this theme into the usertheme folder, but I've noticed that
the theme doesn't now pick up the button images. When you first set
the theme you get the images from the previous theme and the next
restart you get question mark images in place of the buttons. Is AIR
trying to cache these assets so it could be looking in the original
theme location? Is this possible and is there a way to clear its
cache?
On Jul 7, 4:30 pm, "Ed Finkler" <funkat...@gmail.com> wrote:
> First off, you can put themes like this in the "userthemes" directory,
> which is in the same location as your preferences.json file. On OS X,
> it's someplace like this:
> You'd make a directory in here for the theme (like "urchin") and then
> put the theme files inside it.
> The advantage of putting it here is that this directory does *not* get
> overwritten when you install a new version. The standard "themes"
> directory does.
> These directories may be too hard to find. I'm not sure I'm 100% happy
> with the current location. Maybe we should put these in the user's
> Documents directory? It isn't quite as good a fit semantically, but
> semantics don't matter if people can't use them.
> On Mon, Jul 7, 2008 at 10:14 AM, urchino <nick.sturr...@googlemail.com> wrote:
> > I just uploaded a Spaz theme called 'urchin' to the file storage area
> > of this group - please try it out. Just unzip into the themes folder
> > and restart Spaz.
> > It has a few limitations in that it's designed for a fixed-width main
> > tweet list as the posts appear on non-tiled bitmap backgrounds, but
> > there's no apparent way to stop the main window from being resized to
> > any width (is there?). It also has the drawback that postings that use
> > large amounts of glyph characters (e.g. chinese / japanese) could
> > potentially wrap onto more lines than will fit onto the tweet
> > background, and so I have limited height of the main text block for
> > each tweet because i'm not interested in reading the full text of
> > these chinese / japanese tweets.
> > So it's far from perfect, but aren't we all? ;)
It looks like the proper solution to this will be something I've wanted to do for a while: stop embedding images within html and only use theme CSS for this kind of thing. This is really a more flexible, all-in-one approach that will also handle theme switching a lot better. It means you'll need to make some pretty minor modifications to your theme for the next release, though. I'll post more info on that as I get the changes completed.
On Mon, Jul 7, 2008 at 11:56 AM, urchino <nick.sturr...@googlemail.com> wrote:
> I moved this theme into the usertheme folder, but I've noticed that > the theme doesn't now pick up the button images. When you first set > the theme you get the images from the previous theme and the next > restart you get question mark images in place of the buttons. Is AIR > trying to cache these assets so it could be looking in the original > theme location? Is this possible and is there a way to clear its > cache?
> On Jul 7, 4:30 pm, "Ed Finkler" <funkat...@gmail.com> wrote: >> This is totally awesome.
>> First off, you can put themes like this in the "userthemes" directory, >> which is in the same location as your preferences.json file. On OS X, >> it's someplace like this:
>> You'd make a directory in here for the theme (like "urchin") and then >> put the theme files inside it.
>> The advantage of putting it here is that this directory does *not* get >> overwritten when you install a new version. The standard "themes" >> directory does.
>> These directories may be too hard to find. I'm not sure I'm 100% happy >> with the current location. Maybe we should put these in the user's >> Documents directory? It isn't quite as good a fit semantically, but >> semantics don't matter if people can't use them.
>> On Mon, Jul 7, 2008 at 10:14 AM, urchino <nick.sturr...@googlemail.com> wrote:
>> > I just uploaded a Spaz theme called 'urchin' to the file storage area >> > of this group - please try it out. Just unzip into the themes folder >> > and restart Spaz.
>> > It has a few limitations in that it's designed for a fixed-width main >> > tweet list as the posts appear on non-tiled bitmap backgrounds, but >> > there's no apparent way to stop the main window from being resized to >> > any width (is there?). It also has the drawback that postings that use >> > large amounts of glyph characters (e.g. chinese / japanese) could >> > potentially wrap onto more lines than will fit onto the tweet >> > background, and so I have limited height of the main text block for >> > each tweet because i'm not interested in reading the full text of >> > these chinese / japanese tweets.
>> > So it's far from perfect, but aren't we all? ;)
really nice theme, I like it. small comment -- for my eyes, there's not quite enough differentiation between regular "green" tweets and replies. as i say, that's my (old) eyes so no big deal.
Good point. New version in file store - I swapped the green reply with
the regular blue so replies are now in blue and the normal timeline is
in two (very similar ;) shades of green... it looks better I think
although if you'd rather see other colours let me know.
On Jul 7, 10:42 pm, Graeme <dunl...@gmail.com> wrote:
> really nice theme, I like it. small comment -- for my eyes, there's not
> quite enough differentiation between regular "green" tweets and replies. as
> i say, that's my (old) eyes so no big deal.
Yeah, I don't think :selected will work. It's something that we'll have to apply with a class programatically. We'd make the request on click, and wait for the response to confirm that it was successful from Twitter. Then we could turn on the fav light 8)
> works fine. the selected state doesn't, however.
> On Jul 10, 10:24 am, urchino <nick.sturr...@googlemail.com> wrote: >> I have updated this theme to work with version 0.4.2.1. All seems good >> to me.
>> One question - I was wondering if the hover / select for the favourite >> icon can be achieved with CSS entries by adding:
|
