NOTE: I discovered Lighthouse while typing this up, I've decided to submit anyway in case someone else runs into the same thought I did. Maybe a mention of lighthouse is warranted on the "how-to-compile" page. I'll pick a unassigned bug off light house and see what I can do :)
Hello everyone,
I've been using plex for about 5 months now and I've decided that I'd like to contribute. So far I was able to get everything set-up and have managed to compile & debug the code. Thanks a bunch for the really great "how to compile" page in the wiki by the way. I had a couple of small items to try out (just to learn my way through the code), but have discovered while scanning the forums lots of phrases like "we are currently working on that" or "we will no longer develop features for the current library since a complete re-write is currently underway". I was wondering if there is an easy way to tell what is currently in development? It would certainly suck for me if I added something only to have it wiped out because the piece I worked on was undergoing a complete re-write.
Sorry if I should be able to tell this already. I've never used GIT before (I will be reading up on this week).
I still don’t seem to be able to easily find tickets that say stuff like “Don’t fool with this class because it will be destroyed with a complete re-write of the library”. Am I missing something obvious? I’ll have some time to spend going through lighthouse tonight. Along with GIT this will be the first time I’ve ever used it.
We should definitely tag items in Lighthouse with “wontfix” as well as “starter” (something that’s good for someone starting out).
Why don’t you let me know where your interests are (e.g. “I love subtitles!”) and I would be happy to suggest some stuff you might be interested in? Otherwise, feel free to contact me via email to discuss more
i would also like to contribute code. Is there some more documentation on the code out there? Or just the “How to compile”-Wiki page and the code itself? Is there any good place to start or will the debugger be my best friend for the next days?
That's certainly the approach I took - after staring at the code for a very long time I eventually decided to just build it and start stepping through the area I was having trouble with, which proved most enlightening..
'course then I went on holiday and erased all that knowledge with far too much good Tequila -_-
ok i started with setting everything up for compiling and it works. but i have still a question.
why does the “How to Compile” Wiki says that i have to set PLEX_HOME to /Applications/Plex.app/Contents/Resources/Plex?
I don’t have Plex installed there. So this won’t work. But setting PLEX_HOME to the Resource folder of the app i build does also not work, because of all the missing resources. But where are this resources? Maybe I’m just blind or stupid
This are my first steps with XCode so maybe I’m missing something.
UPDATE:
Ok got this working with setting PLEX_HOME to the root of the project dir and copying the MediaStream skin to the skin plugin.
No, PLEX_HOME should really be set to the Plex folder inside a released app bundle. Things like the skin, keymaps, media server, scrapers etc. are developed independently of the main app and copied in before release.
What is the reason for this? Wouldn't it be easier to have everything in the same repository? So everybody who can fix/change something can do it the the repository?
I've logged a few that are very minor and I can't imagine would impact anything else if you got them sorted out. Admittedly they are library related, which isn't ideal given it is getting replaced, but it might be a good place to start poking around:
This one is probably the best - it is simply a wrong default answer to a question.
[http://plexapp.lighthouseapp.com/projects/...-default-answer](http://plexapp.lighthouseapp.com/projects/15067/tickets/224-deleting-sources-remove-items-from-library-wrong-default-answer)
This one is a bit more complex...
[http://plexapp.lighthouseapp.com/projects/...second-question](http://plexapp.lighthouseapp.com/projects/15067/tickets/225-deleting-sources-no-way-to-back-out-from-second-question)
Do note that neither of these have been vetted to make sure the consensus is consistent with my opinion. I think they are no brainers, but others may disagree.
