Extending the base class to DatePickerlnputs

Chapter 05: System Implementation

5.2 Extending the base class to DatePickerlnputs

5.2.1 Define properties of the sub-classes

1. Create widgets.py file to contain all the sub-classes.

2.

All classes will extend the BaseDatePickerlnput class.

3.

Classes will override the default values to render different date-picker widgets.

5.2.1 Exporting the DatePickerlnput Classes

lmporting

into init

.py makes selected CIasses, functions, etc accessible to the package level

so

they

can

be conveniently imported from

the

package. So

we will

import

the

DatePickerlnput classes to

_init

^{.py file to} make it accessible outside of the package.

38

5.3 Publish to a Github repository

GitHub

lnc. is a

web-based hosting service

for

version control using

Git. lt is

mostly used for computer code. !t offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features.

5.3.1 Objectives

1. Create a fresh repository _[1]

2.

Short, memorable _but self-explanatory name for the repository

3.

Add a description to the repository that best describes the package

4.

Make the repository public for community suggestions and feedbacks

5.

lnitialize this repository with a README which best represents the package.

I

T

l

_*

=

.

I

5.4 Publishing to PyPl

The Python Package lndex (PyPl) is a

repository

of

softvyare

for the ^python

programming 'language- PyPl helps find and installsoftware developed and shared by the python communig.

Package authors use PyPl to distribute their software.

.z

:

*

t;

t I=t.

t:

I=t1 E_

I

f:

E

c

Fi'j

=j.

5.4.1 Objectives

!

^{Retease lristory}

*

^{Downtoad files}

1.

Host the package on PyPl for easy instaltation via pip _[2].

2.

Give the package a unique name that is self-explanatory and search friendly

3-

Upload and maintain different versions of the package with proper dependencies.

8ootstrop3,,'Boofsfrrp4 oafePirlrerfnp&L tri,?iePrrkerfnput, Octelirn eqickertnput^&tronr&picirerlnpuf.. -yeorFickerinpr.,tr r,ffilh d at*-ra _{n Ee-} p i cker fu nct onclr4. fcr {'tlngo uers;on Z 0.5. i. t i, l. I 0 s n d l.

I

Project description

This django widEet containE Bootstrap3y'Boor:trap4 BateFickerinput, Timepickerlnput, DateTirneFickertnput. l.{onthPickerfnput, yearpickerlnpLrt _r,'r'ith date-range-picker functiona[ity for django version 2.0,s, 1.11, 1"J.0 *nd i..g. The r,vidget implernents bootstrap- datetinrepicker r.,4 to shor,r' beotstrap-datepicker in django model forms _and cuslom forms and can b= configured easily for date-rnnge selection.

Figure 5.2: The PYPI page of the package

Navig*tion

4A

5.5 Publishing to Django Packages

Django Packages is a directory of reusable apps, sites, tools, and more for your Django projects.

This is the

plaee

to list

python packages

that are

specific

to

django framework.

This

directory contains a huge collection of django reusable resources for the passionate developers to find and implement in their own projects. _[3]

1.

List the package to a place specific to Django development

2.

Make the package more available to Django developers.

Repo Activity -r3t'tttfed I +;etl

5.5.1 Objectives

Releases

j:_

:::

Documentation

FyFi

Repo

Comparison Grids

$ite*

using this Figure 5.3: The Django Packages page of the Package

I

5.6 Publish Demo pages

5.6.1 Demo with Bootstrap 3

C? *!jae rgo-hootsirap-datet:icker-pius _Gfi Giihilb Demo vi'ith Esetstrap 3 ilit?.ir ?r,ith gr-,iltrstrs$ q

dja

n

go-bootstra p-datepicker-p

_I

us wid get co

m

pon ents

glart _clal€:

2018-05-21

End.tab:

05J232018 stsrt tine:

0e.31 End tnr*:

0s 3t SErtdatetim.:

05i16,2018 12.3.1 EITI .taEtrilE:

05J16i2018 12.31 Stan m6nth:

2018-85-01 End rEofifr:

2018-06-30 Start yBil:

2i,174 1-01 Enal year

