Project specific coding conventions

关注

转载最新推荐文章于 2026-09-01 15:13:56 发布 1.1k 阅读 AI 写同款· GEO 优化 ›

AI视频生成技术：从扩散模型到游戏剧情二创实践扩散模型作为当前AI内容生成的核心技术，通过逐步去噪的过程实现从文本到视频的转换。其技术原理基于深度学习框架，能够理解自然语言描述并生成连贯的视觉内容。在工程实践中，这种技术显著降低了视频制作门槛，使创作者能够快速将文字剧本转化为动态视频。特别是在游戏剧情二次创作领域，AI视频生成技术展现出巨大价值，能够保持角色形象一致性并处理复杂场景转换。以《崩坏：星穹铁道》为例，本地部署的AI视频生成工具支持文生视频和图生视频两种模式，通过WebUI或API接口实现批量任务处理，为游戏爱好者提供了便捷的剧情可视化解决方阅读详情

Project specific coding conventions

1. Brackets

All brackets (class, method, if, try, etc) must begin and end on a new line. Example :

public class SomeClass
{
    public void someMethod()
    {
        if (xxx)
        {
        }
    }
}

Brackets are mandatory, even for single line statements !

// Incorrect
if (expression)
    // some code

// Correct
if (expression)
{
    // some code
}

2. Blank Spaces

keywords followed by a parenthesis should be separated by a space. Example :

while (true)
{
    // some code
}

Blank space should appear after commas in argument lists. Binary operators should be separated from their operands by spaces :

a += c + d;
a = (a + b) / (c * d);

while (d++ = s++)
{
    n++;
}

printSize("size is " + foo + "/n");

3. Indentations

4 spaces. NO tabs . Period. We understand that a lot of you like to use tabs, but the fact of the matter is that in a distributed development environment, when the cvs commit messages get sent to a mailing list, they are almost impossible to read if you use tabs.

4. Comments

Javadoc SHOULD exist on all your class members (methods + class variables), including the private ones. Also, if you are working on existing code and there currently isn't a javadoc for that method/class/variable or whatever, then you should contribute and add it. This will improve the project as a whole.

Also add code comments when you think it's necessary (like assumptions), especially when the code is not obvious.

5. Author references

If you contribute to a file (code or documentation), add yourself to the top of the file (below the existing authors). For java files the preferred Javadoc format is:

@author devnickname

7. Class variables

Class variables should not have any prefix and must be referenced using the this object. Example :

public class SomeClass
{
    private String someString;
[...]
    public void someMethod()
    {
        logger.debug("Value = " + this.someString);
    }
}

8. Parameter names

Method parameters should not have any prefix. For example :

public void someMethod(String className)
{
}

9. Line length

Avoid lines longer than 120 characters for Code, comments, ...

10. Versioning

All .java files should have a @version tag like the one below.

@version $Revision$ ($Author$)

11. Qualified imports

All import statements should containing the full class name of classes to import and should not use the "*" notation :

An example :

// Correct
import java.util.Date;
import java.net.HttpURLConnection;

// Not correct
import java.util.*;
import java.net.*;

收录于

Java技术类

标签

#javadoc #variables #import #class #comments

AI角色扮演深度指南：从提示工程到实战调校，打造沉浸式对话体验提示工程（Prompt Engineering）是引导大语言模型（LLM）生成高质量、定向输出的核心技术。其原理在于通过精心设计的文本指令，为模型设定清晰的上下文、角色与任务边界，从而将通用的文本生成能力转化为特定场景下的解决方案。这项技术的核心价值在于极大地提升了人机交互的深度与效率，使AI不再是简单的问答工具，而是能扮演特定角色、进行复杂推理的协作伙伴。在应用层面，提示工程广泛应用于智能客服、内容创作、模拟训练、产品设计等多个领域，尤其在构建沉浸式、可控的AI角色扮演对话系统中发挥着关键作用。本文聚焦于阅读详情

Project specific coding conventions

Project specific coding conventions

1. Brackets

2. Blank Spaces

3. Indentations

4. Comments

5. Author references

7. Class variables

8. Parameter names

9. Line length

10. Versioning

11. Qualified imports

相关推荐