Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to use an approval workflow to accept or reject additions to my sharepoint site. The caveat is that I don't want any changes that are pending approval to appear. Only changes that have been submitted and approved should be visible to others who open the page.
Is a workflow the best way to go about this? If it is, what do I need to change from the OTB Approval solution to have only approved changes be visible? Or is this a code-only problem that I need to dig deeper to solve?
I'm currently testing this with a Calendar web part, but the solution to this could potentially apply to any other type added to the page.
The way I see it, there are two requirements:
Being able to change your site and have the updates only visible to a select few
(optional) A workflow to handle the process.
So the first requirement could be handled by the SharePoint Publishing Infrastructure. Take a look at the interwebs and see if that would work for you. You could also just require approval for items added to the library where your pages are stored but that doesn't seem as straightforward.
I mentioned your second requirement being optional because it might be overkill depending on your situation. You would want to require approval on the library, then attach a workflow to the library. But if you're in constant contact with the approver(s) otherwise, it might be just as easy to say "he dude, check out the 'About Us' page, if you like it, click the approve button in the toolbar".
Hope that helps. There's probably a bunch of different ways to go about it.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I need help being pointed in the right direction (to the right documentation or tutorial) since I don't know exactly what this programming would be filed under.
Basically, I saw an app that had a section of 'Deals' on food and drinks at stores. You had to use the app to redeem the deal, but you could only use the deal once. It seemed that the table view of deals was being populated by a PList from a server (because it is constantly updated) BUT when you choose a deal and use it, it disappears from the table view (because you claimed it).
Now I was thinking it could be coding using an if else statement declaring integer values (and if they weren't equal to the integer, then the deal wouldn't display) but that can't be the case because if I close out the app and reopen it, the deal still isn't in the list. Am I right in assuming that somehow the PList or database is being updated by the user interaction? Are databases for each user being created when someone downloads the app (or starts it)?
I'm kinda in the dark about it and trying to figure out how they pull this off. I'm not sure if I'm way off base and there is some sort programming that I'm possibly not even aware of. Any thoughts? Thanks!
You should investigate NSFetchedResultsController - it allows to perform a lot of pretty things with your data + database.
Check this tutorial.
Also, take a look at the Apple documentation.
Core data basics strongly required.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
First and foremost, I would like to say I am very, /very/ new to programming and the like. If I decide to build this, this would probably be my first "large" project i've ever done myself.
What I am looking to build is a very simple Chat/IM client to use for the users in our office network. It would just call us their Windows logon name and use that to IM and the like. I'm talking a very simple client, with a list of names of people who are logged into the network, and option to IM them and an option to do a multiple user chat. It doesn't have to be visually stunning.
How difficult would this honestly be? Is it possible for me, someone who has very little knowledge when it comes to programming to teach myself how to build it?
If not, can you explain why this would be very difficult and what already built clients would work well for what I am using?
This is a big application. Your first parts will suck and refactoring it later will suck even more. I suggest building something small in the first place and then step from one bigger project to another.
XMPP/Jabber is IMHO the best solution for office IM. Most clients like Pidgin, Adium etc can connect to it. Every bigger company I worked for in the last years used it. Take a look at Openfire - A free open source XMPP server that you can directly connect on and which is easy to set up: http://www.igniterealtime.org/projects/openfire/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am going to be taking over from a developer here at work soon. Hence, I'll be supporting all the applications that he has written over the last few years.
My question is, when supporting an application that you probably don't know much about, what kind of documentation is most helpful to get a handle on how to fix problems, extend functionality, modify functionality, etc? I'm thinking it would need to give you an overview of what the software does, what interfaces it has to other software, what databases it uses, usernames, passwords, and so on.
Is there such a thing as a software support document? Referrals to any templates would be most helpful.
BTW, unfortunately, there are no requirements documents, specs, etc! So, really my question is, if my colleague had a day to write a single document for each application so that I could (more easily) support it, what would that document be and/or what would it look like?
I would ask for primarily some sort of flow chart/schema of the way the app functions.
I would want to be able to know how each file interacts with other files (and the database). So this way, you'd know where to start to fix a bug or add a new feature, etc.
So to do a quick, text mockup of it:
Index.php -> Login.php -> Dashboard.php
Index.php:
Has login box. Submits login into to login.php
Login.php:
Verifies data with database entries, shows error on fail or sends to Dashboard.php
Dashboard.php:
Once logged in this acts as a main menu
Something along these lines? For basic documentation I'd think this is the way to go.
Hope this helps. Good luck!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I have looked at some autofills for Firefox. But they are not designed with the developers' needs in mind. General internet surfers will need a tool to fill in many different forms with constant values for each form. Developers need exactly the opposite, when you want to test a part of your app you'll need to fill a single (or a couple of) forms many times with different (but valid and sensible) data.
So, does such a thing exist? An autofill to fill form inputs based on perhaps a class name (email, password, address, url, ...)?
I strongly feel if it doesn't exist someone should roll up their sleeves and make one! I for one will put in my share if some others want to team up. But right now, I am desperately in need of one if it exists
Pretty nice extension for chrome Web Developer Form Filler especially for web-developers.
You can save as many sets of data as you want, assign a hotkey and fill a form just by pressing it.
https://chrome.google.com/webstore/detail/web-developer-form-filler/gbagmkohmhcjgbepncmehejaljoclpil
Why not just go with a bookmarklet like https://github.com/dsheiko/autofill
it's a dead simple script that serves me fine for years
One way is to use Greasemonkey.
Example script:
"Auto Fill any forms with custom information":
http://userscripts.org/scripts/show/39313
EDIT: Link may be broken but I'm sure you are capable of finding many Greasemonkey references.
Please check out my extension, Form Filler, which allows you to do exactly what you need: fill out your forms with random dummy data.
https://chrome.google.com/webstore/detail/form-filler/bnjjngeaknajbdcgpfkgnonkmififhfo
I think you will love IRobotSoft web automation software. See a similar question here:
http://irobotsoft.org/bb/YaBB.pl?num=1254517661
This is an auto form filler you are looking for. But this is a chrome plugin. This takes care of the developers need to fill valid data automatically by reading the properties. It also saves value against the form element if you make changes to it. Hence a must try for developers. Here is the link
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm planning to create a custom system for comments. I was wondering about comment moderation. For approving comments, is it as simple as just creating a field called "Moderated" in MySQL?
What's a good suggestion for countering spam? Akismat?
If you design your columns to have a status column, so only approved comments are displayed, then you could use a DATETIME column called approved date:
COMMENTS table
comment_id, INT, primary key
comment_detail, VARCHAR
approved_date, DATETIME, NULL
This way, you know it was approved and when. But it also relies on staff to approve things before they are visible. It's unclear if there are other statuses involved in your proposed comment system - if there are, it might require a COMMENT_STATUS_CODE table.
You could use a bit field called Moderated which has 0 for unmoderated and 1 for moderated. Then, from your app, simply query those comments which have Moderated = 1. There are various ways of countering spam, which also depends on how you're moderating comments. If you're manually reading each comment before they appear on the site, then spam wouldn't really get through to the site itself, but it could still get to your inbox. You could use a Captcha program such as ReCaptcha. This will make it trickier to submit multiple comments with a bot.
It's highly depend on your site traffic.
Yep, a 'moderated' flag would enough if your traffic is low now, but later you should look forward for another technics (captcha, spam dbs etc, filter apps).
You can check the comments manually, and thats the best, but later you cant check every comments.
But I dont know anything about your site traffic.