2!1 8-1 2-31

a

Figure 5.4: The demo page with bootstrap 3

l

* [- li

l

E

_:

.- 't

Jr

:

5.6.2 Demo with Bootstrap 4

O d: a-:g* ^- bcot:i ^ia!-r- d a ier; irk* r-p ⁱ u: o n fi itnub

dj

a n g o ^-

bootstrap ^-d atep

ic [<er-

plu s wid

g

et ca m pon entg

'::1

LJ

n

t

jr t_*

t

:f

*

=

?:

#

ffi

ET

5.7 Publish package documentation (README)

No matter how the quality

of a

product is,

a

book

is

always judged by it's cover. The cover

of

a

repository

is the

README

of a

Github repository.

The

README should contain

the

following informations to reflect the important aspects of the package.

1. A small introduction to what the repository is all about.

2.

Some repository badges to reflect some insights of the quality of code inside.

3.

An image to to display the end result of the package.

4.

Some demo links to see the package in action.

5.

Prerequisites of the package.

6.

Detailed usage guide of the package.

7.

Licence and Acknowledgements

5.7.1 The lntroduction

dja ngo

^-

bootstra p-datepi cker- plus

Su I\.Io

Hay 3016

Tu l.!e Th Fr

5u

^{Ir4 o}

tu5ay 201

I

Tu lAle Th

',.j"

Fr 5a

l__l

08 31 5a

x +

_+_I

+

44

i

=

!

t

*

= +

5.7.2 Demo, Getting Started

Demo

a :',:..i1:".:':,, . ':-:::l:l:':.1 ^+,

Getting

Started Frerequisites

. P.,i-ra-r ^:- = :.3 . [:_;.-:i;* -i:1.I1 r !;1151-1;,>= li

r lXl.ir; r= l.l -t

Installing i-:-:: r.: r'.t,>-,.

:._. _-_:___r_:

i

':.;;iii :i ;:;;::l:r:- :,j,.:',

)

jii!li'',' , '.*:l:t: ':r iala::i{a- ^:a: ':r'ii:i. '";1a i.Ltr+ -,;-, i"!r.,':_r:;ir., i r.jlif :+i::i;:i ;r..tr:,-) aar ;;i j+-r!.:. i:,: ;;1:j

'. -.h E:::;:.i: r:. i:::-:: '--:-.-:; ):.,2- :a-.:1.--: ---i -: . ti j+:-.:-;!.: 'i : ' ;-. t:.---; ;

=,)i'i-r::a ^' i:'!;-5-i,;:j :i''i rlt Liii'r: _.r.ii. "r,.,: ii {i?1t? _-1't-

: :

t

e

5.7.3 Usage

Usage

