Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I'm trying to make it so that a player can ASK [PERSON] ABOUT [TOPIC], TELL [PERSON] ABOUT [TOPIC], or THINK ABOUT [TOPIC] in Inform 7. I started like this for modeling THINK ABOUT [TOPIC]:
A topic is a kind of thing. A topic is either known or unknown. A topic is usually unknown.
Pondering is an action applying to one thing. Understand "ponder [something]" as pondering. Understand "think about [something]" as pondering.
Carry out pondering:
If the noun is a topic, say "[description of noun]" instead.
But then I realized that I'd probably want the same mechanism to be used for thinking about both abstract topics and concrete things. I've also got the problem that unless the topic is a concrete thing that is present in the room, Inform considers it out of scope. I don't know how to solve that. At the same time, I do want most topic to start out as out of scope, but come into scope as they are suggested by previous topics.
In thinking about what I'm trying to accomplish, it seems rather similar to the system used by Emily Short et. al. in Alabaster. The source imports an extension called Threaded Conversation, but I don't see where that comes from.
In short, I need a conversation system which:
allows discussion of both objects and abstract concepts,
allows discussion of things not present,
restricts discussion to things the player is aware of, and
allows new topics to be brought into scope by other topics.
Your best bet at this point probably is to adapt Eric Eve's Conversation Package to your needs; it's found here: http://inform7.com/extensions/Eric%20Eve/Conversation%20Package/index.html.
The system Alabaster uses isn't yet released.
(also, it's pretty awesome to see I7 questions here, but if you have pressing technical questions you're probably better off at the Intfiction forums).
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Recently, I was reading a paper whose name is "On the Effectiveness of Concern Metrics to Detect Code Smells: An Empirical Study".
I come from a non-English speaking country, and I can not quite understand what Concern Metrics means in the field of software engineering.
It is not referring to the relationship between objects?
I have some understanding of java and c #, some people may be able to use java to give me an example.
Thanks.
Like it is said in the paper's abstract: "While traditional metrics quantify properties of software modules, concern metrics quantify concern properties, such as scattering and tangling." Are you familiar to the cross-cutting concern concept? This question provides examples of concerns: Cross cutting concern example Try to read papers on aspect-oriented programming (AOP) to grasp more concepts in order to understand better the relationship between concerns and code. The metrics are attempts to quantify, for instance, the amount of scatterness of a concern (e.g. login) over the source code.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
Recently, I am working on my course project, the topic is the creation of a new hybrid software process model by integrating Scrum and Team Software Process (TSP). Integration of these two models will be based on the SEMAT Essence Kernel Framework.
I am wondering:
Which steps should be followed for this integration (like
determination of the roles and artifacts in these two models)?
What should be the criteria to decide on good sides?
Thanks in advance!
The best way I think I can answer this question is by quoting the agile manifesto.
"Individuals and interactions over processes and tools"
Agile is about people, teamwork and craftsmanship. It's about involving the customer closely to figure out what really is needed - and delivering that, in small increments of working software. Agile is inspect and adapt, based on experimental delivery and the feedback and evidence that comes from that.
Trust yourself. Work closely together and you can do this. The best learning often comes from doing. :)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have done some searching around the Internet and SO looking for an introduction or analysis of what makes data.table so fast, but I've only found a lot of (very helpful) manuals, no breakdown of what goes into the programming. (I am more or less completely floored that I can't locate a published paper for data.table, not even something from JStatSoft.)
I've had an algorithms class so I know about sorts and linked lists and binary trees and such, but I don't want to make any amateur guesses (especially when I go to explain to academic people why it's a good idea to use it). Can anyone offer a short, topical summary with references? This question references a slide presentation which is cool, but the info comes in pieces (and even the documentation for, say, setkey() doesn't cite a data.table reference, but goes to Wikipedia).
What I am looking for is something that is both not the source code and not a list of Wikipedia topics, but an ideally "official", sourced answer (thus making it canonical, which could help a lot with all the questions orbiting around this topic).
(It would be great if there was a technical paper out there I could cite for this (the citation() for data.table is just the manual, but of course it's not directly relevant to the question as far as SO is concerned.)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am going to develop a journal system which has paper submission and review actions with evalution forms,something like OJS system. I want to use drupal for it but I am not sure if it is a good choice.
Does Drupal have ability to create such applications ?
It is a very generic question. To answer some part:
Drupal can be customized and used for a lot of projects, thanks to the powerful community and module developers.
Let me give a glimpse of possibilities, you can find the rest:
Each paper can be a content type. Each user can have specific roles and permissions (eg. publisher, editor, reviewer etc) who are allowed to do specifically what you allow them to do. They can apply for higher roles as well.
Each review process can be captured and maintained using workflow module. There are plenty of tutorials for that.
List of articles can be shown with various properties and filters using views. They can be shown in various regions of a theme you select or make of your own (or customize).
The community can be built using forums.
In short there are thousands of possible ways you can make this. But one note from personal experience: sometimes you will find extremely tough things to be done in simple ways, while simple things will take time. This is mostly because like all systems, it takes a bit of time to get used to with the drupal api.
Best of luck!
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
How many people actually write an SDD document before writing a single line of code?
How do you handle large CSCI's?
What standard do you use for SDD content?
What tailoring have you done?
I certainly have. Historically and on recent projects.
Years ago I worked in organisations where templates were everything.
Then I worked other places where the templates were looser or non-existent or didn't fit the projects I was working on.
Now the content of the software design is pretty much governed by what I need to describe to get the idea across to the audience.
"before writing a single line of code" there wouldn't be a a lot of detail. The documents I produce before I start coding are meant to get the idea of what we need to build across to the affected teams and senior management so they introduce high level architecture, functionality, technologies, risks and scope. Those last two are really important. The rest is to show other teams where you need to interface with them and to leave managers with a lingering notion that cool stuff is happening.
Most big software companies have their own practices. For example Motorola has detailed documentation for every aspect of software development process. There are standard templates for each type of documents. Having strict standards allows effectively maintain huge number of documents and integrate it with different tools. Each document obtains tracking number from special document-tracking system. They even have system (last time I seen it was in stage of early development) for automatically requirements tracking - you can say which line of code relate to given requirement\design guideline.
I would suppose that most people who write SDD documents and use terminology like CSCI have to be using a specific software development methodology and most likely are working for some serious government customer. They usually tend to take their preparations quite seriously and the documents are ready and approved before any development starts.
In an Agile process the development and the design document could be developed in parallel. It means that there will be plenty of refactoring to be done but it usually delivers very good results in the end.
In more formal processes (like RUP) a SAD document is mostly created during the elaboration/prototyping phase based on the team research.