Skipper support site - Recent questions in Information

[Solved] Problem with connecting to HTTPS license server (curl_easy_perform - Couldn't resolve host name)

Wed, 02 Sep 2015 15:40:15 +0000

Hello,

I've download Skipper and try to run trial. As state in documentation a network licence validation is performed. GREAT IDEA !!! ... if the licence server is correctly working ! :-(((

For me, no trial licence, just a Activation Failed and a message
"curleasyperform(), url:https://cloud.atlantic18.com/stark
failed: Couldn't resolve host name"
The URL was perfectably reachable but return a really significant error message "Ouuuuuuups, something wrong."

I hope it won't be the same during 14 days... and that other error messages in the application are more significant ;-)

JGrx

[Info] How to run Skipper on Mac OSX 10.8 and older

Sat, 07 Feb 2015 12:37:48 +0000

Starting with Skipper 3.0.2 we have to upgrade our build servers to OS X 10.9. (It's because of new Apple codesign v2 policy).

If you need to run Skipper on OS X 10.8 and older it's necessary to install some additional libraries which are shipped with 10.9+ but are missing on 10.8.

To do that, use brew with following command:

brew install xz

It's possible that based on your OS it will be necessary to install some additional libraries. The best and preferable way is to upgrade your OS at least to 10.9.

MongoDB ODM support

Wed, 28 Jan 2015 14:12:22 +0000

We are almost ready to release MongoDB ODM support for Skipper. The status of implementation can be considered as 100% complete.

Now, we would need as many testers as possible to find all possible issues in import/export or ORM properties. MongoDB support is a large step forward because there was a lot of new objects in the model:

collections
entities in collection
embedded
associations/embedded to collections

Here are some example screenshots how new objects look like:

Please download the latest beta from our beta download page and let us know!

[Info] Trial License activation failed: You're trying to activate obsolete version of the application

Wed, 25 Jun 2014 11:16:59 +0000

With release of Skipper, activation of new ORM Designer 2 trial versions will not be possible anymore.

You can download the trial version of Skipper (ORM Designer 3) instead:
www.skipper18.com/en/download

For all users (regardless if they have tried ORM Designer in the past or if they have active maintenance), full 14 days of Skipper trial is available.

[Info] Template library

Fri, 13 Dec 2013 12:21:06 +0000

Hello Everybody,

With the version 2.2.7 we have launched a new system for model element templates. Now you can define almost anything as a template, and if you find something that cannot be done like this, let us know.

How templates work is documented in the template guide and the template reference.

However this is heavy stuff and to ease your start with new templates, and provide with some real-world examples, we have prepared a predefined template library. If you miss some template there, or if you have some template that is really useful in your projects, share it with the community.

[Info] ORM Designer localization and community translations

Mon, 25 Nov 2013 20:49:07 +0000

Hi everybody,

We have just finished support for community translations in the ORM Designer. So far we have added translation to Czech but we plan adding additional languages on the go.

ORM Designer uses Qt language libraries, so with a source text we have prepared you can easily translate everything in the ORM Designer GUI and if you want you can post your translations here for others to share. Once you have the files with translation it is as easy as just copying it inside of ORM Designer directory and the new language can be used.

How to translate
All necessary files and a brief guide how to translate or how to upload the translations are in our documentation.

If you want, you can post translated files on this site, we will appreciate it and community will love you.

Vote for new translations
Please vote for community translations that you like. Also you can vote for translations that are still missing so we will know on what translations we should focus next.

[Downloads] Skipper Beta

Thu, 31 Jan 2013 09:02:15 +0000

Changes in version 3.4.4.1854

Doctrine2: added module-level 'property-visibility' setting (private/protected/public). Enables using PHP 8.4 property hooks by exporting entity properties as public, removing need for getter/setter boilerplate. Configure per bundle in module's Doctrine2 configuration. (New!)
Doctrine2: added module-level "property-visibility" setting (private/protected/public) (New!)
PHP 8.1+ readonly support. Added readonly as a recognized PHP property/class modifier. Entities using readonly properties (public readonly string $name) or readonly class declarations now import and export correctly.
PHP 8.1 enum support: parser now correctly handles enum declarations, enum cases with values, and enums implementing interfaces
PHP 8.1 intersection type support: parser handles Type1&Type2 syntax in property type declarations
PHP 8.0+ keyword support: parser recognizes match expressions, arrow functions (fn), and yield statements
PHP 8.2 DNF type support: parser handles parenthesized compound types like (Countable&Iterator)|null in property declarations
Doctrine2 simple traits support — all traits are imported and flattened directly to the entities
Fixed: PHP import now correctly resolves use statement references (e.g., use Entity\User\User) when used in targetEntity and other ::class expressions, instead of incorrectly prepending the current file's namespace.
Fixed: PHP import now correctly handles fully qualified class references with leading backslash (e.g., \Application\Entity\File::class) in targetEntity and other annotations, instead of incorrectly prepending the current namespace
Doctrine2: Fixed PHP grouped use statement import, Skipper now correctly resolves class references from grouped declarations like use Customer{User, User\Team}
Fixed grammar in error messages (doesn't exists -> doesn't exist) and improved ORM/MVC framework error message wording
Fixed case-insensitive annotation import: annotations with non-standard casing (e.g. @ORM\column instead of @ORM\Column) are now correctly recognized during import
Fixed empty region remaining after Doctrine2 trait import flattening

Latest Skipper beta version is 3.4.4.1854

Windows

Linux

Skipper for Linux 64-bit.zip (portable version)

MacOS

[Info] Doctrine2 annotations support

Tue, 13 Nov 2012 07:52:52 +0000

Hi all,

We have some really exciting news for you. Today is a big day for us as weâ€™re releasing first public beta of ORM Designer 2. This version comes with a whole new code leaving almost nothing but the product name unchanged.

One of the new key features is native support of Linux, OS X and Windows systems. But these are old news to the ones following us on twitter or blog. Now we are adding another great feature that many of you were asking for. As of now ORM Designer fully supports Doctrine 2 annotations. It was a big challenge for us, we accepted it and now we can say we accomplished it ;-).

As with any beta and especially with the first beta version please bear in mind that you might experience bugs or unexpected results. Please let us know about these issues and weâ€™ll make sure itâ€™s fixed in a future revision.

You can download new version of ORM Designer 2 here. But before you do, please read more about how annotations support works:

How annotations import/export works?

When we began implementing annotations support we had to figure out how to update your code without changing or removing anything but the Doctrine mapping. We defined explicit rules for add, update and remove actions:

ADD - Add anything generated by ORM Designer if thereâ€™s no collision with your code:

Namespace definitions
Default namespace definitions
Entity class (if generating new code)
Variable declaration
Variable annotations declaration
todo: getters, setters, collections adders and getters(see the next section)

UPDATE - ORM Designer updates only Doctrine2 annotations within namespace "Doctrine\ORM\Mapping".

DELETE - This is the most important. ORM Designer NEVER removes anything from your code with the only exception of Doctrine2 annotations from namespace "Doctrine\ORM\Mapping".

If you add field to your Entity by using ORM Designer, new variable with annotations is added.
If you remove this field from your ORM Designer model, only annotations of this variable is removed!
Variable itself is left in code and you remove it manually if you want to.
The same is true for associationsâ€™ variables
And the same applies for the class itself. If you remove your class from diagram, the file is kept untouched. You shall remove the class if you want to manually.

Annotations:

ORM Designer evaluates complete namespaces when parsing your source code.
The tricky part is @Entity definition without namespaces. For such cases ORM Designer has a list of Doctrine2 annotations to recognize it also without namespace qualification.
Default namespace used with ORM Designer is a recommended Doctrine2 format "@ORM\Entity".

REFORMAT

Because ORM Designer sometimes adds code snippets to your code, it's necessary to add this code as smoothly as possible. For that ORM Designer follows these rules:

Code snippet is always inserted to the best position, not only to the end of file.
When adding new variable, search for a similar variable in the code.
When adding namespace definition, add it as last item of your namespace definitions list
When modifying annotations, keep ORM annotations together and keep other annotations without modifications.
When inserting anything new, scan for file indention and use the same (If you're using two spaces for indention, ORM Designer indent new code with two spaces, if you're using tabs, ORM Designer uses tabs.)
ORM Designer recognizes some annotation types and might sometime unify these annotations (Doctrine 2 only). For example array(1,2,3) is exported as one-line, but if you have array of complex structures, each element is exported on separate line with adequate indention!

Definition files scanner
Another part of annotations support is new project scanner. Because entities defined by annotations can be located anywhere in the project in several files, we implemented also fast annotations scanner which helps you to find all your definition files.

Usage is to YML or XML definitions import. Simply choose your project's root directory and let ORM Designer do his job. Depending on project size scanning and importing can take some time, because ORM Designer needs to scan ALL your PHP files. We already test it on large projects (~4500 files and ~200 entities) and scanner takes about 5-10seconds, import less than a minute.

What can be done next

Currently ORM Designer imports/exports only annotations and variables. In the future it will be also possible to perform one-time export of getters and setters functions. But before that, we need to know what format / content of these functions is preferred most.
Now our importers/exports support only core Doctrine2 annotations. But in the future will be also possible to import other annotations based on or even vaguely related Doctrine2. Right now we know about:
- @Asserts
- @JMSSerializer http://support.orm-designer.com/28/feature-request-jmsserializer-support
- Do you have any extension you want to see in ORM Designer? Let us know!

Samples

For those of you interested in how ORM Designer exports PHP files, here are some examples:
- http://pastebin.com/DaXHRi7z
- http://pastebin.com/N7YRZDP7
- http://pastebin.com/q4UpMSUK

Summary

Although we spent a lot of time on annotations support and just annotation parser itself is covered by more than 200 unit tests, there will be probably some bugs. Please be patient and report us all bugs you might experience so we can bring you better ORM Designer 2 in near future.

Thank you all and thanks for helping us making a better tool for ORM developers!

Ludek

[Info] ORM Designer2 development status

Thu, 08 Nov 2012 17:22:35 +0000

ORM Designer2 was already released. Here is a list summarizing already implemented, waiting and abandoned features.

Implemented

Native multiplatform support for Windows / Linux (Ubuntu) / MacOS
ORM Doctrine
ORM Doctrine2
ORM PropelPHP
Annotations support for Doctrine2
New property system (indexed/ordered/unordered structures, ordering behaviors,...)
New javascript base script support for imports/exports
New configuration system enable more customisations (Global/Orm/Mvc/Orm&Mvc/Project levels)
New configuration loader, each project can have different configuration
New template system for defining new project, primary fields, association fields, ...
PDF Export
Import from other sources like Workbench
and much more ;-)
Saving model to several xml.
- Load/Save window state (size, position, skin, ...)
- Main screen
- Progress screen or progress widget in status bar
- ORM CakePHP