(Llstorn Forrn usage

t,ie er

:::=,':'i ;,'-' r';:a-:

46

=

t

F

=

5,7.4 Customising the Options

Testing & Quality ^Management

=

6.1 Unit-Testing

ln

computer programming, unit testing

is a

software testing method by which individual units of source code, sets

of

one

or

more computer program modules together

with

associated control data, usage procedures, and operating procedures, are tested to determine whether they are fit for use.

6.1 .1 Unit-Testing tools

There are many tools for creating tests in Python. Some of these tools, such as pytest, replace the built-in unittest framework. Other tools, such as nose, are extensions that ease test case creation.

Note

that

many

of

these tools

are

also used

for

integration testing by writing

the test

cases to exercise multiple parts of code at once.

unittest

is the built-in standard library tool for testing Python code.

pytest

is

a

complete testing tool that emphasizes backwards-compatibility and minimizing boilerplate code.

nose is an extension to unittest that makes it easier to create and execute test cases.

Hypothesis is a unit

test-generation

tool that

assists developers

in

creating

tests

that exercise edge cases

in

code blocks. The _best way

to

get started using Hypothesis

is

by going through the well-written quickstart.

testify

was a testing framework meant to replace the common unittest+nose combination.

However, the team behind testify is transitioning

to

pytest so it's recommended you do not use testify for new projects.

a a

a a

6.1 .2 Code for Testing

=

t

E

49

6.1.3 Unit-Testing with pytest

pytest is a mature full-featured Python testing tool that helps you write better programs. The pytest framework makes it easy to write small tests, yet _scales to support complex functional testing for applications and libraries.

Test Results:

Figure 6.'t: pytest unit-test results

6.1.4 Unit-Testing with Travis-Cl

Travis

Cl is a

hosted, distributed continuous integration service used

to

build and

test

software projects hosted at GitHub. Open source projects may be tested at no charge via travis-ci.org.

6.1.4.1 Travis-Cl build flow

6.1 .4.2 Travis-Cl Result

F

{3 .+€

*""#

E

Figure 6.2: travic-Cl build result

51

6.1.4.3 Travis-Cl build history

!i*Fr€

i*d*

=

,,,=*{13

6.2 Code-Coverage

ln computer science, test coverage is a measure used to describe the degree to which the source code of a program is executed when a particular test suite runs. A program with high test coverage, measured

as a

percentage,

has had more of its

source code executed during testing, which suggests

it

has

a

lower chance

of

containing undetected sofiware bugs compared

to a

^program

with low test coverage.

6.2.1 Coveralls. io stats

s#ersffeg&s

^?.

!&

{F

tf ct

*

+

tr#tr$ffi sr #Js$€##"###r$rffiss :#gflgtr$#trfftr "f*#$

*ir{q,"rf

:+1:r':.J+rii;

ffi#

q,.-".s

t&1T

$t"i[* *ii

*R&i{{t{ r",.t*:?$*

sffiffiffin

M

ffi

E

53

6.2.2 Coveralls.io details and builds

f0vEFsrs,s

=4

fiefE?{T

frlj't*s

ffi

^r--i::;.:j

ffiSE

ffi

^j--.:::

Figure 6.4: coveralls.io report

6.3 Maintainability

Maintainability

is an

estimate

of

technical

debt in the repo

based

on a

standardized 1O-point assessment of Duplication, Cyclomatic Complexity, Cognitive Complexity, and structural issues.

6.3.1 Code-Climate Report

The 10 checks outlined below are enabled by default in Code Climate.

.

,Argument

count

- Methods or functions defined with a high number of arguments

.

Gomplex Iogic - Boolean logic that may be hard to understand

.

File length - Excessive lines of code within a single file

r ldentical blocks of code -

Duplicate code

which is

syntactically identical

(but may

be formatted differently)

o Method complexity -

Functions

or

methods

that

may

be

hard

to

understand (Cognitive Complexity)

o

Method

count

- Classes defined with a high number of functions or methods

.

Method length - Excessive lines of code within a single function or method

o

Nested

control flow

- Deeply nested control structures like if or case

.

Return statements - Functions or methods with a high number of return statements

. Similar blocks

of code - Duplicate code which is not identical but shares the same structure (e.9. variable names may differ)

ai

^coar crtraalg

",..-:i-'

il'r37

(-.)i.i''i:,i.)-:.-ji-r,:t--::,1

i:'-t ;

^,:-.

-:',j

^._ i,,.:i'-i_rl.

j::,

, .

:

, _'. al

:

^,.',, li

55

Project Success

.

7.1 Project Stats on Github

a a a

1,11:..r::*::

7.1.1 Watchers

watching

a

Repository registers

the

user

to

receive notifications

on

new discussions, as well as events in the user's activity feed. See Repository Starring for simple repository bookmarks.

These are the developers cunently watching this repository for instant notification of any updates published to this repository.

O r.lt:,r1:ir - ; * i..:rii a.

Watchers

Watchers:7 Stars: 39 Forks: 5

iir-,iai : :, ":i.11

;ii.ti nit ^;1

{!

L ,8 'slt

? )i. .a L ^-tj i; ^11;;:;,

iti.:

5

*

^{r:1 *, t',, :;t} _1:;-: :.: ii.:

* li'.':..3 ^-: t:i. t ^7: lj: :. t I ^j..-; I ^i_

i::: : '

t i'__))'-.\

i:i:.

O ij.i.:t:ir -

56

7 .1

.2 Stars

Repository Starring

is a

feature

that lets

users bookmark repositories. Stars are shown next to repositories to show an approximate level of interest. Stars have no effect

on

notifications or the activity feed. For that, see Repository Watching.

The project has received 39 stars and this number is still ^growing as more and more developers find out this package. The usefulness and quality of a project is reflected by these stars provided by the developers who are using it.

Starred by

Stargazers

:L;l'

A.

*&*

I -. ._. r ^.._

i :: :

^

^::;

r _- -,.--,:.

r . -'-'r -- ^I

t

&u{

7 .1

.3 Forks

A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.

&

7 .1

.4 Msitor Graph

The visitor count keeps on rising as days pass by proving the project is reaching more and more developers making this project a success.

r:'- *

a-

-\,=

=5q- "L €-

-'C----

:,2r, ;ts;- ii::. :i:-r :.-z1 l- :i'

.-\

t -l "t

.,, \ ',i

.'\ ',\

".i \ _aF_-_r___-**

:- :-i i- ;i l- :,- )-::a

728 ,I2B

€

t

E*ferrng r:tel

.:

-il

(},

$ ::

^{' ' i- ,, :',,,}

$ ':'- : ",:,: : : : i::j :j;: :

$

^{:'.: ::,}

$ ^:

^{.;, :r,:;: :: -,}

:

: :::.'

._J I i :i"r'-

Ft1:ltlat ir-rfitefrl

le

f:,t=j

tr

l-a,

is]

+

7.2 Activity on Stack-Overflow

7.2.1 Questions on Stack-Overflow

There are 12 questions on stack-overflow about this project all asked by django developers who were having difiiculties

to

implement

this

package to their django powered site. These questions provided a lot information to help make the project more user-friendly and easier to implement.

This activity on stack-overflow shows this package is receiving traction more and more developers are being interested in using it in their own project.

:.t;.rckoverflow

Search Results

$ ^S:ac" !!.{!.:#

a-

r

E

60

7.2.2 Answers on Stack-Overflow

This

answer

were

posted encouraging

the use of this

^package

in

django

site

describing the installation setup and usage

of

it which has received

5

votes by

the

community members. This shows developers are really appreciating this package as a useful tool for their django sites.

- J;':rluary ^2OOil

lu ^{vlo Tu lYe Th

ffi

. Augu:.t iO13

511 l*:s Tri LVtr Th fr frS*t

:,

l,r_:

L _'.

O{tal}.} 200} Fr

5{r f;l$ Tir ^t.!.ie Th

5.1

ffi

ffi

#E

:#

*

*

I

r

Conclusion

t

l

I

ts r'

I

-

j

r

i

r

F

=n

L

E E

I

F

8.1 The Experience

hlcrking in this project was

a

big opportunity

for

me.

I

have leamed

a

lot about

the

open-soLirce contribution to community software development. The following will indicate the leaming ftom this project.

1.

The design and development strategy of a django package.

2.

Publishing a well-appreciated project to the biggest online community Github and maintain a meaningful commit history

3.

Unit-testing complex scenarios of software development.

4.

^{Writing code} with

well

accepted code

writing

guidelines (PEP8).

5-

Working with the Travis-Cl build system and incorporating build system to a repository.

6.

^Generate repository coverage reports

with

Coveralls.io.

7.

Learning code maintenance guidelines provided by CodeClimate.

8.

Writing clear and thorough documentation of how to use a software.

9.

^{Packaging and} uploading a package to PY?I

Sthon

^{Packages Index.}

10. Developing a project with end-user follorv ups. bug reports and feature requests.

11. Developing a product

with

a thoughrful user-*perience"

8.2 Future Work

The package

is

published online

on

both Github and

PyFl

package index and thus available to django developers to implement in their django

power#

sites. lt's receiving lot of appreciation and new features suggestions that

will

keep

the

project growing. Here

is a

summary

of my

preseili thoughts of future works.

1.

Developing

a

clock-like

Ul for the tim+picker that looks

more

neat and

provide _easier selection of time.

2.

There _are some bugs present in the date'picker library used

to

render

the Ul

all listed on

=

F

.

*

,

-