I am trying to move some code into a bower package, and my code depends on prototypejs. Prototypejs is not in the bower registry (or it wasn't-- actually I just added it incorrectly, so this question is a bit like asking how to avoid spilling milk after it is already running off the table). What is the proper way to go about getting it there?
I thought I could just point the registry to the prototypejs repo on github, but that resulted in a checkout of files which did not include a built prototype.js file, and it seems it can't be built with the latest version of ruby/rake. So, one option would be to create a new github repo with the built version (downloaded from the website) and a bower.json file. Development on prototypejs seems to have stalled (according to github), so it is unlikely the author(s) would be doing that anytime soon.
DISCLAIMER
I'm beating my own drum but this should help
My PrototypeJS repo has updates in it as well as can be built using grunt and has the actual finished build files in it. Please take a look and see if it works for you.
https://github.com/jwestbrook/prototype
I would create a repo with as you suggested for now, but still try to submit a PR on the upstream repo.
Related
Working through the learning document on figment.io and am wondering what I'm missing. My thought is that the doc here is in need of some updating, but I could be wrong. First, The GitHub repo that we download in this lesson does not have the path /contracts/rust/Cargo.toml. Second, the repo is also missing a package.json which causes the initial attempt at yarn build:rs to fail. Creating a simple package.json like the following:
{
"name": "my-supercool-package"
}
Gets past the error indicating that the package.json cannot be found, but fails with the following:
yarn run v1.22.17
error Command "build:rs" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Is all of this a part of the test or is the doc on figment.io in need of updates?
You are right, the GitHub repo referred to on Figment does not contain the files and folders that you need to follow the tutorial. I'm guessing the original code on the GitHub repo has been updated since. It also looks like the tutorial on Figment is outdated. It refers to the NEP-4 standard
NEP-4, which is defined in a language-independent way that is more
compatible with NEAR.
However, it is not recommended as it is out of date and does not follow the standards the NEAR SDK has set currently. It's better to follow the NEP-171 standard instead.
That being said, I think I would follow the instructions on the GitHub repo directly. Maybe use the Figment tutorial as a supplement to understand the general principles (though the standard is different.)
I'm kinda new to using composer (but I think it is awesome) so please pardon the noob question.
Folks are requesting exports fancier than csv so I thought I'd install phpOffice excel using composer. But, the master is 'build failing' and the develop is 'build error'. An I correct in assuming the master build failed means I should not install this with composer because it won't work?
In researching this I also found phpOffice spreadsheet, but that appears to be in development still.
Any other alternatives if I cannot use phpOffice excel due to the build status issue?
Regardless of what package you are talking about, if the builds for any of the branches are failing it just means that the builds for any of the branches are failing, that's it.
The master and develop branches may be well ahead of the latest tag, and chances are the maintainers are experimenting with it, and working towards a passing build again.
If you trust the maintainers not to release broken software, then it's safe to use one of the tagged versions, so for example, run
$ composer require phpoffice/phpexcel:^1.8.1
to install the latest stable version.
Note It appears that phpoffice/phpexcel:1.8.1 has been released on 2015-05-01; quite some time has passed since. Whether or not this package works for you, then, is something you have to find out for yourself.
For reference, see:
https://packagist.org/packages/phpoffice/phpexcel
I am new to xamarin and using XLab packages. I can see that Xlab packages are not stable yet however community is strongly supporting. In test
project I have added packages using Nugets. Now I found one issue in camera API of it so, how should I fix it. I have just
library files so, I can see code or fix it immediately.
Should I include the code of it? Because I can't wait for community to fix the issue and get the updated package of it? Yes If I will fix something then
I would love to contribute to open source community.
FYI: I am using PCL approach for development.
Best option would be to fork the GitHub repository and work on the sample application.
You can also get a copy of the source without cloning but then you cannot create a pull request for any code fixes. You can still report any bugs you find but it will be easier to contribute to the project by forking the project.
In anticipation of making some modifications to ckeditor, I'm trying to build it from source, as described in the documentation here. I want to build a version that is, as nearly as possible, identical to the version I already have installed on my production web server, so there won't be any surprises when I deploy my modified version later. Here are the steps I've followed:
Clone the git repository
git checkout 4.3.3 (this is the version on the production server)
copy the build-config.js from the production server to ckeditor-dev/dev/builder/ (my production version came from the online builder; the config is at http://ckeditor.com/builder/059ce76c63ea2ff01636265c46f713c5)
cd dev/builder ; ./build.sh
there were complaints about missing plugins (scayt and wsc) so I downloaded them as zip files (scayt_4.3.3.zip and wsc_4.3.3.zip) and unzipped them in ckeditor-dev/plugins
tried ./build.sh again
It apparently completed successfully, but the result in release/ckeditor is not a match for the production version as I had hoped. It contains a lot of plugins that I didn't ask for, and I know they're not dependencies of plugins I did ask for because the production version works fine without them. For example, I have release/ckeditor/plugins/adobeair which is not mentioned in my build-config.js.
The main ckeditor.js file is not a match for the production version either. i can see that part of the reason is that there is a different timestamp and version string ("4.3.3 DEV"), but there are lots of other changes too, which I can't easily examine because it's minified. And I can't really trust that this file was built correctly, since the plugin list wasn't built correctly. Also I can't break the build process down into smaller steps find out what it's doing because there's no source.
In a desperate move to try to understand what's going on, I reduced the plugin list in build-config.js to just the about plugin and ran ./build.sh again. This caused release/ckeditor/plugins to get even bigger!
Can anyone explain why the build.sh can't give me anything close to the version I downloaded from the online builder?
(By the way, this question is here instead of on the CKEditor support forum because they wouldn't let me post it there. Called me a spammer!)
CKBuilder which is used by the build script in https://github.com/ckeditor/ckeditor-dev is exactly the one which is used by http://ckeditor.com/builder. The difference is caused by different arguments passed to it.
By default CKBuilder adds all plugins, even those omitted in build-config.js, to the package, although it doesn't merge them into the ckeditor.js. They are available to be enabled on demand. So ckeditor.js is not bigger than that downloaded from http://ckeditor.com/builder.
To build a package with only those plugins which you specified in build-config.js pass -s option to the build script:
> ./dev/builder/build.sh -s
You can also check other options:
> ./dev/builder/build.sh --help
As you'll find there it is possible to change the version, leave JS and CSS unminified etc.
PS. Sorry for the spam filter on forum.
I just installed red5 on my server, and the install seems to work fine. As you can see here: http://onelifemedia.com:5080
I got this far by using this walkthrough: http://www.webhostingtalk.com/showthread.php?t=1046590
The /demos page gives me a 404 error. So I logged onto the server, and checked to see if the "demo" directory was already there. It was not.
The applications that I installed were a directory up from the root directory. I'm not sure if this is right or not.
Either way, my end goal is to actually get something working besides the main page. If I can get the demos to work, then hopefully I should be well on my way.
I guess my questions can be broken down like this:
Does anyone know how to get the demos working?
Should I forget about the demos, and try to start writing my own code?
If I should write my own code, how should I go about installing it? Since the installer is not properly installing the demos.
Thanks
The tutorial is good but you dont need the admin app. Use the installer link in the tutorial and install the demo you want to use. The content of the "demos" directory is only the swf files used to access the server demos which you use the installer app to install. For instance , select "oflaDemo" and then from the main page navigate to demos/oflaDemo et voila.
I know I'm biased being a core developer, but we've attempted to make the server as ez as possible to use.
I could install demos from the latest svn trunk, Checkout the source, use ant&ivy to build and run the server and you can install two sample apps(oflaDemo and SOSample).
You may need to use ivy commands resolve some of the common issues during installations.
E:\dev\red5\java\server\trunk>ant ivyclear dist
()Red5 user mailing list may help you, because this is not exactly problem with Red5 source.
()http://stackoverflow.com/questions/11156222/red5-demos-not-working/11935532#11935532
I could resolve the issue based on the information in Red5 users mailing list and comments by Mr.Mondain in one of the posts in Stackoverflow