How arindammanidas/personal_desk works
Project type and purpose
• From the README (“Personal Desk: A simple windows application for day to day tasks. Wrote this as a college project”) and the file tree (extension .xaml/.vb, a .sln and .vbproj), we see this is a standalone WPF (.NET) desktop application written in VB.NET. It is monolithic, contains multiple windows (Calendar, Journal, Drawing, Notes, Phone, RSS config, Lock, Expense, About), and uses local file-based storage (RTF, XML, TXT, ink files).
File structure
• Top-level assemblies:
• PersonalDesk.sln / .vbproj – Visual Studio solution & project.
• App.xaml / App.xaml.vb – WPF application entry point.
• UI:
• MainWindow.xaml(.vb) – dashboard/launcher.
• Individual windows (CalendarWindow, DrawingWindow, JournalWindow, NotesWindow, PhoneWindow, RssConfigWindow, LockWindow, ExpenseWindow presumably) each with .xaml/.vb.
• Data/Storage:
• bin/Debug folder contains runtime artifacts plus sample data files: PDeskNotes.txt, PDeskRSS.txt, PDeskExpense.xml, PDeskDraw.ink, various date-stamped RTF journals.
• Supporting assets:
• Fonts folder, Simple Styles.xaml (resources & styles), PDeskHelp.pdf, User Manual.pdf.
• Build & deployment:
• ClickOnce publishing artifacts under bin/Debug/app.publish.
README for additional insights
• Minimal description; no explicit architecture notes. We infer standard WPF code-behind approach with file-based persistence.
a. Main components
1. UI Layer – WPF Windows & XAML resources
2. Application Layer – App.xaml startup & navigation logic
3. Business Logic Layer – code‐behind event handlers & any shared services
4. Data Access Layer – file I/O module reading/writing TXT/RTF/XML/ink files
5. Local Storage – Windows file system (data folder under user profile or app data)
6. .NET Framework – WPF runtime, Expression.Drawing library (see Microsoft.Expression.Drawing.xml)
b. Relationships & interactions
• User interacts with each Window (UI Layer)
• Windows invoke Business Logic to process commands (e.g., save a note, load calendar entries)
• Business Logic calls Data Access to read/write local files
• Data Access reads/writes to local storage (bin/Debug under development, real path under AppData in production)
• App.xaml orchestrates startup, dependency injection (if any), and window navigation
c. Architectural patterns/design principles
• Layered architecture (UI → Application → Business Logic → Data Access → Storage)
• Separation of concerns: XAML for UI, VB code-behind for behavior, files for persistence
• Resource dictionary (Simple Styles.xaml) for consistent theming
• ClickOnce deployment for updates
d. Key technologies & libraries
• WPF (.NET Framework 4.0)
• Visual Basic .NET
• Microsoft.Expression.Drawing for ink/drawing support
• File-based persistence (TXT, RTF, XML, .ink)
Detailed capture of essential elements
• Major window as a sub-component under UI Layer
• Resource dictionary (Simple Styles.xaml) linked into UI Layer
• ClickOnce publishing artifacts under a “Deployment” annotation, but keep it outside the runtime boundary
• Microsoft.Expression.Drawing as an external library dependency