Donate | Contact | Search
'searching', queries, filtering (see all those elsewhere 4 other notes also?) (main ?)
- ocode: OBJECTS and manipulation by classes etc (with code) sch terms: scripting om code main
- and in this?: consider if relevant yet: ANYTHING THAT BELONGS TO A CLASS has to have ability to be managed by query OR category? (also noted under queries)
- 'searching', queries, filtering (see all those elsewhere 4 other notes also?)
- now
- use cases
- related to 'searching'?:
- could also use similar means to sharing, in the part where you just go traverse the model, and having found an entity you indicate it w/ a keystroke
- (reserve one, removed from the current long list of letters?), and it unwinds all the way back?
- by fields, or man'ly & save/del the search info, as entities, or? in a group? w/ a 'has' rel on the RTG class, like 'entity'?
- maybe just break it out of the (or modify?) obj chooser to
- make the sch results show '>>', '>' as needed (or do they alr?)
- if group is limited by class, make the search be, also?
Copyright 2015-2024 Luke A. Call | OM Home
Contact (won't put you on a mailing list): comments@onemodel.org (but for replies see the mailing lists)
(Content generated selectively from a OneModel instance.)