Novemberborn, Straight lines circle sometime

sIFR 3 Feature List

As I’ll have to focus on course-work and money-making-work in the next few weeks here is a feature list for sIFR 3. Of course, when something turns out to be too hard to implement, it’ll be removed from the list. Don’t take it for granted!

sIFR itself will be easier to use, and there’ll be a number of small fixes for edge-cases. Speed improvements are high on the list as well, obviously.

link | sifr3 sifr | 12 March 2006, 16:31


Comments

  1. That will definitely be good! All the important future improvements are listed! well done. now we just need to sit and wait :-)

    Sahar | 13 March 2006, 19:18 | link

  2. Awesome, Mark. I have got to buy you a beer sometime. :P

    Branstrom | 13 March 2006, 23:49 | link

  3. I’m really really lookin’ forward to this!

    Egor | 15 March 2006, 05:48 | link

  4. I don’t know if this is a good place to do so, but I’ve got an idea for sifr3 I’d like to mention: Make the CSS selector engine a seperate and optional component. For instance, I like using jQuery, which has it’s own selection engine, so it’d be nice to not have duplicated funtionality. I could easily see a plugin for jQuery making some nice glue.

    $('#foo h1.classy').sifrReplace(...);
    

    I might be a very niche case but I think that would be an excellent improvement for sifr3. Or how hard would it be to hack out the selector engine in sifr2?

    Anyway, thanks for the work on sifr. I love it, and I hate it (those are my favorite type of things)

    mitchell | 15 March 2006, 19:34 | link

  5. Hey Mitchell,

    The selector code already lives in it’s own namespace, so I figure it’d be possible to replace it with a wrapper for jQuery or other implementations.

    Mark Wubben | 15 March 2006, 20:06 | link

  6. Mark,

    What do you know? I find myself unsurprised. I probably could have found this out with a peek at the source, but thanks for the quick response.

    mitchell | 16 March 2006, 00:09 | link

  7. Any chance we might see a fix for wrapping text? Currently if text wraps the text will also enlarge. (unless I am an idiot and this has already been fixed in some version)

    cody lindley | 21 March 2006, 23:50 | link

  8. Cody, it’s under “font sizing” ;-)

    Mark Wubben | 22 March 2006, 08:49 | link

  9. Mark, have you heard about the “content injection in flash with XHTML and sifr” method that was recently used to re-design the Pontiac web site?

    I don’t like their choice to replace large swaths of text with this method, but it definitely has speed and flexability on its side. Their technique might contain some ideas that could be incorporated into sIFR3.

    Adam Messinger | 29 March 2006, 16:05 | link

  10. Hey Adam,

    Yeah, I heard about it. I actually share your feelings regarding it’s use, but I don’t think they added anything which might be of use for sIFR 3. Could you elaborate, or was it just a hunch?

    Thanks,

    Mark Wubben | 29 March 2006, 17:02 | link

  11. Currently when using sIFR, the background colour is declared in the .js file. This poses a problem with style sheet switching, ie. If the default body background is black you’d also get the sIFR’s to be black too. That is if you wanted it to match. However once switched to an alternate style sheet that has a different background colour, you’re left with the original black background of the sIFR text– which doesn’t look pretty.

    sIFR can be transparent, however as I understand, it isn’t well supported. FlashCSS looks to be a saviour if the background attribute is supported through CSS, unless currently there is an alternative solution…

    Hayden | 30 March 2006, 12:00 | link

  12. Mark: Just a hunch, really. The speed is what really caught my eye. Giving the sIFR3 demo another shot on a day that I don’t have 50 tabs open, however, I see that it’s already plenty fast. Great work!

    Adam Messinger | 2 April 2006, 04:45 | link

  13. So any ideas as to when sIFR 3 is slated for release?

    Daniel A. Munz | 6 April 2006, 15:14 | link

  14. Hi Daniel,

    I’m still hoping before July, but I’m quite busy with other things too.

    Mark Wubben | 6 April 2006, 16:08 | link

  15. I’m extremely excited to see the kerning & leading (line-height) features. In many cases the default look is adqueate but being able to fine tune these essenital type attributes will seperate good type from excellent type.

    Kudos again, I love V2 already.

    Mark Fox | 24 April 2006, 21:28 | link

  16. Great Work! The work you guys are doing is amazing.

    Not sure if anyone else has already mentioned this … if I add “font-style:italic” and “font-weight:bold” to .sIFR-root, sIFR will silently fail. Currently my work around has been to create a sFIR swf with bold and italic already applied.

    Example: ‘.sIFR-root’ : { ‘text-align’: ‘left’, ‘font-weight’: ‘bold’, ‘color’: ‘#e29148’, ‘font-style’: ‘italic’}

    Thanks again, I can’t wait for the final release!

    Daniel Smith | 15 September 2006, 20:55 | link

  17. Daniel, that’s because Flash doesn’t have the glyphs to render in italics or bold. Your method adds them, as intended.

    Mark Wubben | 15 September 2006, 22:41 | link

Leave your comment

Please keep it polite and on topic. Yes, your e-mail address is required, but it's kept private. HTML is not allowed in the comments but you can use Markdown. Non-contributing comments run the risk of being removed. Especially if the website seem “fishy”. Spammers, beware.

(required)
(required, kept private)
(optional, but let's share it!)
(required)

Remember my details


Novemberborn: Extra

About the author

Mark Wubben is a hacker/writer in Enschede, the Netherlands.

Read more about Mark...

Go to

Jobs (NL)

Xopus zoekt programmeurs! Verbeter de code en win!

Please donate

If you like sIFR, please consider making a donation so I can spend more time on it. Thank you.

sIFR Documentation

See the documentation for sIFR 2 and sIFR 3.

Subscribe