Waiting

Print support

Abandonded

Summary window (Is here anyone who ever use it? ;-))

Ideas

To use annotations to implement Java Hibernate suport.

Do you miss some feature? Let us know! Create new question about this feature and let other users vote. Most popular requests will be implemented.

Help us decide what feature implement next

Thu, 08 Nov 2012 17:16:13 +0000

ORM Designer2 becomes more stable and better by every release. Although we have still several things to improve (nicer application icon, weird font on license screen,..) we would like to hear your opinion what to implement next.

Currently we're working on annotiations. It is definitely the most required function since we've released Doctrine2 support first time. We expect to have first public results during next week, but don't want to promise it because there are still few challenges awaiting.

We also want to know how many of you uses Propel or CakePHP. Based on feedback we're receiving it looks like that most of users are Doctrine2 and Doctrine programmers.

Please help us to prioritize feature development in ORM Designer2. Shall we implement CakePHP support, Propel support, Print or PDF export as first? And what next?

Do you have some ideas for a new feature? Share it with us!

[Info] Previous ORM Designer2 beta releases

Thu, 08 Nov 2012 13:45:21 +0000

Latest ORM Designer 2 beta version is 2.1.3.643

Change log

2.1.6.677

Panel visibility control from Ribbon doesn't work properly
Fixed invalid project tree ordering
Progress splash screen enhancement
Storing window positions enhancement
Fixed crash when closing ORM Designer with multiple projects opened
Serializing theme flags (apply theme on child windows, apply theme on dock windows)
Fixed size of "Save modified files" dialog in Linux
Fixed filesystem paths migration from V1 to V2
Refactorized file system path manipulation (platform dependent paths)
Fixed migration of project name from V1 projects to V2
New setting to display tab bar only when more than one tab is available
New setting to hide welcome tab when another tab is available
Doctrine2 new suffix mode without-suffix for generating file names without ".dcm" or ".xml"
Fixed bug in default module background color
Fixed tab focus ordering on all dialogs
Enable tab-key on all plain-text widgets to change focus
Draw grid lines by using dot-style instead of solid style
Set association field types based on inverse side
Fixed correct association field name generator when multiple columns with same name already available
Fixed many to many association wizard for self-mn-association
Configuration for many-to-many field type
Fixed many-to-many wizard for self-reffering M2N associations
Configurable naming convention for Doctrine, Doctrine2, Propel association fields
Fixed default path in SaveFile dialog when choosing module storage path
Fixed invalid relative export path. Export path is now relative to module path, not project root path. It's necessary to manually fix all old export paths!
Removed field description from schema.yml export
Refactorized Doctrine1 ManyToMany import/export mechanism. task
Fixed migration of MN relations from V1 to V2 when association from MN table to E table has any ORM attribute (onDelete, onUpdate,....)
Changed project tree search from case sensitive to case insensitive
Many to Many association context menu fix
Display save project popup when exiting app with modified project
Key shortcut DEL and BACKSPACE to delete any object in model
Fixed crash when removing entity with comples ORM properties
New shortcut for SaveAs (Ctrl+Shift+S) and export ORM (Ctrl+Shift+E)
New shortcut to close current model CTRL+W
Fixed many-to-many association splitted flag serialization
Remember diagram grid settings
New interactive welcome screen
Display modified flag when ORM Property was changed
New shortcut to add field to current position in Entity editor (CTRL+INSERT)
Don't add multiple empty fields when already existing empty field at the end of field list.
Remove association owner field when removing association
Fixed project migration from ORMD1 when v1 project contains duplicate Region names
Fixed issue with duplicating file names in RecentFileList
Fixed redrawing of association types in model when changed in edit dialog
Fixed redrawing of association types in model when changed in edit dialog
Fixed serializing fields in entities in correct order
Fixed deploy to newer Ubuntu versions (12.10)
Fixed deploy to Debian wheezy
Refactorized association editor gui. Better aliases description
Fixed issue with Unicode chars in text description on Linux

