Archive for March 6th, 2014
Posted by jpluimers on 2014/03/06
The @appmethod secret.
Wow. Out of the blue, I just read Embarcadero Launches AppMethod, A New Multi-Device Development Platform For Native Apps | TechCrunch. And I’m impressed.
In short:
At SXSW 2014 (which is running now, its agenda has a schedule from March 7th till March 16th), Embarcadero announces appmethod, to be released in beta on March 18th, 2014 for building native cross platform applications. Many have found out you can apply for the beta at www.appmethod.com.
More and more people are bumping into the appmethod link, for instance on FaceBook, on Google Plus, at Delphi Bistro and #Appmethod starting with the @appmethod secret by Joy Ruff.
Below are a few my observations from following all of the above links. Read them, especially the TechCrunch. I expect interesting posts from others to follow really soon now (:.
I’m only a few hours ahead of you readers, but I’m having a positive vibe just for these reasons: Read the rest of this entry »
Posted in Android, C++, Delphi, Delphi XE5, Development, iOS Development, JSON, Mobile Development, Object Pascal, OS X FMX, Pascal, SOAP/WebServices, Software Development | Tagged: embarcadero, Multi-Device, TechCrunch | 15 Comments »
Posted by jpluimers on 2014/03/06
Like When DelphiSpeedup cannot register itself in Delphi on Windows Vista/7/8, GExperts also had problems installing on Windows Vista and up when Delphi runs in a non-elevated account.
It said it installed fine, but it didn’t get included when Delphi was started. The reason was that it got installed in the wrong root key.
What happened is that GExperts installed itself into the HKLM root:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Borland\BDS\5.0\Experts]
GExperts=C:\Program Files (x86)\GExperts for Delphi 2007\GExpertsDelphi2007.dll
But it should have installed itself in the HKCU root: Read the rest of this entry »
Posted in Batch-Files, Delphi, Delphi 2007, Development, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2014/03/06
When using the Windows FIND console application, it will insert a dashed line
C:\Users\Developer>echo Foo > %temp%\foo.txt
C:\Users\Developer>find "Foo" %temp%\foo.txt
---------- C:\USERS\DEVELOPER\APPDATA\LOCAL\TEMP\FOO.TXT
Foo
This is really annoying when using FIND to parse files, and redirect the output fur further processing.
But there is a way around it, as find will not emit the dashed line when it the input is not a file, but stdin: Read the rest of this entry »
Posted in Batch-Files, Development, Scripting, Software Development | 1 Comment »
Posted by jpluimers on 2014/03/06
Interactive map of Raspberry Pi showing which components is what. Hoover your mouse over the board to see the meaning of the components.
RaspMap – Raspberry Pi Component Map.
–jeroen
Posted in Development, Hardware Development, Raspberry Pi | Leave a Comment »
Posted by jpluimers on 2014/03/06
Consolidation of HDD manufacturers (image from WikiMedia)
Earlier this year I wrote about Accessing Mac Hard Drives from Windows 7/8: Boot Camp Support Software 5.0.5033 and mentioned that there are also a few solutions for writing NTFS volumes from Mac OS X.
Thanks to dhardy03, I learned that Seagate now provides NTFS drivers for Mac OS X for Free. The installer name indicates it is an OEM version of the Paragon NTFS drivers for Mac OS X.
I’m not sure yet if it works only on Seagate drives, but since the only other HDD manufacturers left are Toshiba and Western Digital (Toshiba is a much smaller HDD manufacturer than WD and SD), it is a substantial part of the market.
I might try NTFS-3G as well, but that hasn’t been updated for a while and has been replaced by the commercial Tuxera product.
–jeroen
via:
Posted in Apple, Mac, Mac OS X / OS X / MacOS, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, OS X 10.8 Mountain Lion, OS X 10.9 Mavericks, Power User, Uncategorized | Tagged: HDD, NTFS, Paragon NTFS | Leave a Comment »
Posted by jpluimers on 2014/03/06
If you run FastMM4 in FullDebugMode, then here are two tips that new (and sometimes existing users) often overlook:
- If you set the
FullDebugMode directive in the IDE, build your project.
- Don’t forget to give your EXE access to FastMM_FullDebugMode.dll (x86), or FastMM_FullDebugMode64.dll (x64) which are stored in the FastMM4 download and in the precompiled directory of the source code.
Either put that DLL in your path, or copy it to your EXE directory.
- Make sure your EXE can write in the directory of the EXE.
The first makes sure all units are compiled with FullDebugMode (Delphi does not always do that automagically).
The second makes sure your EXE can access the DLL that writes out your *MemoryManager_EventLog.txt file containing memory leaks and other issues FastMM4 detected.
–jeroen
Posted in Conference Topics, Conferences, Delphi, Delphi 2007, Delphi 2009, Delphi 2010, Delphi XE, Delphi XE2, Delphi XE3, Delphi XE4, Delphi XE5, Development, Event, FastMM, Software Development | 2 Comments »
Posted by jpluimers on 2014/03/06
Every now and then I need to go back to an old Delphi version, which nowadays means try and get it and all the tools installed on something newer than Windows XP.
When installing on Windows Vista and up (I usually run Windows 7 or 8.1), the DelphiSpeedUp installer barfs with something like this:
---------------------------
Installdelphispeedup105
---------------------------
Cannot register DelphiSpeedUpLoader.bpl.
---------------------------
OK
---------------------------
Andreas Hausladen (@AndyHTech) came to the rescue: Read the rest of this entry »
Posted in Delphi, Delphi 2007, Delphi 7, Development, Software Development | 1 Comment »
Posted by jpluimers on 2014/03/06
In this series of PowerShell postings, the below quote by Don Jones from Concentrated Technology is a must:
Proper formatting, including a little whitespace here and there, can make your Windows PowerShell commands a heck of a lot easier to understand.
But please don’t limit this to PowerShell code.
I see too many code at clients, even at conferences and magazine articles that are badly formatted.
Even more important: when you ask or provide for help on a forum or community site: please properly format your code examples. That makes it much easier for your audience (often yourself) to grasp the meaning.
For PowerShell: note that most syntactic elements provide for a very natural line continuation (so you can write really readable code), except for CmdLets, so often you will see { at the end of a line to make the most readable code.
–jeroen
via: Windows PowerShell: Whitespace, Please | TechNet Magazine.
Posted in .NET, Delphi, Development, PowerShell, Scripting, Software Development | Leave a Comment »
The Wiert Corner - irregular stream of stuff 