20:02:05: Eraser_: EDEV: does the new nodes nodelet now double up peoples new writeups? like if they sumbit 2 in a row, or in rapid succession?
20:08:10: conform: EDEV: woah, yeah. weird.
22:17:20: atesh: EDEV: Okay.. I was thinking about this.. Some people use their Personal Nodelet for a basic customized Vitals, so shouldn't we make it easier on them, allowing them to move links up and down on the nodelet?
22:26:17: JayBonci: EDEV: Speaking of the Personal Nodelet, what's with the limit on the number of nodes you can have there. I use it as a checklist of things i need to do, respond to, writeup, etc... why can I only have like ten things?
22:26:42: JayBonci: EDEV: Maybe a low level power to double the number of items you can keep in there? Just a thought...
22:28:18: JerboaKolinowski: EDEV: and another thing..:) when you visit a node that's already in your personals, E2 knows not to ask if you want to add it, so why not ask if you want to remove it?
22:38:02: JerboaKolinowski: EDEV: Oops! E2 doesn't know - I was thinking of bookmarks. But it could do a comparison, I suppose....
22:41:38: atesh: EDEV: But the idea would actually work well with having a remove bookmark instead of add bookmark. And I'm sure that adding in code comparison for the personal nodelet would work well, too.
22:42:32: JerboaKolinowski: EDEV: Hmm. It's puzzling that addpersonalnodelet takes a node_id, but the links in the actual nodelet come up as links to node titles, rather than ids. Isn't this a little inefficient?
23:01:31: JayBonci: EDEV: JK: I'm kinda puzzled as to why you'd think that's at all inefficient. Mapping ids to names == really easy. ids are a primary key in the database. Mapping names to ids == hard. We'd need to SQLSelect to find them... It's the way to do it..
23:06:43: JerboaKolinowski: EDEV: JayBonci Indeed, and we map names to ids every time someone clicks on a link in personals. I'm assuming that clicking is more frequent than adding, so perhaps the node_id should be stored, too, since we have it when we are in addtopersonal.
23:08:50: JerboaKolinowski: EDEV: admittedly, the ramifications for the present code are not straightforward :)
23:29:41: JerboaKolinowski: EDEV: Well, I've modified the existing code for personals along the above lines, but I can't test it! Anyone interested / what should I do?
previous day | next day
full month | entire archive