A non-technical question
I have been helped by a few folks (here on SO) with my questions and would like to acknowledge them in my package.
How can I do that, should I add them with ctb (contributor) role, or is there another role available for people who might not have provided actual code/content but have helped in tackling issues.
Thanks
I've been trying to work out why fr:number field breaks in repeating grids. First two rows function fine but from the third row onwards no change events are sent, the value is not saved to fr-form-instance and formatting is not done to the value. I've been searching if someone else has had this problem but I haven't found any mention of this problem what so ever and have not been able to pinpoint the cause of this problem.
So my question: Does someone know if this was a known problem in 4.0.1 and if yes then can it be fixed or circumvented in some way without updating Orbeon?
Our company is using Orbeon 4.0.1 and apparently it's too costly in work hours to update because of some company specific modifications done so update is not an answer I can really use.
You're unlikely to get much help in the community for issues that have been fixed in newer versions. So, I would recommend you first try to reproduce the problem with the latest release (4.10 at the time of this writing).
If you do reproduce it, post about it on Orbeon Forms forum (Stack Overflow isn't really for bug reports).
If you don't reproduce it, i.e. if the problem has been fixed, it will be to you to weigh the cost of upgrading to 4.10 vs. the cost of getting support from Orbeon through a PE subscription.
We have found the limitations of Saxon-HE (see table) at the point of using Extensibility using reflexion and EXSLT extension function.
We are evaluating to purchase few licenses for the servers and development team members and we are short of time to evaluate every tool, considering that purchasing and distributing the license will also consume our time.
Apparently there is a previous version of Saxon called Saxon-B that saxonica is not longer maintaining but it claims to support Extensibility using reflexion and according to this Q&A supports EXSLT too.
My question is, could we stick with Saxon-B (an open-source solution) for those features mentioned or should we purchase those licenses?
Finally I am replying myself.
We have given a try to Saxon-B during last few days and it works perfectly for the needs we have (mentioned in the question). We have not found any minor/major bug so far.
Thanks Saxonica team for keeping available as open-source the Saxon-B version.
Edit: Saxon-B is no longer compatible with Java 8 and above.
Searching online, I see lots of people asking for features to have multiple levels of sub-tasks, and proper sub-task functionality (like FogBugz). But I don't know if it's planned in future versions, or if plugins exist to provide this functionality.
Does anyone know?
we're working on a plug-in for multi-level subtasks. See details and follow us at http://h4j.almworks.com
As for current solutions, you may use links as a very limited workaround. There are also some hacks to allow creation of sub-sub-tasks, see comments to http://jira.atlassian.com/browse/JRA-4446
Update: the add-on has been released in 2011 and went far beyond just multiple hierarchy levels. Currently it's at version 4 and it's one of the most popular add-ons for JIRA. See https://marketplace.atlassian.com/plugins/com.almworks.jira.structure/server/overview
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
During a typical day programming, I implement functions in a way that I would like to remember. For instance, say I tuned a DB insert function that, when I come across the situation again, I want to find what I did to resuse.
I need a place to keep the solution(what I did), and I need to find it somehow, which may be months or a year later. Using a mind map sort of idea, I was thinking about a personal wiki, but then I heard the stackoverflow podcast mention using this site for such a reason. Does anybody else keep track of slick things they've done so that they may find it sometime in the future. If so, what did you use, and in general, how do you use it?
i like to personal blog idea and using the stack for it. i'll try the idea of posting at the stack and then answering it myself, with the benefit of other people potentially giving their opinion.
As long a the stack will be around for a while :)
Jeff Atwood recommends using Stack Overflow for this kind of thing. Post a question (your problem) and then post an answer (the solution you found). This lets you share the information with the world, and maybe get some valuable feedback or better solutions.
(Wow, I got downvoted for repeating what Jeff Atwood said. I won't do that again, I promise.)
I use neomem all the time. I write notes to myself. Then I can later search for it.
You may find these questions useful
Where do you store your code snippets?
Tracking useful information
What is you preferred site for code snippets?
I use a personal Wiki, my del.icio.us bookmarks and my own blog for that. Usually my blog: When I learn something that I know I might stumble on again I write a short post in my blog.
I use WikiDPad or Wiki-On-A-Stick. It works not only for code snippets but also to take notes, record typical problems you get and how to solve them and documentation. Take my word for it, it makes your job a LOT more easier if you have proper notes... and add the power of interlinking to it and you have a killer resource. I have very bad memory and taking notes has improved my performance by an order of magnitude. It also saves you from having to ask someone the same question twice or thrice. Also, if anyone asks the same question, you can just helpfully point them to the wiki and they can read it and add to it if they need to.
The technical term for what you are thinking of is "code snippets", and googling for that will find you many programs designed to store them for a variety of platforms, including entirely web-based ones such as this one.
I set up dekiwiki on a server at work that my coworkers and I use for company specifics stuff but also for general programming tips that arise as well.
A simple wiki, may be useful. SeeTiki Wiki
I always put it on my blog. Not only am I able to get back to it later, there is also a chance that it can help someone else as well.
It's oldschool, but I keep notes in a notebook. Makes remembering solutions (or the problems that caused them) a bit easier. Usually I make 1-2 pages of notes a day.
The digital equivalent of this would be keeping a private blog or journal. Easy enough to add a search program to help you find stuff.
Worthwhile things that my boss might be interested in, like bugs and user calls all get entered into bug tracking software where it is more formally handled.
I use the excellent Trac project management system for my personal projects, and I use it's wiki as a brainstorming and note-taking tool. And, because it also hooks into the Subversion repository and the bug tracking system, I can link from my notes right to a particular section of code or a bug report.
I keep my personal projects on assembla. Wiki, Issue Tracking, Source Control... very useful.
Check to see if your editor has some kind of annotations feature. Ideally you could link a particular location in code with a small note, and store it in a centralized place. If it doesn't, that kind of plugin wouldn't be too hard to build, your biggest hurdle is going to be how to link the piece of code to a file (due to the volatile nature of code) and even that one isn't insurmountable.