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 1 year ago.
Improve this question
I've been tasked to make a web app that users can drag and drop images to a container, depending on the size of the image, it needs to be able to snap in to place until the container is full.
I'm only a beginner programmer, I'm not too sure how to even begin (I've been "googling" for the last couple of days). I'm only going to host the app on a local server.
Can someone point me in the right direction?
Would Python be the best bet here?
Is a Web App even a good approach to this? I'm only going with a web app, so users can access through localhost.
There's no data stored (yet). Just saving as pdf and printing.
I'm not sure what other features will be added in the future, but would be good to have future proofing.
Thank you in advance!
Dispite of my comment I'll give you some directions...
I'll upset a bunch of people, but I don't think python and web are a good match...
You should study a client-side framework like react, that has NPM modules to easily drag and drop, and to organize children in containers in smart ways.
The PDF part is tricky, theres a thing call ghostscript that can "printscreen" a html rendered page and make pdfs, or some tool that do the same using a headless browser.
Can be done, but won't be trivial...
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
H!
I have created a website, where all the files are of the type CSS, js, pug, and when I want to publish the site, I need to give an index.html file from which the site will start. The problem is that I do not have such a file.
Does anyone know how to deal with such a problem?
And in addition, I started the site by running it in localhost: 3000 does anyone know how to start it now so that it will work when I upload it.
Thanks in advance to all the helpers.
Your mention of localhost:3000 implies that you have written a website which depends on Node.js for server-side code (at a minimum this will involve the translation of your Pug templates into HTML on demand).
There are two general approaches you can take to solve this problem:
Find hosting which supports your server-side code and deploy your Node.js application to it. (This will not be typical static or shared hosting).
Generate static HTML documents from your application and upload those HTML documents. (The specifics will depend on exactly what your server-side implementation does and will probably be a significant amount of work. Typically if you wanted to take this approach, you would have used a framework designed to output static sites from the outset).
Obviously if you have your server-side code processing user input (such as form submissions) option 2 will not work.
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 2 years ago.
Improve this question
I am trying to set up a website with MediaWiki on a Shared Hosting service and am getting frustrating results. First I am going to list what I want out of my website and will show the hosting details to show you what kinds of problems I am running into here:
So the main objective of the website is to run a database of events in human history (relating to World War 2)
I want to use the Visual Editor extension to create a more visual style to edit articles (which requires Parsoid) so that editors won’t have to go through the pain of using the old wiki editor and memorizing the different characters needed for specific things and so that editing the whole thing won’t look like a complete mess.
I want to make it so that only selected accounts/people can create and edit content on the site.
I want to be able to have some sort of forum so that people can ask questions and communicate with each other.
I want my site to have a certain kind of style (which I know is a skin but was wondering what's the best way to create one is. Also, do skins also come with the ability to customize the site to have certain functions? Because I have seen sites like halopedia which seems to be running on MediaWiki but have a lot of different kinds of functions and all that. )
I want to create some sort of email system for my thing (although I could just maybe use another service which would be easier)
These are pretty much the main things that I want but there are some smaller things that I can ask how to do some other time as they are not mandatory right now. Here are the details for the hosting service that I use for the website just to give you guys a better understanding of my situation here.
I am using Bluehost as the hosting service and cPanel as the file management system
The website is currently on a shared hosting plan and the best one that I could get without spending a lot a month.
I used Softaculous to download MediaWiki onto my website.
One of the main things that I have been having trouble with is installing Parsoid to install the VisualEditor extension onto the site. The problem is that to install Parsoid you need Node.js which I can’t install on my hosting service because it is shared hosting. However I tried following the instructions on the page that shows you how to do it using Heroic but have been having trouble with that too.
If you wait a few weeks, MediaWiki 1.35 will be released with a PHP implementation of Parsoid.
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 5 years ago.
Improve this question
I have a website where I put music, but I do not want anyone downloading it, or it gets harder and just listening online, like YouTube.
Unfortunately, no. It is a bit like trying to prevent someone from recording an on-air broadcast. When you send video data over the internet to someone's player, they can simply store the information being sent to the player unless you obfuscate it and make it so that the player will only work under certain circumstances and will not share the data. This, by definition, is DRM.
What DRM attempts to do is control the reading of the data entirely, so that it can not be copied. This has varying degrees of success and rarely, if ever, works particularly well. It may keep honest people honest, but if you are sending someone data in a way that they can access it, measures to try to stop them from copying it are... difficult. The most advanced systems use special display drivers and encrypt the data right up to the point it is being displayed on the screen (HDCP), that way other software on the computer can't directly pull the information off the frame buffer being prepared for the screen.
There may be some ways you can mildly obfuscate the access to your video, but ultimately, if you send it in the clear, it is trivial for a knowledgeable viewer to store the datastream. If you use DRM, it is substantially harder, but still likely to be able to be worked around by a dedicated attacker.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
It seems that anymore I have no clue what is going to happen when I launch the Help of a program. Which makes it all that much more confusing when having to decide how to create a help file for my application.
For example, it might open my web browser to local instance of an html file. It might point to a web-hosted help website. It could load up the Windows Help and Support center. It may load a chm file. It could load up a custom help form with menus, etc.
What is the "correct" way to implement a help?
I like the idea of chm file, but it makes it hard for me to push any updates to users without them updating the application. Same can be said for a local html based help file.
I also like the idea of doing a web hosted help file because I can update it as needed with new information, but what does that mean for users who don't have an active internet connection? For example (in my case, my software will be used equally in a car-mounted laptop with no internet connection and on a desktop computer with an internet connection)
I'm curious to know what is commonly done when creating a help file, and what authoring tools are used, if any.
A solution I have used for the mobile applications, is to have a local html help file which the application renders for help content in a web view. We then had a background mechanism to check against a service for help updates and download the updated HTML and other static content as appropriate. This way you always have a local HTML file which doesn't require a connection, and renders quickly (since there is no download required for viewing).
The most subtle way is providing a Compiled HTML (CHM) help file.
There are many free and paid apps that help create documentation. You could try Rahman CHM Maker or KEL CHM Creator.
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 7 years ago.
Improve this question
I browsed some of their sites. They always point to bug list as start of participating project.But, as a newbie in that project? How can I fix bug at the beginning?
Can anybody give me some suggestions about this?
Issac Truett's answer is good.
My only suggestion would be to pick a project and download their source code. Most open source projects use CVS, Subversion, or Git to manage the source code.
Pick an integrated development environment (IDE) that supports the language of the project and attach the IDE to their source code manager.
Spend some time getting familiar with the source code, and the bug list will make more sense.
Almost every Open Source project I've ever seen has a stack of minor issues in the corner - cosmetic or otherwise largely inconsequential things that nobody has considered worth their time. If you just want to get your foot in the door, that's probably a good way to introduce yourself. Just find something easy, make sure you implement it well, and follow the project's rules on coding style, submission for review, etc.
Or, ask the project. "I'm new, I want to help, this is my skill set. Would someone be willing to mentor me?"