New "Classic" Components for Delphi XE7. Blog by Roman K. at http://blog.kassebaum.eu/?p=379 (Orpheus, Abbrevia, VirtualTree, SynEdit, LockBox, AsyncPro, PowerPDF). I'm really happy this is happening (and pushed quite a bit).
New "Classic" Components for Delphi XE7. Blog by Roman K. at http://blog.kassebaum.eu/?p=379 (Orpheus, Abbrevia, VirtualTree, SynEdit, LockBox, AsyncPro, PowerPDF). I'm really happy this is happening (and pushed quite a bit).
http://blog.kassebaum.eu/?p=379
http://blog.kassebaum.eu/?p=379
Great idea (and clever strategy by Embarcadero / Marco)!
ReplyDeleteBTW why host at SourceForge when XE7 now has Git built in? Why not host at GitHub?
ReplyDeleteGreat ! Thanks for your efforts.
ReplyDeleteHope CBuilder support as well as Delphi
ReplyDelete! Thanks!
I've been wanting something like this for years. Great that it's finally happened. Good job guys.
ReplyDeleteSam Shaw All of the components support both Delphi and C++Builder. That's a change from the past we asked to put attention into.
ReplyDeleteSteve Maughan I think because other projects were already on SourceForge, but repositories are not all SVN.
Orpheus is Mercurial.
ReplyDeleteI too, wished it was on GitHub, but I'll take it wherever. I used TP Orpheus as a paying customer in the early Delphi days.
Steve Maughan I used sourceforge because most of the original components except VirtualTree where hosted there. I prefer Mercurial to GIT.
ReplyDeleteI thought JAM software were now maintaining VirtualTreeView? Is this going to be a fork or are you guys working together? http://www.jam-software.com/virtual-treeview/
ReplyDeleteHow are going to organise the repositories? It would be nice to have a separate stable branch/tag for each Delphi release. This makes it easier to organise the repositories as externals so that our revisions pull in the correct third party code.
ReplyDeletePaul Thornton
ReplyDeleteYes, I'm alreading working with branches. This is one of the reasons why I moved to DVCS.
Just - great news and thanks!
ReplyDelete:)
I keep getting a 500 when I try to check out Abbrevia? Any ideas.
ReplyDeleteI've aslo blogged at "Open Source "TurboPack" Components for XE7" at http://blog.marcocantu.com/blog/2014-october-turbopack-xe7.html
ReplyDeletePaul Thornton These are forks and should be treated as such. I wasn't given any heads up that they were doing this to Abbrevia and the changes made included things intended to make merging them back into the official repositories more difficult.
ReplyDeleteDitto on branch treatment. I'm not comfortable at all that only the latest and greatest Delphi version is supported.
ReplyDeleteRussell Weetch
ReplyDeleteDid you try
hg clone https://hg.code.sf.net/p/turbopowerabbrevianew/code
Great effort to push customers to buy the newest Delphi. Or to push them away from Delphi altogether...time will tell. I for one thank you for breaking the XE2 implementation of Lockbox. No hard feelings though, Delphi will cease to be relevant in my company sooner or later, and I have less and less arguments to defend it.
ReplyDeleteOliver Holmes
ReplyDeleteYou can still work with your old version. Why do you expect to get updates for XE2?
Roman Kassebaum and XE7 compatibility will always be there, even when XE10 is launched. I can only see positive things from this initiative.
ReplyDeleteRoman Kassebaum just tried again (using tortoise Hg) got further, but asked for a username and password
ReplyDeleteRussell Weetch
ReplyDeleteDo you have a sourceforge account? Otherwise try the zip archive.
Roman Kassebaum
ReplyDeleteI didn't have an old version. I had to look for it in the SF repo. I'm not blaming anyone for nothing, just saying that professional component developers such as TMS don't follow that practice and I'm glad for that. The XE6 version btw claims to have XE2 packages...whis is only true for the filenames. I know that this is just the result of buggy implementation of compiler switches in Delphi...but still.
Oliver Holmes
ReplyDeleteBut I haven't changed the old version. I simply created a new project which now supports XE7. Before I will create a XE8 version I will put the XE7 one in a branch.
OLD:
ReplyDeletehttp://sourceforge.net/projects/synedit/
and NEW:
http://sourceforge.net/projects/syneditnew/
For example(and as I understand it):
1. If someone choose to not to use "new" synedit - always can use the "old" synedit;
2. If I make a backup copy for XE7 - after three recharges I can use "new" SynEdit in my XE10 and... my "old" backup copy in XE7;
This dispute about the old versions and the new versions is a little...
:( ( ??!@#?)
For me this technology is very usable and also very comfortable.
I mean the possibility to get the newest versions of the components as soon as possible after recharging of the Delphi.
Sometimes I choose to not to use the opensource components (in my newest projects and with using of the newest EMB technologies) because they are updated too slowly.
Now if I'm sure that the newest Embarcadero technologies are compatible with this list of components - that is great.
The game changed...
I love this game!
:)
"One reason is to avoid tons of ifdefs."
ReplyDeleteI laughed out loud with that reason.
Roman Kassebaum
ReplyDeleteAh, perhaps I should emphasize again, that I'm talking about LockBox... ;)
Oliver Holmes
ReplyDeleteBut LockBox2 had completely been changed in the past. Someone has created LockBox3 which is not compatible.
Roman Kassebaum logging in did the trick
ReplyDeleteRoman Kassebaum
ReplyDeleteI am using Lockbox 3.4.
Is there anyone on this forum, that nows where to download Virtual TreeView?
ReplyDeleteI followed the link that Marcu is referring to, but it seems broken.
http://sourceforge.net/projects/virtualtreenew/
New home at http://www.turbopack.net
ReplyDeleteTodd Frankson
ReplyDeleteI just fixed the readme. :-)
Roman Kassebaum
ReplyDeleteThat may be, but when creating a new multi-device app, the component tab is disabled....
Even after getting around that, it does not Decrypt a file on android that was encrypted and saved in a win32 XE7 program.
Todd Frankson
ReplyDeleteI split OnGuard into two repos, one for VCL and one FMX. Then the IDE has no problems with it. I think I should do the same with LockBox.
If you like you can send an email to Marco and vote for it.
The encryption issue seems to be a bug. Can you send to me a small test app?
Sure.
ReplyDeleteGive me a day or two to do the small app.
Roman Kassebaum I am having an issue now duplicating the failure...
ReplyDeleteLet me look into this further