Also soliciting ideas or requests for A45 if anyone wants to nag me. I
am not sure what I plan to do for A45 yet. The time away sort of made
me forget my intentions.
Would be nice to also have it included in a games file area as well without duplicating the file.
Would be nice to also have it included in a games file area as well without duplicating the file.
Thanks I'll consider how this could best be handled and make a note on
the TODO list. The file areas in general could use a complete revamp to be honest.
They've been mostly unchanged since the 1990s besides adding in the
index file area thing and archive viewer.
Ooh! I wanted to ask if you could jot down in the TODO about finishing file attachments to messages. I see it was *kind of* setup, but it's non-functional.
Ooh! I wanted to ask if you could jot down in the TODO about finishin file attachments to messages. I see it was *kind of* setup, but it's non-functional.
The reason I haven't bothered with that is because no one uses local messages, and echomail doesn't allow file attachments.
The file areas in general could use a complete revamp to be honest. They've been mostly unchanged since the 1990s besides adding in the
index file area thing and archive viewer.
The file areas in general could use a complete revamp to be honest. They've been mostly unchanged since the 1990s besides adding in the index file area thing and archive viewer.
I'd suggest a split window approach to the file lister if you decide to revisit that, since the classic paging lister kind of gets overwhelmed on file bases that can contain hundreds of entries with long descriptions.
For example you could have the file list on one side navigable by
lightbar or type-ahead find while the currently selected file's description is on the other side. That should make it more convenient to browse regardless of description length and give it a more similar feel
to the existing indexed listers.
Its fully thread safe and can scale up as demonstrated by those screen shots of you having like 30+ BINKP session going in MIS back in the day! (Its the identical code being used between fidopoll and mis)
The reason I haven't pushed for it yet is that I want to make sure there aren't other open issues, because I think it could just compound the problems and make it harder to track down a problem...
And if I'm being completely honest about it, the fact that I don't
suffer from the same massive outbound queue like you do probably makes
it easier for me to unintentionally forget about it. Out of sight out
of mind kind of thing.
My thoughts are mostly centered on the fact that we need get to a point where the existing stuff is working well enough that you're comfortable using it reliably. With their being rumors of some transfer issues and possible FLO stuff, I think those need to be confidently addressed first.
Maybe I could make a fidopoll2 kind of thing like I did with MIS a
couple of years ago?
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 16 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 22:20:36 |
| Calls: | 133 |
| Files: | 50,534 |
| D/L today: |
137 files (63,614K bytes) |
| Messages: | 323,396 |