What's the difference between ArSceneView, ArFragment, and ScenView? I've seen all of these being used in Google's examples for ArCore but I don't understand the difference between them and the interchanging of them in different applications. The websites for each don't provide much information and aren't helpful to a beginner. What general properties are different between these? What should be used when?
Thanks!
Related
I'm studying Swift from an architectural perspective as I believe Swift offers multiple tools to build a house. I understand how arrays, dictionaries, and sets differ in regards to how values are stored however now that I've grasped this concept I'd like to know if they differ in regards to performance? Maybe there are things I haven't thought of but right now I'm thinking I'd choose one of these Swift tools based on how I'd like the information to be regurgitated further down the road in the program. So if there is anything additional I should know about or consider when picking one of these tools, please feel free to comment and I'll research the concepts further.
Thanks in advance.
-a noob
I am doing a project for school and the question says
"Prepare a high-level explanation of the interface for the user. The user is the intended audience of this explanation, so the code is not relevant. "
How do I provide a high level explanation without using some kind of code?
I find that a lot of software is sorely missing "high level explanation". Modern programming languages tend to make the code fairly easy to understand at the microscopic level; and comments on methods and properties in interfaces can help the user with detail about how to use the interface. However, the user needs to first understand the overall domain concepts and design approach before the detailed documentation can be useful. Pulling those concepts out of detail comments and the code can be difficult. High-level explanation can help the user tremendously.
I've searched for at question like this and i dont think there are one.
As the title says... I know there are huge differences between how to do things in (R)UP and in XP as a way of developing systems, but what are the really?
I'm trying to write a nice explanation that i can give to other people so they hopefully easy can understand the differences.
I want to compare the following subjects:
Design
Documentation
Prototyping
User involvement
Usability
Technical quality
Test
I'm not trying to start a discussion, just want to know if you know any good sites that could have the information i'm looking for or if you have a answer for one of the subjects. I have allready written some of it myself but due to the fact that i dont want it to be a subjective comparison, i then ask you.
You might find this useful
XP vs RUP (pdf)
RUP and XP are not mutually exclusive. Comparing the two is like comparing apples and oranges -- you can enjoy both. Many companies following RUP choose to include some or all of XP practices.
For the basics, the wikipedia articles are a good start:
http://en.wikipedia.org/wiki/IBM_Rational_Unified_Process
http://en.wikipedia.org/wiki/Extreme_programming_practices
I'm working on a large search engine system.
However, I'm not familiar with the background.
Where can I find materials about indexing and page ranking?
You can always look at the google research stuff. It is naturally very intense stuff but interesting none the less.
Modern information Retrieval
A very known and a good book that will introduce you to these concepts.
I would like to know which steps and which concepts do you follow when you're starting a web application from scratch.
When you're asked to develop a new web application and the only thing you're told is which features are wanted, how do you do ?
How and in which order do you conceive all the different layers in your application, from the database design to the UI design, without forgetting the back-end ...
Which tools do you use ? which rules do you follow ?
Thanks in advance.
I like to start with a story board. I use mock screens for the examples.
I find this article very resourceful.
Hope it helps :)
Structured process you must know to develope a web appplication
Any answer to this question is exceptionally subjective.
In regard to how and in what order, you can refer to these threads, which are clearly inconclusive:
Which is more important? DB design or coding?
https://stackoverflow.com/questions/329160?sort=votes#sort-top
In regard to the tools, here is a thread:
What do you use for web development and why you think it rocks?
The rules you follow are partially tied to the tools you use, and partially tied to the design you choose. You should have a sense of the benefits and limitations of available frameworks and tools to do what you need done.
In designing the app, you can do as much pre-planning as you feel is necessary to understand the problem (i.e: story-boarding, ui mockups, entity relationship diagramming, functional specifications, etc.). The goal is to know what problems you are solving and what interactions you expect the user to enact on the application, and then use suitable technologies to achieve that goal - optimally in the most efficient and flexible manner possible.
Try to write a bit of a functional specification, just something simple to capture in writing the different functions that the app will have to handle. Once you have this done, you can sit down and work out what framework / language / platform / etc. best suits your needs. At this stage mockups will also help - try to find out exactly what screens you need and what information has to be on each screen - don't worry about the layout, just the necessary information. From there you can go on to coding up each of these screens - make sure that you only provide functionality that is in your design - there's no need to overcomplicate things just because you can.