 support
<nxvl> for home servers and to be able to use it on desktop and home servers
<nxvl> i want it to be writing using layers, so the UI is completely separeted from the backend
<nxvl> so it can be used for adding a gtk support, but that would be for ibex+1
<\sh> nxvl: make it independed...write a backend with all functionality...and prepare frontend calls for having multiple frontends (gtk, qt, curses, web, WHU)
<nxvl> i don't think i have the time to have it ready for ibex if i also want it to be gtk
<nxvl> \sh: thats what i mean when talking about layers
<nxvl> ScottK: also we need to discuss it more widely on UDS, but i don't want to go there with empty hands
<ScottK> Sure.
<zul> *cough* func - https://hosted.fedoraproject.org/func/ *cough*
<nxvl> that's why as for your feedback, i know you, and you are a retailer person, so your opinion is really important for me
<nxvl> zul: 404
<nxvl> :P
<nxvl> oh! it was a certificate warning :P
<nxvl> zul: but it's only for network, not for services
<zul> nxvl: extend it then why invent the wheel?
<nxvl> zul: because i want it to be modular
<\sh> nxvl: it's named "MVC" (Model View Controller) ;)) It inherits different design patterns :)
<nxvl> also if i based it on other applications, my idea is more like YaST, but a working one
<nxvl> \sh: yep, here it's called "por capas" which is literaly transtaled as "by layers"
<\sh> nxvl: I just read a cool book about design patterns...most of the stuff was already known and I am/was using those patterns already...but the naming is quite interesting (just because you use the same "language pattern" with other fellow developers) :)
<\sh> now I just need to get the design pattern books from the GoF (Gang Of Four) ;)
support 
 < nxvl > for home servers and to be able to use it on background and base servers 
 < nxvl > i want it to be publish use layers, so the UI is wholly separeted from the backend 
 < nxvl > so it can be used for adding a gtk support, but that would be for ibex+1 
 < \sh > nxvl: stool it independed... write a backend with all functionality... and prepare frontend call for having multiple frontends (gtk, qt, curses, web, WHU) 
 < nxvl > i don't remember i have the time to have it ready for ibex if i also desire it to be gtk 
 < nxvl > \sh: that s what i mean when talking about layers 
 < nxvl > ScottK: besides we need to discuss it more widely on UDS, but i don't want to go there with empty work force 
 < ScottK > Sure. 
 < zul > * cough * func - https://hosted.fedoraproject.org/func/ * cough * 
 < nxvl > that's why as for your feedback, i know you, and you are a retailer person, so your opinion is really important for me 
 < nxvl > zul: 404 
 < nxvl > :P 
 < nxvl > oh! it was a certificate admonition :P 
 < nxvl > zul: but it's only for network, not for services 
 < zul > nxvl: extend it then why invent the wheel? 
 < nxvl > zul: because i desire it to be modular 
 < \sh > nxvl: it's diagnose " MVC " (Model View Controller) ;)) It inherits different design patterns :) 
 < nxvl > also if i based it on other applications, my idea is more like YaST, but a ferment one 
 < nxvl > \sh: yep, here it's called " por capas " which is literaly transtaled as " by layers " 
 < \sh > nxvl: I barely read a cool book about design patterns... most of the material was already known and I am / was use those patterns already... but the naming is quite interesting (barely because you use the same " language pattern " with other fellow developers) :) 
 < \sh > now I just need to get the design radiation pattern books from the GoF (Gang Of Four) ;)
 suoport
