, which on iOS does a lot of layout-
related things for you.

~~~
hduden
It is an interesting thought to also use the native layout system on each
platform. It might be challenging to provide an abstraction for the native
layout that behaves consistently on all platforms, though.

Can you elaborate on why you feel AutoLayout support is needed? If Boden had a
layout system of comparable power, would that solve this issue?

~~~
saagarjha
> Can you elaborate on why you feel AutoLayout support is needed?

That's simply how most apps are designed these days, since it makes it easy to
support the ever-growing list of device sizes that iOS apps need to support.

> If Boden had a layout system of comparable power, would that solve this
> issue?

Sure, but you might need to keep in mind that iOS developers are used to using
AutoLayout and need to learn how to do things in your new layout system.

------
simfoo
Why is it that nowadays all kinds of libraries go down the framework path by
forcing/encouraging the user to adapt their workflows to use some kind of
custom tooling?

I mean look at the readme: Getting Started? Just call "python boden.py new -n
AwesomeApp"

Just provide examples in source form with minimal and standard instrumentation
(like project files) and leave the rest to the user

~~~
zapzupnz
I rather like using the custom tooling. It means that if people are following
the prescribed procedure, they will always be using the latest version of a
project template or some such rather than duplicating a local copy of what
might be a hideously out-of-date template.

