|
| 1 | +# ObjectUI vs Shadcn: Component Mapping Guide |
| 2 | + |
| 3 | +**Quick Reference**: Understanding the relationship between ObjectUI Renderer and Shadcn UI components |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## Conceptual Distinction |
| 8 | + |
| 9 | +### Shadcn UI Components |
| 10 | +- 📦 **Pure UI Component Library** |
| 11 | +- 🎨 Built on Radix UI + Tailwind CSS |
| 12 | +- 💻 Requires writing React code |
| 13 | +- 🔧 Controlled via Props |
| 14 | + |
| 15 | +### ObjectUI Renderer |
| 16 | +- 🔄 **Schema Interpreter** |
| 17 | +- 📋 JSON configuration-driven |
| 18 | +- 🚀 Zero-code usage |
| 19 | +- 🔗 Automatic data binding and validation |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +## One-to-One Mapping |
| 24 | + |
| 25 | +| Shadcn UI | ObjectUI Renderer | Enhanced Features | |
| 26 | +|-----------|---------------|---------| |
| 27 | +| `<Input />` | `{ type: "input" }` | ✅ Expressions, ✅ Validation, ✅ Data Binding | |
| 28 | +| `<Button />` | `{ type: "button" }` | ✅ Action Mapping, ✅ Loading States | |
| 29 | +| `<Select />` | `{ type: "select" }` | ✅ Dynamic Options, ✅ Remote Search | |
| 30 | +| `<Dialog />` | `{ type: "dialog" }` | ✅ Conditional Display, ✅ Form Integration | |
| 31 | +| `<Table />` | `{ type: "table" }` | ✅ Basic Table Rendering | |
| 32 | +| `<Card />` | `{ type: "card" }` | ✅ Dynamic Content, ✅ Action Buttons | |
| 33 | +| `<Form />` | `{ type: "form" }` | ✅ Validation Engine, ✅ Submit Handling | |
| 34 | +| `<Tabs />` | `{ type: "tabs" }` | ✅ Dynamic Tabs, ✅ Lazy Loading | |
| 35 | +| `<Badge />` | `{ type: "badge" }` | ✅ Status Mapping, ✅ Color Rules | |
| 36 | +| `<Alert />` | `{ type: "alert" }` | ✅ Conditional Display, ✅ Auto-dismiss | |
| 37 | + |
| 38 | +--- |
| 39 | + |
| 40 | +## ObjectUI Exclusive Components |
| 41 | + |
| 42 | +These components have no direct Shadcn counterparts and are advanced business components unique to ObjectUI: |
| 43 | + |
| 44 | +| Component | Type | Purpose | |
| 45 | +|------|------|------| |
| 46 | +| **data-table** | Complex Component | Advanced table with sorting/filtering/pagination | |
| 47 | +| **timeline** | Complex Component | Timeline/Gantt chart | |
| 48 | +| **filter-builder** | Complex Component | Visual query builder | |
| 49 | +| **chatbot** | Complex Component | Chatbot interface | |
| 50 | +| **tree-view** | Data Display | Tree structure | |
| 51 | +| **statistic** | Data Display | Statistical metric cards | |
| 52 | + |
| 53 | +--- |
| 54 | + |
| 55 | +## Usage Comparison |
| 56 | + |
| 57 | +### Scenario 1: Simple Form |
| 58 | + |
| 59 | +#### Shadcn Approach (React Code) |
| 60 | +```tsx |
| 61 | +import { Input } from '@/ui/input'; |
| 62 | +import { Button } from '@/ui/button'; |
| 63 | + |
| 64 | +function LoginForm() { |
| 65 | + const [email, setEmail] = useState(''); |
| 66 | + const [password, setPassword] = useState(''); |
| 67 | + |
| 68 | + const handleSubmit = async (e) => { |
| 69 | + e.preventDefault(); |
| 70 | + await fetch('/api/login', { |
| 71 | + method: 'POST', |
| 72 | + body: JSON.stringify({ email, password }) |
| 73 | + }); |
| 74 | + }; |
| 75 | + |
| 76 | + return ( |
| 77 | + <form onSubmit={handleSubmit}> |
| 78 | + <Input |
| 79 | + value={email} |
| 80 | + onChange={e => setEmail(e.target.value)} |
| 81 | + placeholder="Email" |
| 82 | + /> |
| 83 | + <Input |
| 84 | + type="password" |
| 85 | + value={password} |
| 86 | + onChange={e => setPassword(e.target.value)} |
| 87 | + placeholder="Password" |
| 88 | + /> |
| 89 | + <Button type="submit">Login</Button> |
| 90 | + </form> |
| 91 | + ); |
| 92 | +} |
| 93 | +``` |
| 94 | + |
| 95 | +#### ObjectUI Approach (JSON Schema) |
| 96 | +```json |
| 97 | +{ |
| 98 | + "type": "form", |
| 99 | + "api": "/api/login", |
| 100 | + "fields": [ |
| 101 | + { |
| 102 | + "name": "email", |
| 103 | + "type": "input", |
| 104 | + "inputType": "email", |
| 105 | + "placeholder": "Email", |
| 106 | + "required": true |
| 107 | + }, |
| 108 | + { |
| 109 | + "name": "password", |
| 110 | + "type": "input", |
| 111 | + "inputType": "password", |
| 112 | + "placeholder": "Password", |
| 113 | + "required": true |
| 114 | + } |
| 115 | + ], |
| 116 | + "actions": [ |
| 117 | + { |
| 118 | + "type": "button", |
| 119 | + "label": "Login", |
| 120 | + "actionType": "submit" |
| 121 | + } |
| 122 | + ] |
| 123 | +} |
| 124 | +``` |
| 125 | + |
| 126 | +### Scenario 2: Data Table |
| 127 | + |
| 128 | +#### Shadcn Approach |
| 129 | +```tsx |
| 130 | +import { Table } from '@/ui/table'; |
| 131 | + |
| 132 | +function UserTable() { |
| 133 | + const [users, setUsers] = useState([]); |
| 134 | + const [page, setPage] = useState(1); |
| 135 | + const [sort, setSort] = useState('name'); |
| 136 | + |
| 137 | + useEffect(() => { |
| 138 | + fetchUsers(page, sort).then(setUsers); |
| 139 | + }, [page, sort]); |
| 140 | + |
| 141 | + return ( |
| 142 | + <div> |
| 143 | + <Table> |
| 144 | + <TableHeader> |
| 145 | + <TableRow> |
| 146 | + <TableHead onClick={() => setSort('name')}>Name</TableHead> |
| 147 | + <TableHead onClick={() => setSort('email')}>Email</TableHead> |
| 148 | + </TableRow> |
| 149 | + </TableHeader> |
| 150 | + <TableBody> |
| 151 | + {users.map(user => ( |
| 152 | + <TableRow key={user.id}> |
| 153 | + <TableCell>{user.name}</TableCell> |
| 154 | + <TableCell>{user.email}</TableCell> |
| 155 | + </TableRow> |
| 156 | + ))} |
| 157 | + </TableBody> |
| 158 | + </Table> |
| 159 | + <Pagination page={page} onChange={setPage} /> |
| 160 | + </div> |
| 161 | + ); |
| 162 | +} |
| 163 | +``` |
| 164 | + |
| 165 | +#### ObjectUI Approach |
| 166 | +```json |
| 167 | +{ |
| 168 | + "type": "data-table", |
| 169 | + "api": "/api/users", |
| 170 | + "columns": [ |
| 171 | + { |
| 172 | + "name": "name", |
| 173 | + "label": "Name", |
| 174 | + "sortable": true |
| 175 | + }, |
| 176 | + { |
| 177 | + "name": "email", |
| 178 | + "label": "Email", |
| 179 | + "sortable": true |
| 180 | + } |
| 181 | + ], |
| 182 | + "pagination": { |
| 183 | + "pageSize": 20 |
| 184 | + } |
| 185 | +} |
| 186 | +``` |
| 187 | + |
| 188 | +--- |
| 189 | + |
| 190 | +## Selection Guide |
| 191 | + |
| 192 | +### Use Shadcn UI (Direct Native Components) |
| 193 | +✅ Highly customized interaction logic required |
| 194 | +✅ Complex component behavior difficult to express in Schema |
| 195 | +✅ Performance-critical optimization (avoid Schema parsing overhead) |
| 196 | +✅ Existing large React component codebase |
| 197 | + |
| 198 | +### Use ObjectUI Renderer (Recommended) |
| 199 | +✅ Rapidly build data management interfaces |
| 200 | +✅ Configuration-driven, easy to maintain |
| 201 | +✅ Dynamic UI required (fetch configuration from server) |
| 202 | +✅ Low-code/No-code platforms |
| 203 | +✅ AI-generated UI |
| 204 | + |
| 205 | +--- |
| 206 | + |
| 207 | +## Hybrid Approach |
| 208 | + |
| 209 | +ObjectUI supports embedding custom React components within Schema: |
| 210 | + |
| 211 | +```json |
| 212 | +{ |
| 213 | + "type": "page", |
| 214 | + "body": [ |
| 215 | + { |
| 216 | + "type": "card", |
| 217 | + "title": "User Statistics", |
| 218 | + "body": { |
| 219 | + "type": "custom", |
| 220 | + "component": "CustomChart", |
| 221 | + "props": { |
| 222 | + "data": "${chartData}" |
| 223 | + } |
| 224 | + } |
| 225 | + }, |
| 226 | + { |
| 227 | + "type": "data-table", |
| 228 | + "api": "/api/users" |
| 229 | + } |
| 230 | + ] |
| 231 | +} |
| 232 | +``` |
| 233 | + |
| 234 | +```tsx |
| 235 | +// Register custom component |
| 236 | +import { registerRenderer } from '@object-ui/react'; |
| 237 | +import CustomChart from './CustomChart'; |
| 238 | + |
| 239 | +registerRenderer('custom', ({ schema }) => { |
| 240 | + const Component = schema.component; // "CustomChart" |
| 241 | + return <CustomChart {...schema.props} />; |
| 242 | +}); |
| 243 | +``` |
| 244 | + |
| 245 | +--- |
| 246 | + |
| 247 | +## Frequently Asked Questions |
| 248 | + |
| 249 | +### Q: How is ObjectUI Renderer performance? |
| 250 | +A: Compared to using Shadcn directly, there is a slight overhead (<10%), but with virtualization and caching optimizations, the difference is negligible in real-world applications. |
| 251 | + |
| 252 | +### Q: Can I override ObjectUI Renderer styles? |
| 253 | +A: Yes! You can override styles by passing Tailwind class names via the `className` property. |
| 254 | + |
| 255 | +### Q: How do I extend components not supported by ObjectUI? |
| 256 | +A: Use `registerRenderer` to register custom renderers, or use `type: "custom"` to embed React components. |
| 257 | + |
| 258 | +### Q: Does ObjectUI Renderer support TypeScript? |
| 259 | +A: Full support! All Schemas have complete TypeScript type definitions. |
| 260 | + |
| 261 | +--- |
| 262 | + |
| 263 | +## Additional Resources |
| 264 | + |
| 265 | +- 📚 [Component API Documentation](./components/) |
| 266 | +- 🎨 [Storybook Examples](https://storybook.objectui.org) |
| 267 | +- 🔧 [Custom Renderer Guide](./guide/custom-renderers.md) |
| 268 | +- 💡 [Best Practices](./community/best-practices.md) |
| 269 | + |
| 270 | +--- |
| 271 | + |
| 272 | +*Last Updated: 2026-01-23* |
0 commit comments