I would like to contribute to Nextcloud because there are some issues that are quite easily fixed but aren't by the developers.
Now this might sound like a stupid question, but I can't find ANY information on how the code is structured. There is no documentation I could find whatsoever.
I also can't find any information of other people developing with Nextcloud as issues on Github are not answered.
Is there any information available or is it only Open Source in the sense that all structure is kept private by Nextcloud GmbH and only the code is made public?
Specifically I am looking for information on which Vue.js component does what and where I would have to look to find the functions that are doing what I'm searching for.
Related
I'm developing a web Application using PHP. And there i need to use commenting system. One of my senior suggested me to use Drupal for the commenting system, i referred some websites, but i got a contradicting answers. Some of them says "integrating Drupal with any website application will not be consistent". Is that right? Or may i use Drupal comments in my PHP Application?
I know this is not a programming question, still i need to get some experts advice for this. so i post my question here.
In short, if the rest of your project is built in Drupal, then absolutely use Drupal's comment system. If not, you're probably better off using something else.
Drupal is a flexible content management system and framework that provides way more out-of-the-box functionality than just comments. The comment system is relatively tightly coupled to Drupal's nodes and entities and isn't currently intended to be used stand alone. Using just the comment module in Drupal would entail quite a bit of work just in disabling the parts you wouldn't be using and then figuring out how to integrate with the parts you needed. You would be in uncharted territory, with little to no documentation available to help you figure out how to do all that.
If you just need a comment system, you're better off using a stand-alone comment service (such as Disqus or IntenseDebate) or using a package tailored for comments (such as juvia or EasyPageComments) or writing your own comment system.
I realise there is quite a bit on this in other posts and i am getting my teeth into those too, but i just want to clear one fundamental point up before i get into detail.
I have read in depth the integration document and i understand the principles. The iFrame is a corollary of server integration with a couple additions to the communication with the Sage server as i understand it; but that is for later. What i am completely stumped by is this php downloadable integration kit.
The document states that we just need to issue some value name pairs and I feel completely happy with that. The document also states that there are examples of the posts and the notificationURL reply posts that are needed in the integration kit.
In the integration kit i find two directories: demo and lib. Following the instructions to integrate the SQL into my dev environment I can get the demo to work. I can use it to make a purchase from their CD shop, but the calls and code to initialise the Sage are buried all around a really really complicated directory structure with loads of includes and external calls to throw you off the scent. I have looked atlots of the files and nowhere do i see any name/value pairs being passed. In the lib directory are a config file, and a constants file with lots of variable declarations and an initialisation file which presumably starts the whole thing off somehow, but just gives a blank screen in a browser. There is a folder called classes with many many files defining various classes, but no help files or useful notes.
What there is not is any explanation of what to do or any examples. So this is my question for anybody who has done this recently: Do i just need to post some value pairs to the server specified in the documentation (easy peasy), or do i need to have the sage files present on my server and initialise some objects and relevent properties within the class structure in the integration pack etc. The two are pretty much poles apart for me, particularly without any help files to navigate the classes structure.
Does anybody know which is the correct solution and where the mentioned exmples might be hiding.
Thanks for any help.
I am new to Github, and want to find some good written PHP website application source code to read. But simply type 'php' as keyword and search on Github is not that effective. Is there any better way to do it?
Also, are PHP frameworks source code good to read and learn?
I think on github there is also a lot of bad written code. I can tell you that maybe working with an CMS might be something for you. While creating Plugins for CMS systems you learn the CMS itself part by part. This way you may understand why things are how they are.
In general, noone simply starts reading Code. You read Code to understand how you interact with an external system.
I have looked and looked all over to find a way to make something similar to PhpBB's automod system they use for their software.
I cannot seem to find anything similar to this with the whole xml find and replace code updater and mod installer.
I may just be typing in the wrong keywords in Google, but does anyone know of any system like this available before I start trying to make my own?
EDIT: I mean more like a code updater. For example find and replaces in a php file.
FIND:
?>
ADD BEFORE:
echo "this is text added before the ?>";
I realize this could be done with str_replace but there is surely a system out there that already does this reliably.
The reason that a system doesn't exist outside of phpBB is because it's an incredibly poor way to manage modifications. Your question does not make it clear what you want to gain from this, but since it is your own code, you should definitely not look to copy something so awful.
For “patching” code
If you want the ability to apply updates to your code, then you should look at handling it through version control. For instance, you could develop and test in a local git repository, and once you are happy, push the changes to the server. You have many options here from a basic update script to a fully-fledged Continuous Integration solution.
phpBB have implemented a solution for patching code on your live site via a Web interface, which has many issues with security, verifiability and maintainability among others.
For exposing “plugin” functionality
If you want the ability to register plugins in parts of your code, then you should architect your code as such to allow it to be handled easily. Wordpress, MediaWiki and other projects can help you write such a structure.
I've been using Doctrine since a long time, and always felt the documentation is one its weakest spot. I've no problems myself looking in stackoverflow, irc and even looking at the code directly, but, my coworkers tend to ask me a lot just because the documentation isn't there or is to complicated or vague.
Is there a way I can contribute to Doctrine documentation, btw I haven't found nothing about that in the site, hence this question :S
The documentation is in the git repository over at github. Fork the repo, make changes/additions, and send pull requests.