|
Yeah but JSOP still uses IE and he’s armed and angry. We’ve bravely decided to support IE for a little while longer.
cheers
Chris Maunder
|
|
|
|
|
I am pretty sure he uses IE because the Government still uses IE, not because he likes it. John works government contracts, I believe.
|
|
|
|
|
I'm pretty sure he uses it because he likes to ensure I'm not bored.
cheers
Chris Maunder
|
|
|
|
|
dandy72 wrote: I've always been one of those guys for whom IE "just works" Are you saying that IE has the Edge?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
IE has the Edge, but Edge sure doesn't have the...IE?
Ummmm...no, that doesn't work.
|
|
|
|
|
Chris Maunder wrote: Spend the afternoon retro-fitting nice, neat, sensible JavaScript into kindergarten style JavaScript that IE can understand.Repeat.
Let me shorten this for you Chris
- Javascript
|
|
|
|
|
(you don't really have to answer, but I'd like your thoughts)
In all seriousness though, I have what is either
A cool Json library (now supporting JsonPath) with one of the most ambitious demo projects ever built.
Or, a cool Tmdb API access library with multilevel caching with a neat little Json component on the side.
It's the same solution.
Should I present it as two articles, each focusing on the relevant bit - like a Json one, and then a separate one for the Tmdb access api?
Or should I try to roll this whole mess into one article?
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I'd roll them both into one big birthday cake and eat the lot myself, defending it from all others with large sharp implements.
Happy birthday!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
thanks, i think you're suggesting one article.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
No, I'm just firmly in favour of cake.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I was told the cake is a lie
Portal - 'Still Alive' - YouTube[^]
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Yeah - but that wasn't a birthday cake.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yes.
Happy birthday.
|
|
|
|
|
I agree with one or the other or both of your statements.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I don't agree with any of them.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Agreed.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Yes, one big article and happy B-Day
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
I'd do it as two articles, each focusing on the relevant bit. Even though the solution is a single product, there are two distinct topics to cover. Information is more readily absorbed in small chunks, like chocolate.
Will Rogers never met me.
|
|
|
|
|
Happy birthday, and 2 articles please.
/ravi
|
|
|
|
|
Tell me more about this "JsonPath".
Does it require reading an entire Json document into memory at once or can it read a stream an object at a time?
|
|
|
|
|
Full JSON path only works over a loaded document.
However, there is a JsonTextReader that works a lot like XmlReader but it does have extremely fast skip mechanisms, including "SkipToField" that only do a partial parse.
You can use the reader to navigate to the node you want, and then you can call ParseSubtree() to only load that subtree into memory, and then you can use JSON path on that.
The trouble is I didn't implement the JsonPath, someone else did under the MIT license and I'm using it in my code. It's quite cryptic and undocumented so I think i might be able to modify it eventually, but not at the moment. It only works on an in memory model.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I'd be in favor of two articles. One article that goes into all details just might prove to be too much for someone who's only interested in one part or the other. I'd say, write an article that dives into the details of your library, and then the second article (which can link to it) can focus on demonstrating how to use the library in your real-world app.
If I've already your description correctly.
|
|
|
|
|
you got it exactly right. this was my first inclination and i'm inclined to go with it after reading all the comments here.
Thanks for your input.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Cool. I'm looking forward to it them.
|
|
|
|
|
I'd start writing about one of them and then see if the second flows nicely into that or requires a second artyicle.
GHood kluck, I'll be waiting to read it or them!
CQ de W5ALT
Walt Fair, Jr.PhD P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|