Visual Format String Grammar

本文介绍了一种用于描述用户界面布局的语言,通过符号和规则定义视图之间的位置及大小关系。详细解释了如何使用该语言来指定不同视图组件间的连接、约束条件以及它们与父视图的关系。

Symbol

Replacement rule

<visualFormatString>

(<orientation>:)?(<superview><connection>)?<view>(<connection><view>)*(<connection><superview>)?

<orientation>

H|V

<superview>

|

<view>

[<viewName>(<predicateListWithParens>)?]

<connection>

e|-<predicateList>-|-

<predicateList>

<simplePredicate>|<predicateListWithParens>

<simplePredicate>

<metricName>|<positiveNumber>

<predicateListWithParens>

(<predicate>(,<predicate>)*)

<predicate>

(<relation>)?(<objectOfPredicate>)(@<priority>)?

<relation>

==|<=|>=

<objectOfPredicate>

<constant>|<viewName>(see note)

<priority>

<metricName>|<number>

<constant>

<metricName>|<number>

<viewName>

Parsed as a C identifier.

This must be a key mapping to an instance ofNSViewin the passedviews dictionary.

<metricName>

Parsed as a C identifier. This must be a key mapping to an instance ofNSNumberin the passed metrics dictionary.

<number>

As parsed bystrtod_l, with the C locale.




我们以 btn1 和btn2 为例子

[btn1]-[btn2] 这个 “-” 标准连接字符 ,表示相距标准距离,好像是 8

[btn1 (>= 10)] btn1 宽度至少为10

H:|-50 -[btn1]-30-| “H“表示水平,”|”表示父视图, 这说明 btn1 在水平方向距离父视图左边50 右边30

[btn1(==btn2)] btn1 和btn2 宽度相等

[btn1 (>= 10,<= 50)] btn1的宽度在10和50 之间


说下这个<view>

我们可以这样写

|-[btn1]-|

也可以这样

|- 50-[btn1]-|

也可以这样

|-(>=10,<=30) - [btn1 (>=30)] -(<=20)-|



