Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Ideas and Suggestions for User Interfaces #1159

Open
2 tasks done
luckyyyyy opened this issue May 19, 2023 · 1 comment
Open
2 tasks done

[Feature] Ideas and Suggestions for User Interfaces #1159

luckyyyyy opened this issue May 19, 2023 · 1 comment
Labels
feature New feature or request

Comments

@luckyyyyy
Copy link
Contributor

luckyyyyy commented May 19, 2023

Search before asking

  • I had searched in the issues and found no similar issues.

Feature Request

While the Laf positioning is for non-coders to be able to use, I still suggest that the interface of Laf can evolve towards the direction of VSCode.

Currently, the entire interface resembles a backend system, which is not very user-friendly and lacks aesthetics.

  • Avoid using rounded corners.
  • Reduce the spacing between sections to make the interface more compact and increase the visible area for code editing.
  • Incorporate MonacoEditor in more places, such as the log viewing interface.
  • Use a console interface similar to Chrome's console, which provides a more user-friendly output for console.log logs.
  • Use MonacoEditor with line numbers in the interface for API testing and database management, making it easier to view and edit.
  • It is not recommended to use the cmd+r shortcut as it may conflict with the browser's refresh shortcut.
  • The code editing area currently uses overflow: hidden, which prevents MonacoEditor tooltips from being displayed. It is advisable to reconsider the layout approach.
  • Consider adding the ability to switch between tabs for functions.
  • Use more navigation components instead of divs, as this allows for opening new tabs with the right-click function.

I am willing to contribute the aforementioned suggestions. May I ask if it's possible to develop and debug Laf.dev by connecting to it locally without deploying k8s to the cloud?

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
@luckyyyyy luckyyyyy added the feature New feature or request label May 19, 2023
@0fatal
Copy link
Contributor

0fatal commented Jul 20, 2023

You can modify base url of api via the .env file on the frontend side, which I assume eliminates the need to deploy the back-end manually, and eliminates the need for k8s?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants