How to Improve UI of Web Application using Shiny - shiny

I have prepared a Web application on predicting the price using regression, with the help of shiny.
However I want improve the front end UI aesthetically.
Foreg. Such as changing font style to Italic in slider input, changing background color of main panel etc.
Can you please direct me?
Thanks

Since you didn't provide a reproducible example and exactly the UI elements you want to change (foreg. aren't detailed enough), I'm going to direct you to RStudio's Website. This will give you the basic concepts of how to accomplish what you are trying to do.

Related

Floating comments/ chat section

Hey guys this is my first question here.
I’m envisioning having a floating(picture in picture) chat/ comments section. Where users can interact with each other, but it will be able to move freely on a computer screen independent of the website. I’m trying to get some guidance on whether something like this exits or if it’s possible. Thank you.
Here is a link to a simple chat application that have minimize window.
https://pusher.com/tutorials/chat-widget-python

How to apply a dark theme to a shiny application

I would like to apply a dark theme to a shiny application (darkly, sandstone, cyborg ect) but the DT datatable produced does is almost impossible to read.
I am aware that this question has been asked before but the answer does not work for me. Using the DataTable example (https://shiny.rstudio.com/articles/datatables.html) could someone please let me know how to resolve this issue (i.e how to use a dark theme and produce a datatable that is readable?
Thank you

Changing background color in easy gui

I did not find any useful link that talks about how to change the background color in easygui.
Is there a way to change the background color in EASY GUI ?
No, sorry, there is not way to set the background color.
At the moment, easygui has an easy interface, but is not as powerful as many users want. We hope to change that in the future and have added your question as an enhancement:
https://github.com/robertlugg/easygui/issues/49
In order to do what you want you should build your GUI using another framework. I would suggest Tkinter, not because its the for-sure best, but because it is also simple and fairly standard. You can look at the source code in easygui.py on how it was done previously, or search for 'tkinter' in your favorite Internet browser.

How to design a Web application in django for mobile devices (phones / tablets) [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Is it possible to analyse the clients browser and serve a special designed layout for mobile devices?
In addition how to implement some fancy widgets usable on mobile-devices like "dropdown" and other things like date/time choices and so on? Not to forget the Style and art of whiping from one sceen to the next in smartphone or tablet way - How goes that?
I'm new on this kind of app/web - development, so any hint would be fine.
Conclusion so far: Use a Responsive Webdesign like bootstrap to address issues concernig small screens and changing aspect ratios and something like jQuery as Toolbox for Widgets.
The concrete question now ist how to implement all this into a 0815 'django app'?
I would suggest you to give a chance to Twitter Bootstrap http://getbootstrap.com/
It's becoming more and more popular when it comes to development of responsive web sites.
They recently realeased new version (Bootstrap 3) which is really great and it helps you to easily control what and how to disply on specific screen size.
If you want to learn more about it you could also visit this youtube channel http://www.youtube.com/user/CodersGuide?feature=watch
Well you can certainly make a list of common browser strings and create custom layouts for browsers most common on Android/iOS and serve those directly. (not preferred)
However the generally preferred method is to use CSS media queries for responsive web. These queries look something like:
#media screen and (min-device-width:321px)
{
...
}
#media screen and (min-width:769px)
{
...
}
#media screen and (min-width:1025px)
{
...
}
And in those locations where it says ... you can do custom classes/positioning/styling for all your elements. But Google is your friend in finding good tutorials for these.
Also there are many CSS/JavaScript libraries out there to create good buttons/layouts for mobile devices. These libraries often take into account that the touch areas for buttons need to be larger then the visible area, that there is enough spacing between elements. Often they also include "mobile" widgets, e.g. fancy dialog selectors that pop open and look just like the native popups on iOS or Android. Once again Google will be your friend.
If however you find yourself forced to do browser string comparisons don't expect your guess at the device to be correct. Browser strings are quite tricky and don't reveal a lot of information of the device. E.g. you may have no idea if the visitor is using Chrome for Android on a tablet or a smartphone. You can use browser strings to determine if the user is on Android or iOS for instance. But for Android don't expect to be able to identify all possible screensizes/devices on the market from the browserstrings.

How to work with Interface builder and Rubymotion. Workflow

I am building an iOS app using Rubymotion. I am constructing the UI with the help of Interfaceb Builder. In the screen that I am working on I got the following elements:
Navbar
Label
TableView
I am populating the tableview via an API call. All works fine but I am not sure I am doing things like I am supposed to do. From what I can understand IB is only used to "draw" the UI instead of coding it, nothing more?
This is my controller code. Again, it works fine but I think I am not following "best practice".
http://pastie.org/5368976
There are many different ways of figuring out how you want to build your views.
If you are not doing a crazy amount of custom designed UI, then I don't see why I would not use something like #colinta's Teacup.
I would avoid using storyboards to build a UI. Please see the thread here.
On that note, don't hesitate to check out the discussions on the Ruby Motion Google Group if you can't find the answers on SO. The group seems very active.
Also, IRC: irc.freenode.net, #rubymotion