2.1.4.656

Fixed issue with attaching existing ORM schema file
Fixed issue "invalid relative path" when exporting/saving project

2.1.4.655

Separated data and visual in project XML files
Multifile project support
Annotations - Don't add ?> mark to the end of updated PHP file
Annotations - fixes based on user feedbacks
Internal - each element in diagram has uuid
Use relative paths inside ORMD project (external module path, export path)
Attach existing ORMD module file to project
Import new ORM schema file to existing ORMD project
PDF Export
Diagram draw optimization
Fixed migration of module colors from ORMD v1 project to v2 defect
Fixed migration of modules sizes and positions from v1 to v2 project
Fixed migration of comment and region visual settings from v1 to v2
New SaveAs dialog
New HTTP-like license server protocol on port 80
Enhanced support for SQLite in-memory database
Upgraded SQLite to version 3.7.14.1 (faster in-memory operations)
Upgraded LibXml to 2.9.0
Upgraded LibXslt to 1.1.27 (better transformation speed)

2.1.4.647

Support MacOs scroll and zoom
Annotations - Fixed crash when @Entity has empty ()
Annotations - Fixed invalid import of many-to-many join column reference
Fixed Windows32/64 installer - missing annotations .osc file

2.1.3.643 - second release

Fixed PropelORM support on Linux and MacOS
Updated MacOS deploy script to correctly deploy App icon

