aswinrajeev / blogly Goto Github PK

The status updates for the application should appear live on the footer.

In the custom image blot created for the purpose of supporting local-src attribute for images in Quill editor, existing attributes such as width are not supported.

When running the application, a warning entry is issued to the console:

(node:2821) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

This has to be fixed.

Integrate the UI, backend with Blogger Adapter to enable a minimal blog publish capability

As an initial integration, the application should be integrated with Blogger. Google already have an API Docs for Blogger integration.

The required API's and pre-requisites for integration with Blogger has to be explored and listed.

The further documentations could be found at:

• Blogger API: Using the API
• Blogger API: Getting Started

The main UI mockup for the application would help understand the user experience and initial interactions with the application.

Info/error dialogs in Linux does not show up any buttons. This makes the dismissing the dialogs difficult.

The UI created for the blogging has to be integrated with the Google API service at the backend for a minimum viable application.

Embed an HTML code editor into the application so that the fine tuning to the blog post HTML can be done from within the application. This should serve as a workaround for issues like #19.

User should be able to add tags to the blog post. As an initial implementation a list of strings as the post should be fine.

The select all keyboard binding is not supported in the application. This could be due to a missing menu item for the same.

If the side panel has been closed, it does not open when clicking on the sidebar icons. The user would need to click on show side panel from the menu.

Also, the close action on UI does not reflect on the backend, causing the user to click the menu twice (first to hide, and then to show) to get the side panel.

Add support for inserting read more () in Quill editor.

When published a post, the file attribute of blog post model is not getting set at the client-side. This results in no confirmation when deleting.

Every time the user switches to the post list panel from another panel, or just opens it, the current post gets refreshed. This results in loosing unsaved changes.

When switched to post configs (tags) panel, the switch editor feature stops working.

Create a basic project setup with Electron and Angular configurations.

The post list is not getting rendered on the application start-up. This is probably because of the asynchronous updating of the list in the angular service.

Uploading the images to Google Drive and linking the same in the blog post results in delayed loading of the images. As a solution to this, keep a local copy of the image and create a map of the local URL to the one uploaded.

Instead, of setting the remote URL to the post image, set the local URL. Later when publishing, replace this local URL with that of the remote.

A facility for exporting and importing of blog posts would be required for effective utilisation of Blogly.

In HTML editor, the content should be rendered after beautifying. Currently the crude contents are too hard to read.

Currently the images included in the blog post are getting uploaded in full size and as a inline data, rather than uploading the image to google servers and linking it.

When post configs (tags), or post info panels are selected, the corresponding sidebar items are not highlighted. Also, when loaded the posts panel is not highlighted by default.

The quill toolbar items may have more items than required. This may need to be revised, so that only the required ones can be maintained.

When creating a new blog post, an error occurs when switching to HTML editor.

A basic UI layout could be created for the application, as per design specified in #1

The change blogs directory feature does not seem to work after the architecture changes. This probably might have been missed.

Development has to be completed for the left panels, Settings, Tags and Info panels.

Currently the application supports publishing directly after typing. However, there is no provision to store draft blog posts locally. This would severely impact the capability of the application as a standalone blogging utility.

The app icon does not show up in Linux.

MacOS has an amazing system spell checker and auto complete system. But somehow it doesn't work with Blogly.

For the application to achieve a first release criteria, the menus should be developed. The initial set of menus may include the following structure:

• File
  • New
  • Import
  • Save
• Blog
  • Import from blog (...)
  • Draft to blog (...)
  • Publish to blog (...)
• View
  • Toggle HTML editor
  • Enter full screen
  • Hide / show side panel
• Help
  • About Blogly Beta
  • Guidelines to use
  • About the author

When the post is published before the timeout, the time-out attempt fails resulting in an error.

The client side of the application has to be modularised according to the architecture (as specified in #34).

Showing the image base64 data in the HTML editor makes it cumbersome to edit the HTML. A work around for this would need to be figured out.

Google API handler (blogger adapter) has to be separated into blogger adapter, drive adapter, and google auth handler.

This is a sub task of #34 (Implement architecture changes)

The server end of the application has to be modularised according to the architecture (as specified in #34).

The component level architecture for Blogly need to be revised and development changes to be done accordingly.

When trying to publishing a post that was already shared as draft to blogger, the post is still shown as a draft. Similarly, reverting an already published post to draft is also not working.

An index file has to be kept to keep a tab on the files in the workspace. This index file has to store the sequence of the files worked upon, and the meta data about the posts - like title, contents extract, tags etc.

When a new file is to be added into the workspace, this file would not thus show up in the posts list. The post has to be explicitly imported from the file or directly from the blog. In such cases, the file data is to be added on to the index.

Blogly application does not quit and remain in the dock of the MacOS even when fully closed. Neither does it open back when clicked.

This should be changed to termination of the app when closed.

Change the currently hardcoded blog address to that selected by the user.

When inserting images to blog contents, there should be an option to re-size the images.

Currently the application supports publishing directly after typing. However, there is no provision to store draft blog posts locally. This would severely impact the capability of the application as a standalone blogging utility. Related to #15.

If a post is initially published and then deleted from the blogger, the publish request does not serve at all.

The technology stack of the application involves selection of the platforms, libraries, APIs to be used. These involves:

1. Desktop application framework
2. UI framework/components library
3. Data persistence framework
4. The libraries to be used for security, visualisation, rich text etc.
5. APIs to be used for integration

Addition of conencted blogs is not working when tested on Linux. Instead of the given details, a blank entry is getting added.

Currently configured routing methods doesn't work. Another mechanism has to be found so that the side panels can be effectively navigated.

Currently when the images are inserted through Quill editor add-on, the image is directly inserted as base64 data. It is then uploaded to Google drive during publish and then onwards stored as a direct link pointing to the drive image location. This causes the image to not load when offline and huge HTML markup before publish.

Alternatively, the image would need to be first copied to a local location, upload the image to the drive during the add-on invocation itself. The local file href has to be inserted into the Quill editor and a map needs to be maintained with the local location against the drive location. Anytime the publish happens, the image src need to be changed to the drive location.

A comprehensive error handling technique is required to keep a tab of the errors that are produced from the application.