• Advertisement


  • Content count

  • Joined

  • Last visited

Community Reputation

126 Neutral

About Liguria

  • Rank

Personal Information

  • Interests
  1. Hierarchical Data in a Web Application

    Wow, that escalated quickly! Good stuff! I'm very glad to hear it made such an incredibly positive turn. And yes, with that many users and data permutations you'll want to seriously rethink your data structures and representation. I wish you all the best and hope it'll continue growing steadily!
  2. Hierarchical Data in a Web Application

    There are generally 2 very good reasons to use JSON instead of XML when dealing with (client-side) web applications: JSON stands for JavaScript Object Notation and as the name implies, it's a direct relative of JavaScript and therefore very suitable and easy to deal with in JavaScript code. It's a lot less verbose than XML, while still human readable (all the opening and closing tags required for valid XML take up a lot of space while not necessarily offering much benefit) . Depending on how much data we're talking about, that can make quite the difference in bandwidth requirements for your application (number of bytes being transferred over the wire to make your application work). Creating an 'output generator' that processes your data and outputs it to either XML, JSON or code (e.g. JavaScript) is definitely worth the effort if you expect you'll have to do that more than a couple of times in the future. It's also a nice exercise if you've never created a 'data processor' like that before.
  3. Hierarchical Data in a Web Application

    How are you generating the XML at the moment? I sure hope you are generating it in an automated way. If not, I strongly suggest you do so because manually decorating data so it's valid XML will become old real fast. You can easily modify your XML generation code/logic to generate JSON instead. Or even better, just output straight JavaScript that creates and populates an object immediately. No need for parsing later on. As mentioned before, you can easily put that generated code/data in its own separate .js file and include that in your HTML page as you would with any other .js file.
  4. Quadtrees, Octrees, BSP Trees, etc. are commonly known as 'Spatial Partitioning' or 'Spatial Subdivision' methods.
  5. Self-hosting the Epoch Compiler: Day Three

    Man, these 'captain's log book' style of entries are among the most interesting I have read so far.   Even though it seems you're not getting a whole lot of feedback/comments on the Day One/Two/Three/Etc... entries, please DO keep posting them.    Very, very entertaining!!   Oh, and good luck fixing and perfecting your compiler-compiler of course :)
  6.   I understand that, which is why I tried to point out that in your box-art it's spelled wrongly as 'Jericheo'.
  7. Looks nice overall.   I have one point of critique though: There's a spelling error in the logo (most prominently visible in the box-art). Unless you misspelled the protagonist's name wrong everywhere else (which seems unlikely), I don't think it should be 'Jericheo'.   Otherwise, good luck with the project!
  8. Plith's gameplay video

    Your game looks very interesting. It makes me think of a very nice twist between Tetris and Four in a Row. Keep up the good work and finish strong! Liguria
  9. How many people have bailed on Gamedev.net?

    [quote name='Waaayoff' timestamp='1299586057' post='4783078'] [quote name='SuperVGA' timestamp='1299585003' post='4783076'] I visited several times a day before the makeover. Now it's once or twice a week. The new layout simply annoys me. Can't really put a finger on why, but gamedev.net feels more dead now. Wish it would be changed back. [/quote] I know what you mean.. i loved the old design.. this one is just plain weird. It makes me feel like i'm browsing a social network website. [/quote] Same here. It doesn't feel like GameDev.net anymore. It doesn't work smoothly enough to really enjoy visiting. That plus the fact that the last few active threads are not shown at the top of the page is just a shame.
  10. A quick topic to say thanks...

    I congratulate you sincerely. Well done mate! So you must be the guy on the right of the screen: [url="http://www.youtube.com/watch?v=3TjbL5jrpQA"]BAFTA Interview[/url]
  11. Still looking for game engine

    Sorry for ignoring the DirectX11 requirement for now, but why would you want to pay for an engine? There's plenty of freely available engines/game-kits available (Unity, Unreal) that will allow you to do anything you can think of, if you have the creativity in you (that you would need even if you pay for an engine). I suggest you give it a try with one of those free engines first, before paying a lot of money and get disappointed soon. Do you have experience in game making? (you say you're retired, but not what from..)
  12. polar01, an octree is one of the most useful spatial subdivison method that I ever implemented. Even/especially with millions of polygons you get good results, depending on your configuration. (disclaimer: I'm not an expert on spatial subdivision algorithms!) Also moving entities are rather easily moved between nodes in an octree. There's are lot of information available all around the net about octrees. I'd suggest you have a look at that. You may even come up with a hybrid solution, mixing several methods. Don't restrict yourself to a single point of view! (that's the good thing being a programmer; you've got all the freedom :) )
  13. polar01, you were just a little to fast for me with your reply :) What kind of rendering are you doing? Are you implementing a software renderer? Some extra information might help to determine what could be the quickest solution for you.
  14. Just to clarify (I think we might have a slight misunderstanding due to terminology; which is my fault I'm pretty sure): In the second solution I proposed, I'm talking about casting a 3D ray. When I wrote screen pixel I actually meant a point on the Z==0 plane which relates to a screen pixel. When you have your calculations right and, more important, consistent, inaccuracy shouldn't be a problem, not even for objects that are far away. I never had trouble with it, as far as I can remember. The first solution is definitely the most straight forward and easiest to implement solution if you're only interested in picking top-most objects/entities. That is, if you don't mind having an extra buffer eating up some memory and losing some cycles during rendering (since this would be for an editor-type of application, I guess that shouldn't be an issue).
  15. Two relatively easy solutions: 1) The easiest and fastest way to do it is keeping a buffer of identifiers, which has the same dimensions as your projection buffer. This buffer would be filled with 'identifiers' (pointers (i.e. addresses), for example) by your rendering algorithm, depending on the 'selection mode' (vertex, edge, face, etc). Now you can simply read out the 'identifier' under the mouse cursor to know which 'object' was selected/picked. 2) Another option is to cast a ray from your viewpoint through a 'pixel' on screen and use some intersection math (again, depending on the 'selection mode') to determine what (if any) was selected/picked. I implemented both solutions several times thoughout the years in my software rasterizers. They are really quite simple to get working.
  • Advertisement