-
Notifications
You must be signed in to change notification settings - Fork 5
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
Implement full-width conversation view option #1
Comments
Thank you for your enthusiasm for enhancing GPThemes. Could you share the reasoning behind your interest in this feature? Currently, on tablets and smaller screen devices, the chat bubbles already occupy the full available width. Are you proposing to extend this change to all screen sizes? A better understanding of the use case will help to tailor the approach accordingly. Let's consider why we should be cautious about implementing this proposal:
|
One thing which made me to think about utilizing the available width is when gpt generate codes and sometimes codes lines overflow the codeblock and we have to scroll horizontally to review :) And the other reason is I personally use GPT with sidebar closed ( thanks to their handy keybindings ). so in that case i feel like the chat bubbles should occupy a little more width |
Ah, I see. Thanks for the clarification, now I better understand the scenario where your suggestion makes sense. I agree that the somewhat restricted code block section is a bit irritating in this context. Increasing the maximum width of the chat bubble makes sense when the sidebar is hidden. I plan to add custom styling for some elements in the future, so perhaps I could include the chat bubble width in that. |
Hi @itsmartashub , hope u r doing well, i wanted to mention that, now we do have a little bit of customisation options like themes and fonts, so its possible to include adjusting width container from those options itself |
- Start working on the chat full-width feature - Implement basic UI with switch checkboxes Changes summary: - Initiated the development of the chat full-width feature: - Implemented a basic UI with switch checkboxes to toggle the full-width mode for chats.
Hi there @NeeRaj-2401. Telepathy, cause I just started working on this today. For now, it's a toggle for full width, but in the future I plan to make this option more customizable, allowing the user to choose the width percentage.
EDIT:By the way, if you're "impatient" for the official release, you can track and test the current state of the full-width option by downloading the GitHub Actions build artifacts ( Just be aware that in the new UI, I can't make the user chat |
New one
I think the prompt field is ok as it is right now, but u know the design better than me 😅
Yeah it makes sense
Sure i will give it a try and let you know if there will be any further suggestions from my side, thanks :) |
Prerequisites (Required)
Feature Request Description (Required)
the entire chat section is bounded within a container with certain width, utilise maximum available width,
Screenshots or Videos (Optional)
current :
![image](https://private-user-images.githubusercontent.com/88180887/319059411-a774e894-07cb-4874-acd5-36b55afa87e1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5MTQ0NzksIm5iZiI6MTczOTkxNDE3OSwicGF0aCI6Ii84ODE4MDg4Ny8zMTkwNTk0MTEtYTc3NGU4OTQtMDdjYi00ODc0LWFjZDUtMzZiNTVhZmE4N2UxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE4VDIxMjkzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTIxN2YxODlhOTAzMmJmMGI0YmUzZjE2NjQwMzBlNDc3ZjExZmI5MDllM2E3OWRmZWI5YWRjZmMyMDkxZjI4ZGEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.c5_tDOb1ezgTwyfDuaIOLzVkdRu3zKnDhLvdsbNX8WA)
desired :
![image](https://private-user-images.githubusercontent.com/88180887/319059839-0d799671-5f15-4c22-bd1b-7729d312d9de.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5MTQ0NzksIm5iZiI6MTczOTkxNDE3OSwicGF0aCI6Ii84ODE4MDg4Ny8zMTkwNTk4MzktMGQ3OTk2NzEtNWYxNS00YzIyLWJkMWItNzcyOWQzMTJkOWRlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE4VDIxMjkzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM3MmI5MTk5YzJiNjU0M2JmYTE3ZjAxMjliYjI0N2NlMGJlNDgwYzAxMmFhMWNjMWIxOTllYWUyOWUwZTg2NTcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.aYQPXSUnotX8q2HCMWER7l7OLlojhncKJu4EUdaeyq8)
Additional context (Optional)
No response
The text was updated successfully, but these errors were encountered: