Pages: 1

#1 Re: mORMot 1 » Breaking Up The Big Ball Of Mud » 2017-06-30 18:39:28

rballz

It's mostly a huge datamodule and all data aware controls.  There's almost no classes and hard to ID seams.

So I was thinking of breaking the huge datamodule into smaller, then refactor what each micro datamodule touches into eventual SOA pieces?

#2 mORMot 1 » Breaking Up The Big Ball Of Mud » 2017-06-30 17:32:49

rballz
Replies: 4

I know the docs show some ways to use mORMot in legacy code, but I was wondering:

Has anyone used or have begun using mORMot to refactor a huge legacy code base with any tips / direction?

Anyone due consulting for pay on this sort of thing?

It's very hard to figure out where to stop.

99% of data access is via TTables (With nexusdb), all ui mixed with business logic.  Every single issue you would expect from legacy Delphi done wrong smile

#3 mORMot 1 » NexusDB support limitations » 2016-03-22 20:24:39

rballz
Replies: 1

Looks like, from the code, mORMot only supports embedded Nexus and possibly only version 3.x of NexusDB?

If so - any strategies to use the framework with nexus + another supported db ?

#4 Re: mORMot 1 » Compilation Error in SynBidirSock.pas » 2016-03-22 19:24:35

rballz

Re Re Re downloading master fixed it.  Thanks!

#5 mORMot 1 » Compilation Error in SynBidirSock.pas » 2016-03-22 15:59:50

rballz
Replies: 2

Line 1572 from master on github.com

    if opcode=focText then
      //ERR Types of actual and formal var params must be identical
      SetCodePage(Frame.payload,CP_UTF8,false); // identify text value as UTF-8 <-- Types of actual and formal var params must be identical
      //ERR
    {$endif}
    Log(frame,'GetFrame');

Delphi Seattle 10 / Win 10

Pages: 1

Board footer

Powered by FluxBB