AR Libs released on GitHub

-
AR Libs released on GitHub

Hello!

I am proud to announce that a bit of my fiddling around has finally found its way on GitHub.

https://github.com/DeerBear/ARLibs

Please feel free to play with it and tell me what you think.
NOTE: I am totally new to the GitHub desktop client and I can't see the code in my browser - please let me know if you don't see anything.
https://github.com/DeerBear/ARLibs

Comments

  1. Nicholas RingNovember 23, 2015 at 12:19 AM

    Awesome but I have some bad news - there is only a Readme.md :-\

    ReplyDelete
  2. Uwe RaabeNovember 23, 2015 at 12:20 AM

    Lean Code!

    ReplyDelete
  3. Andrea RaimondiNovember 23, 2015 at 12:21 AM

    GROAN! I will try to fix this in a bit!

    ReplyDelete
  4. Andrea RaimondiNovember 23, 2015 at 12:25 AM

    Progress! Try now please!

    ReplyDelete
  5. Balázs SzakályNovember 23, 2015 at 12:31 AM

    /sub

    ReplyDelete
  6. Uwe RaabeNovember 23, 2015 at 1:05 AM

    Works now, thanks! May I suggest to move the units into a subfolder named "source" or "src"?

    ReplyDelete
  7. Andrea RaimondiNovember 23, 2015 at 1:14 AM

    I said "progress"... not that I am done :) I noticed that :)

    ReplyDelete
  8. Andrea RaimondiNovember 23, 2015 at 4:12 AM

    Ok, sorry it took so long but I couldn't work on this earlier :) There's a better division now, especially considering that I am going to post more stuff hopefully soon.

    ReplyDelete
  9. David MillingtonNovember 23, 2015 at 7:26 AM

    Could you expand on the use of the dialogs a bit more please? The readme says it lets you write code like this, "var MyDialog : IMyDialog; begin MyDialog := Dialog as IMyDialog; MyDialog.Display; end;"

    But I don't understand either why you can't do that already with whatever dialogs you implement, or what it gives you - or rather, what it is you're contrasting this to. Is the reason for it that using an interface gives you a much more constrained / specific set of methods, unlike using something inherited from TForm?

    ReplyDelete
  10. Andrea RaimondiNovember 23, 2015 at 7:58 AM

    David Millington, a lot of dialogs have the tendency to appear in several places in the application. Every time you need the same dialog, you have to add it, ensure everything is set, etc. With this technique, you define your dialog interface once and use it anywhere, regardless of what changes have been made internally to it. Also, it allows you to compile a different dialog for the same interface (say, a Lite or a Professional version of the same product) for example. There are  a lot of things you can do with this technique and that would require a lot of fiddling to do in the VCL way.

    ReplyDelete
  11. Andrea RaimondiNovember 23, 2015 at 9:21 PM

    Another great thing of this kind of setup is that it allows new employees to actually add value much more easily: imagine a dialog has to be added in a new place. With the "usual way", the new employee has to find it, add it, ensure it's not auto-created, set it up properly and test it. With this library, it's a cast, setting of a few properties and a call :) That's it. What do you think is easier? :)

    ReplyDelete

Post a Comment