In new Xojo was changed the work with pictures for Mac/Cocoa and Linux.
We have improve plugin “Valentina for REALbasic/Xojo” to support these new formats. This fix affects both normal pictures and preview pictures in Valentina Reports.
Root of Application Developer Kits
In new Xojo was changed the work with pictures for Mac/Cocoa and Linux.
We have improve plugin “Valentina for REALbasic/Xojo” to support these new formats. This fix affects both normal pictures and preview pictures in Valentina Reports.
OS X 10.8 has option “System Settings -> Security -> General -> Allow: MAS App Store and identified developers” on default to be ON, so you cannot installed easy not signed applications and run installers. Note that 10.7 also can have this option enabled on some computers.
To resolve this issue, we have sign vstudio.app and vserver_x64.pkg installer.
Unfortunately we cannot easy sign other our installers (V4RB, V4REV, V4CC, … ) because we using third party installer. So for now, for 5.0, we going to ship these installers not signed. To run them, OS X developer should in the Finder do CTRL + click on icon of installer and choose OPEN command in the contextual menu. In this case you will see the button ALLOW in the OS X security dialog. Click it, and continue as usual.
Frank have contact us with request add ability for V4CC (Valentina for Cocoa) developers to specify the location of journal of a database. This is important for sandboxed applications, which on default can access only their sandbox folder and a file(s) that user specify explicitly.
PROBLEM is that if a user choose somedb.vdb file in the SelectFile dialog , then Valentina engine needs yet to create a journal file near to .vdb file. But for a sandboxed application this is prohibited by OS X. This is why developer want to be able specify another location for journal file.
Btw, this problem exists more of year for SQLite database that is used e.g. in CoreData of Apple, when it is used by a sandboxed app. Strange, but the only advice from Apple is – disable journal file.
We have spend couple of days to add into C++ level and into V4CC ADK this feature. Rest ADKs soon.
Now you can write the following in V4CC:
Few years ago we have added into Valentina Server HTTP port, so it have:
We are glad to inform you, that we already have working Valentina Reports engine with datasource from mySQL.
We have use one of BSD clients compatible with mySQL Server. This resolve any issues related with GPL-license of mySQL native drivers.
Please note, that this mySQL datasource for now works only for Valentina Reports ADK, but not in Valentina Studio – Report Editor. To prepare reports in the GUI Editor you need to use Valentina or Postgre or SQLite database with the same tables. But do not worry, in about 1.5-2 months we will introduce 5.x version of Valentina Studio, with full-featured mySQL plugin also.
Right now, you can make dump of schema of mySQL database, and load that dump into local Valentina DB, then use it as test-db to design report(s). Later, from ADK application, just specify mySQL datasource against this report(s). For mySQL you should use connection string of kind
theReport = my_project.MakeNewReport( "report_1", "mysql://host=192.168.2.33, user=admin, passw=admin", "SELECT fldName, fldPhone FROM tblPerson" )
Historically, we have developed at first VPHP as client-only ADK of Valentina Server. Later we have add vphp_standalone version of archives, which included the whole Valentina engine, and can work without VServer. Actually we have this for all other Valentina ADKs, such as V4RB, VNET, V4REV, … But for VPHP we have got two archives, where others ADKs did have one.
The same did happens with VODBC ADK …
For 4.9.1. release we have decide “resolve” this issue. Now on FTP present only “standalone” full archives, but they are renamed to just vphp_4 style.
We have note that put_ID() should not be in the public interfaces of Schema Objects, because developer should not be able change ID of a scheme object.
We have check our sources, and found that only I_Field interface did have such method. So we move it into internal I_FieldEx interface. In the C++ header this method marked as DEPRECATED, and do nothing now. We believe that nobody from C++ developers have used it.
We will consider future ability to do “SET PROPERTY ID of Object name” via SQL, but this will be recommended for use by our own SQL scripts only.
Problem is that if you are a C++ developer and use VSDK for development,
then work with Values of Fields of cursor looks as:
I_Cursor_Ptr pCursor = db->SqlSelect( ... ); ... String s = pCursor->get_Field("Name" )->get_Value()->get_String(); double d = pCursor->get_Field("Weight")->get_Value()->get_Double(); ...
In contrast, for such languages as REALbasic or VB syntax is more short:
String str = pCursor.StringField( "fldName" ).value
We have decide that for C++ developer we can have set of simple macros that will allow C++ developer syntax as:
String str = GET_STRING( pCursor, "fldName" );
These macros are located in the: sources/FBL/VShared/VSQL/publ/Interfaces/VSQL_I_Cursor.h
Note, that more complex values as DateTime, Binary, still should be used in old way, because VSDK do not know format you goingto use. May be you can add own macroses in your project that looks similar and do job you need.
Now C++ developer can write simpler code as
ArrayOfValues_Ptr pValues = new ArrayOfValues(); pValues->AddItem( toValue_varchar(mName) ); pValues->AddItem( toValue_double(70.5) ); pValues->AddItem( toValue_long(size) );
Instead of:
ArrayOfValues_Ptr pValues = new ArrayOfValues(); Value_varchar* pValueName = new Value_varchar(); pValueName->put_String( mName.begin(), mName.end() ); pValues->AddItem( pValueName ); Value_double* pValueD = new Value_double(); pValueD->put_Double( 70.5 ); pValues->AddItem( pValueD ); ...
David Simpson has written an excellent article over on Omegabundle.com called Converting FileMaker Pro Databases into LiveCode Applications. dot com Solutions makes a powerful utility product called FmPro Migrator Platinum Edition that is a part of the latest Omegabundle for LiveCode 4.2011 offering. More than a utility, its really a one of a kind solution for porting Apple FileMaker Pro and Microsoft Access databases into full LiveCode applications, which in turn makes it possible to port the data store over to Valentina DB.
We have add a new great feature into Valentina Studio PRO:
Import XCODE model into Valentina Database Schema.
Import Wizard allows you to specify for each link between tables its kind to be one of:
Foreign Key, ObjectPtr or BinaryLink.
Details please read on this Valentina WIKI page
A group of developer tool makers that support REAL Studio have put together a fantastic bundle of $3200 of pro tools for only $399 – the Omegabundle. This offer lasts only through 2.14.2011 – ie Valentine’s Day. Continue reading Omegabundle 2011 for REAL Studio Developers Extended to 2.14.2011
We have made two new x64 products on request of Valentina developers:
* VSDK x64 WIN
* VServer Embedded x64 Linux
Paradigma Software has joined with a group of professional development tool vendors to produce and release Omega Bundle 2011 for the REAL Studio environment. This limited time package contains $3200 worth of tools but available in this set for $399 – over 80% savings.
Continue reading Paradigma Software Participates in Omegabundle 2011 for REAL Studio
In version 4.8 we add one more cool feature to Valentina for Cocoa (V4CC) ADK – Interface Builder plugin!
V4CC Interface Builder Plugin allows you to develop a Cocoa application with embedded V4CC.framework without writing any code to link GUI with a Valentina database. Instead you will use bindings and few Valentina Controllers.
You can read Manual of V4CC IB plugin and learn few tutorial lessons.