.net 8.0 <PackageReference Include="indice.Edi" Version="1.12.0" /> 将X12文档反序列化为.NET对象,解析處理EDI850文件 完整代碼 EDI Serializer/Deserializer. Used to read & write EDI streams. This is a ground up implementation and does not make use of XML Serialization in any step of the process. This reduces the overhead of converting into multiple formats allong the way of getting the desired Clr object. This makes the process quite fast. Tested with Tradacoms, EDIFact and ANSI ASC X12 (X12) formats. Using attributes you can express all EDI rules like Mandatory/Conditional Segments, Elements & Components as well as describe component values size length and precision with the picture syntax (e.g 9(3), 9(10)V9(2) and X(3)). Quick links Installation Attributes Example usage Deserialization (EDI to POCOs) Serialization (POCOs to EDI) Contributions The Picture clause Roadmap Installation To install Edi.Net, run the following command in the Package Manager Console. Or download it here PM> Install-Package "indice.Edi" Attributes. The general rules of thumb are : Attribute Description EdiValue Any value inside a segment. (ie the component value 500 in bold) UCI+001342651817+9907137000005:500+9912022000002:500+7 EdiElement Elements are considered to be groups of values otherwise known as groups of components. One can use this attribute to deserialize into a complex class that resides inside a segment. For example this can usually be used to deserialize more than one value between + into a ComplexType (ie the whole element into a new class 9912022000002:500 in bold) UCI+001342651817+9907137000005:500+9912022000002:500+7 EdiPath To specify the path EdiSegment Marks a propery/class to be deserialized for a given segment. Used in conjunction with EdiPath EdiSegmentGroup Marks a propery/class as a logical container of segments. This allows a user to decorate a class whith information regarding the starting and ending segments that define a virtual group other than the standard ones (Functional Group etc). Can be applied on Lists the same way that [Message] or [Segment] attributes work EdiMessage Marks a propery/class to be deserialized for any message found. EdiGroup Marks a propery/class to be deserialized for any group found. EdiCondition In case multiple MessageTypes or Segment types with the same name. Used to discriminate the classes based on a component value Example usage: There are available configurations (EdiGrammar) for EDIFact, Tradacoms and X12. Working examples for all supported EDI formats can be found in the source code under tests. EdiFact sample POCO classes TRADACOMS sample classes (UtilityBill) X12 sample classes (850 Purchase Order) Note that all examples may be partialy implemented transmissions for demonstration purposes although they are a good starting point. If someone has complete poco classes for any transmition please feel free to contribute a complete test. Deserialization (EDI to POCOs) The following example makes use of the Tradacoms grammar and deserializes the sample.edi file to the Interchange class. var grammar = EdiGrammar.NewTradacoms(); var interchange = default(Interchange); using (var stream = new StreamReader(@"c:\temp\sample.edi")) { interchange = new EdiSerializer().Deserialize<Interchange>(stream, grammar); } Serialization (POCOs to EDI) In this case we are instantiating our POCO class Interchange and then fill-it up with values before finally serializing to out.edi. var grammar = EdiGrammar.NewTradacoms(); var interchange = new Interchange(); // fill properies interchange.TransmissionDate = DateTime.Now; ... // serialize to file. using (var textWriter = new StreamWriter(File.Open(@"c:\temp\out.edi", FileMode.Create))) { using (var ediWriter = new EdiTextWriter(textWriter, grammar)) { new EdiSerializer().Serialize(ediWriter, interchange); } } Model Annotated POCOS example using part of Tradacoms UtilityBill format: public class Interchange { [EdiValue("X(14)", Path = "STX/1/0")] public string SenderCode { get; set; } [EdiValue("X(35)", Path = "STX/1/1")] public string SenderName { get; set; } [EdiValue("9(6)", Path = "STX/3/0", Format = "yyMMdd", Description = "TRDT - Date")] [EdiValue("9(6)", Path = "STX/3/1", Format = "HHmmss", Description = "TRDT - Time")] public DateTime TransmissionStamp { get; set; } public InterchangeHeader Header { get; set; } public InterchangeTrailer Trailer { get; set; } public List<UtilityBill> Invoices { get; set; } } [EdiMessage, EdiCondition("UTLHDR", Path = "MHD/1")] public class InterchangeHeader { [EdiValue("9(4)"), EdiPath("TYP")] public string TransactionCode { get; set; } [EdiValue("9(1)", Path = "MHD/1/1")] public int Version { get; set; } } [EdiMessage, EdiCondition("UTLTLR", Path = "MHD/1")] public class InterchangeTrailer { [EdiValue("9(1)", Path = "MHD/1/1")] public int Version { get; set; } } [EdiMessage, EdiCondition("UTLBIL", Path = "MHD/1")] public class UtilityBill { [EdiValue("9(1)", Path = "MHD/1/1")] public int Version { get; set; } [EdiValue("X(17)", Path = "BCD/2/0", Description = "INVN - Date")] public string InvoiceNumber { get; set; } public MetetAdminNumber Meter { get; set; } public ContractData SupplyContract { get; set; } [EdiValue("X(3)", Path = "BCD/5/0", Description = "BTCD - Date")] public BillTypeCode BillTypeCode { get; set; } [EdiValue("9(6)", Path = "BCD/1/0", Format = "yyMMdd", Description = "TXDT - Date")] public DateTime IssueDate { get; set; } [EdiValue("9(6)", Path = "BCD/7/0", Format = "yyMMdd", Description = "SUMO - Date")] public DateTime StartDate { get; set; } [EdiValue("9(6)", Path = "BCD/7/1", Format = "yyMMdd", Description = "SUMO - Date")] public DateTime EndDate { get; set; } public UtilityBillTrailer Totals { get; set; } public UtilityBillValueAddedTax Vat { get; set; } public List<UtilityBillCharge> Charges { get; set; } public override string ToString() { return string.Format("{0} TD:{1:d} F:{2:d} T:{3:d} Type:{4}", InvoiceNumber, IssueDate, StartDate, EndDate, BillTypeCode); } } [EdiSegment, EdiPath("CCD")] public class UtilityBillCharge { [EdiValue("9(10)", Path = "CCD/0")] public int SequenceNumber { get; set; } [EdiValue("X(3)", Path = "CCD/1")] public ChargeIndicator? ChargeIndicator { get; set; } [EdiValue("9(13)", Path = "CCD/1/1")] public int? ArticleNumber { get; set; } [EdiValue("X(3)", Path = "CCD/1/2")] public string SupplierCode { get; set; } [EdiValue("9(10)V9(3)", Path = "CCD/10/0", Description = "CONS")] public decimal? UnitsConsumedBilling { get; set; } } Contributions The following is a set of guidelines for contributing to EDI.Net. Did you find a bug? Ensure the bug was not already reported by searching on GitHub under Issues. If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring. Did you write a patch that fixes a bug? Open a new GitHub pull request with the patch. Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable. Build the sourcecode As of v1.0.7 the solution was adapted to support the dotnet core project system. Then it was adapted again since the dotnet core tooling was officialy relased (March 7th 2017 at the launch of Visual studio 2017). In order to build and test the source code you will need either one of the following. Visual studio 2019 + the dotnet sdk 8.0 (for v2.0.0 onwards) Visual studio 2017 + the dotnet core workload (for versions v1.1.3 - v1.x.x) Visual studio 2015 Update 3 & .NET Core 1.0.0 - VS 2015 Tooling (for versions v1.0.7 - v1.1.2) VS Code + .NET Core SDK for more information check .Net Core official page. The Picture clause The Picture Clause is taken from COBOL laguage and the way it handles expressing numeric and alphanumric data types. It is used throughout tradacoms. Symbol Description Example Picture Component c# result 9 Numeric 9(3) 013 int v = 13; A Alphabetic not used - - X Alphanumeric X(20) This is alphanumeric string v = "This is alphanumeric"; V Implicit Decimal 9(3)V9(2) 01342 decimal v = 13.42M; S Sign not used - - P Assumed Decimal not used - - Roadmap (TODO) Implement serializer Serialize to write Clr classes to edi format (Using attributes). (planned for v1.1) Start github wiki page and begin documentation. Create a seperate package (or packages per EDI Format) to host well known interchange transmitions (ie Tradacoms Utitlity Bill). Then anyone can fork and contribute his own set of POCO classes. Disclaimer. The project was inspired and influenced by the work done in the excellent library JSON.Net by James Newton King. Some utility parts for reflection string parsing etc. are used as is
11-28
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值