ผลต่างระหว่างรุ่นของ "CuneiForm"

CuneiForm (ดูต้นฉบับ)

รุ่นแก้ไขเมื่อ 13:23, 5 เมษายน 2567

เพิ่มขึ้น 1,331 ไบต์ , 5 เมษายน 2567

→‎Define

Tenko

ผู้ดูแลระบบสิทธิแต่งตั้ง, ผู้ดูแลระบบอินเตอร์เฟซ, ผู้ดูแลระบบ

1,844

การแก้ไข

@@ บรรทัดที่ 8: / บรรทัดที่ 8: @@
 <syntaxhighlight lang="python" line="1">
 class LoginForm(FlaskForm, CuneiForm):
-     company = StringField(lazy_gettext("Company"), validators=[InputRequired(lazy_gettext("Required!"))])
+     company = StringField("Company", validators=[InputRequired("Required!")])
-     username = StringField(lazy_gettext("Username"), validators=[InputRequired(lazy_gettext("Required!"))])
+     username = StringField("Username", validators=[InputRequired("Required!")])
-     password = PasswordField(lazy_gettext("Password"), validators=[InputRequired(lazy_gettext("Required!"))])
+     password = PasswordField("Password", validators=[InputRequired("Required!")])
-     clear_session = BoolField(lazy_gettext("Log-out of other sessions"), default=True)
+     clear_session = BoolField("Log-out of other sessions", default=True)
-     submit = SubmitField(lazy_gettext("Log-in"))
+     submit = SubmitField("Log-in")
      def validate_company(self, company):
@@ บรรทัดที่ 22: / บรรทัดที่ 22: @@
 </syntaxhighlight>
+'' Developers might find uses of {{code|BoolField}} and {{code|IntField}} in CuneiFox code base unfamiliar. This convention is to avoid name conflict betweem WTForm and Peewee.''
+=== Special Value Types ===
+This feature plays a crucial role in ensuring consistent value formatting for client-side output. While it originated as a solution to address browser formatting inconsistencies, it has evolved to serve several other purposes within the CuneiFox framework.
+==== Original Intentions ====
+Reading through the CuneiFox code base, one is sure to notice the excessive use of StringFields where one would expect DateFields, TimeFields, FloatFields, and IntegerFields as supported by WTForms. This design choice stems was made to address a challenging browser behaviour. Modern browsers tend to enforce formatting of fields marked as certain types based on the user's locale setting, which can be tied to either the operating system or the browser itself. This automatic formatting can be difficult to override or reverse, leading to inconsistencies and confusion on the user's part especially when switching workstations.
+To address this issue, CuneiFox developed its own value typing. Our approach applies our custom-made JavaScript code on unformatted and untyped (as far as the browser is aware) fields. This way, the formatting rendered on the client-side perfectly obeys the company's specific preferences within the CuneiFox system.
 == Initiate ==