|
A strategy-pattern; implement a serializer for each desired format. Give each one an extension, and have the user choose a serializer using the OpenFileDialog.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Yeah, might do that eventually!
In fact when I read it, it was so obvious that I immediately assimilated your idea!
But I have to say... I didn't think of it before!
|
|
|
|
|
Maps, grids and rich text - looks like a D&D campaign runner
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
"When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey
"just eat it, eat it"."They're out to mold, better eat while you can" -- HobbyProggy
|
|
|
|
|
Damn, you know it now!!
What is your address? For the hitman, you see!
|
|
|
|
|
Oops... I was thinking too to a D&D campaing runner but I'll wait to have experience as a dungeon master before designing it.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
"When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey
"just eat it, eat it"."They're out to mold, better eat while you can" -- HobbyProggy
|
|
|
|
|
Damn, more competition, I should hurry up! :P
I am almost as good as a Javascrip Map editor I found (but on desktop: undo, redo, save, etc.. :P )
getting there....
|
|
|
|
|
There are two questions to ask:
1. Has the text format value over the binary (human reading, simple parsing)?
2. There is any reason not to make public the binary format (binary format will be smaller)?
Around these two questions you have to decide...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
For the binary: Writing the specification will be very tedious.. but sharing and documenting the reading DLLs will be easier and acceptable!
Plus it won't be that famous that it needs official spec.
Text value is only for the benefit of human tinkerer.. might be simpler to .. I dunno.. maybe write some quick script tool to generate dungeon or something....
|
|
|
|
|
Super Lloyd wrote: tool to generate dungeon Old, but good tool...[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
good tool!
|
|
|
|
|
If you have multiple people editing a map at the same time, as long as it's well structured, you could gain some benefits from merge tools that are already available. Binary files you get no such benefit, and it will always be last in wins.
|
|
|
|
|
Maybe...But as I see you never merge files when you work with binary...You merge objects in the memory...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I didn't mean in-app. I was thinking more along the lines of source control and working with contributors in a non-realtime setting.
|
|
|
|
|
Super Lloyd wrote: I am working, albeit very slowly, on my take over the world project.
How is Pinky[^] anyway?
Mongo: Mongo only pawn... in game of life.
|
|
|
|
|
I only know from second hand....
Us, evil genius, are a secretive bunch!
|
|
|
|
|
I'd go binary for large data. If someone cares enough to edit that crap then they'll know enough about how to translate it anyway.
Jeremy Falcon
|
|
|
|
|
Right, indeed!
|
|
|
|
|
Nah, do what Microsoft did. Save everything as XML!
Marc
|
|
|
|
|
Seems like a perfectly logical way to save an image...
="1.0"
<image>
<pixel offset="0">
<byte offset="0">
<bit offset="0">0</bit>
<bit offset="1">1</bit>
<bit offset="2">1</bit>
<bit offset="3">0</bit>
<bit offset="4">1</bit>
<bit offset="5">1</bit>
<bit offset="6">1</bit>
<bit offset="7">0</bit>
</byte>
<byte offset="1">
<bit offset="0">0</bit>
<bit offset="1">1</bit>
<bit offset="2">1</bit>
<bit offset="3">0</bit>
<bit offset="4">1</bit>
<bit offset="5">1</bit>
<bit offset="6">1</bit>
<bit offset="7">0</bit>
</byte>
<byte offset="2">
<bit offset="0">0</bit>
<bit offset="1">1</bit>
<bit offset="2">1</bit>
<bit offset="3">0</bit>
<bit offset="4">1</bit>
<bit offset="5">1</bit>
<bit offset="6">1</bit>
<bit offset="7">0</bit>
</byte>
<byte offset="3">
<bit offset="0">0</bit>
<bit offset="1">1</bit>
<bit offset="2">1</bit>
<bit offset="3">0</bit>
<bit offset="4">1</bit>
<bit offset="5">1</bit>
<bit offset="6">1</bit>
<bit offset="7">0</bit>
</byte>
</pixel>
...
</image>
Jeremy Falcon
|
|
|
|
|
Use power of BSON, Luke!
|
|
|
|
|
I've been researching refresh rate and other display characteristics, thinking another monitor might make a difference.
My take on higher refresh rates (> 60 hz.) is they make a difference for gamers and people watching videos, but i'm not sure they would be any more readable, or less migraine-inducing (during long sessions).
Just curious if anyone else with older/diminishing eyesight here has considered this issue.
thanks, Bill
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
|
|
|
|
|
I think that anything over 100,000hz is going a bit far!
veni bibi saltavi
|
|
|
|
|
It's soooooooooooooooooo refreshing.
|
|
|
|
|
I'm not going to mention what organ this post suggests may be diminishing in capacity
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
|
|
|
|
|
Probably defaulting back to the question: what are you gonna use it for?
For me, I've got pretty bad eyesight buuuut never really had too much of an issue with lower refresh rate screens. They're nice to have to be sure but when I'm working on user input apps which are mostly lots of entry forms or a general intranet which has lots of relatively static content web parts, it's fine.
As you've alluded to though, when I've been working on graphically based bits of work, it's really noticeable what the difference is. And certainly if I'm working on input based on visuals (last one was a point on a map thing) it needed to be quite high for my purposes because I was running through so many different weird scenarios in a short space of time when compared to a regular end user.
Budgetry reasons though, would that be the thing restricting you? I would personally go with higher, just because then you're covered in both scenarios whereas a lower one wouldn't.
|
|
|
|