Improve feature: DXF Text String Names

Issue #714 resolved
legija created an issue

In Optitex, and in other CAD software, text from DXF files each get recognized in separate strings according to a global "dictionary"

In order to facilitate easier importing, with automatic recognition of text in the importing software, the current strings should be appended with:

Valentina Currently

1. Name of Detail

2. Letter

3. Material type

4. Cut number

5. Placement

DXF/Layout Resulting Name

1. Piece Name: xx

2. Piece Code: xx

3. Material: xx

4. Quantity: xx

5. Do not use

Suggestion for Roman:

It is currently possible to make a "pattern label" in Valentina.

This pattern label contains the following information:

Valentina Currently

1. Pattern Name

2. Pattern Number

3. Company/Designer Name

4. Customer Name

5. Pattern Size

6. Measurement File

7. Date of Creation

DXF/layout string

  1. Do not use. I explain later.
  2. Merge with resulting Pattern Name
  3. Author
  4. Do not use. I explain later
  5. Size
  6. Use this as Pattern Name! (so 1., combined with 2.)
  7. Creation Date

So Pattern Label would be added to biggest piece only, then look like this:

Style Name: measurementfileblabla, 00012

Creation Date: 30-06-2017

Creation Time: 10:57:01

Author: bespoketailor

And Detail Label would look like:

Piece Name: Fabric_FrontLeft

Piece Code: AX

Material: Fabric

Quantity: 1

Now about Pattern Number. Right now, in the Pattern Properties under General Info, there is a string called Pattern Number. I don't really understand the philosophy behind this and have a better suggestion.

Right Now, you give a Pattern a name, AND a code. Why both? Name can also be a code. (It usually is)

If code automatically increments/increases when making a new layout, this will be logical. You have a constant, which is the "Pattern Name" this always takes the value from the measurement file. Then you have "Pattern Number", And each time you make a new layout, it goes from example "00011" to "00012". This would then be added after the "Pattern Name" with a ",".

Comments (24)

  1. Roman Telezhynskyi repo owner

    Also, please remove .vit from measurement file in Pattern Label.

    You can disable this string in pattern options.

  2. Roman Telezhynskyi repo owner

    I don't really understand the philosophy behind this and have a better suggestion.

    This is not my idea. @tusuzu, will tell you why.

  3. Roman Telezhynskyi repo owner

    Probably i will do it in my way this time. I see very low flexibility of current approach. We need something more flexible and powerful.

    I am thinking about constructor with placeholders.

  4. legija reporter
    You can disable this string in pattern options.
    

    The entire string yes, but what I mean is the ".vit" extension -after- the measurement file name.

  5. legija reporter
    Probably i will do it in my way this time. I see very low flexibility of current approach. We need something more flexible and powerful.
    I am thinking about constructor with placeholders.
    

    I will follow your advice as usual.

    The most important thing is to have certain things recognized in other software without manual labor. So you import a dxf file into a third party software, and everything just imports. With all the information directly transferring.

  6. Susan Spencer

    Pattern names separate from Pattern numbers are useful, but not for DXF.
    The total export bundle is discussed in issue #457 for upload to our pattern share/online catalog which will allow pattern names and numbers.
    Systems interoperability is one of the foundational ideals behind Valentina, since the earliest beginning in 2010.
    Here are examples of successful companies using pattern names with, and without, pattern numbers:
    These companies use automated interfaces to generate patterns and envelopes, and to display uploaded patterns in catalog format without manual intervention.


    CollettePatternWebsite2.png

  7. Susan Spencer

    If code automatically increments/increases when making a new layout

    This image shows current autoversioning with export file names in Layout mode. Is there a need for a change to this feature, or is this sufficient?

    ExportFile_autoVersioning.png

  8. Susan Spencer

    @bespoketailor Do you want to import your Valentina layouts into a CAD program? If so, this issue is about creating a DXF-ASTM export file using the specification here.
    Please change the name of this issue to reflect that you are asking for a Valentina export file to import into a CAD system, not for sending to a cutting table or other CNC machine.

    Issue #391 is for exporting to DXF-AAMA format, which is optimized to contain only the data required for sending to cutting table & CNC pre-processing software, uses file extension .aama, and is not meant to be viewed or edited or changed.

  9. legija reporter

    I was asked by Roman to detail how the text strings in dxf could be expanded. This is separate from dxf-astm/aama and seperate from cutfiles.

  10. Susan Spencer

    It seems now that we need three DXF exports, tuned to the import requirements of the receiving program.

    1. DXF-AAMA (for cutting table, and future marker layout feature)
    2. DXF-ASTM (for import into other pattern making systems)
    3. DXF r12 or r14 (for import into CAD systems)
  11. Roman Telezhynskyi repo owner

    It seems now that we need three DXF exports

    I don't think so. How is this related to how should look labels? As i understood, the problem here is how user want organize a label look, which fields and how should be present. Current way is very restricted. We need some sort of template support.

  12. Roman Telezhynskyi repo owner

    It seems now that we need three DXF exports, tuned to the import requirements of the receiving program.
    DXF-AAMA (for cutting table, and future marker layout feature)
    DXF-ASTM (for import into other pattern making systems)
    DXF r12 or r14 (for import into CAD systems)

    And yes, here you are right. We will support three standards. So, you half right. :)

  13. legija reporter
    It seems now that we need three DXF exports, tuned to the import requirements of the receiving program.
    DXF-AAMA (for cutting table, and future marker layout feature)
    DXF-ASTM (for import into other pattern making systems)
    DXF r12 or r14 (for import into CAD systems)
    

    I don't fully agree on this. We need two DXF export functions. As I detailed before, Valentina right now doesn't posess certain capabilities required for full operation in a mass production environment. Before that gets developed, Valentina needs to be ready to deliver data to a program that does already posess those capabilities.

    Therefore the solution is to make a more advanced dxf file come out of valentina, besides the normal dxf. That should either be DXF AAMA or DXF ASTM. Both at the core are exactly the same, they just get structured differently afaik. Maybe ASTM is a little more advanced but it serves the same purpose - that is, to transfer any and all information from one system to another (data exchange :) )

    Some apparel focused CAD programs have the ability to detect those formats, other normal CAD programs like autocad don't. As far as I know and understand, if you import a AAMA or ASTM file into a normal cad program, it will still read that format, just not take advantage of the extra functionality.

    So you need two, but this is, like roman said

    How is this related to how should look labels? As i understood, the problem here is how user want organize a label look, which fields and how should be present. Current way is very restricted. We need some sort of template support.
    

    Completely unrelated to this issue. Whether or not we export in "flat" dxf or "advanced" dxf, a new way to structure labels needs to be developed. Either for people who just want it differently, or in my case, to get my CAD program, to automatically detect and apply certain info on different pieces.

    1. I export in DXF flat or DXF advanced
    2. I import into Optitex
    3. Optitex detects a workpiece
    4. Optitex detects text, which it then tries to read
    5. If it says "Cut 1 of fabric" Optitex doesn't understand
    6. If it says "Material: Fabric" and "Quantity: 1" then it will automatically apply those paramaters to the imported workpiece.

    That's what this issue is about and it is unrelated to whatever export is neccesary, that is another issue entirely.

    Another scenario may be that company or individual X has gotten used to making their labels on patterns in a certain way. In this case, the current solution, as Roman correctly said, is very restrticted, and can not be adjusted. Therefore some template function or whatever is preferrable so people can customize this to their needs.

  14. Log in to comment