-
-
-
-
-
-
-
-
You'll probably notice that quite a few things feel inspired by Twitter, as that kind of layout is basically where a lot of user expectation is.
This is the first thing I noticed, particularly the way most elements are boxed up — most with a small border radius. (the main container, the main nav, the user information (when viewing on a larger screen)).
Were these elements put in boxes for UX clarity or because you intend to allow forums to add their own background images behind the main content/header?
There's also a lot of mid grey which to my eyes reduces contrast and clarity throughout — particularly in the drag to upload area when writing a post.
I did a quick mock of removing a lot of the boxes (attached), but it would obviously have implications on the main content background and header background choices.
I'd also be interested to hear your thinking on the start a conversation/event placement. On a smaller screen (<990px) they disappear into the sidebar and it becomes a little unclear on how to find the buttons again. Presumably mobile users don't create as many threads, but 990px is still quite large.
On the whole, it functions and looks great. Really good job!
-
Very true.
I guess to me, that's the distinction between an application and a more traditional published web page. History in an application isn't necessarily tied to the state, it's often just the view or frame: e.g. iPhone mail, an email's state is updated when returning to the list view.
I guess it's also similar to a browser's :visited CSS.
(Just thinking out loud here.)
-
Think I may have just misunderstood the WebKit page cache / unload event actually.
Yes, hitting the back button and updating that page's state.
More info here: https://www.webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/
-
-
Fungus isn't fixable generally - the fungus actually eats the coating of the lens element.
You can try disassembling it to remove it and hope it hasn't damaged the coating too badly
As to whether it will impact the usage - it depends on which elements have suffered (generally speaking the elements closer to the rear of the lens will have more of an obvious effect on image quality)
Given that its only a 1.8, its probably simplest to pick up a fungus free replacement
It was only a £25 lens. Yeah, probably best to just replace if it seems to affect the image too much.
Thanks! I'll post up some shots with it once developed.
-
-
Okay, Just bought a lovely Olympus OM2n and a couple of lenses. A 28mm and a 50mm.
The 50mm has a lot of noticeable fungus, something I've not had to deal with before. Is this easily fixable, or is it not worth it (the fungus is all the way around the front part of the lens, and a little inside)?
click for bigger image:
-
-
-
-
-
I'm trying to do something similar, so I bought a LaCie 2TB d2 Network drive.
It plugs into the LAN, and i'm accessing it over wifi.Not sure if it's a problem with the LaCie or the wifi, but browsing through it in Finder is painstakingly slow — playing video files from it just about works, but by the time I get to the movies folder, I've all but lost the will to live. Does anybody else have (good) experience of these setups?
Anyway, the LaCie is not working for me, so I'm thinking about using a mac mini (with an extra server-grade HD stuffed into it) to use as a local backup/media fileserver as well as a bit of a web server playground.
Just need to find out the best way to get an SQL, php, python and ruby dev environment up on it. Not sure if I need to go nginx or apache, or both.
Decisions decisions.
-
-
I was originally coming from the "put the thread title in the URL" camp, but given both of your extremely well detailed posts, I completely agree.
VB, do you have a reference in the w3c or similar for resource/query string usage?
Just read through your API.Perhaps the problem I was thinking about was looking at a link to a thread cross posted in another thread. It's often said as ~"see this thread: lfgss.com/thread10023.html".
Perhaps this is more about hinting, inline with the link, about which thread it points to. E.g.:
http://www.lfgss.com/attachment.php?attachmentid=69954&stc=1&d=1372713673
to
http://www.lfgss.com/attachment.php?attachmentid=69955&stc=1&d=1372713673
(quick mockup, but perhaps useful?) It does mean more API calls.
-
Two things that are a most probably quite minor at this time in development, but are really meaningful once you start to use the forum.
- Part feature request, part question:
· Meaningful, human-parsable URIs for threads/pages/microcosms.
· What's the best way of attacking this, what are the problems with it, and is having threads with the same name (and a numbered suffix) a problem, per domain?
(tell me if/why I'm wrong about this, by the way).
- For when sending out subscription-based emails:
· have nice, well-formatted HTML (including images — or quick links to images), with a text-only fallback. (or even better, let the user choose between plain text and HTML).
- Part feature request, part question:
-
-
Do the cambium saddles have a rough texture? Could do without white patches on the arse with jeans!