I was asked to do a system that have an approval cycle , for example resignation form , so multiple people must approve parallel or sequential , what is the best and fast way ? to use a workflow engine or to build something from scratch

@TomW I will definitely take a look & as far as I remember I didn't get any good documentation and there is some complexity on setting GLOBAL_VARIABLE or things like that & it is not straight forward. But I will try with this api. And will keep update you.

@Squirrelkiller Android is so straight forward. They have their own official sdk & for C#..it is history. And also not straight forward as android, currently I have this much info. I will keep posted.

@CaptainObvious I don't logically see any purpose behind it, especially with a copying function, but it was given to me as a requirement for this specific copying program I'm making. They didn't give me details as to why it should be recursive

It's probably one of the worse application concepts that would need to be made recursive but I'm still trying to achieve it

@CaptainObvious I was just told to make a file copying facility which would contain a recursive algorithm to copy the files. That's all the information that was available other than general things like functionality of the program which I've met all of

@zadders Yeah, I Think @CaptainObvious is right, and the intention was that the file hierarchy would be traversed recursively, not the file copy itself. But there really is no reason not to go and clarify.

WPF noob question: I'm learning about data bindings, but I don't understand where/how to construct the object responsible for the content. A WPF window/page/usercontrol seems to only allow parameterless constructors, and data bindings seem to go to local properties or again things with parameterless constructors. But many user interfaces only make sense with some sort of content to work on. What am I misunderstanding?

For example, I have a UI that works on a certain kind of file. It is only meaningful with such a file specified. I don't understand where to pass the information which file to work on.

@CaptainObvious So, like a two-step construction? I would construct the window/control, then it would have no data (which is probably invalid/not meaningful in some form), and then I'd pass it the object?

I'm just trying to wrap my head around this situation: user selected a file. I now want to create a MyFileOperatorClass, constructed with the file as a parameter, and the main window's content should switch to a UI appropriate for operating on this type. What would be the standard way to execute this change? Construct the class, then the new UI, then set the UI's DataContext to the class?