Source: roll a dice – Google Search
Inspired by [WayBack] Sure, Google. Sure.
–jeroen
Archive for the ‘Software Development’ Category
roll a dice – Google Search
Posted by jpluimers on 2018/09/13
Posted in Algorithms, Development, Fun, Quotes, Software Development | Leave a Comment »
TIdHTTPWebBrokerBridge example for a standalone Indy based SOAP service
Posted by jpluimers on 2018/09/12
Since I tend to forget what bits and pieces are needed for TIdHTTPWebBrokerBridge, the below code piece from:
- [WayBack] Creating SOAP server at runtime [Edit] – embarcadero.delphi.webservices
- [WayBack] Delphi 7 Indy Standalone Web Services/SOAP Server
The [WayBack] WebReq.WebRequestHandler Function returns a reference to the global [WayBack] TWebRequestHandler object. This object manages all the Web modules in the application, and creates Web request and response objects when the application receives HTTP request messages: TWebRequestHandler keeps a pool of active Web modules. In response to a request from the application, TWebRequestHandler creates a request object and assigns it to one of the active Web modules.
The code below is the Indy counterpart of hooking up a classic WebSnap WebBroker (you could also hook the Web.WebBroker.Application.WebModuleClass to TMyWebModule instead of the WebRequestHandler.WebModuleClass, as Web.WebBroker.Application.WebModuleClass is a TWebApplication which inherits from TWebRequestHandler).
Share this:
Posted in Conference Topics, Conferences, Delphi, Development, Event, Software Development | Leave a Comment »
Windows service states and service state transitions
Posted by jpluimers on 2018/09/12
States via [WayBack] SERVICE_STATUS structure (Windows)
Value Hex Meaning SERVICE_CONTINUE_PENDING 0x00000005 The service continue is pending. SERVICE_PAUSE_PENDING 0x00000006 The service pause is pending. SERVICE_PAUSED 0x00000007 The service is paused. SERVICE_RUNNING 0x00000004 The service is running. SERVICE_START_PENDING 0x00000002 The service is starting. SERVICE_STOP_PENDING 0x00000003 The service is stopping. SERVICE_STOPPED 0x00000001 The service is not running.
State transition overview
It’s complex as a table, so there are two.
- The initial state is SERVICE_STOPPED.
- Most logical targets are in italic.
Common transitions:
| From state | To state |
|---|---|
| SERVICE_STOPPED | SERVICE_START_PENDING |
| SERVICE_START_PENDING | SERVICE_RUNNING |
| SERVICE_START_PENDING | SERVICE_STOPPED |
| SERVICE_START_PENDING | SERVICE_STOP_PENDING |
| SERVICE_RUNNING | SERVICE_STOPPED |
| SERVICE_RUNNING | SERVICE_STOP_PENDING |
| SERVICE_STOP_PENDING | SERVICE_STOPPED |
Infrequent transitions:
| From state | To state |
|---|---|
| SERVICE_RUNNING | SERVICE_PAUSE_PENDING |
| SERVICE_RUNNING | SERVICE_PAUSED |
| SERVICE_PAUSE_PENDING | SERVICE_PAUSED |
| SERVICE_PAUSE_PENDING | SERVICE_STOP_PENDING |
| SERVICE_PAUSE_PENDING | SERVICE_STOPPED |
| SERVICE_PAUSED | SERVICE_RUNNING |
| SERVICE_PAUSED | SERVICE_CONTINUE_PENDING |
| SERVICE_PAUSED | SERVICE_STOP_PENDING |
| SERVICE_PAUSED | SERVICE_STOPPED |
| SERVICE_CONTINUE_PENDING | SERVICE_RUNNING |
| SERVICE_CONTINUE_PENDING | SERVICE_STOP_PENDING |
| SERVICE_CONTINUE_PENDING | SERVICE_STOPPED |
Share this:
Posted in Development, Software Development, Windows Development | Leave a Comment »
delphi – How to make a combo box with fulltext search autocomplete support? – Stack Overflow
Posted by jpluimers on 2018/09/12
Interesting solutions based on the TLama first answer at [WayBack] delphi – How to make a combo box with fulltext search autocomplete support? – Stack Overflow
Via: [WayBack] Nice solution by TLama – Thomas Mueller (dummzeuch) – Google+
–jeroen
Share this:
Posted in Delphi, Development, Software Development | Leave a Comment »
Schema Central: XML vocabularies with all their XSD schema’s in a nice browsable overview including references, explanations and examples
Posted by jpluimers on 2018/09/11
Schema Central, by [WayBack] Datypic, Inc. (Priscilla Walmsley) is to golden that I quote the whole index page below.
The index refers to XML vocabularies. Each vocabulary page links the corresponding XSD pages. Each XSD page lists documentation, elements, etc. Each element page then documents the element, shows where it is referenced from.
Welcome to Schema Central, an interactive tool to traverse and search XML schemas. Please choose your XML vocabulary of interest to get started. Don’t see the XML vocabulary you use? Ask us to add it.
Core XML Technologies
- XML Schema: 1.0 and 1.1
- XML 1.0
- ISO Schematron
- XLink
- XProc
- XSLT: 1.0 and 2.0
- XInclude
- XForms: 1.0 and 1.1
- XML Catalogs 1.1
Presentation-Oriented Standards
- XHTML 1.0: (strict), (transitional) and (frameset)
- XSL-FO 1.1
- CALS Table Model (Oasis XML Exchange Table Model)
- MathML 2.0 and 3.0
- SVG 1.1
Office/Narrative Document Standards
Business Document Standards
- OAGIS® 9.4.1, 10
- UBL 2.0, 2.1 and 2.2
- StratML
- FpML
- 5.5: Confirmation, Pretrade, Recordkeeping, Reporting, Transparency
- 5.0: Confirmation and Reporting
- XBRL 2.1
NIEM-related Standards
- NIEM: 2.0, 2.1, 3.0, 3.1, 3.2 and 4.0
- LEXS: 3.1.4 and 4.0
- ULEX: 1.0 and 2.0
- N-DEx IA (Incident/Arrest) 2.1
- N-DEx IBP2 (Incarceration/Booking Probation/Parole) 2.1
- ANSI/NIST-ITL 2011
Miscellaneous
Web Services Technologies
- WSDL: 1.1 and 2.0
- SOAP: 1.1 and 1.2
- WS-Addressing 1.0
- WS-AtomicTransaction 1.1/1.2
- WS-BPEL 2.0
- WS-BusinessActivity 1.2
- WS-CDL 1.0
- WS-Coordination 1.2
- WS-Discovery 1.0 and 1.1
- WS-Eventing
- WS-Notification 1.3 (includes WS-BaseNotification, WS-BrokeredNotification and WS-Topics)
- WS-Policy 1.5
- WS-ReliableMessaging 2005 and 1.1/1.2
- WSRF (Resource Framework) 1.2 (includes WS-BaseFaults, WS-Resource, WS-ResourceProperties, WS-ResourceLifetime and WS-ServiceGroup)
Security-Related Technologies
- IC Trusted Data Format (Public version; includes IC-ARH, IC-EDH, IC-ID, IC-TDF, IC-ISM, IC-NTK)
- SAML 2.0
- WS-Security
- WS-SecurityPolicy 1.2 and 1.3
- WS-SecureConversation 1.4
- WS-Trust 1.3 and 1.4
- XML Encryption
- XML Signature
- XACML 2.0 and 3.0
Site developed and hosted by Datypic, Inc.
Please report errors or comments about this site to contrib@functx.com
[WayBack]
If I ever need a long term XML/XSD/XSLT/XQuery hire, this is the “about” information I need:
Datypic provides consulting services and training, specializing in XML, content management and SOA/Web Services architecture and development. We are experts in XML-related technologies such as XML Schema, XSLT and XQuery, and have extensive experience with software development and implementation.
We participate in consulting projects ranging from one day to many months, anywhere in the world. We can arrange to work remotely or at your site, whichever you prefer.
For more information, please read about our services or our company, or contact us as pwalmsley@datypic.com.
Recent news from Priscilla Walmsley
- I recently updated my book XQuery to match the final XQuery 3.1 recommendation. You can read more about it or order it from O’Reilly or Amazon.
- I recently taught a course at the XML Summer School on Refactoring XSLT. Slides are available as a PDF.
- More information about my recent books and articles is available on this site.
–jeroen
Share this:
Posted in Development, Software Development, XML, XML/XSD, XPath, XSD, XSLT | Leave a Comment »
Delphi 10 Seattle and up try “recover” unchanged files in the `$(BDS)` tree
Posted by jpluimers on 2018/09/11
Every now – after some period of inactivity – I get an error like this when not having changed the file at all:
--------------------------- Error --------------------------- Cannot create file "C:\Program Files (x86)\Embarcadero\Studio\18.0\Source\DUnit\src\__recovery\GUITestRunner.pas". Het systeem kan het opgegeven pad niet vinden. --------------------------- OK Details >> ---------------------------
This has been present since ever since Delphi 10 Seattle introduced the “recovery” feature on unchanged files in a read-only directory tree like for instance $(BDS).
It assumes the __recovery subdirectory has been created (which it cannot, but never raised an error about), then barfs when it cannot find the directory.
This is a classic example of “nice idea, bad execution, not caught by thinking through all the test cases”.
I think one of the roles played, is that cursor movements are part of the undo/redo stack. My suspicion is that this raises a “changed” flag, where in fact the file is unmodified.
Het systeem kan het opgegeven pad niet vinden.is the Dutch version ofERROR_PATH_NOT_FOUNDerror code0x03EnglishThe system cannot find the path specified.
Related:
- [WayBack] System Error Codes (0-499) | Microsoft Docs
- [WayBack] c++ – ERROR_PATH_NOT_FOUND vs ERROR_FILE_NOT_FOUND, what is the difference? – Stack Overflow
- [WayBack] windows – What’s the difference between PATH_NOT_FOUND and NAME_NOT_FOUND – Stack Overflow
–jeroen
Share this:
Posted in Delphi, Development, Software Development | 2 Comments »
A refefernce to 6502 by “Remember that in a stack trace, the addresses are return addresses, not call addresses – The Old New Thing”
Posted by jpluimers on 2018/09/11
On x86/x64/ARM/…:
It’s where the function is going to return to, not where it came from.
And:
Bonus chatter: This reminds me of a quirk of the 6502 processor: When it pushed the return address onto the stack, it actually pushed the return address minus one. This is an artifact of the way the 6502 is implemented, but it results in the nice feature that the stack trace gives you the line number of the call instruction.
Of course, this is all hypothetical, because 6502 debuggers didn’t have fancy features like stack traces or line numbers.
Source: [WayBack] Remember that in a stack trace, the addresses are return addresses, not call addresses – The Old New Thing
Which resulted in these comments at [WayBack] CC +mos6502 – Jeroen Wiert Pluimers – Google+:
- mos6502: And don’t forget the crucial difference in PC on 6502 between RTS and RTI!
- Jeroen Wiert Pluimers: +mos6502 I totally forgot about that one. Thanks for reminding me
<<Note that unlike RTS, the return address on the stack is the actual address rather than the address-1.>>
References:
[WayBack] 6502.org: Tutorials and Aids – RTI
RTI retrieves the Processor Status Word (flags) and the Program Counter from the stack in that order (interrupts push the PC first and then the PSW).
Note that unlike RTS, the return address on the stack is the actual address rather than the address-1.
[WayBack] 6502.org: Tutorials and Aids – RTS
RTS pulls the top two bytes off the stack (low byte first) and transfers program control to that address+1. It is used, as expected, to exit a subroutine invoked via JSR which pushed the address-1.
RTS is frequently used to implement a jump table where addresses-1 are pushed onto the stack and accessed via RTS eg. to access the second of four routines.
–jeroen
Share this:
Posted in 6502, 6502 Assembly, Assembly Language, Development, History, Software Development, The Old New Thing, Windows Development, x64, x86 | Leave a Comment »
Spelling with element symbols from the Periodic table
Posted by jpluimers on 2018/09/11
The [WayBack] Periodic table – Wikipedia contains many symbols.
Combing them allows you to spell word. Not all words, but many of them can be spelled.
So I was glad finding the below article that started with the same fascination I had in chemistry class.
It has a great explanation of the algorithm, references to computer science literature and a nice Python implementation.
via: [WayBack] One of the best programming articles I’ve read in a while – This is why I Code – Google+
–jeroen
Share this:
Posted in Algorithms, Development, Fun, LifeHacker, Power User, Python, science, Scripting, Software Development | Leave a Comment »
Delphi XE6 and up regression: “‘9999-12-31 23:59:59,1000’ is not a valid date and time” when passing a SOAP message with 9999-11-31T23:59:59.9999999; QC144171
Posted by jpluimers on 2018/09/06
A valid SOAP message with <urn:timeStamp>9999-11-31T23:59:59.9999999</urn:timeStamp> in a xs:dateTime field return '9999-12-31 23:59:59,1000' is not a valid date and time from a Delphi application with this SOAP response:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>'9999-12-31 23:59:59,1000' is not a valid date and time</faultstring>
<faultactor/>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The reason is this exception:
exception class EConvertError with message ''9999-12-31 23:59:59,1000' is not a valid date and time'.
This is from a .NET based test case passing in timeStamp = DateTime.MaxValuewhich is handled perfectly fine by other SOAP web services tested.
I know about different resolutions of time stamps, but would never expect the 999.9999 milliseconds to be rounded up to 1000 as it is always safer to truncated away from an upper limit.
A test using Soap UI [WayBack] with this parameter finally worked (max 3 digits second fraction):
<urn:timeStamp>9999-12-31T23:59:59.999</urn:timeStamp>
The true origin of problem is in this method in the Soap.XSBuiltIns unit which has been unchanged since at least Delphi 7:
function TXSBaseTime.GetMilliSecond: Word; begin Result := Round(FractionalSeconds*1000); end;
The problem exposed itself because as of Delphi XE6 the core of function TXSBaseCustomDateTime.GetAsDateTime piece was changed from
Result := EncodeDateTime(Year, Month, Day, Hour, Minute, Second, 0);
to
Result := EncodeDateTime(Year, Month, Day, Hour, Minute, Second, Millisecond);
A combination of lack of test cases and understanding XML specifications failed to reveal this bug.
The standards specify (among others):
'.' s+ (if present) represents the fractional seconds;
The above is not limiting the amount of digits, not talking about milliseconds either.All ·minimally conforming· processors ·must· support year values with a minimum of 4 digits (i.e., YYYY) and a minimum fractional second precision of milliseconds or three decimal digits (i.e. s.sss). However, ·minimally conforming· processors ·may· set an application-defined limit on the maximum number of digits they are prepared to support in these two cases, in which case that application-defined maximum number ·must· be clearly documented.
Delphi not only limits the fractional second precission, it changes the limit over time and does not document the limit. Three strikes…s -- represents a digit used in the time element "second". The two digits in a ss format can have values from 0 to 60. In the formats described in this specification the whole number of seconds ·may· be followed by decimal seconds to an arbitrary level of precision. This is represented in the picture by "ss.sss". A value of 60 or more is allowed only in the case of leap seconds.
Given buggy the fractional second handling through milliseconds, the leap second handling is ripe for a test case as well.
Strictly speaking, a value of 60 or more is not sensible unless the month and day could represent March 31, June 30, September 30, or December 31 in UTC. Because the leap second is added or subtracted as the last second of the day in UTC time, the long (or short) minute could occur at other times in local time. In cases where the leap second is used with an inappropriate month and day it, and any fractional seconds, should considered as added or subtracted from the following minute.
The reproduction is quite simple:
Share this:
Posted in .NET, C#, Conference Topics, Conferences, Delphi, Development, Event, SOAP/WebServices, Software Development, XML, XML/XSD | Leave a Comment »
playing with IOT
Posted by jpluimers on 2018/09/06
Interesting stuff:
Open-source home automation platform running on Python 3. Track and control all devices at home and automate control. Installation in less than a minute.
Source: Home Assistant
Via:
CounterDesk
@Dysan • 18 mei 2017 09:47Ik doe dus een hoop met home-assistant (https://home-assistant.io/) en wat custom Python scripts/apis wat allemaal op een oude laptop met ubuntu draait (10w verbruik).
De Horizon Box specifiek gaat via Harmony Hub, kan via de standaard integratie of via eigen brouwsels. Lifx en Nest heeft standaard integratie met Google Home. Al heb ik voor Lifx zelf het een-en-ander geschreven in Python om bijvoorbeeld scenes op te slaan en op te roepen met voice commando’s, dat kan weer niet standaard. NS API gaat ook via die Python API en wat er terug gezegd wordt (in het Nederlands) gaat via home-assistant.
Het voordeel van zelf zoiets bouwen is dat ik alles makkelijkers aan elkaar kan knopen dan bijvoorbeeld via IFTTT en Stringify o.i.d.. Zo kan ik bijvoorbeeld “Hey Google, sexy time” roepen en dan veranderd mijn verlichting langzaam naar iets romantischers (denk rood/oranje/roze), speelt er een zwoel lounge muziekje op mijn Sonos van een samba share, gaat de tempratuur wat omhoog en gaat mijn tv aan naar het chromecast kanaal en speelt er van die zelfde samba share een mp4 met een haardvuurtje.
Vet cheesy, I know, ik moet er de eerste vrouw nog mee verrassen
maar het was ook vooral als demo van wat ik allemaal kan aansturen, bedoeld als grapje voor vrienden etc.
Google voegt een notificatiefunctie toe aan zijn Home-speaker. Als gebruikers een belangrijk bericht krijgen, zullen de ledjes op de speaker de aandacht gaan trekken van de gebruiker. De speaker gaat vooralsnog niet uit zichzelf spreken.
Source: Home-speaker van Google krijgt notificatiefunctie – Beeld en geluid – Nieuws – Tweakers
–jeroen
Share this:
Posted in Development, IoT Internet of Things, Network-and-equipment, Power User, Software Development | Leave a Comment »
The Wiert Corner - irregular stream of stuff 