tinyjo: (webdesigner - chez geek)
Emptied of expectation. Relax. ([personal profile] tinyjo) wrote2004-01-12 02:04 pm

To-do: website

  • Determine definitely once and for all if it's possible to run the site on non-Windows servers. If it definitely isn't, consider whether I can be bothered to re-write the whole thing in some cross platform language (Python?). If I do decide to re-write it, that rewrite comes before anything else.
  • Add some stuff to the quotes engine to make it easier for me to categorize stuff
  • Write own referrer script which, for example, saves the query string from search engine referrals
  • Publish some more stuff under writings. Sort out some sort of license statement on that page.
  • Update the login refresh script so that I don't have to remember to keep logging in before I can change the currents
  • Finish the bookmarks functionality - allow subcategories, edit/delete, move to "Links" folder
  • Publish quotes engine as open source
  • Publish bookmarks engine as open source

The main reason that I'm considering the re-write is that I really want to get away from my Windows dependence. I've got a Linux install on my laptop now which I'm not using much because I can't use it to work on my website at all. More than that, I'm seriously considering switching to a Mac when I get my next laptop (which I expect to be towards the end of this year) but I've got to be able to work on my site on it otherwise there's almost no point. The site code is all in ASP with VBscript, so TBH it probably is Windows only. It would be good to expand my web technologies range to include some non-proprietary languages though, I suppose, it just seems like a lot of work.

Of course, the fact that I'm seriously considering switching to Mac is one of the other reasons that I haven't ended up using Linux very much. The learning curve is pretty steep and if I'm just going to switch away from it in a years time I'm not sure it's worth it. My other gripe, which I guess some of you might be able to help me out with, is that I don't like my current email client - Sylpheed. It's quite good, but I hate the fact that you can't seem to turn off the preview pane and I seem to remember it taking more clicks than I liked to open an email in a new window (or possibly you had to do it from the mouse, not the keyboard) which is my preferred way of reading email. I like the Outlook interface for email - can anyone recommend something for Debian with a similar mechanic?

[identity profile] shepline.livejournal.com 2004-01-12 06:59 am (UTC)(link)
My Dad swears by Eudora for his mail (I believe this is normal for scientists/academics).

I would be interested in the Quotes engine once you've publish it - any plans to publish the Currents/Previously engine like you did for the Gallery?

The other thing I'm really jealous about your site with is the way that you've integrated this journal so completely into your site (did you say it was done by ASP?). I'd love to do that too, but it would require me:

  • understanding how to create/modify S2 styles and I just can't get my head round that

  • learning enough about ASP to integrate it - I'm okay modifying things and tinkering at the edges, but from scratch...? *shivers*

[identity profile] tinyjo.livejournal.com 2004-01-12 07:13 am (UTC)(link)
I can't stand Eudora - I like being able to have lots of emails open in different windows if I need to.

re Currents, that's a good point actually - the intention is to publish all of my tools from this site eventually, so I'll add it to the list. I will, of course, announce them here when I do publish them.

The integration is a combo of an S2 style and ASP work, yes :) I don't mind trying to help out if you can come to me with specific questions - I'm not very good at being general.

As a starting point, you need your S2 style. You want this to duplicate the layout you want on your site (the comments pages, for example, will still be pulled directly from LJ). What you should be aiming for is that all the head code and bits that you don't want in your embedded journal should be in the Page::Print function and the bits you actually do want to embed for each page should be in the Page::print_body function (you can, and probably will, have specific ones of these for each view).

Hmmm. That may or may not make any sense. If I'm actually in one evening, we could get together on IM and I'll try to help you out if you like and you can always email questions.