I'm a wordpress developer, but for a customer we are gonna set up moodle courses.
Some courses are fine and are linking to other courses on other sites that tracks completion.
But on some courses we are gonna set up a youtube video with vidtrack.
This vidtrack is logging in the database mdl_youtube that the user with id something is stating the video, pausing and reached the end.
It's this END that we are interested in.
None of us has ever been using moodle so this is kinda new.
We have been checking the activity completion in the course but can't find anything that will let us use this logging to the database from vidtrack.
Is this something that we have to code on our own? And where in moodle source code do we do this?
Hope you guys understood the question.
I will answer all the questions that you have in case i left something out or are very bad at explaining the problem.
Have a nice day.
The only solution that seems to me without getting into coding is that, put all your files through SCROM packages in SCO and then divide them into segments.
If it is a long video, this would definitely be a good strategy because even though one cannot force students to actually see the video, at least they would be forced to wait for each segment to end and then click on the next section.
Thanks!!
Related
I am here to ask a question about server-side updates.
When someone make an update to, for example: A Google Play Store's app, the update do not appear immediately, and takes longer for someone than for others.
Same on websites or webapps: When (for exaple) Google updates the YouTube server-side, they say that it may take longer to be applied on your Account.
Why does this happend?, Is something about CDNs? in that case: How much time does take a CDN to replicate the content from the original server? Isn't that immediate?
Thank you so much, if I made any misstake on the redaction, please feel free to correct it.
Thanks.
the update action itself does not take much time, but when a company makes updates they do not leave them available for everyone, but only for a small group of users for test and feedback and if the group is happy with these changes, the testing circle expands and so on until these updates are available to everyone or maybe not. so that's what takes time!
Thank you in advance for reading this. Here is the situation. I have been working on a online guitar shop using Magento CE 1.7 for several months. I greatly underestimated the cost of the site and I know that is my fault not the client who by the way is a great guy. There where many issues that took a lot of time including having to move it from a testing server to the real domain, many logo tweaks etc. I am almost done with it and really need to “stop the bleeding” so to speak however there is one feature that he really wants that I am at my whits end with.
Its a custom order form for guitar pickups. He had one on his old site that was don’t in ASP and besides not knowing ASP we are now on a Unix server.
His requirements are “the ability for someone to choose a category (ie: 7-string, Strat Replacement, Tele Replacement, etc) , and then have it be able to only show options that are applicable to what that selection. I want customers to be able to see descriptions of each pickup somewhere on this page. I also want people to be able to see what the covers/colors look like when they choose that.”
I was able to use the way back machine to at least show you guys what he wants, here is the link http://web-beta.archive.org/web/20120127233223/http://www.axepalace.com/pickup_order.asp
Here is my attempt to create it with a product with lots of options. http://axepalace.com/pickups/bare-knuckle/bkp-order-form/bare-knuckle-pickup-order-form.html
So could anyone please give me some feedback / suggestions. My sanity would really appreciate it!
Whats the best way to start to train an end user in a CMS like DOTNETNUKE?
The end user will want to add edit and delete there own content. They will need to install modules and understand how everything works?
Should i create a manual? is there a way to plan some training?
any ideas?
edit: the end users are VERY I.T illiterate, they struggled to even understand the rich text editor. I need to train them on how to use the form and list module and the HTML module for editting content. They want a document of some sort, this is really old school.
PD24, for what most customers do it usually only takes 5-10 minutes of training. I usually create a couple Jing Videos which is a free screen and audio recording tool. I go through and do voice over as I create a page, edit text, add photos, add modules and record it. Then I send them the links they can reference if they ever need a reminder.
Works great! (boooo to manuals, no one reads those and they take a lot of time to make!)
& DNNcreative is probably too detailed for your client, that's a good resource for DNN implementers.
We have a variety of videos in the video library on DotNetNuke.com you could point users to those for specific topics.
We (DotNetNuke Corp) also provide custom training solutions, we could develop a custom training program for your client that fits the scope of your project and delivery requirements. If you want more info feel free to email me at training#dnncorp.com.
Have a look into www.dnncreative.com, they have some awesome tutorials for developers and users.
I'm new to iOS Development and am trying to make an application that essentially sorts through a list of 300 names or so. I've got the Drill-Down part of the application down, aside from the detailView, but am now faced with a challenge.
What I would like to do is have users select from 3 fields with a UIPickerView to come up with shorter lists for every time a user is looking for a person. I'd like to use a .plist, but I also have an XML feed of the information. Before I waste all of my time structuring these data sources, does anybody have a good overview as to how I should approach this?
Also, I've asked some this question before, and they tell me to read up on introductory iOS development topics. I understand the mechanics of development, I just can't ever figure out how to approach a task properly. (I'm working on it!)
Thanks in advance. I'd share an image to help clarify, but my rep isn't high enough.
Snip: It looks like I misread your intention which makes my earlier comments irrelevant, you want to have the user select one of 3 options to shrink the list, if I'm not mistaken.
Some more questions for you, so I take it that this XML feed is going to be potentially changing between times that the user loads up the app? Will it only ever grow or are those 300 or so names that are loaded once set for good? The reason I ask so that you can maybe see my train of thought is whether or not using Core Data might be useful. You could easily store your large list locally, save time having to reload this large list frequently, and also you can use the built fetchedObjectController to search your collection of names. I'll keep thinking about it and once you get a chance to answer these questions we can continue.
Ill check back for an edit or comment, and see if I can give you an approach. Also, maybe edit your question with any of your own approach ideas and we could also start from there and refine them if needed.
Edit 2: From the information in the comments this is one of the ways that I could see this being done that make sense to me:
Since you seem to be able to control the information you receive from the feed I would set it up to send you only the contacts that need to be added/removed. You could handle this a few ways depending on your deployment intentions but I would go with the following:
Find a way to signal a first time run of the application, and as a result all contacts would be new, and you could populate your list fully with a slightly longer first time setup. Then any further changes could be quickly handled by smaller edits made to the local list.
You would need to set up Core Data for your application, which should be fairly straightforward in your case, and after this you can use the built in NSFetchRequest to do your searches that will then quickly return a list of narrowed down contacts. As for the physical picker that is just a matter of building the UI which will require some design from your end as you are the only one that knows what you are going for in that regard. Depending on the complexity of your app and what functionality you will want to include you could get away with 1-2 views that simply do the displaying of the contacts in a table and then the picker just reloads when appropriate.
I'm not familiar with the implementation of XML Feeds and receiving data from them, but I have done XML Response parsing into Core Data from a SOAP service before and they shouldn't be terribly different.
Regarding resource to get you started should you need them, I would recommend the following:
eBooks:
http://www.techotopia.com/index.php/Objective-C_2.0_Essentials
http://www.techotopia.com/index.php/IPhone_iOS_4_Development_Essentials_Xcode_4_Edition
Tutorials:
http://www.raywenderlich.com/
The eBooks I have linked are both absolutely fantastic and one of the few xCode 4.0 books that I was able to find that seemed to be of an actual usable quality. They both contain easy to follow and clear tutorials on simple and more advanced aspects of programming for iOS.
Ray's site is an immensely helpful resource as it contains both a very active forum base for iOS programming in addition to a constantly growing tutorial collection as there are 4-5 people that constantly are creating new tutorials that the community votes on and suggests every week. It contains some more advanced topics than the above books and I would recommend looking at it after doing a few walk through/tutorials from the books.
I'll stick around if you have any further questions, otherwise you can send me a notification via these comments, or just post another question and someone is bound to help you out!
-Karoly
As I'm starting to develop for the web, I'm noticing that having a document between the client and myself that clearly lays out what they want would be very helpful for both parties. After reading some of Joel's advice, doing anything without a spec is a headache, unless of course your billing hourly ;)
In those that have had experience,
what is a good way to extract all
the information possible from the
client about what they want their
website to do and how it looks? Good
ways to avoid feature creep?
What web specific requirements
should I be aware of? (graphic
design perhaps)
What do you use to write your specs in?
Any thing else one should know?
Thanks!
Ps: to "StackOverflow Purists" , if my question sucks, i'm open to feed back on how to improve it rather than votes down and "your question sucks" comments
Depends on the goal of the web-site. If it is a site to market a new product being released by the client, it is easier to narrow down the spec, if it's a general site, then it's a lot of back and forth.
Outline the following:
What is the goal of the site / re-design.
What is the expected raise in customer base?
What is the customer retainment goal?
What is the target demographic?
Outline from the start all the interactive elements - flash / movies / games.
Outline the IA, sit down with the client and outline all the sections they want. Think up of how to organize it and bring it back to them.
Get all changes in writing.
Do all spec preparation before starting development to avoid last minute changes.
Some general pointers
Be polite, but don't be too easy-going. If the client is asking for something impossible, let them know that in a polite way. Don't say YOU can't do it, say it is not possible to accomplish that in the allotted time and budget.
Avoid making comparisons between your ideas and big name company websites. Don't say your search function will be like Google, because you set a certain kind of standard for your program that the user is used to.
Follow standards in whatever area of work you are. This will make sure that the code is not only easy to maintain later but also avoid the chances of bugs.
Stress accessibility to yourself and the client, it is a big a thing.
More stuff:
Do not be afraid to voice your opinion. Of course, the client has the money and the decision at hand whether to work with you - so be polite. But don't be a push-over, you have been in the industry and you know how it works, so let them know what will work and what won't.
If the client stumbles on your technical explanations, don't assume they are stupid, they are just in another industry.
Steer the client away from cliches and buzz words. Avoid throwing words like 'ajax' and 'web 2.0' around, unless you have the exact functionality in mind.
Make sure to plan everything before you start work as I have said above. If the site is interactive, you have to make sure everything meshes together. When the site is thought up piece by piece, trust me it is noticeable.
One piece of advice that I've seen in many software design situations (not just web site design) relates to user expectations. Some people manage them well by giving the user something to see, while making sure that the user doesn't believe that the thing they're seeing can actually work.
Paper prototyping can help a lot for this type of situation: http://en.wikipedia.org/wiki/Paper_prototyping
I'm with the paper prototyping, but use iplotz.com for it, which is working out fine so far from us.
It makes you think about how the application should work in more detail, and thus makes it less likely to miss out on certain things you need to build, and it makes it much easier to explain to the client what you are thinking of.
You can also ask the client to use iplotz to explain the demands to you, or cooperate in it.
I also found looking for client questionnaires on google a good idea to help generate some more ideas:
Google: web client questionnaire,
There are dozens of pdfs and other forms to learn from