oraclechunk3.json

{"QuestionId": 1597932, "AnswerCount": 1, "Tags": "<css><flash><dhtml><lightbox>", "CreationDate": "2009-10-20T23:40:33.563", "AcceptedAnswerId": "1597983", "Title": "Forcing lightbox/dhtml over flash", "Body": "<p>I have read a lot of posts about how you can force lightbox (or other dhtml things) above flash by modifying the embed-tag with wmode=\"opaque\". Just modifying the z-index of lightbox (or whatever else you want above the flash) simply is not enough.</p>\n\n<p>But what if you cannot control the embed-tag? </p>\n\n<p>I am working with a client that has a banner-system, where I do not have control of the embed tag... </p>\n\n<p>Is there really nothing I can do to force the html over the flash-item, that does not require manipulating the embedding of the flash?</p>\n", "Lable": "No"}
{"QuestionId": 1985734, "AnswerCount": 4, "Tags": "<delphi><form-designer>", "CreationDate": "2009-12-31T14:59:49.797", "AcceptedAnswerId": "1985868", "Title": "How to implement a winform dialog in Delphi without IDE?", "Body": "<p>I don't have the Delphi IDE installed. Can I still design forms?</p>\n", "Lable": "No"}
{"QuestionId": 2216392, "AnswerCount": 7, "Tags": "<unit-testing>", "CreationDate": "2010-02-07T08:18:36.810", "AcceptedAnswerId": "2216807", "Title": "How to write unit test and not get bored in development of FOSS project?", "Body": "<p>I'm developing cross-platform project that would support :</p>\n\n<ul>\n<li>Four C++ compilers - GCC, MSVC, SunStudio, Intel,</li>\n<li>Five Operating Systems: Linux, OpenSolaris, FreeBSD, Windows, Mac OS X.</li>\n</ul>\n\n<p>I totally understand that without proper unit testing there is no chance to perform proper QA on all these platforms.</p>\n\n<p>However, as you all know writing unit tests is extremely boring and slow down development process (because it is boring and development of FOSS software shouldn't be such)</p>\n\n<p>How do you manage to write good unit-testing code and not stop writing code.</p>\n\n<p>If you at least get salary for this, you can say - at least I get something for this, but if you don't, this is much harder!</p>\n\n<p><strong>Clarification:</strong></p>\n\n<p>I understand that TDD should be the key, but TDD has following very strict restrictions:</p>\n\n<ol>\n<li>You have exact specifications.</li>\n<li>You have fully defined API.</li>\n</ol>\n\n<p>This is true for project that is developed in customer-provider style, but it can't be done for project that <strong>evolves</strong>.</p>\n\n<p>Sometimes to decide what feature do I need, I have to create something and understand if it works well, if API is suitable and helps me or it is ugly and does not satisfy me.</p>\n\n<p>I see the development process more like evolution, less development according to specifications. Because when I begin implementing some feature, sometimes I do not know if\nit would work well and what model would it use.</p>\n\n<p>This is quite different style of development that contradicts TDD.</p>\n\n<p>On the other hand, support of wide range of systems requires unit tests to make sure that\nexisting code works on various platform and if I want to support new one I only need to\ncompile the code and run tests.</p>\n", "Lable": "No"}