In Blogger, I need to edit a page all the time, because of frequent updates. Each time I want to edit the content, I am redirected to the editing page, like what happens on a Stack Exchange site for a new user trying to edit content.
Is it possible to add a real time quick--inline (Ajax?)--editing customization to Blogger, like the one a Stack Exchange user gets at 2,000 reputation (See the attached picture)? This will help me in reducing lot of unwanted wastage of time.
Edit: I searched for inline WYSIWYG editors, and found TinyMce; but don't have proper idea on going through the process of integrating it. The process of integrating it is going through complex steps, if anyone has any quick steps for integrating it, it will be helpful.
Picture Link:
Quick Edit in Stack Exchange at 2,000 or more reputation
Edit (2/2/17): I am now trying Open Live Writer, which doesn't give inline editing ability inside the site itself, but instead in its own field interface with the looks of the original blog. This doesn't help in seeing the blog being updated live in the web, but it will be updated even if not seen. To see it we need to make an extra step of looking it in the web, this is still a step which could be eliminated. This is better than before, but I am still looking for inline editing within the blogger site as like StackExhcange does.
As the creator of the question said on the comments, he asked the question on Google Product Forums and the formal response was:
There's no such a native feature available for inline editing.
There's no Blogger plugin supported that could resolve the issue.
The full response can be found here:
https://productforums.google.com/forum/#!topic/blogger/nzGbwr92zjY;context-place=forum/blogger
Related
Apologies in advance for code overkill. I don't have any idea where the problem lies, so I'm just going to have to paste in the whole thing. I don't think what I've been trying to build is particularly complex- but I AM now particularly out of my depth. I got misled when the previews at Email On Acid looked fine all along as I was busy editing away, copy pasting code and viewing the result as I went along. But when I sent the email to my Android device there wasn't any stacking for the small screen. All three columns are rigidly there and the text has not adapted.
I've realised belatedly after researching this as much as I could and reading an excellent article on table-based spongy/fluid design by Nicole of Merlin of Email Wizardry that media queries are not good. The template I used in EOA has them unfortunately. And now I need to repair my email newsletter before I get lynched by the committee of the non-profit I am carrying this out for gratis.
I could give up trying to build it to spec and head over to Mosaico to make something generic, but this email newsletter at least needs to contain internal links!
Could you have a squizz at my code and give even a general pointer as to where I might have gone wrong and what to do to fix it?
Thanking you in advance. Code to follow by attached text file:
...actually the code won't even paste in here: 'formatted wrongly' I can't find any option that will allow me to communicate the code to other users here. Tried getting the content temporarily hosted, but they had a character limit my project exceeded. Could attach text file if I could find a way. Apologies for the noob questions! But really want to complete this!
This is the first time I am trying to contribute to Mozilla. I went through several articles and documentation/resources to get a hang of what could be the best first steps to get started. I started off from this page http://whatcanidoformozilla.org1 and chose to start off with Java.
On initial tinkering I was taken to https://wiki.mozilla.org/Mobile/Get_Involved and eventually https://wiki.mozilla.org/Mobile/Fennec/Android/Suggested_workflow resource suggested that the best way to get started with it would be to pick up some simple bug and propose a patch for it.
So then I went to http://www.joshmatthews.net/bugsahoy/?java=1&simple=1 and this specific bug drew my attention. The description of the bug mentioned this :
There are some methods that we share (or can share) across our DB
implementations, like appending PARAM_SHOW_DELETED, PARAM_LIMIT, or
PARAM_PROFILE.
These are currently spread across LocalBrowserDB, TabsAccessor,
URLMetadata, and so on. It'd be nice to clean these up.
Question 1. Now how do I get some more context on what exactly is the bug and what is required to be done ?
As of now there seems to be 2 patches already submitted from what I understood (and please correct if my understanding is wrong here). So to get some context about the bug I went ahead and opened up the first patch submitted here.
It gave me some idea as to at least where exactly is the code itself that needs to be fixed. And I found it here
Question 2. Am I on the right track on how to figure out the code that needs to be fixed ?
Question 3. Even after reaching the DBUtils.java file I could not find any documentation about what the class basically does, or where does it fit into the whole picture. Could someone please help me with this, as to how do I figure out what a class is supposed to be doing etc. or at least some documentation around it?
You're on the right path. Basically, the What Can I Do For Mozilla website is a quick and easy way to let you discover projects you might be interested in, so it's the first gateway to the coding contributions.
That said, you did good in picking a bug to start off. However, as you saw the bug was already being worked on by somebody else (marked as Assigned). Your best bet is to find some new "good first bug" to work on. This might be a complicated task, as Bug's Ahoy shows only a few not owned good first bugs.
You should try to get in touch with the Fennec team, either via email or IRC (the latter for quicker responses).
Now, to answer your questions, in a more general way
Question 1. Now how do I get some more context on what exactly is the
bug and what is required to be done ?
Usually, this should be described in the first comment in the bug, on Bugzilla. If that's not the case, feel free to drop a message there and ask for more directions. You can also flag the reporter or the mentor of the bug using the needinfo functionality, as they are usually better shown.
As you can see, somebody asked for more info in comment 1 and some new directions were given.
In general, you won't find a patch with code on the bug itself, but you might find links to files and more precise directions on what to change and how. If not, again, feel free to ping the reporter and/or mentor.
Question 2. Am I on the right track on how to figure out the code that
needs to be fixed ?
You're on the right path. In general, if there are no links to files or DXR on the bug, but some code is mentioned, you can look it up using DXR, as you did.
Question 3. Even after reaching the DBUtils.java file I could not find
any documentation about what the class basically does, or where does
it fit into the whole picture. Could someone please help me with this,
as to how do I figure out what a class is supposed to be doing etc. or
at least some documentation around it?
What I usually do when navigating the Firefox code and need some more background on a not so well documented class, is browse the change log for that file, clicking on the Log button in the top-right panel on DXR (when displaying the file). It will show you a list of bugs that affected the file. You can even trace back the original file that implemented it, to get more context.
On the other hand, if you're only interested to the history of a single line of code within a file, then the blame tool is your friend. It tells you who last touched the line, the changeset and the related bug number. That is also accessible from where you can find the Log, here.
In the case of DBUtils.java, however, it looks like the class just holds some utility functions for database access.
To see how something is being used within the Firefox codebase, you can still use DXR. Here's a sample search for the DBUtils object.
I am currently in an internship and making a website for someone. I have nearly finished the website and they would like a way to easily edit the website without messing around too much with code. They have no development team and once my internship is over, obviously they'll be stuck and they would like a way to edit the content on the website. How can I go about doing this? I mentioned a WordPress site to them but they didn't like the sound of that. Are there any other ways in which I can allow them to have this functionality?
Cheers
You can either create a Wordpress-similar, with a login, and while navigating through pages they would have options normal users do not have (e.g: delete, etc).
Or you could create an admin dashboard, where there would be every settings.
I think the second one is the best option for you, as it doesn't require you to modify any pages already created, and you will not have to adapt the style of your website to those supplementary options which would be shown on every pages if you used the first option.
Edit:
Or you could have all the content of the website in files, so that they simply need to edit the files to change the content. Even though I think option 2 is better, this one is a lot simpler to put in place.
I remember reading a while back on some random website about a program that would look at multiple pages on an HTML site and detect the differences/similarities between the pages to automatically detect which parts were template "boilerplate" and which parts were new content, and then based on this, automatically spit out just the parts that are content.
Unfortunately, I didn't remember enough details about this utility to actually find it on google, so I wonder if any of you guys have run across anything like this, and CAN remember the name of it.
Thanks.
Murphy's Law (or is it some other law) has stricken, and I've found it just moments after I'd given up and posted this question. The project I am thinking of is this:
http://code.google.com/p/boilerpipe/
Thanks.
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
The reason for asking this question is to get a good idea about how best to present an open source project for my own projects. How can one best make a project attractive to potential new users and/or developers? Clearly projects vary in nature and scope so when answering it may be necessary to qualify any suggestions which are contingent on these factors.
It would also be interesting to see some good examples of the best presented projects out there!
Here are some things that I look for on the landing page of an open source project, in approximate order of priority
Elevator pitch: what does this software do
Download link for the latest version
Latest news; what's new in new versions
Documentation link
Link to discussion boards/mailing lists/bug tracker; how to talk about it and report problems
Link to the source code/revision control system
Explain what it does, probably also by explaining the problem it solves. If you can do that in big type (somewhere between the size of a Stack Overflow question heading and the text of the actual question) in 2-3 sentences, so much the better, you can link to the "learn more" page where you do the deep dive.
Make it very easy to download a copy and get started. (A big "download now" link is good. MoFo did this very well with the Get Firefox site and that pattern has spread appropriately. If it's a package install e.g. a Ruby gem, spell out the steps.)
Show where people can go to ask questions, and/or the documentation. You do have documentation, right? (Or you're working on it?)
Beyond that, link to the necessary stuff: code repository for those who want to browse, a more detailed "about" page (that might be part of the documentation), list of contributors (might also be part of the documentation) but the big part is to answer Why and How as succinctly as you can.
Basically, that's the story. Your first page is the first slide or two of your presentation.
For new/potential users:
Overview or outline of what it does (the pitch)
Screenshots or examples of some core features
I think the majority of your returning visits will be from developers using your project; think of what you as a developer might need:
Clearly visible link to download latest build or source
Link to your SCM repository & how to contribute
Link to API docs
Link to issue tracker
Users of your project are interested in this things, in order of purely subjective importance:
Downloading your apps
Knowing what your apps does (project descriptions, screenshots)
Get Help and Documentation
How to report bugs
How to get access to the source and to contribute
How I would do it is to have a huge download link in the first page, with a short description of what your program is (max. 1-2 paragraph). Then there should be a link in obvious place longer description; forum/mailing list and documentations; and how to contribute and to report bugs.
Rationale
Why download links first instead of project description first?
Your user likely come from two sources:
articles referring your project, or your project announcement forums
search engine
In both cases, it is very likely they already have an idea of what your project is about before landing on your page. In the first case, they have read the article; while in the second case, they are searching for a tool similar to your project.
However, for the second case, it is likely that they are still not sure that your project really are what they are looking for; that is why you add a brief project description on the side of the download link. This is to ensure them your project is/is not what they are looking for.
Why "Help and Doc", "Bug Report", then "Contribute"?
That's the order that user will do when they have problems with your program. First, they will look at the help and documentations, then maybe ask a few people in the forums; failing that, now they will file a bug report or feature requests; then if nobody took interest on the bug report/feature request, some will then have have the willingness to contribute.
You can get ideas from:
Open Office: http://www.openoffice.org/
Firefox: http://www.mozilla.com/
Sourceforge: http://www.sourceforge.net/
Google Code: http://code.google.com