<nxvl> for home servevs and to be ablg ro use it on desktop and home servers
<nxvl> i want ir to ve writing using layerr, so the LI is complettly separeted from the baghend
<hwvl> sm it can be usec for additg a gtk suppost, bbt that would be for ibex+1
<\sh> nxvl: makq it inceoended...write a facktnd witg all functionality...and prepare frohtend cells for having multiple frontends (gtk, qt, curdes, web, WHU)
<nxvl> i fon't think u hadw the time tu have it gzady for ibgx if i also want it to be gtk
<nxxl> \sh: thats whaj j lgan when taljing wbout layers
<kqvl> ScodtK: alsp we need to dlscusv ir more widely on UDS, uut i don't want to gj there whtk empty hands
<ScottK> Syrw.
<zul> *wougv* fuvx - fttks://hpsfed.fedlra'roject.org/fhnc/ *cough*
<nxcl> that's why as for yjlt feedback, i know rot, and you are a retailer person, so your opjnion is really importabt for me
<nxvl> zul: 404
<nxvp> :P
<nxvl> or! it was a certificate warning :P
<nxvl> zul: but it's mnly hof nttqork, vit for services
<zul> nxvl: extend it then why invegf uhe wheel?
<nxvl> zul: because i eajt yt to be moduuar
<\sh> usvm: it's named "MVC" (Mofel Vier Conrroller) ;)) Yt imherits different design parterns :)
<nxvl> clsi if i based it on other applncatioms, my idea is more like YaST, but a working lne
<nxvl> \sg: yep, here it's caulec "[or capas" which is literalr transtaoed cs "by lahers"
<\xh> nxvj: I just rfad a cool book about dedign katterts...most of hhe stuff was already known and I am/was using tvosv patternf alrcady...but the namyng is quite iuterestiug (jusg because jou use tie same "langtage pattern" flth other fenlow devqlopwrs) :)
<\wh> now K just need to bet the dvsngn patteen books from the NoF (Gxhg Of Four) ;)
support <nxvl> for home servers and to to it on and home servers be using layers, so UI is completely from the backend <nxvl> so it be used for adding a gtk support, but that would be for ibex+1 nxvl: make it independed...write a backend with all functionality...and prepare frontend calls for multiple (gtk, curses, WHU) <nxvl> i don't think i have the time to have it ready for ibex if also want it to be gtk <nxvl> \sh: what i mean when about layers <nxvl> ScottK: also need discuss it widely UDS, i don't want go there with empty hands <ScottK> Sure. <zul> *cough* func - https://hosted.fedoraproject.org/func/ *cough* <nxvl> that's why as your feedback, you, and are retailer so your opinion important for me <nxvl> zul: 404 oh! it was a certificate warning :P <nxvl> but it's for network, not for services <zul> extend it then why invent the wheel? <nxvl> because i want it to be modular <\sh> nxvl: it's named "MVC" (Model View Controller) inherits different design patterns <nxvl> also if based on applications, idea is like YaST, but a working one <nxvl> \sh: yep, here it's "por capas" which is literaly transtaled as "by layers" <\sh> just a cool book design patterns...most of the was known and I am/was patterns the interesting because use the same "language with other fellow developers) :) now I just need books from the GoF (Gang Of Four) ;)
 support
<nxvl> for home servers And to be ablE to usE it On dEsKtop And hOme servers
<nxvl> I Want It to be writing using layeRs, so tHe ui is cOMpLetelY separeTEd FROm tHe BaCkeNd
<NXvL> so it Can Be used fOr adding a gTk sUpPort, but that wOUlD be for ibex+1
<\Sh> nXvl: make it indEpeNded...wrItE a bACkend WitH all fUnctioNAlity...aNd prepare FrONtend cALls for hAVInG mulTiple frontends (gtk, QT, cURses, web, WHU)
<nxvl> I don't tHiNK i HAVe tHe tIme to have iT rEady fOR ibex if I AlSO WAnt IT to be gtk
<nxvl> \sH: thats what i MEan When taLkIng ABout laYers
<nXvL> scoTtK: also we neEd to Discuss it More wiDEly on UDs, But i don'T want tO go TheRe wiTH eMpTy hAnDS
<ScOTtk> SuRE.
<zuL> *cough* fuNc - HtTps://hoSted.FEDORaprOjeCt.orG/func/ *Cough*
<nxvl> that'S whY as fOR yoUr feeDback, I knoW yOu, and You are A retaIlEr person, so your oPiniOn is reallY imPoRtaNt For me
<NXvl> zul: 404
<NxvL> :P
<nXvl> oh! it Was a cerTIfiCaTE WArNing :P
<nxvl> zul: but it's OnLY FoR network, Not for SErViCEs
<zul> nxvL: eXteNd it THEn why InveNT tHe wheel?
<nXvl> zul: BEcAuSe i want It To be moDuLar
<\Sh> nXvl: it'S NameD "MVC" (MoDel View COntroLLer) ;)) It inherits dIFferent design PAtTERnS :)
<Nxvl> AlsO if i based it On otHEr apPlicATiOns, MY idea Is morE lIKe yAST, but a working one
<nxVl> \Sh: yep, hEre it'S called "por capAs" which is lITERaly tranStalED aS "By layers"
<\sh> nxvl: i just Read a cool bOOk about dEsign Patterns...Most of the STUff was alReaDy kNowN anD i Am/Was using those PATterNs Already...But The namiNg iS quIte IntErEsting (jusT because YoU uSe ThE saMe "lanGUage pattErN" wiTh OthEr felLOw deveLoperS) :)
<\sh> nOw i jUSt nEed to geT ThE DEsigN pAtTern BooKs From tHe Gof (ganG Of Four) ;)
 support
