පැරණි වින්ඩෝස් සංස්කරණවල ඇති (එය වින්ඩෝස් එක්ස් පි වියහැක)
සරල පින්තූරු වීවරයට සමාන නමුත් වැඩිදියුණුකල විවරයක අවශ්‍යතාවය තිබුනි.
එහිදී .webp වැනි නව ගොනු ආකෘති වලට සහය දීම.
වින්ඩෝස් ටයිටල තීරය ඉවත්කර නවීන පන්නයේ ග්‍රැෆික අතුරුවතක් සෑදීම.
එයට අමතර බොත්තම් එකතුකිරීම
ටැබ සහිත අතුරුවතක් සෑදීම
ගැන අවධානය දුනිමි.
වම් සහ දකුණු හී යතුරු යොදාගෙන පින්තූරු අතර මාරුවිය හැක.
මෙය දැනට මාගේ සම්මත පින්තූරු වීවරය ලෙස පාවිච්චි කරමි.
මෙය සෑදීමේදී Chat GPT සහායකය යොදා ගත්තෙමි.
මෙය සැදීමේදී .net core 9 පාරිසරිකය පාවිච්චි කලෙමි.
එහෙත් .net4 වැන්නක් යොදා ගත්තේ නම් හොඳයැයි සිතේ.
ප්‍රභව කේතය මේ සමග එවමි. එය යොදාගෙන .net4ට ගැලපෙන මෘදුකාංගය සැදිය හැක.
මෙහි වැඩිදියුණු කලයුතු අංග සඳහන් කරන්නේ නම් මැනවි.
ගොඩක් ලස්සනයි විසුල කාවින්ද
ReplyDelete@ Jagath
ReplyDeleteමේක මරු
It sounds like you've done a great job creating a custom image viewer that meets your needs, especially with the help of ChatGPT. It's impressive that you've incorporated features like .webp support, a modern UI without the traditional title bar, extra buttons, and a tabbed interface. Using the arrow keys for navigation is a convenient touch.
Converting Your .NET Core 9 Application to .NET Framework 4
Converting a .NET Core 9 application to .NET Framework 4 (like .NET 4.x) can be a bit challenging, as .NET Core (now just .NET) and .NET Framework are different platforms with distinct APIs and project structures. While .NET Core aims for cross-platform compatibility and modern development, .NET Framework is Windows-specific and has a more mature ecosystem for certain types of desktop applications.
Here's a general approach and what you need to consider:
* Understand the Differences:
* .NET Core/5+: Uses SDK-style project files (.csproj). More lightweight, cross-platform, and has modern APIs.
* .NET Framework: Uses older .csproj formats. Windows-only, and some APIs might differ or have different implementations.
* Identify Incompatible APIs:
* UI Framework: If you used WPF or WinForms, the core UI elements are generally compatible. However, modern UI paradigms or specific controls in .NET Core might not have direct equivalents in older .NET Framework versions.
* Third-Party Libraries: This is often the biggest hurdle. Any NuGet packages you used in your .NET Core 9 project must have compatible versions available for .NET Framework 4. If a library is only for .NET Core, you'll need to find an alternative or implement the functionality yourself.
* System APIs: While many System.* namespaces are similar, some new APIs introduced in .NET Core 9 might not exist in .NET Framework 4.
* Conversion Steps:
* Create a New .NET Framework Project: Start by creating a new Windows Forms App (.NET Framework) or WPF App (.NET Framework) project in Visual Studio, targeting .NET Framework 4 (or 4.x, whichever is most suitable).
* Copy Source Code: Carefully copy your C# source code files (.cs files) from your .NET Core project into the new .NET Framework project.
* Add References:
* NuGet Packages: For each NuGet package you used in your .NET Core project, search for a compatible version for .NET Framework 4. Add these packages to your new project using the NuGet Package Manager.
* System References: Ensure all necessary System.* assembly references are added to your project. Visual Studio usually adds common ones automatically for .NET Framework projects.
* Resolve Compilation Errors: This is where the bulk of the work will be.
* API Differences: For any code that uses .NET Core-specific APIs, you'll need to refactor it to use equivalent .NET Framework APIs.
* Missing Libraries: If a third-party library doesn't have a .NET Framework 4 version, you'll need to replace it.
* Project File Changes: Older .NET Framework project files are more verbose. You generally won't need to manually edit them unless you encounter specific build issues.
* Test Thoroughly: After you get it to compile, you'll need to rigorously test the application to ensure all features work as expected and that there are no runtime errors.
Why .NET Framework 4 Might Be Desirable
Your intuition about using .NET Framework 4 might stem from a desire for broader compatibility with older Windows systems, as .NET Framework 4.x is often pre-installed or easily installable on a wider range of Windows versions compared to .NET Core runtime which might need to be bundled with your application or downloaded separately by the user. This can simplify deployment for certain target audiences.
මෙහි වැඩිදියුණු කටයුතු අංග
DeleteSuggested Improvements for Your Image Viewer
Here are some areas where you could enhance your image viewer, building on the great work you've already done:
* Performance Optimization:
* Lazy Loading: For very large folders with many images, load thumbnails or images only when they are about to be displayed, rather than loading everything at once.
* Caching: Implement a simple cache for recently viewed or loaded images to improve responsiveness.
* Asynchronous Loading: Load images on a separate thread to prevent the UI from freezing, especially when dealing with high-resolution images.
* Image Manipulation Features:
* Basic Editing: Add options for common image adjustments like rotation, flipping, cropping, and perhaps basic brightness/contrast adjustments.
* Resizing/Scaling: Allow users to resize images directly within the viewer.
* Enhanced Navigation:
* Thumbnail Strip: A small strip of thumbnails at the bottom or side of the viewer could provide a quick visual overview of images in the current folder.
* Folder Navigation: Easy ways to navigate to parent folders or other image directories.
* Zoom Functionality: Implement smooth zoom in/out with mouse wheel support.
* Metadata Display:
* EXIF Data: Display relevant EXIF metadata (camera model, date taken, exposure settings, etc.) for photos. This could be in a collapsible panel.
* User Experience (UX) Enhancements:
* Settings/Preferences: Allow users to customize aspects of the viewer, such as default zoom level, background color, or navigation preferences.
* Drag-and-Drop: Enable dragging and dropping image files or folders into the viewer to open them.
* Context Menus: Right-click context menus for common actions like "Open containing folder," "Delete," or "Set as wallpaper."
* Slideshow Mode: A simple slideshow feature with customizable delay.
* Accessibility:
* Keyboard Shortcuts: Ensure all critical functions can be accessed via keyboard shortcuts, not just arrow keys.
* High DPI Support: Ensure the UI scales correctly on high-resolution displays.
* Modern UI/UX Refinements (even more!):
* Animations: Subtle animations for transitions between images or UI elements.
* Dark Mode/Themes: Offer different color themes for the interface.
* Gesture Support: If applicable (e.g., for touch screens), implement pinch-to-zoom or swipe gestures.
You've built a solid foundation, and these suggestions can help you take your image viewer to the next level! Good luck with the conversion if you decide to proceed with .NET Framework 4.