i want to know..
how can i know SCORM version that are my company use?
and I want to know the latest version of SCORM..
Because i read moodle docs but dont know how to check it
If you are trying to determine which version of SCORM some content is using, the easiest way is to look at the contents of the imsmanifest.xml file.
There are some templates for what the manifest files should look like for different versions here. You can also probably tell by looking at which set of XSD files are included with the package as those will vary between SCORM versions as well.
A simpler way is to import the course into the freely available SCORM Cloud. Launch the course from the "SCORM Test Track Sandbox" section and then click on "View Debug". Expand the Activity Data tree until you see the "Course Information" node and it will tell you which learning standard the course is using.
If you are trying to determine which version of SCORM your LMS supports, the easiest way is to just ask your vendor. You can also just try importing packages of various versions to see what works. Sample content from every version is available here. If you are referring to Moodle, I know that they have support for SCORM 1.2 and very basic support for some of SCORM 2004. If you need full SCORM 2004 support in Moodle, look here.
Related
I'd like to use ag-grid community in plain JS project, which could be commercial soon. I don't know much about license policies.
From documentation I could suggest that community library is stored here?
src="https://unpkg.com/ag-grid/dist/ag-grid.min.noStyle.js
Further, I'm intersted in Tree Data (Legacy) feature, which is free. But it's source library looks like:
src="https://unpkg.com/ag-grid-enterprise#18.1.1/dist/ag-grid-enterprise.min.js
Am I breaking the license rules using this feature? How should I use it correctly? What if I use enterprise lib in non-commercial project, would it work?
You can indeed use the old tree data implementation without the enterprise version, there's a quote I didn't notice before which sums it up:
https://www.ag-grid.com/javascript-grid-tree-data/
How Tree Data is managed in ag-Grid was changed in ag-Grid v14. This
page presents the new way of working with Tree Data. The old way was
part of ag-Grid free, the new way is part of ag-Grid Enterprise. The
old way is deprecated but you can still use it, but we will not be
enhancing it. For documentation on the older version of the grid prior
to v14 see Tree Data (Legacy).
In their demo of old tree data, the JavaScript file used should really be the "community" version instead of the enterprise one. They just use the enterprise version in all demos to make it easier.
I'd like to know where to find a "table" that lets me know if a specific opcode is compatible with a specific version of the IBMi O.S.
Example:
LEAVESR introduced in V4R4
Is there anything like this?
This may be of use to you. This page is a list of operation codes available to the RPG compiler in IBM i 7.3. There is a dropdown towards the top that let's you select a different OS version.
This would allow you to compare operation codes between OS versions.
You can also use this What's New page to see every version back to V3R2.
I'm not aware of anything quite as specific as your question, but all elements are documented in a similar way in the ILE RPG Reference manual. The link is for ILE RPG for IBM i 7.3, but earlier releases have the same section according to the release. So, having just the latest gives you essentially the complete list of changes for all releases.
If you download a .PDF every few versions/releases, you can have a full history of "What's New" even if some future release truncates the section. If you think over the latest section, it should become clear that just having new op-codes isn't totally sufficient.
My team is using more and more NuGet packages as a way to break the system into smaller pieces and share things between parts. We have adopted a sort of SRP principle for packaging, creating small and hopefully cohesive packages that do just one thing (logging, auditing, security stuff, etc).
Ideally they should be so cohesive and self-contained that it would be straightforward to know what package will contain what you need. However we are not yet there and sometimes is difficult to know what package you should add to access some functionality.
My question is: is there any way to publish and navigate package content information? Like, for instance, in MSDN you can see what assembly contains a class. Would it be possible to know something like that, at the package level?
Thanks.
It's a very localised version, but there is a package searcher for the ASP.NET 5 packages hosted on NuGet. It might be possible to host a version that looks at a wider scope at some point.
https://packagesearch.azurewebsites.net/
The closest functionality I can think of is implemented in ReSharper. However it can only search the packages in nuget.org(closed issue on GitHub). Since packages don't expose type info, JetBrains built a custom index and that's the only data source it can query.
InterWorks has a Workbook SDK as part of its Power Tools for Tableau product. Does anyone know how they are able to do this? The SDK can access a workbook without Tableau Server so I don't think it's the JavaScript or REST API.
A Tableau workbook (.twb) file is in XML format. The structure may change between versions, but is relatively straight forward to follow. Most Tableau file formats are also XML. The formats ending in an x (like .twbx) are zipped directories that contain the XML file along with other files.
This means it is not too tough to read information from these XML files, or even modify them. I've edited them by hand in rare cases. Usually there is a better choice than hacking the XML internals, but you can. Just backup your file first, and don't expect Tableau support to help you if it leads to strange behavior on your workbook.
In addition to the Interworks SDK (which is a COTS product), Chris Gerrard published a free Ruby library for accessing Tableau workbooks https://rubygems.org/gems/twb (or gem install twb) and released the source on github https://github.com/ChrisGerrard/TWB, along with a few (but not all of) the scripts he's written that use the twb classes https://github.com/ChrisGerrard/TableauToolsRuby.
Chris gives some useful examples and scripts on his blog Tableau Friction, including this clever article on automatically documenting the relationships among calculated fields
http://tableaufriction.blogspot.com/2015/02/more-calculated-field-analysis-fields.html
Using twb, you can write simple Ruby scripts easily to look at workbook structure. Since Tableau can change the format when they release new versions of the software, using the SDK or twb Ruby gem could isolate your scripts from changes to the format.
Tableau has also released a Document API that supports a modest number common changes to workbooks - so you can write a script to say, update the connection string on a set of workbooks.
So you have at least four choices:
Use Interworks SDK and tools that come with support, documentation and a price tag.
Use the free open source twb library, and either reuse existing Ruby scripts or develop the ones you need. And hopefully contribute the source if you extend.
Roll your own XML parsing scripts.
Use the Tableau Document API if it supports your use case. https://github.com/tableau/document-api-python
In all cases, do backups and be prepared for some adjustments when Tableau releases a major or minor version update. Patch releases are pretty safe.
Is there an extension that would check whether there are newer versions available to the installed extensions on a Joomla site, and would notify the site administrator?
Ideally, I am looking for something similar to Drupal's "Update" module.
I understand that there is no central place for keeping all these modules and their versions for Joomla, but at least a lot of them are available on the Joomla Extensions site, along with the needed information, so perhaps somebody wrote a tool that checks that source?
Aha, looks like this is to be included in Joomla 1.6, according to this description (check out the "Find Updates" button, looks great).
But if you are using Joomla 1.5 until 1.6 is stable check out: http://extensions.joomla.org/extensions/core-enhancements/installers/9332
Excellent for keeping components up to date :)