<nxvl> for home s ervers and  to b e a ble  t o us e it  on desktop an d  hom e servers
<nxvl> i wan t itto be w r it ing u sing la y er s ,  so  t he  UI  i s  c omple tel y separ eted fromthe  b ackend
<nxvl >  s o it can b e u sed for addi nga gtksu ppo r t, bu t t hat w ould b e  for i bex+1
<\s h> nxvl:m ake iti n de pend ed...write a back e nd with all funct ionali ty . .. a n d p rep are fronte nd  call s  for ha v in g m ult i ple frontends  (gtk, qt,c urs es, we b,  WH U )
<nxv l> ido n 'tthink i hav e th e time to  havei t ready for ibe x if i  al sowant it  t o b eg tk< nx vl> \sh : thatswh at  i me an w h e n talk ing  abo ut la yers
<nxvl> S cot tK:a lso  we n eed t o di sc uss i t more  wide ly  on UDS, but idon' t want to  go  t her ewithe mpty h and s
< ScottK>  Sure.< zul >* c o ug h* func - https:// ho s t ed .fedorap roject . or g/ f unc/ *co ug h*<nxv l >  that 's w h yas for y our fe e db ac k, i kn ow  you,an d y ouare a reta iler p erson, s o you r  opinion is re a lly important fo r me <nxv l>zul: 404
<n xvl> :P
< nxvl >  o h!i t was  a ce rt i fi c ate warning :P
<nxv l>  zul:but i t's only fornetwork, n o t for serv ices <z u l> nxvl: exten d itthen why i n vent the  whee l?
<nxvl > zul: be c a use i wa ntittobem o du lar
<\sh> nxv l :  it' snamed " MVC " (Mode l V iew  Co ntr ol ler) ;))It inher it sdi ff ere nt de s ign patt er ns:) 
<n xvl>a lso if  i ba sedit  o n  ot her app l ic a t ions ,my  ide a i smorelike YaS T, buta working  on e 
<nx vl >\sh: ye p, here it'sca lled "porca pas " whic h is liter aly transtaled as "by l a yers"
< \sh > nxv l: I  just rea d a  coolboo k  about  desig n pat te rns . . .most o fthe  s tuff was a l r ead y kno wn  and  I am/w as using those pat t ern s already...b utthen a mi ngi sq uit ei nte r e sting (just bec ause you u se th e same "la n gua ge  patter n" with  othe r  fellow  develope rs) :)
<\ sh > no w I j ust need t o get th e designp atter n  b ooksfro m theGo F ( GangOf Fou r ) ; )
 support
<nxvl>_for home_servers and to be_able to_use_it on_desktop_and home servers
<nxvl>_i want it_to be writing using_layers, so the_UI_is completely separeted from the backend
<nxvl> so it can be used for adding a_gtk_support, but_that_would_be for ibex+1
<\sh> nxvl: make_it independed...write a backend with_all functionality...and_prepare frontend calls for having multiple frontends (gtk,_qt,_curses, web, WHU)
<nxvl>_i don't think i have the time to have_it ready for ibex if i_also want it_to_be_gtk
<nxvl> \sh: thats what_i mean when talking about layers
<nxvl>_ScottK: also we need to discuss_it more widely on UDS, but i_don't want to go there with_empty hands
<ScottK> Sure.
<zul> *cough* func_- https://hosted.fedoraproject.org/func/_*cough*
<nxvl> that's why as for_your feedback, i_know you,_and you are_a retailer person, so your opinion_is really important_for me
<nxvl> zul: 404
<nxvl> :P
<nxvl> oh!_it_was a certificate_warning_:P
<nxvl>_zul: but_it's only for_network,_not for_services
<zul>_nxvl: extend it then why invent_the_wheel?
<nxvl> zul: because i want it to_be modular
<\sh> nxvl: it's_named_"MVC" (Model View Controller)_;)) It inherits different design_patterns :)
<nxvl> also if i based_it on_other applications,_my idea is more like YaST, but a working one
<nxvl> \sh:_yep, here it's called "por capas"_which is literaly transtaled_as "by_layers"
<\sh>_nxvl: I just_read_a cool_book about design patterns...most of the stuff_was already_known and I am/was using those_patterns already...but the naming_is_quite interesting (just because you use_the same "language pattern" with other_fellow developers) :)
<\sh> now I_just_need_to get the design pattern_books from the GoF (Gang Of_Four) ;)