Matt I'm just saying it doesn't matter when I decide since you'll have your own fork anyway. It's just a matter of where the "main" copy is, and with GitHub and Git in general, that's just a social construct :.
Fair enough. I suppose it's something we should do at some point anyway. It's just that there are number of work items to do to set this up as an organization that make this a bit of a pain. By the sounds of it your gonna go the organisation route.
Geuss refactoring the code is gonna be annoying. If I may inquire for a seperate project of mine , what is required to create an organisation? What is the actual process? If you don't have the time to answer then that's fine :. Here's what I'll do. I'll make the organization, create a repo for Ripme-Android, and add you as a contributor to that repo. We can add the main ripme project repo to that organization later, but it allows you to start your project with the main repo in a logical place for how we're planning to move forward.
As for the details of making an organization, you can think of it like an "account" that you access via your normal account's log-in and which can have more than own "owner". As for the other details, it's been a while since the last time I made one. But basically it means that we will have a centralized place to go with a name that isn't one of our usernames and instead represents the project as a whole.
Looks like someone already registered a user with the name ripme so we can't register the organization as "ripme". My work WiFi was being rather dodgy, so I was unable to download Android Studio, I'll try again tomorrow when I am at work again if that doesn't work Ill just go to my local library and download there during the weekday, cause it's a decent sized download.
If my work WiFi isn't flaky today, I'll have android studio downloaded and I'll have started on the app by the end of tonight. I've got Android studio I still need to download the SDK and have git cloned the repo and sub module.
But haven't had the chance to start on this project. I have still yet to see how much effort is needed to port the java code to the equivalent API I'm blaming this on work taking up all of my time;. Matt no worries, take your time. I'm also busy until February and won't be able to do any coding until then. I will follow through it just may be really slow.
One quick question, what part of the java code do you think will bring me the most trouble ignoring the java code for the UI as it's irrelevant? Matt Honestly no idea. I've never done a port of a desktop Java app to Android and my Android app dev experience is very little to practically nonexistent.
I think the biggest practical challenge is the huge space requirements an app like this commands. Not sure if that will be an issue for Android devices. Uploading directly to the cloud to save space locally makes some kind of sense but the technical problem there is the bandwidth required download image, upload image -- 2x the bandwidth of simply downloading -- I don't think there's any way to have the images you're downloading beamed directly to the cloud storage and bypass the device -- that would require support from each respective service of allowing you to retrieve a file from anywhere on the web.
Actually that's my major technical concern that really should be improved before tackling other work. See and the anti-pattern of forcing https links to http as supported by So there's some major technical hurdles before we're app-viable, but that doesn't mean we can't prototype.
In regards to cloud storage, it'll seem more like a wait and see approach, coupled with research, and how the original app has implemented the feature. This is a area that definitely requires a look into at the minimum. Either way it'll be a little while before we get a semi functioning app, but that's the fun isn't it. I'll hopefully at least be able to update the repo in the coming days. Technically your computer, the 3rd could be wrong number party, could tell the source where to send the data, or the cloud where to get the data from, but that's quite special arrangement which to me sounds the same as opening SSH connection and running a command.
That arrangement wouldn't be negotiable with the source without owning it yourself or a friend own it or something along that line. As for my progress, I have some other side projects that need to be finished first and this is around last on the list I'm probably gonna be like what metaprime is and won't be able to do much till February. I'd like to say work has slowed down, some of my side projects are almost complete, it's near the beginning of a new month, so you I'm gonna try again at this :.
I'm thinking this is most likely not supported as it could be easily and heavily abused. Most likely taking advantage of cloud storage would require download and upload which is twice the bandwidth cost to a mobile device. Besides that and privacy on mobile networks or when using e.
Not uploading picture as has personal details and it's a prick to Balck out on a mobile. I'm currently at this very moment reinstalling Ubuntu as my previous installation has borked died, filesystem corruption on itself. Matt oh no! Hopefully you didn't lose any data or work! Yes, I think the share option involves reuploading downloaded content, although I could be wrong.
I wasn't imagining this being implemented via the share menu personally, but that's an interesting approach. I believe only a few files got corrupt, the most recent files I was working on, but no biggie, I booted a love USB and. I wasn't saying implementing via share menu idea does sound cool [Goto Imgur Album page, share, ripme-android, URL gets passed to ripme-android app]but not planning to implement anytime soon , I was more pointing out the fact that Google drive had a save to Drive option.
Ah yes, I was just brainstorming today about how to make a mobile app experience not terrible. Yea it's a cool idea. I've gotta stop putting bit off and have another crack at doing this, cause at the current moment I keep putting it off to work on porting a device tree for my android device so I can build LineageOS. I'll be setting Android Studio back up again tonight, let's see how many gradle errors I get this time ;.
I'm sorry, completely forgot about this side projects, been a bit engrossed in trying to port LineageOS to my android phone have a look at my recent commit history.
So thanks metaprime for giving me write access to the Rip-Me-Android repo, it reminded me of the project. So time for me to take another crack at it, let's hope I don't get some many damn gradle build errors as last time.
Matt I was surprised to find you didn't have write access already. Was just auditing access when I added the ripme-wiki repo :P. This thread has been back and forth for several months now, has there been any other discussion on if anyone is thinking about contributing to the mobile development?
I have done several mobile applications and im going to be playing around with some ideas that I have for it. Yea feel free to give it a go, I haven't been able to do much until really recently I just got internet access at home about a week ago. I saw that you were dealing with that a couple of months ago and yeah a bork is less than pleasant. Im going to be throwing my ideas at the wall this weekend.
One of the ideas that i'm looking into having an api section within the settings so that the user can plug in their own api keys for the supported sites in case the main keys go down. Either way I have a hobby for the next few weeks. Yea, I'm going to be replacing my hard drive with another spare I've got tomorrow, and will be getting everything setup up again tomorrow's.
Tests can be marked as beeing slow, or flaky. Default is to run all but the flaky tests. Slow tests can be excluded to run.
After building you can run tests, quoting might be necessary depending on your shell:. Please note that some tests may fail as sites change and our rippers become out of date. Start by building and testing a released version of RipMe and then ensure that any changes you make do not cause more tests to break.
Skip to content. Star 2. Downloads albums in bulk MIT License. Branches Tags. Could not load branches. Could not load tags. Latest commit. Git stats 2, commits. Failed to load latest commit information.
May 10, Ignore rips subdir of repo in vscode. Nov 30, May 9, Sep 1, Add style check utilities. Jun 19, Aug 7, Feb 25, Fixed travis config. Aug 19, Nov 13, Nov 19, Apr 26, Aug 30, Added maven plugin to make builds reproducible; build.
May 31, Improve deployment script add file hash as sanity check. Feb 16,
0コメント