DISQUS

carlo.comments: carlo.log → Jan 7th 2004, 11:37 GMT

  • Arbus · 5 years ago
    Can't wait.
    Uh, I won't have to lear anything new, will I?
    I *hate* that.
  • Carlo Zottmann · 5 years ago
    Nah. If anything, I try to make it even simpler. Deal? :)
  • Morn · 5 years ago
    Arbus, don't trust this Gossip guy. Run while you still can. IT'S A TRAP!
  • Tom · 5 years ago
    Please, please, please, please, pretty please with a cherry on top, release the code!
  • Carlo Zottmann · 5 years ago
    Mwahahaha! No. :P

    I'm not completely ruling out the very slight possibility of eventually releasing the source code under some circumstances at some point in the future, tho, but for now, no public code.
  • entipy · 5 years ago
    Tease
  • terpsichoros · 5 years ago
    Maintaining public code isn't a huge hassle, unless you want it to be. You just put up tarballs every time you've got a working version - if someone sends you changes you're not interested in, you say "thanks but no thanks" and let them fork.

    Any chance of getting textile input in g-blog v2?
  • Hooloovoo · 5 years ago
    hehe textile - I remember asking about that at one point for GLUE.

    As I said elsewhere, let me know if you need/want a tester.
  • terpsichoros · 5 years ago
    yeah - I forgot who'd posted it, but it's pretty nifty. Thanks for pointing it out; I use it on my political blog. (Which is Movable Type with MT-Textile)
  • Carlo Zottmann · 5 years ago
    Textile is definitely on my list. I'm even considering to ditch the old markup completely in favor of Textile.
  • Hooloovoo · 5 years ago
    heh...

    [Link]

    good things come to those who wait... :p

    Edited on Jan 8th 2004, 12:30 by Hooloovoo
  • entipy · 5 years ago
    How would it make things different on the user's end, exactly?
  • Carlo Zottmann · 5 years ago
    Do you mean Textile, entipy? Or v2 as whole?
  • entipy · 5 years ago
    Textile, sorry.
  • Carlo Zottmann · 5 years ago
    The markup code for text input (entries, comments) would be slightly different. This is both good and bad; good, because it'll produce valid XHTML code which means lists would finally work right ;) and has more features, bad (slightly bad, that is) because you'd have to learn a new markup if you want to write markup yourself -- but you could also use the markup links above the textareas (Bold, Italic, Underlined, Image etc.). If you mostly use those, chances are good that you wouldn't even have to care.

    If you want to know what Textile is like, take a look at the creators' example page. You'll notice that while it is different in type and form of markup, it comes with much more features and offers more flexibility. For instance, you can embed tables.
  • terpsichoros · 5 years ago
    Even Textile v 1 is pretty nifty - see
    The description of Textile for Movable Type
  • entipy · 5 years ago
    Ahh. I didn't look at the page long enough before. Heh.

    I got it now. Thanks.
  • Carlo Zottmann · 5 years ago
    But I've already refactored the original PHP version of Textile 2beta (functions, functions, nothing but functions) into a PHP class.
  • Hooloovoo · 5 years ago
    sweet - planning on releasing that class?
  • Carlo Zottmann · 5 years ago
  • Hooloovoo · 5 years ago
    doh...


    hehe cool.
  • Arbus · 5 years ago
    Remember, no learning nothin' new. Nope. Nothin'.