MobileRead Forums - View Single Post

Divingduck · 09-06-2016, 06:21 PM

@DaltonST,
You're welcome. I thought you like that

Give me a little bit time to take a closer look on your latest version and come back to you.

Edit:
I took a look

Well, where to start? In general I think for someone who had nothing in the past, this is much better then nothing, because with a little bit thinking around this is a good starting point (automated import of all files for an embroidering design). I guess, users of the pcs format will like the import of some basic metadata too. To import this in the comment field is no bad idea, because from there users can move the data then to custom fields if they wish to do this. This will preserve you to blow up your interface and give a user some freedom to be flexible.

With the color information I have a little problem. First your statement for hus isn't correct. Most of the actual home embroidery formats have color information in the design file. The problem is to identify the information. You are showing a representative RGB code for a thread color. I guess for most embroiderer this information is useless. They need a thread color number of a thread manufacturer. The other point with that is, mostly you will find no real thread color info. Instead you will see only a default value for a thread 1,2,3... Then you need a separate design information from the design company. (e.g. Color 1 is a Mettler Poly Sheen thread No 2170 with name Chiffon a.s.o.)
What are useful information?
Number of Stitches, number of used colors, thread manufacturer (if available), size of an embroidery (mm and inch). My own set have 13 entries, so a lot more.

Best regards, DD

Edit: just recognize, that's already implemented:
A other point are the formats. PCS and HUS is fare to less. The major formats are ART, DST, EMB, EXP, JEF, PES, SEW, VIP, VP3 and XXX as binary import formats or give a user the possibility to define/extend a free set of formats. I think the last one is the better solution.

09-06-2016, 06:21 PM	#923
Divingduck Wizard Posts: 1,166 Karma: 1410083 Join Date: Nov 2010 Location: Germany Device: Sony PRS-650	@DaltonST, You're welcome. I thought you like that Give me a little bit time to take a closer look on your latest version and come back to you. Edit: I took a look Well, where to start? In general I think for someone who had nothing in the past, this is much better then nothing, because with a little bit thinking around this is a good starting point (automated import of all files for an embroidering design). I guess, users of the pcs format will like the import of some basic metadata too. To import this in the comment field is no bad idea, because from there users can move the data then to custom fields if they wish to do this. This will preserve you to blow up your interface and give a user some freedom to be flexible. With the color information I have a little problem. First your statement for hus isn't correct. Most of the actual home embroidery formats have color information in the design file. The problem is to identify the information. You are showing a representative RGB code for a thread color. I guess for most embroiderer this information is useless. They need a thread color number of a thread manufacturer. The other point with that is, mostly you will find no real thread color info. Instead you will see only a default value for a thread 1,2,3... Then you need a separate design information from the design company. (e.g. Color 1 is a Mettler Poly Sheen thread No 2170 with name Chiffon a.s.o.) What are useful information? Number of Stitches, number of used colors, thread manufacturer (if available), size of an embroidery (mm and inch). My own set have 13 entries, so a lot more. Best regards, DD Edit: just recognize, that's already implemented: A other point are the formats. PCS and HUS is fare to less. The major formats are ART, DST, EMB, EXP, JEF, PES, SEW, VIP, VP3 and XXX as binary import formats or give a user the possibility to define/extend a free set of formats. I think the last one is the better solution. Last edited by Divingduck; 09-07-2016 at 04:38 AM.