View RSS Feed

Development Team Blog

  1. Diagnosing Studio and compile time performance problems

    by , 22-Mar-2010 at 08:00 AM (Development Team Blog)
    When it comes to performance working in the Studio as a developer, as opposed to running the application, there are generally two performance critical areas. The first one is the Studio Parser, which is the foundation for CodeSense, Visual Modeling, Go-To-Definition and more. The second performance critical area is when compiling. Unnecessarily long and slow compile times can make for a very frustrating experience working with the Visual DataFlex Studio.

    Sometimes you may not even ...

    Updated 17-Mar-2010 at 05:25 PM by Sonny Falk

    Categories
    Uncategorized
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	comp-perf.jpg 
Views:	1331 
Size:	26.8 KB 
ID:	3799   Click image for larger version. 

Name:	parse-perf.jpg 
Views:	1275 
Size:	29.0 KB 
ID:	3800   Click image for larger version. 

Name:	studio-load.jpg 
Views:	1277 
Size:	29.8 KB 
ID:	3801   Click image for larger version. 

Name:	studio-parse.jpg 
Views:	1346 
Size:	51.5 KB 
ID:	3802   Click image for larger version. 

Name:	bigws2.jpg 
Views:	1310 
Size:	50.7 KB 
ID:	3803   Click image for larger version. 

Name:	bigws1.jpg 
Views:	1318 
Size:	23.6 KB 
ID:	3804  
  2. Why Some Files Are Not Migrated to the Latest VDF Revision

    We try to make migration from any Visual DataFlex revision to the latest revision as smooth as possible for our developers, but one migration-related question has come up repeatedly in the forums: "Some of the files in my workspace didn't get migrated. What's going on?"

    The migration wizard uses the same code parser that the Studio uses to determine what to migrate. As Sonny recently discussed in his blog Under the Hood: The Studio Parser, most source code files are not autonomous, ...
  3. Under the Hood: The Studio Parser

    by , 28-Aug-2009 at 08:00 AM (Development Team Blog)
    The Visual DataFlex Studio parser is actually two separate parsers, one is parsing source code and the other is parsing the tree structure output by the first one. The first one is internally referred to as the CDS(Code Data Structure) Parser, and the second one is referred to as the Metadata Parser. But often they are referred to collectively as the Studio Parser, as the technical distinctions are often irrelevant unless you're discussing Studio internals. The CDS and Metadata parsers are also ...
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	pr1.jpg 
Views:	982 
Size:	24.1 KB 
ID:	3761   Click image for larger version. 

Name:	pr2.jpg 
Views:	1014 
Size:	24.7 KB 
ID:	3762   Click image for larger version. 

Name:	vd1.jpg 
Views:	938 
Size:	50.4 KB 
ID:	3763   Click image for larger version. 

Name:	ddoexpl.jpg 
Views:	941 
Size:	38.9 KB 
ID:	3764