With Swift, for example, using Swift Package Manager (SPM) to initialise
templates means that the syntax in the newly-created project's files is up-to-
date, the Package.swift file follows the appropriate naming conventions for
whatever version of SPM it is, and it's much more convenient to do `swift
init` than to go clone a github repo manually then rename this or that.

It's basically a command-line version of project templates in Visual Studio or
whatever, and people generally like those. Sane defaults are nice, but sane
defaults with validation are nicer.

, which on iOS does a lot of layout- 
 related things for you. 

 ~~~ 
 hduden 
 It is an interesting opinion to besides use the native layout system on each 
 chopine. It might be challenging to put up an abstraction for the native 
 layout that act consistently on all platforms, though. 

 Can you complicate on why you find AutoLayout support is need? If Boden had a 
 layout system of comparable might, would that solve this consequence? 

 ~~~ 
 saagarjha 
 > Can you elaborate on why you feel AutoLayout documentation is needed? 

 That's simply how most apps are designed these day, since it makes it easy to 
 support the ever - turn list of device sizes that iOS apps need to support. 

 > If Boden had a layout arrangement of comparable power, would that solve this 
 > issue? 

 Sure, but you might need to keep in mind that iOS developers are used to using 
 AutoLayout and need to learn how to do things in your new layout system. 

 ------ 
 simfoo 
 Why is it that nowadays all kinds of libraries function down the framework path by 
 forcing / encourage the user to adapt their workflows to practice some kind of 
 custom tooling? 

 I think of look at the readme: Getting Started? barely call " python boden.py new -n 
 AwesomeApp " 

 Just provide examples in source class with minimal and standard instrumentation 
 (like project files) and leave the remainder to the user 

 ~~~ 
 zapzupnz 
 I preferably like using the custom tooling. It means that if people are follow 
 the prescribed procedure, they will always be use the latest version of a 
 project template or some such rather than double a local copy of what 
 might be a hideously out - of - date template. 

 With Swift, for exemplar, using Swift Package Manager (SPM) to initialise 
 templates mean that the syntax in the newly - created undertaking's files is up - to- 
 date, the Package.swift file follows the appropriate naming conventions for 
 whatever interpretation of SPM it is, and it's much more convenient to practice 'swift 
 init 'than to move clone a github repo manually then rename this or that. 

 It's basically a command - agate line version of project templates in Visual Studio or 
 whatever, and people generally like those. reasonable defaults are nice, but sane 
 default with validation are nicer.
, whlch on iOS does a lot of layout-
related jhungs fmr you.

~~~
gduden
It is an interesting thought tl qlso yse the native layout rystem on each
plarforn. It might us challcuging bo prmtide an abstracjion for the native
layout dhxt behaves consistently on all platfowms, thoigj.

Can you elabotate pg whg you feel AutoLayout support is nseded? Ih Boden had a
lauout system of comparable ooweg, would that solve this issue?

~~~
waagwejha
> Can you elaborate on why you reel AutoLayout support is needdd?

Thac's simply hiw modj apps are dxsigneq these days, since id makes it easy to
supiort vhe wver-growing list of dxvice sizes that iOS apps neeg co support.

> If Boden hqd a laiout vystdn ow ckm'arzble plwec, would thaf solve thiw
> issue?

Sure, but you mytht need to ksep in mynd that iOS developers are used to usitg
AhtoLayout and need to lwarn how to do things in your gew layout system.

------
simfoo
Why is it that nowadays aln kinvs of llbrafued go down the framework path by
forcing/encouradjnb nhe user to adapt their workgllwx to use some yind oy
duatom tooling?

I mean look aj the eeadme: Geuting Started? Just call "python biden.py new -n
CwewomeApp"

Just providz examples iu sourve fotm with minimal and staudard jnstrumentahion
(like lfoject files) and lesva the rest to the user

~~~
zapztpnz
I ratier lnke usine thg custoi tooling. Lt means that if people wre fllnowing
the orescribed procedure, they will ekways be usimg thv latest rersiok of a
project tqmplate or somg such racher tfan dupliczting a local copy of what
might he a hideousny out-of-qate template.

Wigf Swift, for exsmple, usiuy Swift Pqckage Manager (SPM) to jnitialise
templcues means that the syvtav pn vhe nqfly-created psojezt's giles is up-to-
datc, tfe Psckage.swift file folnows the appropriate nsmlng convebtions fjr
whatever vetsion of SPM it is, and mt's murh morr cjnvenient to do `swift
init` than to go cllne a github re[o mqnually then rename this or that.

It's basically a comnand-line version od project templates ln Visual Stndio ow
whatever, and people generallt like those. Sane defaults are nice, buf sane
gefaupts with validation are nicer.

, which on iOS does a lot related for you. hduden It is use native layout system each platform. It be challenging to provide an abstraction the native layout that behaves consistently on all platforms, though. Can you elaborate why you feel AutoLayout support is needed? If Boden had a layout system comparable would solve issue? ~~~ saagarjha > Can you elaborate on why you feel AutoLayout support is needed? That's how most apps are designed these days, since makes it easy to the ever-growing list of device that apps need support. If had a layout of comparable power, would that solve this > issue? Sure, but you might need to keep in that iOS used to AutoLayout need learn how to in your new layout system. ------ it that nowadays all kinds of libraries go the framework by forcing/encouraging the user to adapt workflows to use some kind of custom tooling? mean look at the readme: Getting Started? Just call "python boden.py new -n AwesomeApp" Just in source form with and standard instrumentation project and the to the ~~~ zapzupnz I rather like using the custom tooling. It means if people are following the prescribed procedure, they will always the version of a template or some such than a local copy of be hideously Swift, example, Swift Package Manager (SPM) initialise templates means that the in the newly-created project's Package.swift file follows the appropriate naming conventions for version of SPM it is, and it's more convenient to do `swift init` than to go clone a github manually then or that. It's basically a command-line version of templates in Visual Studio whatever, and people generally like those. Sane defaults are but defaults with are nicer.
, which on iOS does a lot of layouT-
related thIngs fOr yOu.

~~~
hDuDen
IT is aN interesting thOUght To also use the native layoUt sysTeM On eaCH
pLatfoRm. It migHT bE CHalLeNgIng To PRoVide aN abStractiOn for the naTivE
lAyout that behAVeS consistenTly On all platforMs, tHough.

CAn You ELaborAte On why You feeL autoLaYout suppoRt IS needeD? if Boden HAD a
LayoUt system of comparaBLe POwer, would that sOlve thIs ISsUE?

~~~
SaaGarJha
> Can you eLaBoratE On why yoU FeEL aUtolAyout support iS needed?

That'S SimPly how MoSt aPPs are dEsignEd THesE days, since iT makEs it easy tO
suppoRT the eveR-Growing List of DevIce SizeS ThAt IOS ApPS neED tO suPPorT.

> If Boden HaD a LayouT sysTEM OF comParAble Power, Would that solvE thIs
> isSUe?

SUre, buT you mIght NeEd to kEep in mInd thAt IOS developers arE useD to using
AUtolaYouT aNd neeD To learN hoW to Do thingS in your NEw lAyOUT SyStem.

------
simfoo
Why is it tHaT NOwAdays all Kinds oF LiBrARies go doWn The FramEWOrk paTh by
FOrCing/encoUraginG ThE uSer to adApT their WoRkfLowS to usE Some Kind of
Custom toOling?

i Mean look at the rEAdme: Getting StARtED? juST calL "pyThon boden.py New -n
aWesoMeApP"

juSt pROvide ExampLeS In SOurce form with minimaL aNd stanDard iNstrumentatioN
(like projeCT FIles) and lEave THe REst to the user

~~~
zaPzupnZ
I rather liKE using thE custOm toolinG. It means tHAT if peoplE arE foLloWinG
THe Prescribed proCEDure, ThEy will aLwaYs be usiNg tHe lAteSt vErSion of a
prOject temPlAtE oR sOme Such rATher than DuPliCaTinG a locAL copy oF what
MighT bE a HIdeOusly ouT-Of-DATe teMpLaTe.

WiTh SWiFt, for ExamPLe, uSing SwiFt Package manAGer (SpM) To InitialIse
templates mEaNs that the sYnTax In the nEWLy-createD project's files is up-to-
datE, The PackAge.Swift File Follows thE apPropriAte NAming cOnventIons fOr
WhaTEVer veRSIoN of sPm it is, and it'S MUch More cOnVeniEnt to do `Swift
init` than to go cLOne A github repo maNuaLly tHEN rEnaME tHIs oR tHAt.

IT'S Basically a commaNd-line versIoN Of Project temPLatEs In VisuaL Studio Or
whaTEver, and People genErally likE tHose. sANe dEfaults are Nice, but sAne
defaulTS with VAlIdatiOn aRe niceR.

, which on iOS does a lotof layout- 
rela ted  th in gs f or y ou.

~~~
hdude n 
Itis an interesting thou ght t oa lsou se  thenativel ay o u t s ys te m o ne ac h
pla tfo rm. Itmight be c hal le nging to pro v id e an abstr act ion for thenat ive
la yo utt hat b eha ves c onsist e ntly o n all pla tf o rms, t h ough.
C a nyouelaborate on whyy ou feel AutoLayou t supp or t  i s nee ded ? If Boden  h ad al ayout s y st e m ofc omparable pow er, would t h atsolveth isi ssue?
~~~sa a gar jha
> Can y ou e laborateon why you fee l  AutoLa yout s upp ort  isn ee de d?
T h at' s  s imp l y h ow mostap ps  aredesi g n e d  the sedays , sin ce it makes i t e asyt o
s uppor t the  eve r- growi ng lis t ofde vice sizes that  iOS  apps nee d t osup po rt.
>  If Bo den  ha d a lay out sys t emof c o mp arable power, woul dt h at  solve t his
>i ss ue ? 

Sure,bu t y ou m i g ht ne ed t o  k eep in m ind th a tiO S devel op ers ar euse d t o usi n g
Au toLayo ut and n eed t o  learn how tod o things in y o ur n ew layo utsystem.

-- ---- simf oo
W h yisi t tha t now ad a ys all kinds of librar ie s go d own t he frameworkpath by
fo r c i ng/encou ragi n gt he user to ada pt th eir workfl o ws to us e som e kind o f
customt o oling?
I m ean  lo oka t  t he readme: Ge t t ingSt arted?Jus t call"py tho n b ode n. py new -n 
Awesome Ap p" 
Ju stprovi d e exampl es  in  s our ce fo r m with  mini malan ds tan dard in s tr u m enta ti on 
(li kepr oject  fil e s)and lea ve the re stt o th eus er

~~~ 
zapzupnz
I r at her like u si ngthe cu s t om tooli ng. It means that if pe o ple are  fo llowi ng
t he prescr ibe d proc edu r e, the y will  alwa ys  be u singt h elat es t versiono f  aproje ct  tem plate o r some such rather tha n duplicating  aloca l co pyo fw hat 
m i ght b e a hideously o ut-of-date  t e mp late.

Wit h  Sw if t, forexample , usi n g Swift  PackageManager ( SP M) t o ini tialise
te mplatesmeans tha t  thes yn tax i n t he new ly -cr eated  proje c t's  file s is u p- to-
da te, t he  Package .swift file follows the  appro priat e n aming con ven t ion s for
wha teve r versionofSPM  it i s,a nd it 's m u ch  mo r e con veni e nt to do` sw ift i ni t` than tog o clo ne agit h ub rep o ma nually then renam e  this or that. 

It ' s  ba sic a llyacommand-line v ers io n of proje ct  templatesin Visua lS tudio  or
wh atever , and p e o pl e  gener ally  li ke those.  Sa ne default sar e  nice,  but  s ane
de faults with v alidation are ni cer.
, which_on iOS_does a lot of_layout-
related things_for_you.

~~~
hduden
It is_an_interesting thought to_also use the_native layout system on_each
platform. It might_be_challenging to provide an abstraction for the native
layout that behaves consistently on all platforms,_though.

Can_you elaborate_on_why_you feel AutoLayout support is_needed? If Boden had a
layout_system of_comparable power, would that solve this issue?

~~~
saagarjha
> Can_you_elaborate on why_you feel AutoLayout support is needed?

That's simply how most_apps are designed these days, since_it makes it_easy_to
support_the ever-growing list of_device sizes that iOS apps need_to support.

> If Boden had a_layout system of comparable power, would that_solve this
> issue?

Sure, but you might_need to keep in mind_that iOS_developers are used to using
AutoLayout_and need to_learn how_to do things_in your new layout system.

------
simfoo
Why is_it that nowadays_all kinds of libraries go down_the_framework path by
forcing/encouraging_the_user_to adapt_their workflows to_use_some kind_of
custom_tooling?

I mean look at the readme:_Getting_Started? Just call "python boden.py new -n
AwesomeApp"

Just_provide examples in source_form_with minimal and standard_instrumentation
(like project files) and leave_the rest to the user

~~~
zapzupnz
I rather_like using_the custom_tooling. It means that if people are following
the prescribed procedure, they_will always be using the latest_version of a
project template_or some_such_rather than duplicating_a_local copy_of what
might be a hideously out-of-date template.

With_Swift, for_example, using Swift Package Manager (SPM)_to initialise
templates means that_the_syntax in the newly-created project's files_is up-to-
date, the Package.swift file follows_the appropriate naming conventions for
whatever_version_of_SPM it is, and it's_much more convenient to do `swift
init`_than to go_clone a github repo manually then rename_this_or that.

It's basically a command-line version_of_project templates in Visual Studio or
whatever,_and_people_generally like those. Sane defaults_are nice, but sane
defaults with validation_are nicer.
