Folder


Object Hierarchy:

Object hierarchy for Folder

Description:

public class Folder : FileBase

Represents a directory/folder in the project.

Can also represent a project when is_project = true. Projects are folders with is_project = true (no separate Project class).

Project Management

On the daemon,

project_files
and children hold the full project graph (
ollmfilesd/Folder.vala
). The client keeps neither — file lists and path lookups are RPC at the caller ([`2.10.4.9`](../../docs/plans/2.10.4.9-ACTIVE-v2-caller-cutover.md)).

Git Integration

During filesystem scan the daemon discovers repositories and checks ignored paths (

ollmfilesd/Folder.vala
). The UI process does not scan.

Client vs daemon

This file is the **client** Folder (UI process). Scan, DB, and tree build live on the daemon. Methods such as

read_dir
and
load_files_from_db
are not compiled into the client build — see
ollmfilesd/Folder.vala
. At cutover this replaces
libocfiles/Folder.vala
in the app.

No

project_files
or hydrated children on the client.


Namespace: OLLMfiles
Package: ollmchat

Content:

Properties:

Static methods:

Creation methods:

Methods:

Inherited Members:

All known members inherited from class GLib.Object
All known members inherited from interface OLLMrpc.Bin.Serializable