2.1.3.643

PropelORM support on all platforms

2.1.2.641

Open .ormdes from MacOs doesn't work
Application icon for macos / windows
Fixed visual project size migration from old ORMD1 projects
Can't change background color of module
Fixed storage of comments location when inside of another region
Bug in migrating model layout from ORMD1 projects
Implemented migration of regions and comments from ORMD1 project
Added missing serialization for comments
Fixed load/save of regions and recursive child
Also colors of regions and comments can't be changed

2.1.1.633

App crash when click on checkbox "detect_relation" in ORM Property editor
Bug in bool attribute type in ORM Property editor
Small font on the license window (MacOs)
Invalid spacing between checkboxes on project tree (MacOs)
Fixed License dialog UI on Mac OS
Fixed License windows resizing
Fixed migration from ormd1 to ormd2 project with lot of many to many relations
Move Ribbon QuickBar between Main button and tabs on Ubuntu and MacOS

2.1.1.631

Many to Many wizard fix
Display version of libraries in about window
updated crash sender window size
several internal fixes and optimalizations

2.1.1.628

Doctrine2 XML/YML support
Discriminator value for base entity (Load,Save,Import,Export).
ManyToMany association ordering for owning/inverse side
Bug in property editor when ORM structur refer to another structure
Bug in many-to-many editor, app can crash
Replace vcredist.exe from installer by including msvcp100.dll and msvcr100.dll

2.1.0.626

Mouse cursor does not change when selecting "Inheritance","Association" or "ManyToMany" like in ORMD1 defect closed
Closing a project by right-clicking on the tab would be great. defect closed
Open project from command line sometimes crash defect closed
"File" -> "Exit application" not working defect closed
Unsaved changes will be discarded when exiting with close button (red X at top-right) - defect closed
Missing "Save" question when closing project with modification defect closed
Imported project is stored in temp without SaveAs question defect closed
Same with Versionable and "children" defect closed
When editing Timestampable relation, removing an "options" "value" from either created or updated leads to the hole behavior being deleted defect closed
Fixed crash when deleting complex attribute structure defect closed
New entity: Name is not selected for overwriting defect closed
"Export to ORM" seems to not do anything (disconnected button from action) defect closed
Fixed loading empty Timestampable (and any other) behavior for Doctrine1 defect closed
ESC no longer close whole app when pressed on UnhandledException window enhancement closed
Open multiple .ormdes project from command line at once defect closed
Open .ormdes from Windows explorer doesn't work defect closed
Removed debug console from release version of app defect closed